From nobody Tue Jan 14 08:55:53 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA71120A2D for ; Tue, 14 Jan 2020 08:55:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dHPBOKLK23q for ; Tue, 14 Jan 2020 08:55:44 -0800 (PST) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 087C0120A32 for ; Tue, 14 Jan 2020 08:55:42 -0800 (PST) Received: by mail-io1-xd2b.google.com with SMTP id x1so14558469iop.7 for ; Tue, 14 Jan 2020 08:55:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=uwj2RHOtzAZDp0nBDSGGNLpB2CBTNpygy0p4PzRiOxE=; b=sdpdun9YXUsrcaoILlvzJj4oQrcnWgbl87/3DW+J/nCuXy096ziiInXU3MIaACNWQV +3lfbfkhwbmCPgYY6YofpiIJ3uK9g0WbIBAZBGNQkmG+y1IDj2b/0UGmVV1yg6ExrHse lAt3C41RIKqr8tkfTIE3VH6rrgzrgEahwV/C+1jk4vNoXTu4sA9YMviAoztOmUqfDGyT R84dFtSV3gXPFnt0XJIa1soR3Nsae/Xq66ocgUCiRpDOlSRQJRXK2Jo9QLFKlbZwNOqQ oCuJdqqU4/128Dl2rXjaYRyr51XhguJR6BfMP2fgTS3Nl0X3aPqohfiT0SmRlTS91/c8 3XlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=uwj2RHOtzAZDp0nBDSGGNLpB2CBTNpygy0p4PzRiOxE=; b=hvnspEirLNse1llXbxzB4G1TRK3x7wbwAdtFUyIaXptJgz3UXvR1D56xxxte3EazWq I2/XcSCnmfkoDPstPSusNPMjDk3SJOlVyT2ZaUcnkNrR6FrvLPtwLlFMaymWRzoz7RMw ZFMdHvx9rkFwMMB5CwYxzWU/tcuvSRT1UV/48xpHw/7IIozaNiy0tPqH+4P7llqBVMaJ zOBHiLHwNXfIKVL5v4/3EoJRVTe48YohzMSfEl9t2Q+5oQ0FddfYUJljEGaMjYJFhKHA KFFQdA/MVGrclSvVOJUGAtN8x1dXrTwVk1wFOFJOdgJaFCngnpDvYlh0aWqXRiWGCnkD To4Q== X-Gm-Message-State: APjAAAUb+E0Fg3VGUUGzASI22OePb6pe/TPLgBUoDxqyaDftSFULh9A5 gqXxp749upKBxwPWcs1abt9eIjy+TkC7JxwlCGW5wQhE9v8= X-Google-Smtp-Source: APXvYqy5EvGJNVZZIE/NCGx3deBD+JCv1cEfhd7InX2jgMUbx2g57scOdLzfkgUAehG1Pd1pmSq+z/S1gQSXFj6VW1U= X-Received: by 2002:a6b:bcc1:: with SMTP id m184mr18228563iof.289.1579020940917; Tue, 14 Jan 2020 08:55:40 -0800 (PST) MIME-Version: 1.0 From: "M. Ranganathan" Date: Tue, 14 Jan 2020 11:55:04 -0500 Message-ID: To: iot-onboarding@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Iot-onboarding] How to locate the EST server on a network? X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 16:55:51 -0000 Hello, I am experimenting with EST. How does a device find the address of the EST server on a network so it can do a "simple enroll" ? Thanks, Ranga -- M. Ranganathan From nobody Tue Jan 14 09:37:42 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67DD21209E1 for ; Tue, 14 Jan 2020 09:37:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.949 X-Spam-Level: X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsPcHK1Rs0WK for ; Tue, 14 Jan 2020 09:37:35 -0800 (PST) Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 501881208FE for ; Tue, 14 Jan 2020 09:37:35 -0800 (PST) Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 69161548047; Tue, 14 Jan 2020 18:37:28 +0100 (CET) Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 63497440059; Tue, 14 Jan 2020 18:37:28 +0100 (CET) Date: Tue, 14 Jan 2020 18:37:28 +0100 From: Toerless Eckert To: "M. Ranganathan" Cc: iot-onboarding@ietf.org Message-ID: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [Iot-onboarding] How to locate the EST server on a network? X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 17:37:41 -0000 EST is not an automated secure enrollment protocol. Thats the one key piece missing from it, and the reason why we are writing the BRSKI specification effectively extends EST with automated enrollment. EST is sufficient for secure automated renewal / key rollover, but only for insecure automated initial enrolment. For secure automated enrolment you would need BRSKI. If you want to use BRSKI, you would use the DNS-SD service name brski-registrar, see BRSKI draft section 8.6. If you just want to do EST alone (again, that would only result in insecure "duckling" initial enrolment but sufficient for renewal/rekeying), the service name in DNS is "est". The ACP draft specifies the service names for discovery via GRASP, which i guess might not be your fist choice outside of ANIMA today ;-). Beyond that, there are no standardized discovery mechanisms for EST/BRSKI registrar AFAIK, but i think setting up DNS-SD RRs is also today the most easily done service registration mechanism. I wouldn't recommend hacking around with DHCP anymore for this unless you must support a system setup without DNS available. Cheers Toerless On Tue, Jan 14, 2020 at 11:55:04AM -0500, M. Ranganathan wrote: > Hello, > > I am experimenting with EST. How does a device find the address of the > EST server on a network so it can do a "simple enroll" ? > > Thanks, > > Ranga > > -- > M. Ranganathan > > -- > Iot-onboarding mailing list > Iot-onboarding@ietf.org > https://www.ietf.org/mailman/listinfo/iot-onboarding -- --- tte@cs.fau.de From nobody Tue Jan 14 10:44:15 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93E20120BBA for ; Tue, 14 Jan 2020 10:44:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kV_Git-7c0bz for ; Tue, 14 Jan 2020 10:44:09 -0800 (PST) Received: from mail-pl1-x644.google.com (mail-pl1-x644.google.com [IPv6:2607:f8b0:4864:20::644]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D17A120BB4 for ; Tue, 14 Jan 2020 10:44:09 -0800 (PST) Received: by mail-pl1-x644.google.com with SMTP id s21so5574533plr.7 for ; Tue, 14 Jan 2020 10:44:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=O63vS7K1RCD6nipR1pne8gbMptBk6ZGkRM3+5QBipqk=; b=XCiUKolnBpUX5agXcpVyN4sADXF5i66X4yucJZWAOM7mP7cQarvbkFpURAVQwZVBqV Xqm9ptVMqHd9WQQmOmbFdhN1IsA0doSSEa6KkpEPticQkIpwrFAtyUCuGv/rFKELvloX j6UBh0m3QvvJ9vbPGCy+woC9971bVRMcbqRYwzYOAy+qpzi9oUpRzOUi5gV0B52s968H pXwNjNzPKav8Ptqua6UeZLOIi/iCEnZOxbzK9dVxuniy2SNOM/ao4uvg6AQZE9Ju81I4 LrBdPld6DfW0FWjJxO0+zLaawg2El14KfEznztV5mQUe2GnpH6yPskVQah1/HTyfFMp5 GvNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=O63vS7K1RCD6nipR1pne8gbMptBk6ZGkRM3+5QBipqk=; b=SWxavRgjNkXXLKBI7b/UWzDmXA/VPEHUq7TrTV6WwCmZhxxlrgbLLuOzwYLENTAWm8 N/FehEVOhz9qGitMNCPr1/xwY/ui0Wm63G0x5sQ93YFxlcQywmYoIYLuW/Q3E5aUfVHf TEQ4i+mSgpPXfTrWj/XPu6MJfbqP5WXMwKtJfiOavswLYxapi2GPsYX0fvAFae+Z+y9/ xKjdTOebMdQhq2P1uB83e3as5G7VKpaWnTbCpESVjN5c+tln2FNx9hjPV5hLNbbtULps FdhKH2HeqJbYxWU56AViaoDrP8MajZmtRMqOm1pMgj6IW4Xx+FHYXw+0KbQ/gNE/EiNZ Vvbw== X-Gm-Message-State: APjAAAVgmNrzcta82BZTzGKQUNMVUrBA37i7qnSxshtxsn5GVOh9oUlw c3sP2xmsnyrPwl4qwHgktE8UpHaG X-Google-Smtp-Source: APXvYqzgo9rviVSmPupiwvH9FcCL9CSpLmD/U1rtAJU1QscY/EWT+jV5H3VZlI4dlq/FXXDbDJye6A== X-Received: by 2002:a17:90a:222c:: with SMTP id c41mr29733626pje.35.1579027448301; Tue, 14 Jan 2020 10:44:08 -0800 (PST) Received: from [172.17.0.82] ([111.69.8.186]) by smtp.gmail.com with ESMTPSA id d27sm17791648pgm.53.2020.01.14.10.44.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jan 2020 10:44:07 -0800 (PST) To: "M. Ranganathan" Cc: Toerless Eckert , iot-onboarding@ietf.org References: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de> From: Brian E Carpenter Organization: University of Auckland Message-ID: <28e51f46-cb6b-b396-41ca-3ce5db269f07@gmail.com> Date: Wed, 15 Jan 2020 07:44:03 +1300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Iot-onboarding] How to locate the EST server on a network? X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 18:44:14 -0000 Hi Ranga, > The ACP draft specifies the service > names for discovery via GRASP, which i guess might not be your > fist choice outside of ANIMA today ;-). Definitely not for production. But for pure experimentation, if you like, it wouldn't be hard to put some code together, if you don't have a DNSSD option and you do enjoy Python hacking. Let me know if you want to do that, because I've written very similar code already. Regards Brian Carpenter On 15-Jan-20 06:37, Toerless Eckert wrote: > EST is not an automated secure enrollment protocol. Thats the one key piece > missing from it, and the reason why we are writing the BRSKI > specification effectively extends EST with automated enrollment. > > EST is sufficient for secure automated renewal / key rollover, but > only for insecure automated initial enrolment. For secure automated > enrolment you would need BRSKI. > > If you want to use BRSKI, you would use the DNS-SD service name > brski-registrar, see BRSKI draft section 8.6. If you just want to > do EST alone (again, that would only result in insecure "duckling" > initial enrolment but sufficient for renewal/rekeying), the > service name in DNS is "est". The ACP draft specifies the service > names for discovery via GRASP, which i guess might not be your > fist choice outside of ANIMA today ;-). > > Beyond that, there are no standardized discovery mechanisms for > EST/BRSKI registrar AFAIK, but i think setting up DNS-SD RRs is > also today the most easily done service registration mechanism. > I wouldn't recommend hacking around with DHCP anymore for this > unless you must support a system setup without DNS available. > > Cheers > Toerless > > On Tue, Jan 14, 2020 at 11:55:04AM -0500, M. Ranganathan wrote: >> Hello, >> >> I am experimenting with EST. How does a device find the address of the >> EST server on a network so it can do a "simple enroll" ? >> >> Thanks, >> >> Ranga >> >> -- >> M. Ranganathan >> >> -- >> Iot-onboarding mailing list >> Iot-onboarding@ietf.org >> https://www.ietf.org/mailman/listinfo/iot-onboarding > From nobody Tue Jan 14 13:20:05 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE79120882 for ; Tue, 14 Jan 2020 13:20:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkELWGMxVhhJ for ; Tue, 14 Jan 2020 13:20:02 -0800 (PST) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D47E120110 for ; Tue, 14 Jan 2020 13:20:02 -0800 (PST) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 5A83B3897B; Tue, 14 Jan 2020 16:19:35 -0500 (EST) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5D1B4108F; Tue, 14 Jan 2020 16:20:01 -0500 (EST) From: Michael Richardson To: "M. Ranganathan" , iot-onboarding@ietf.org In-Reply-To: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de> References: <20200114173728.GO14549@faui48f.informatik.uni-erlangen.de> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [Iot-onboarding] How to locate the EST server on a network? X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2020 21:20:04 -0000 --=-=-= Content-Type: text/plain Toerless Eckert wrote: > If you want to use BRSKI, you would use the DNS-SD service name > brski-registrar, see BRSKI draft section 8.6. If you just want to do > EST alone (again, that would only result in insecure "duckling" initial > enrolment but sufficient for renewal/rekeying), the service name in DNS > is "est". The ACP draft specifies the service names for discovery via > GRASP, which i guess might not be your fist choice outside of ANIMA > today ;-). DNS-SD is an optional thing for BRSKI! The MTI is a GRASP DULL message to find the join proxy. If you don't have a device->network trust issue (because your wires carry implicit trust), then you can use EST with IDevID to do enrollment of an LDevID. DNS-SD is a very good way. Owen and Rifaat's Cloud Registrar document provides a number of other interesting options too. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl4eMIEACgkQgItw+93Q 3WWaWgf8CqUIF4agohRrKcbd3rp/WHyFD7x+COxuJxwMT2n8iLk+drNKw6Vw3lCU u+zu2dlu6lbZQ1ko7U2KK9e2B/kvFnTwEYHXI5MzghoyQLUKTrP8u/Y71cPRBl/y Ep17gF2APlDNttqL1BPwd6H0cVcdk4OPgwGQsHtzr3Nj88OHxqOURHTaNsK+oVxl rZ91u0NbjGdYQLbmu0taZeeCLD3f7sjMdVyukM6m2uiGeKbinUyJPVxr9ilK6yox f9bMUbf2PAtwERjx6NpaNuhF9on85gyTMSkjYmcLVOdNq0l6ipGmIAxU7T9vgG5Q r1DAuA/iFm6tCAh51XTwKUpwBLCuhA== =SXS7 -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jan 29 06:22:27 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C72A12009C for ; Wed, 29 Jan 2020 06:22:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id km47kY32mf9b for ; Wed, 29 Jan 2020 06:22:24 -0800 (PST) Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C07612011A for ; Wed, 29 Jan 2020 06:22:24 -0800 (PST) Received: by mail-io1-xd2c.google.com with SMTP id d15so18783268iog.3 for ; Wed, 29 Jan 2020 06:22:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=fkYThgIG1yQCs3W7DYX/q7g6Q1nMv+eHxa6cIvNblag=; b=KLLFRUJyOfsBVFv8FEfx1fQn12AJL69ncWOEbqn/1RTtQMMQfD0zV1iuNyp0E7aDzp zI33UPIBdYM/qO8JVCVMmtfylEqGZZOo/7aRX/on/KwYbcwwZqzVDJFb5Sz+D6duS8nQ yZNm5kwzHqMOVHUJXMhD9eOuG/Yy/oj5rE4B94zYEVovjVGHIrAaLaLY/HbgZgxXtW7Q 0ftURFXk23ZLq81fMNp3yNswjrt/8FrcDWJCCibS+1hbFT2uAzB1H8qCNXYM8qk8e0TU 5xWyg2DNBDNVwgvS8D5AWFW/9AYimf74oxzMlTnaqqiV55LLEFOjVcdQxSO5jJseF6r7 qL3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=fkYThgIG1yQCs3W7DYX/q7g6Q1nMv+eHxa6cIvNblag=; b=P6JhhoYjgxyJIx3xubghMLb5sEchk8Yhwb2uYkKiyECZgvs3RQjkZAai0oNJrWzxox SaJJpokNlUnLIrfTOb85Gxe2Ymk627HYZ62VeYh4KrnGI2JdnYuUEvU80FuL5mb6Pb6K wiqW4Ahz8RhYtYzKoewsNhP1v8H9tdAlT7g9mijAAS9Inx4NyqofY+ZB+294mJenRWAr tRCZlaXV5eWwutcvTCOSLqtZKRkb2vxfJa5VbBO+rOXLdMHWofpYgxEteSwNoFddDvS3 V+leDwzHx9RTO1nLB1jfMQudeOfKpkt2e+t8eiD9M7cmikjKMSZuQ3k4Rnxyx4pHmJid ooTA== X-Gm-Message-State: APjAAAUddTjazCAEN3yfiaWN4phJSwZvxqexaXvjs7gmZIA6PgZpItdL 35Y6CWWP6lPF4FYTBFMcgLKYXp3eUNwgW9dk1+IgsTdv X-Google-Smtp-Source: APXvYqznpMGXLuPtJXxugvTqcvuWWuwWDQMCjjgfH9TRZ4zWOACm8bzg52vtQzRxkv1p5aCz5FEc8qSaAbsOkbSZhMo= X-Received: by 2002:a6b:7e42:: with SMTP id k2mr20057637ioq.52.1580307743483; Wed, 29 Jan 2020 06:22:23 -0800 (PST) MIME-Version: 1.0 From: "M. Ranganathan" Date: Wed, 29 Jan 2020 09:21:47 -0500 Message-ID: To: iot-onboarding@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Iot-onboarding] IETF 107 Hackathon topic: Develop and test DPP code with TEAP. X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2020 14:22:26 -0000 Hello, I see a hackathon topic that proposes to integrate DPP and TEAP. I am interested in this, Are there any drafts, presentations or proposals on this that I can read? Thanks, Ranga -- M. Ranganathan From nobody Wed Jan 29 06:27:40 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3ACC120853 for ; Wed, 29 Jan 2020 06:27:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.5 X-Spam-Level: X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3LB7m2sCowq for ; Wed, 29 Jan 2020 06:27:32 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF830120890 for ; Wed, 29 Jan 2020 06:27:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2754; q=dns/txt; s=iport; t=1580308051; x=1581517651; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=+3DRDJvUDI0k8pPBwla6srkfXJ2EyQ2kOW+xaZ2Efhs=; b=Ec4+/e5a0HE7ZBAIR68pkPy+K9btu2D6l+TlUI8R2zIgbxg2T5PYNviF xxR9TjWhV7d7Zdpd3HCdb9s9RLlIzj3jYWQPWwgPYtkYOuUiQha7XOevZ KyCbawESsFiyH43HA4XjAqhVAJcU6g3fFPfImFDgJ9dwhtUBNjA4N+cyE I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BbAAAzlTFe/xbLJq1mGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYF7gxVUASASKo0XiBaJYYlMiAsJAQEBDAEBGAE?= =?us-ascii?q?KDAEBhEACgk44EwIDDQEBBAEBAQIBBQRthTcMhV4BAQEBAgEBAWwLBQsLBAE?= =?us-ascii?q?TLiEGMAYTgyYBgkoDDiAPrB2CJ4VKgjcNgiCBOIUeDIcQggCBEScggkw+gQQ?= =?us-ascii?q?KgQ1JAQGFJYIsBI1loS9EgkOCTIQNaYpMhCkbgkiMUYtml0SCJIxXgy4CBAY?= =?us-ascii?q?FAhWBaSKBWDMaCBsVOyoBgkEJNRIYDVeNXiCIT4VAQAMwjkcBAQ?= X-IronPort-AV: E=Sophos; i="5.70,378,1574121600"; d="scan'208,217"; a="22742158" Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Jan 2020 14:27:29 +0000 Received: from ams3-vpn-dhcp1105.cisco.com (ams3-vpn-dhcp1105.cisco.com [10.61.68.81]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 00TERR5b026440 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Jan 2020 14:27:29 GMT From: Eliot Lear Message-Id: <93BA7FC9-C4B9-4CF0-9D37-040FEB2FA23F@cisco.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_D255B809-B06F-43C6-86BD-9D869163772D" Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) Date: Wed, 29 Jan 2020 15:27:26 +0100 In-Reply-To: Cc: iot-onboarding@ietf.org To: "M. Ranganathan" References: X-Mailer: Apple Mail (2.3608.60.0.2.5) X-Outbound-SMTP-Client: 10.61.68.81, ams3-vpn-dhcp1105.cisco.com X-Outbound-Node: aer-core-4.cisco.com Archived-At: Subject: Re: [Iot-onboarding] IETF 107 Hackathon topic: Develop and test DPP code with TEAP. X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2020 14:27:40 -0000 --Apple-Mail=_D255B809-B06F-43C6-86BD-9D869163772D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Ranga, TEAP is RFC 7170. We are revising it in draft-lear-eap-teap-brski, and = will be generalizing that draft a bit more before the deadline. DPP is the Wifi Alliance spec available off their web site (wi-fi.org = ). Eliot > On 29 Jan 2020, at 15:21, M. Ranganathan wrote: >=20 > Hello, >=20 > I see a hackathon topic that proposes to integrate DPP and TEAP. I am > interested in this, Are there any drafts, presentations or proposals > on this that I can read? >=20 > Thanks, >=20 > Ranga >=20 >=20 > --=20 > M. Ranganathan >=20 > --=20 > Iot-onboarding mailing list > Iot-onboarding@ietf.org > https://www.ietf.org/mailman/listinfo/iot-onboarding --Apple-Mail=_D255B809-B06F-43C6-86BD-9D869163772D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Ranga,

TEAP is RFC = 7170.  We are revising it in draft-lear-eap-teap-brski, and will be = generalizing that draft a bit more before the deadline.
DPP is the Wifi Alliance spec available off their web site = (wi-fi.org).

Eliot

On 29 Jan 2020, at 15:21, M. Ranganathan <mranga@gmail.com> = wrote:

Hello,

I see a hackathon topic = that proposes to integrate  DPP and TEAP. I am
interested in this,  Are there any drafts, presentations = or proposals
on this that I can read?

Thanks,

Ranga


--
M. Ranganathan

--
Iot-onboarding mailing = list
Iot-onboarding@ietf.org
https://www.ietf.org/mailman/listinfo/iot-onboarding

= --Apple-Mail=_D255B809-B06F-43C6-86BD-9D869163772D-- From nobody Thu Jan 30 23:31:31 2020 Return-Path: X-Original-To: iot-onboarding@ietfa.amsl.com Delivered-To: iot-onboarding@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF890120059 for ; Thu, 30 Jan 2020 23:31:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awnDjs0QQBr4 for ; Thu, 30 Jan 2020 23:31:29 -0800 (PST) Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1578E12001E for ; Thu, 30 Jan 2020 23:31:28 -0800 (PST) Received: from dooku.sandelman.ca (unknown [213.174.99.147]) by relay.sandelman.ca (Postfix) with ESMTPS id 8EAB51F45B; Fri, 31 Jan 2020 07:31:26 +0000 (UTC) Received: by dooku.sandelman.ca (Postfix, from userid 179) id E81471A3885; Fri, 31 Jan 2020 02:31:22 -0500 (EST) From: Michael Richardson To: Eliot Lear cc: "M. Ranganathan" , iot-onboarding@ietf.org In-reply-to: <93BA7FC9-C4B9-4CF0-9D37-040FEB2FA23F@cisco.com> References: <93BA7FC9-C4B9-4CF0-9D37-040FEB2FA23F@cisco.com> Comments: In-reply-to Eliot Lear message dated "Wed, 29 Jan 2020 15:27:26 +0100." X-Mailer: MH-E 8.6; nmh 1.7.1-RC3; GNU Emacs 25.2.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Date: Fri, 31 Jan 2020 08:31:22 +0100 Message-ID: <12667.1580455882@dooku> Archived-At: Subject: Re: [Iot-onboarding] IETF 107 Hackathon topic: Develop and test DPP code with TEAP. X-BeenThere: iot-onboarding@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion of IoT onboarding mechanisms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2020 07:31:31 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Eliot Lear wrote: > TEAP is RFC 7170. We are revising it in draft-lear-eap-teap-brski, a= nd > will be generalizing that draft a bit more before the deadline. DPP = is > the Wifi Alliance spec available off their web site (wi-fi.org > ). Yes, but none of them tell us how to integrate them :-) that's what I think Ranga wants to read about. (me too) =2D-=20 Michael Richardson , Sandelman Software Works -=3D IPv6 IoT consulting =3D- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAl4z18oACgkQlUzhVv38 QpDv6Af/ZUs9oeWeNakAHu7epnxDh8iMt4EYqAx0aIVzmVwnMG2KtnIYtmyzy/n6 +0gkysibutK4gUBBvvoH8ivYtmKi98fLMZPFCTOV/vYXahuDKZNZhbqLCXB4EfzJ LF5L0uf3siewcZoTOv+qT7cU5IuMsDdY4swDUeiT7vNOL6rR7EX5ctYCTrzfc0X5 om3aKk6w/mu1w8ug6B64BM5ePkwtNRjdfjIEGgL93bnk3VbMWhW6pCs5u8AomZ2+ hJ13cBVPujfsaIRQD4Q4QwSH/MjzKTTXTR7xVhkgxwznqTkSucgK/PUIpLzabn3S tydcbR9v3DTwc36HycJsGC63sy6cnw== =oLkN -----END PGP SIGNATURE----- --=-=-=--