From cabo@tzi.org Fri Sep 9 05:41:13 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C07D21F8484 for <6lowpan@ietfa.amsl.com>; Fri, 9 Sep 2011 05:41:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.249 X-Spam-Level: X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPZxGQwc1Kv7 for <6lowpan@ietfa.amsl.com>; Fri, 9 Sep 2011 05:41:12 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 52F2F21F8482 for <6lowpan@ietf.org>; Fri, 9 Sep 2011 05:41:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p89CgwcG002130 for <6lowpan@ietf.org>; Fri, 9 Sep 2011 14:42:59 +0200 (CEST) Received: from [172.23.0.130] (p50990e32.dip0.t-ipconnect.de [80.153.14.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CEFF4ABC; Fri, 9 Sep 2011 14:42:58 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Carsten Bormann In-Reply-To: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> Date: Fri, 9 Sep 2011 14:42:58 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org> References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> To: 6lowpan@ietf.org X-Mailer: Apple Mail (2.1244.3) Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2011 12:41:13 -0000 6LoWPANners, we are now looking at the third WG version (-02) of this draft. Are we ready to do a working-group last-call on this? -- if you see something major that needs to be done before this is = ready, please speak up now. (If you have technical comments, or maybe some editorial suggestions, = these are also useful at this point, although there also will be time to = comment in the actual WGLC.) -- conversely, if you have reviewed the document and like it, please do = speak up (and please do say what you have specifically looked at). Of course, we don't want to go into a WGLC with glaring omissions (I = gather Appendix A is not really a necessary part of this spec), and we = also don't want to go into WGLC if the working group hasn't been able to = review the document or, worse, if nobody actually cares. Please respond to this message by Sep 16. Gruesse, Carsten From samita.chakrabarti@ericsson.com Fri Sep 9 17:13:03 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A79721F87FC for <6lowpan@ietfa.amsl.com>; Fri, 9 Sep 2011 17:13:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.605 X-Spam-Level: X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhuwTmpX7noJ for <6lowpan@ietfa.amsl.com>; Fri, 9 Sep 2011 17:13:03 -0700 (PDT) Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id C898C21F8540 for <6lowpan@ietf.org>; Fri, 9 Sep 2011 17:13:02 -0700 (PDT) Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p8A0EuXw027275; Fri, 9 Sep 2011 19:14:58 -0500 Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.165]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Fri, 9 Sep 2011 20:14:55 -0400 From: Samita Chakrabarti To: Carsten Bormann , "6lowpan@ietf.org" <6lowpan@ietf.org> Date: Fri, 9 Sep 2011 20:14:54 -0400 Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: Acxu7g82IsE0T0bwQDmqPIpgY0JV1QAYC0ug Message-ID: <16D60F43CA0B724F8052D7E9323565D7243F3F6F20@EUSAACMS0715.eamcs.ericsson.se> References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org> In-Reply-To: <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2011 00:13:03 -0000 Hi Carsten, I think this draft is interesting and important too. I am reviewing this draft and have some comments on the editorial and some = technical clarification. Will be sending comments to the authors. Thanks, -Samita=20 -----Original Message----- From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf = Of Carsten Bormann Sent: Friday, September 09, 2011 5:43 AM To: 6lowpan@ietf.org Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE d= raft) 6LoWPANners, we are now looking at the third WG version (-02) of this draft. Are we ready to do a working-group last-call on this? -- if you see something major that needs to be done before this is ready, p= lease speak up now. (If you have technical comments, or maybe some editorial suggestions, th= ese are also useful at this point, although there also will be time to comm= ent in the actual WGLC.) -- conversely, if you have reviewed the document and like it, please do spe= ak up (and please do say what you have specifically looked at). Of course, we don't want to go into a WGLC with glaring omissions (I gather= Appendix A is not really a necessary part of this spec), and we also don't= want to go into WGLC if the working group hasn't been able to review the d= ocument or, worse, if nobody actually cares. Please respond to this message by Sep 16. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan From j.schoenwaelder@jacobs-university.de Mon Sep 12 01:57:04 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6C221F85FF for <6lowpan@ietfa.amsl.com>; Mon, 12 Sep 2011 01:57:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.108 X-Spam-Level: X-Spam-Status: No, score=-103.108 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3FNQmLIlllNm for <6lowpan@ietfa.amsl.com>; Mon, 12 Sep 2011 01:57:04 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 10AA621F85C7 for <6lowpan@ietf.org>; Mon, 12 Sep 2011 01:57:04 -0700 (PDT) Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9C17420CF4; Mon, 12 Sep 2011 10:59:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id eeMORiBoXuJp; Mon, 12 Sep 2011 10:59:05 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3CFC320CFA; Mon, 12 Sep 2011 10:59:05 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id AED571A5B575; Mon, 12 Sep 2011 10:58:53 +0200 (CEST) Date: Mon, 12 Sep 2011 10:58:53 +0200 From: Juergen Schoenwaelder To: johanna.1.nieminen@nokia.com Message-ID: <20110912085852.GA39547@elstar.local> Mail-Followup-To: johanna.1.nieminen@nokia.com, 6lowpan@ietf.org References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 08:57:04 -0000 On Fri, Aug 26, 2011 at 12:48:16PM +0000, johanna.1.nieminen@nokia.com wrote: > Latest version of our draft "Transmission of IPv6 Packets over Bluetooth Low Energy" > https://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ > has been submitted. We are planning WGLC within a couple of weeks and would ask you to send any comments before that. I had a very quick look and found it surprising that there is not reference in the normative reference section to the Bluetooth Low Energy specification. I think such a reference should be added instead of just having text refering to Bluetooth 4.0. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From johanna.1.nieminen@nokia.com Mon Sep 12 03:39:53 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1EC921F8515 for <6lowpan@ietfa.amsl.com>; Mon, 12 Sep 2011 03:39:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.299 X-Spam-Level: X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tQjpXRk1KwL for <6lowpan@ietfa.amsl.com>; Mon, 12 Sep 2011 03:39:53 -0700 (PDT) Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 021E521F8511 for <6lowpan@ietf.org>; Mon, 12 Sep 2011 03:39:52 -0700 (PDT) Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8CAfdiJ025431; Mon, 12 Sep 2011 13:41:54 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 12 Sep 2011 13:41:44 +0300 Received: from 008-AM1MMR1-006.mgdnok.nokia.com (65.54.30.61) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 12 Sep 2011 12:41:43 +0200 Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.204]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0323.007; Mon, 12 Sep 2011 12:41:43 +0200 From: To: Thread-Topic: [6lowpan] Latest version of IPv6 over BT-LE draft Thread-Index: Acxj7bwqMeJce9kfQvayEwuvlbMVbANK7JmAAAfCxjA= Date: Mon, 12 Sep 2011 10:41:42 +0000 Message-ID: <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <20110912085852.GA39547@elstar.local> In-Reply-To: <20110912085852.GA39547@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.21.23.136] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 12 Sep 2011 10:41:44.0684 (UTC) FILETIME=[90B5C2C0:01CC7138] X-Nokia-AV: Clean Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 10:39:53 -0000 Hi, That specification is very broad and not necessarily all features are norma= tive. Johanna >-----Original Message----- >From: ext Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs- >university.de] >Sent: 12 September, 2011 11:59 >To: Nieminen Johanna.1 (Nokia-NRC/Helsinki) >Cc: 6lowpan@ietf.org >Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft > >On Fri, Aug 26, 2011 at 12:48:16PM +0000, johanna.1.nieminen@nokia.com >wrote: > >> Latest version of our draft "Transmission of IPv6 Packets over Bluetooth= Low >Energy" >> https://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ >> has been submitted. We are planning WGLC within a couple of weeks and >would ask you to send any comments before that. > >I had a very quick look and found it surprising that there is not referenc= e in the >normative reference section to the Bluetooth Low Energy specification. I t= hink >such a reference should be added instead of just having text refering to >Bluetooth 4.0. > >/js > >-- >Juergen Schoenwaelder Jacobs University Bremen gGmbH >Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany >Fax: +49 421 200 3103 From esko.dijk@philips.com Mon Sep 19 06:30:38 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 388CD21F8BD5 for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:30:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.099 X-Spam-Level: X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyT8QpYplQh4 for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:30:37 -0700 (PDT) Received: from DB3EHSOBE001.bigfish.com (db3ehsobe001.messaging.microsoft.com [213.199.154.139]) by ietfa.amsl.com (Postfix) with ESMTP id 13E4721F8BCD for <6lowpan@ietf.org>; Mon, 19 Sep 2011 06:30:36 -0700 (PDT) Received: from mail30-db3-R.bigfish.com (10.3.81.253) by DB3EHSOBE001.bigfish.com (10.3.84.21) with Microsoft SMTP Server id 14.1.225.22; Mon, 19 Sep 2011 13:32:58 +0000 Received: from mail30-db3 (localhost.localdomain [127.0.0.1]) by mail30-db3-R.bigfish.com (Postfix) with ESMTP id EC97516B0304; Mon, 19 Sep 2011 13:32:57 +0000 (UTC) X-SpamScore: -52 X-BigFish: VPS-52(zz217bL15d6O9251J542M1432N98dK1db9Mzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944h) X-Forefront-Antispam-Report: CIP:168.87.56.20; KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI X-FB-SS: 0, Received: from mail30-db3 (localhost.localdomain [127.0.0.1]) by mail30-db3 (MessageSwitch) id 1316439177729083_16264; Mon, 19 Sep 2011 13:32:57 +0000 (UTC) Received: from DB3EHSMHS013.bigfish.com (unknown [10.3.81.247]) by mail30-db3.bigfish.com (Postfix) with ESMTP id 954D01BC0052; Mon, 19 Sep 2011 13:32:57 +0000 (UTC) Received: from smtpx.philips.com (168.87.56.20) by DB3EHSMHS013.bigfish.com (10.3.87.113) with Microsoft SMTP Server (TLS) id 14.1.225.22; Mon, 19 Sep 2011 13:32:49 +0000 Received: from NLAMSEXH04.connect1.local (172.16.153.25) by connect1.philips.com (172.16.156.41) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 19 Sep 2011 15:32:49 +0200 Received: from NLCLUEXM03.connect1.local ([172.16.157.42]) by NLAMSEXH04.connect1.local ([172.16.153.25]) with mapi; Mon, 19 Sep 2011 15:29:02 +0200 From: "Dijk, Esko" To: "johanna.1.nieminen@nokia.com" , "j.schoenwaelder@jacobs-university.de" Date: Mon, 19 Sep 2011 15:32:42 +0200 Thread-Topic: [6lowpan] Latest version of IPv6 over BT-LE draft Thread-Index: Acxj7bwqMeJce9kfQvayEwuvlbMVbANK7JmAAAfCxjABZfU2IA== Message-ID: References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <20110912085852.GA39547@elstar.local> <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> In-Reply-To: <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "6lowpan@ietf.org" <6lowpan@ietf.org> Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 13:30:38 -0000 Hello Johanna, just a thought - in that case, perhaps the BT 4.0 spec could be referred to= informative and a specific section on BT-LE as normative? regards, Esko Esko Dijk Philips Corporate Technologies, Research High Tech Campus 34, Eindhoven, The Netherlands esko.dijk@philips.com -----Original Message----- From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf = Of johanna.1.nieminen@nokia.com Sent: Monday 12 September 2011 12:42 To: j.schoenwaelder@jacobs-university.de Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft Hi, That specification is very broad and not necessarily all features are norma= tive. Johanna >-----Original Message----- >From: ext Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs- >university.de] >Sent: 12 September, 2011 11:59 >To: Nieminen Johanna.1 (Nokia-NRC/Helsinki) >Cc: 6lowpan@ietf.org >Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft > >On Fri, Aug 26, 2011 at 12:48:16PM +0000, johanna.1.nieminen@nokia.com >wrote: > >> Latest version of our draft "Transmission of IPv6 Packets over Bluetooth= Low >Energy" >> https://datatracker.ietf.org/doc/draft-ietf-6lowpan-btle/ >> has been submitted. We are planning WGLC within a couple of weeks and >would ask you to send any comments before that. > >I had a very quick look and found it surprising that there is not referenc= e in the >normative reference section to the Bluetooth Low Energy specification. I t= hink >such a reference should be added instead of just having text refering to >Bluetooth 4.0. > >/js > >-- >Juergen Schoenwaelder Jacobs University Bremen gGmbH >Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany >Fax: +49 421 200 3103 _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. From esko.dijk@philips.com Mon Sep 19 06:52:19 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48BE21F8BEE for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.474 X-Spam-Level: X-Spam-Status: No, score=-5.474 tagged_above=-999 required=5 tests=[AWL=1.125, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mt40OWgar1ef for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT) Received: from TX2EHSOBE004.bigfish.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3536821F8BE8 for <6lowpan@ietf.org>; Mon, 19 Sep 2011 06:52:19 -0700 (PDT) Received: from mail83-tx2-R.bigfish.com (10.9.14.241) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.22; Mon, 19 Sep 2011 13:54:41 +0000 Received: from mail83-tx2 (localhost.localdomain [127.0.0.1]) by mail83-tx2-R.bigfish.com (Postfix) with ESMTP id D6C721140095; Mon, 19 Sep 2011 13:54:41 +0000 (UTC) X-SpamScore: -38 X-BigFish: VPS-38(zz217bL15d6O9251J542Mzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944h61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:168.87.56.20; KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI Received: from mail83-tx2 (localhost.localdomain [127.0.0.1]) by mail83-tx2 (MessageSwitch) id 1316440480557220_23784; Mon, 19 Sep 2011 13:54:40 +0000 (UTC) Received: from TX2EHSMHS045.bigfish.com (unknown [10.9.14.247]) by mail83-tx2.bigfish.com (Postfix) with ESMTP id 76885C40050; Mon, 19 Sep 2011 13:54:40 +0000 (UTC) Received: from smtpx.philips.com (168.87.56.20) by TX2EHSMHS045.bigfish.com (10.9.99.145) with Microsoft SMTP Server (TLS) id 14.1.225.22; Mon, 19 Sep 2011 13:54:40 +0000 Received: from NLHILEXH04.connect1.local (172.16.153.45) by connect1.philips.com (172.16.156.152) with Microsoft SMTP Server (TLS) id 8.3.106.1; Mon, 19 Sep 2011 15:54:33 +0200 Received: from NLCLUEXM03.connect1.local ([172.16.157.42]) by NLHILEXH04.connect1.local ([172.16.153.45]) with mapi; Mon, 19 Sep 2011 15:50:53 +0200 From: "Dijk, Esko" To: "johanna.1.nieminen@nokia.com" , Carsten Bormann Date: Mon, 19 Sep 2011 15:54:32 +0200 Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: Acxu7ZD5yELfhJDQQB+hBYvRHzF+rgH42csQ Message-ID: References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org> In-Reply-To: <4AB4A5FC-C722-46C2-8BAD-133E742A2AC7@tzi.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "6lowpan@ietf.org" <6lowpan@ietf.org> Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 13:52:19 -0000 Dear BT-LE authors, all, I haven't done a detailed review but I have one technical comment/question.= The typical case in the I-D is a BT-LE mobile phone, connected to the inte= rnet, acting as a 6LBR and distributing an IP prefix to 6LNs. Is it the int= ention that an IP prefix for the 6LoWPAN can be obtained by the phone via D= HCPv6 ? If so would an ISP support this for a phone connected to their 3G = network? Obtaining an IP prefix by the 6LBR seems necessary to enable routing from a= host on the internet to a 6LN. regards, Esko Esko Dijk Philips Corporate Technologies, Research High Tech Campus 34, Eindhoven, The Netherlands esko.dijk@philips.com -----Original Message----- From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On Behalf = Of Carsten Bormann Sent: Friday 9 September 2011 14:43 To: 6lowpan@ietf.org Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE d= raft) 6LoWPANners, we are now looking at the third WG version (-02) of this draft. Are we ready to do a working-group last-call on this? -- if you see something major that needs to be done before this is ready, p= lease speak up now. (If you have technical comments, or maybe some editorial suggestions, th= ese are also useful at this point, although there also will be time to comm= ent in the actual WGLC.) -- conversely, if you have reviewed the document and like it, please do spe= ak up (and please do say what you have specifically looked at). Of course, we don't want to go into a WGLC with glaring omissions (I gather= Appendix A is not really a necessary part of this spec), and we also don't= want to go into WGLC if the working group hasn't been able to review the d= ocument or, worse, if nobody actually cares. Please respond to this message by Sep 16. Gruesse, Carsten _______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. From j.schoenwaelder@jacobs-university.de Mon Sep 19 06:53:23 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB92621F8BF7 for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:53:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.122 X-Spam-Level: X-Spam-Status: No, score=-103.122 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wkXMsN2WR2Fi for <6lowpan@ietfa.amsl.com>; Mon, 19 Sep 2011 06:53:23 -0700 (PDT) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 07C4921F8BE8 for <6lowpan@ietf.org>; Mon, 19 Sep 2011 06:53:23 -0700 (PDT) Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 667C120C89; Mon, 19 Sep 2011 15:55:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id jTjVpaaORvr7; Mon, 19 Sep 2011 15:55:44 +0200 (CEST) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3C28220C74; Mon, 19 Sep 2011 15:55:44 +0200 (CEST) Received: by elstar.local (Postfix, from userid 501) id 9DF081AEF882; Mon, 19 Sep 2011 15:55:31 +0200 (CEST) Date: Mon, 19 Sep 2011 15:55:31 +0200 From: Juergen Schoenwaelder To: johanna.1.nieminen@nokia.com Message-ID: <20110919135531.GA4103@elstar.local> Mail-Followup-To: johanna.1.nieminen@nokia.com, 6lowpan@ietf.org References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <20110912085852.GA39547@elstar.local> <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 13:53:23 -0000 On Mon, Sep 12, 2011 at 10:41:42AM +0000, johanna.1.nieminen@nokia.com wrote: > Hi, > > That specification is very broad and not necessarily all features are normative. > One can discuss whether its normative or not, but having no reference at all to BT 4.0 in the references section seems somewhat odd as far as I am concerned. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From minjun.xi@nokia.com Thu Sep 22 06:53:23 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6056921F8C40 for <6lowpan@ietfa.amsl.com>; Thu, 22 Sep 2011 06:53:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.999 X-Spam-Level: X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlzxUgprTitG for <6lowpan@ietfa.amsl.com>; Thu, 22 Sep 2011 06:53:19 -0700 (PDT) Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6D121F8C31 for <6lowpan@ietf.org>; Thu, 22 Sep 2011 06:53:18 -0700 (PDT) Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8MDtZBT032127; Thu, 22 Sep 2011 16:55:49 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Sep 2011 16:55:32 +0300 Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 22 Sep 2011 15:53:13 +0200 Received: from 008-AM1MPN1-052.mgdnok.nokia.com ([169.254.2.214]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0339.002; Thu, 22 Sep 2011 15:53:13 +0200 From: To: , , Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: AQHMdtPRK6TlyPrgJ0Sk4OZWWwl9nZVZ1OEA Date: Thu, 22 Sep 2011 13:53:12 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [114.249.158.86] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 22 Sep 2011 13:55:32.0755 (UTC) FILETIME=[4BB61630:01CC792F] X-Nokia-AV: Clean Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 13:53:23 -0000 Esko, DHCPv6 for 6LoWPAN network. In the current version of I-D, there's one chapter (3.2.1) describing "IPv6 Address Configuration", which mentioned "Stateless autoconfiguration". Stateless autoconfiguration is defined in RFC4862, which is different from "stateful autoconfiguration" (aka DHCPv6). Compared with 6LoWPAN over BT-LE, draft-ietf-6lowpan-nd has defined the mechanism to configure IPv6 addresses for 6LoWPAN over 802.15.4. In draft-ietf-6lowpan-nd-17, there're several assumptions for 6lowpan-nd. It says "All nodes in the network have an EUI-64 interface identifier in order to do address auto-configuration and detect duplicate addresses." Also, draft-ietf-6lowpan-nd introduces the Address Registration mechanism and the optional DAD mechanism. DHCPv6 is not optimized for low-power and lossy networks including 802.15.4 and BT-LE. I think it is necessary to make the "IPv6 address configuration" for 6LoWPAN over BT-LE clear in the future revision. Thank you! --=20 Best Regards, Minjun, Xi Nokia Research Center On 9/19/11 9:54 PM, "ext Dijk, Esko" wrote: >Dear BT-LE authors, all, > >I haven't done a detailed review but I have one technical >comment/question. The typical case in the I-D is a BT-LE mobile phone, >connected to the internet, acting as a 6LBR and distributing an IP prefix >to 6LNs. Is it the intention that an IP prefix for the 6LoWPAN can be >obtained by the phone via DHCPv6 ? If so would an ISP support this for a >phone connected to their 3G network? > >Obtaining an IP prefix by the 6LBR seems necessary to enable routing from >a host on the internet to a 6LN. > >regards, >Esko > > >Esko Dijk > >Philips Corporate Technologies, Research >High Tech Campus 34, Eindhoven, The Netherlands >esko.dijk@philips.com > > > > >-----Original Message----- >From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On >Behalf Of Carsten Bormann >Sent: Friday 9 September 2011 14:43 >To: 6lowpan@ietf.org >Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE >draft) > >6LoWPANners, > >we are now looking at the third WG version (-02) of this draft. > >Are we ready to do a working-group last-call on this? > >-- if you see something major that needs to be done before this is ready, >please speak up now. > (If you have technical comments, or maybe some editorial suggestions, >these are also useful at this point, although there also will be time to >comment in the actual WGLC.) > >-- conversely, if you have reviewed the document and like it, please do >speak up (and please do say what you have specifically looked at). > >Of course, we don't want to go into a WGLC with glaring omissions (I >gather Appendix A is not really a necessary part of this spec), and we >also don't want to go into WGLC if the working group hasn't been able to >review the document or, worse, if nobody actually cares. > >Please respond to this message by Sep 16. > >Gruesse, Carsten > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan > >The information contained in this message may be confidential and legally >protected under applicable law. The message is intended solely for the >addressee(s). If you are not the intended recipient, you are hereby >notified that any use, forwarding, dissemination, or reproduction of this >message is strictly prohibited and may be unlawful. If you are not the >intended recipient, please contact the sender by return e-mail and >destroy all copies of the original message. > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan From esko.dijk@philips.com Thu Sep 22 07:58:54 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BC121F8B83 for <6lowpan@ietfa.amsl.com>; Thu, 22 Sep 2011 07:58:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.942 X-Spam-Level: X-Spam-Status: No, score=-3.942 tagged_above=-999 required=5 tests=[AWL=-0.943, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUFy3A-expuv for <6lowpan@ietfa.amsl.com>; Thu, 22 Sep 2011 07:58:53 -0700 (PDT) Received: from DB3EHSOBE006.bigfish.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2BA21F8B80 for <6lowpan@ietf.org>; Thu, 22 Sep 2011 07:58:53 -0700 (PDT) Received: from mail47-db3-R.bigfish.com (10.3.81.251) by DB3EHSOBE006.bigfish.com (10.3.84.26) with Microsoft SMTP Server id 14.1.225.22; Thu, 22 Sep 2011 15:01:23 +0000 Received: from mail47-db3 (localhost.localdomain [127.0.0.1]) by mail47-db3-R.bigfish.com (Postfix) with ESMTP id 6F9C1170423; Thu, 22 Sep 2011 15:01:23 +0000 (UTC) X-SpamScore: -53 X-BigFish: VPS-53(zzbb2dK217bL15d6O9371K9251J542M1432N98dKzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h944h61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: CIP:168.87.56.20; KIP:(null); UIP:(null); IPVD:NLI; H:smtpx.philips.com; RD:smtpx.philips.com; EFVD:NLI Received: from mail47-db3 (localhost.localdomain [127.0.0.1]) by mail47-db3 (MessageSwitch) id 1316703645230836_21663; Thu, 22 Sep 2011 15:00:45 +0000 (UTC) Received: from DB3EHSMHS018.bigfish.com (unknown [10.3.81.243]) by mail47-db3.bigfish.com (Postfix) with ESMTP id 3ECF73F0062; Thu, 22 Sep 2011 14:58:57 +0000 (UTC) Received: from smtpx.philips.com (168.87.56.20) by DB3EHSMHS018.bigfish.com (10.3.87.118) with Microsoft SMTP Server (TLS) id 14.1.225.22; Thu, 22 Sep 2011 14:58:54 +0000 Received: from NLHILEXH01.connect1.local (172.16.153.76) by connect1.philips.com (172.16.156.41) with Microsoft SMTP Server (TLS) id 8.3.106.1; Thu, 22 Sep 2011 16:58:54 +0200 Received: from NLCLUEXM03.connect1.local ([172.16.157.42]) by NLHILEXH01.connect1.local ([172.16.153.76]) with mapi; Thu, 22 Sep 2011 16:55:07 +0200 From: "Dijk, Esko" To: "minjun.xi@nokia.com" , "johanna.1.nieminen@nokia.com" , "cabo@tzi.org" Date: Thu, 22 Sep 2011 16:58:50 +0200 Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: AQHMdtPRK6TlyPrgJ0Sk4OZWWwl9nZVZ1OEA//+gBMA= Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: philips.com Cc: "6lowpan@ietf.org" <6lowpan@ietf.org> Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 14:58:54 -0000 Hello Minjun, I don't see an issue in IPv6 address configuration in 6LNs / section 3.2.1. Rather the question is how the 6LBR (phone) obtains IP prefix(es). I was cu= rious whether a cellular operator would provide either 1) an IPv6 prefix (which the phone could further use for prefix distribut= ion into the LoWPAN) 2) an IPv6 address (in which case the phone needs some other mechanism to= obtain an IPv6 prefix - see below) Quote from draft-ietf-6lowpan-nd: The 6LBRs are responsible for managing the prefix(es) assigned to the 6LoWPAN, using manual configuration, DHCPv6 Prefix Delegation [RFC3633], or other mechanisms. In an isolated LoWPAN a ULA [RFC4193] prefix SHOULD be generated by the 6LBR. If more is known how this is going to work eg for the topology in Fig 5, we= could consider to write it in the I-D. Esko -----Original Message----- From: minjun.xi@nokia.com [mailto:minjun.xi@nokia.com] Sent: Thursday 22 September 2011 15:53 To: Dijk, Esko; johanna.1.nieminen@nokia.com; cabo@tzi.org Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-= LE draft) Esko, DHCPv6 for 6LoWPAN network. In the current version of I-D, there's one chapter (3.2.1) describing "IPv6 Address Configuration", which mentioned "Stateless autoconfiguration". Stateless autoconfiguration is defined in RFC4862, which is different from "stateful autoconfiguration" (aka DHCPv6). Compared with 6LoWPAN over BT-LE, draft-ietf-6lowpan-nd has defined the mechanism to configure IPv6 addresses for 6LoWPAN over 802.15.4. In draft-ietf-6lowpan-nd-17, there're several assumptions for 6lowpan-nd. It says "All nodes in the network have an EUI-64 interface identifier in order to do address auto-configuration and detect duplicate addresses." Also, draft-ietf-6lowpan-nd introduces the Address Registration mechanism and the optional DAD mechanism. DHCPv6 is not optimized for low-power and lossy networks including 802.15.4 and BT-LE. I think it is necessary to make the "IPv6 address configuration" for 6LoWPAN over BT-LE clear in the future revision. Thank you! -- Best Regards, Minjun, Xi Nokia Research Center On 9/19/11 9:54 PM, "ext Dijk, Esko" wrote: >Dear BT-LE authors, all, > >I haven't done a detailed review but I have one technical >comment/question. The typical case in the I-D is a BT-LE mobile phone, >connected to the internet, acting as a 6LBR and distributing an IP prefix >to 6LNs. Is it the intention that an IP prefix for the 6LoWPAN can be >obtained by the phone via DHCPv6 ? If so would an ISP support this for a >phone connected to their 3G network? > >Obtaining an IP prefix by the 6LBR seems necessary to enable routing from >a host on the internet to a 6LN. > >regards, >Esko > > >Esko Dijk > >Philips Corporate Technologies, Research >High Tech Campus 34, Eindhoven, The Netherlands >esko.dijk@philips.com > > > > >-----Original Message----- >From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On >Behalf Of Carsten Bormann >Sent: Friday 9 September 2011 14:43 >To: 6lowpan@ietf.org >Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE >draft) > >6LoWPANners, > >we are now looking at the third WG version (-02) of this draft. > >Are we ready to do a working-group last-call on this? > >-- if you see something major that needs to be done before this is ready, >please speak up now. > (If you have technical comments, or maybe some editorial suggestions, >these are also useful at this point, although there also will be time to >comment in the actual WGLC.) > >-- conversely, if you have reviewed the document and like it, please do >speak up (and please do say what you have specifically looked at). > >Of course, we don't want to go into a WGLC with glaring omissions (I >gather Appendix A is not really a necessary part of this spec), and we >also don't want to go into WGLC if the working group hasn't been able to >review the document or, worse, if nobody actually cares. > >Please respond to this message by Sep 16. > >Gruesse, Carsten > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan > >The information contained in this message may be confidential and legally >protected under applicable law. The message is intended solely for the >addressee(s). If you are not the intended recipient, you are hereby >notified that any use, forwarding, dissemination, or reproduction of this >message is strictly prohibited and may be unlawful. If you are not the >intended recipient, please contact the sender by return e-mail and >destroy all copies of the original message. > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message. From minjun.xi@nokia.com Fri Sep 23 00:41:00 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AAD21F8B5C for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 00:41:00 -0700 (PDT) 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=-2.599, J_CHICKENPOX_52=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbkInH3+BDVE for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 00:41:00 -0700 (PDT) Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 73CED21F8B5A for <6lowpan@ietf.org>; Fri, 23 Sep 2011 00:40:59 -0700 (PDT) Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8N7hRwF011046; Fri, 23 Sep 2011 10:43:32 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 23 Sep 2011 10:42:49 +0300 Received: from 008-AM1MMR1-003.mgdnok.nokia.com (65.54.30.58) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 23 Sep 2011 09:42:48 +0200 Received: from 008-AM1MPN1-051.mgdnok.nokia.com ([169.254.1.146]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.01.0339.002; Fri, 23 Sep 2011 09:42:47 +0200 From: To: , , Thread-Topic: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: AQHMdtPRK6TlyPrgJ0Sk4OZWWwl9nZVZ1OEA//+gBMCAASWZgA== Date: Fri, 23 Sep 2011 07:42:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-headerinfofordlp: None x-titus-version: 3.3.8.1 x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Company Confidential;Project=None; x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IvZFaL30hHLuUAxAOm4SFNChXnT0/AcTwyeJM2sEcAOBgdlmDQL9EA9LeZHenv+sDRJmUBNpxGjyTaDoMRTtG5VyHYxtVde4ZZC5l6VEx7qFp+BMMi/JteiK1UWsUbaJXTFPytCrbYHt5WD6aIIF4cQ0MmR926vTb6o91KRMD12HleZIs6IdAkjXJQ8tEbKa0yiFMMUIXI5TEAF6rZJwom91wRodbx+WbzYnW8ir2f4+L6RbCXoWIzJGjyjpgSFXSiMhSPTV2MQtqOhgA40eAFM= x-originating-ip: [10.233.20.40] Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_004C_01CC7A07.702BCC20" MIME-Version: 1.0 X-OriginalArrivalTime: 23 Sep 2011 07:42:49.0112 (UTC) FILETIME=[645AB980:01CC79C4] X-Nokia-AV: Clean Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 07:41:00 -0000 ------=_NextPart_000_004C_01CC7A07.702BCC20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sorry about that, I misunderstood your question. I have no idea about which prefix should be generated by the 6LBR, which is really one big issue. -- Best Regards, Minjun, Xi Nokia Research Center -----Original Message----- From: ext Dijk, Esko [mailto:esko.dijk@philips.com] Sent: Thursday, September 22, 2011 10:59 PM To: Xi Minjun (Nokia-NRC/Beijing); Nieminen Johanna.1 (Nokia-NRC/Helsinki); cabo@tzi.org Cc: 6lowpan@ietf.org Subject: RE: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Hello Minjun, I don't see an issue in IPv6 address configuration in 6LNs / section 3.2.1. Rather the question is how the 6LBR (phone) obtains IP prefix(es). I was curious whether a cellular operator would provide either 1) an IPv6 prefix (which the phone could further use for prefix distribution into the LoWPAN) 2) an IPv6 address (in which case the phone needs some other mechanism to obtain an IPv6 prefix - see below) Quote from draft-ietf-6lowpan-nd: The 6LBRs are responsible for managing the prefix(es) assigned to the 6LoWPAN, using manual configuration, DHCPv6 Prefix Delegation [RFC3633], or other mechanisms. In an isolated LoWPAN a ULA [RFC4193] prefix SHOULD be generated by the 6LBR. If more is known how this is going to work eg for the topology in Fig 5, we could consider to write it in the I-D. Esko -----Original Message----- From: minjun.xi@nokia.com [mailto:minjun.xi@nokia.com] Sent: Thursday 22 September 2011 15:53 To: Dijk, Esko; johanna.1.nieminen@nokia.com; cabo@tzi.org Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Esko, DHCPv6 for 6LoWPAN network. In the current version of I-D, there's one chapter (3.2.1) describing "IPv6 Address Configuration", which mentioned "Stateless autoconfiguration". Stateless autoconfiguration is defined in RFC4862, which is different from "stateful autoconfiguration" (aka DHCPv6). Compared with 6LoWPAN over BT-LE, draft-ietf-6lowpan-nd has defined the mechanism to configure IPv6 addresses for 6LoWPAN over 802.15.4. In draft-ietf-6lowpan-nd-17, there're several assumptions for 6lowpan-nd. It says "All nodes in the network have an EUI-64 interface identifier in order to do address auto-configuration and detect duplicate addresses." Also, draft-ietf-6lowpan-nd introduces the Address Registration mechanism and the optional DAD mechanism. DHCPv6 is not optimized for low-power and lossy networks including 802.15.4 and BT-LE. I think it is necessary to make the "IPv6 address configuration" for 6LoWPAN over BT-LE clear in the future revision. Thank you! -- Best Regards, Minjun, Xi Nokia Research Center On 9/19/11 9:54 PM, "ext Dijk, Esko" wrote: >Dear BT-LE authors, all, > >I haven't done a detailed review but I have one technical >comment/question. The typical case in the I-D is a BT-LE mobile phone, >connected to the internet, acting as a 6LBR and distributing an IP >prefix to 6LNs. Is it the intention that an IP prefix for the 6LoWPAN >can be obtained by the phone via DHCPv6 ? If so would an ISP support >this for a phone connected to their 3G network? > >Obtaining an IP prefix by the 6LBR seems necessary to enable routing >from a host on the internet to a 6LN. > >regards, >Esko > > >Esko Dijk > >Philips Corporate Technologies, Research High Tech Campus 34, >Eindhoven, The Netherlands esko.dijk@philips.com > > > > >-----Original Message----- >From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On >Behalf Of Carsten Bormann >Sent: Friday 9 September 2011 14:43 >To: 6lowpan@ietf.org >Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over >BT-LE >draft) > >6LoWPANners, > >we are now looking at the third WG version (-02) of this draft. > >Are we ready to do a working-group last-call on this? > >-- if you see something major that needs to be done before this is >ready, please speak up now. > (If you have technical comments, or maybe some editorial >suggestions, these are also useful at this point, although there also >will be time to comment in the actual WGLC.) > >-- conversely, if you have reviewed the document and like it, please do >speak up (and please do say what you have specifically looked at). > >Of course, we don't want to go into a WGLC with glaring omissions (I >gather Appendix A is not really a necessary part of this spec), and we >also don't want to go into WGLC if the working group hasn't been able >to review the document or, worse, if nobody actually cares. > >Please respond to this message by Sep 16. > >Gruesse, Carsten > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan > >The information contained in this message may be confidential and >legally protected under applicable law. The message is intended solely >for the addressee(s). If you are not the intended recipient, you are >hereby notified that any use, forwarding, dissemination, or >reproduction of this message is strictly prohibited and may be >unlawful. If you are not the intended recipient, please contact the >sender by return e-mail and destroy all copies of the original message. > >_______________________________________________ >6lowpan mailing list >6lowpan@ietf.org >https://www.ietf.org/mailman/listinfo/6lowpan The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. ------=_NextPart_000_004C_01CC7A07.702BCC20 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOoDCCAzYw ggIeoAMCAQICBDpVqdkwDQYJKoZIhvcNAQEFBQAwKTEOMAwGA1UEChMFTm9raWExFzAVBgNVBAMT Dk5va2lhICBSb290IENBMB4XDTAxMDEwNTExMDUwNVoXDTE2MDEwMjExMDUwNVowKTEOMAwGA1UE ChMFTm9raWExFzAVBgNVBAMTDk5va2lhICBSb290IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A MIIBCgKCAQEAsrTy8gLmr4LYvp0khVUVHw7ascdl+Cjr+yI5MlZ6J/U6Qsvkiqthgqq8rPcLV0P1 92TfBr27VgKEeCaZe0icS1jC2spM/wRv3j2WxdkKxb9kDJtuCNJaRBqvi5vGTHB15nmEmKuL5f3i rAxeHqPjgS496oWcudzFT1e7Xrc/gWGFYd72+/ykIFXjWOMZv6QpxD8x1hLPyh2YVXRk9U7N7pvm RQNX29g4SCFJY2BBIa5JPlwIF8Nc9IePaC/E/2M4tGMtiOOZlm99EoL7N0hJZtFSvUwdCBud/viH 4DgsKGjNkNKi6pAHc9IaXB6tIykcoYp+L+oe/3+cuEJaCj1EKwIDAQABo2YwZDASBgNVHRMBAf8E CDAGAQH/AgEEMB0GA1UdDgQWBBSNjfefoQ0AITLvqe0iruA79NB9sDAfBgNVHSMEGDAWgBSNjfef oQ0AITLvqe0iruA79NB9sDAOBgNVHQ8BAf8EBAMCAYYwDQYJKoZIhvcNAQEFBQADggEBAIGEPql2 TALyKi/h1J+Mh5XolAtYppcSOLMtBkoA7ZovGBDNvl0VbZs8AAojJqkUoWBB+L6DKyl/jKhNfKcu rWRGRyj7pnbxrKLsI3gmWNWkyo2b60wJwe9fqPD5ZQy3oEiMit9l0Ba6il/k2GqYopUCNMa7mfeb E2LeBy5ChYMiCi97UQSJvAdzEYylTJw8Awc6AiM2Ve5N+XxsmKgNf/2A/5IJ3EZZ+wFRmkI4062A oNU302rqAt0HH88jzoUF4AfYHWl6HpYhGXFbcX44rHINyPmFBRxLYIFJ6ZWUr/mXpL/e6rqFtNWO kV6UoJND7OVZkbLh7F1+lcqXRU8TPBMwggOHMIICb6ADAgECAgRBtbHpMA0GCSqGSIb3DQEBBQUA MCkxDjAMBgNVBAoTBU5va2lhMRcwFQYDVQQDEw5Ob2tpYSAgUm9vdCBDQTAeFw0wNjAzMzAwOTU3 MTFaFw0xNjAxMDIxMTA1MDVaMDMxCzAJBgNVBAYTAkZJMQ4wDAYDVQQKEwVOb2tpYTEUMBIGA1UE AxMLTm9raWEgQkkgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDtFCg3QEjSCg6T IUxoWsNwELh8bBNiUQPCPmg8c2DHQYXWWCSCMb+S0Fvh1qqI1xt+XnzyFq+5eqzGzDj4UaBcG+d9 qxrCFly8sHyoPTryyPrR0EI2UUDWwfS6ojhqgwghRqo8G38TjFusyBtLub/5L6yvWYSOHD+JcB+q VM2fbkArPYK4Ydv8WG/DbHjGn0gKq0zwpVZKI/gCK/QALYvte02NXseqvY9/GOyLtjy3Z8erFv71 KKTq+gxI/7DK55pJf3PoD+kT4kyGm6EF9DTdK4ojMdar17uyX0IOZz/4vkkF0d+60nmnLX63FJPA jUyB0HUNJ32NXDo9UsM38aoNAgMBAAGjgawwgakwDwYDVR0TAQH/BAUwAwEB/zARBgNVHSAECjAI MAYGBFUdIAAwDgYDVR0PAQH/BAQDAgGGMFQGA1UdIwRNMEuAFI2N95+hDQAhMu+p7SKu4Dv00H2w oS2kKzApMQ4wDAYDVQQKEwVOb2tpYTEXMBUGA1UEAxMOTm9raWEgIFJvb3QgQ0GCBDpVqdkwHQYD VR0OBBYEFKcksD7Fg+8EDlB2Sxgy58pW0Sy6MA0GCSqGSIb3DQEBBQUAA4IBAQAC3lEUplDlVNOT Pjz/XFezXx2bV2XbCFindhA3F815Egi55H6/cYezEjoP4QLNEGGl2I3aLvkn5A0T8I4pbiFPhIiu B/frbbGg6k6GjQLe/bFQ8F1mAOOR+GyneKZFPfzaRV0jiIR9QqnMXTf8RvKkCJyFj10MZVsLIy/Y uBkzeP3JhzDhUdtPfwmJN6ZbIhH5uR/2BwAGtgQknb8WX3I4wnhWtMUxB8XmayayYs8qWYeIiVkI FV+sLTkWUWVvvKUjyakBpbAW2vUP84DYsJ8TL1YefNjf/nIOByMcORLuV/1gPjyv00qJbcB59AA+ iXe3zIo8QNcgXG0uPQQFmrGDMIID2DCCAsCgAwIBAgIRAIJFxzs39FK/z3Wc77vH2e0wDQYJKoZI hvcNAQEFBQAwMzELMAkGA1UEBhMCRkkxDjAMBgNVBAoTBU5va2lhMRQwEgYDVQQDEwtOb2tpYSBC SSBDQTAeFw0xMTA2MjAwMzQ3MjVaFw0xNDA2MjAwMzQ3MjVaME8xDjAMBgNVBAoMBU5va2lhMQ8w DQYDVQQLDAZQZW9wbGUxGDAWBgoJkiaJk/IsZAEBDAgxMDM0OTMyMTESMBAGA1UEAwwJWGkgTWlu anVuMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0TZYyfQN1pwLOSVpmHE9iOz/bqDt OS+rsbUw73gfI08JNzJtD8IL9D5ewsWQ6RxezCXIbpFQPGjuW5hPYc6bjyRJWE57LFjUaHJZ52b5 zwQpfGNG2jkrEb59oSK9zZKS6lJswyPu5E9Iupo2+o7QcsKsX7hBmqvZuq3AYcjEmoSFYJssKHf2 G6hpjycxs/DKhuO2Z6l5mVTPkEIGC07HSIl7KmaqXWnIcGyjF6xc8FNLursx2E6Fm7zxAeiDDUXM jVP4Y+0bui8rWIZUuZNldV7HpgNi0/pCNC9m1dkIdDID3YMhW0EY+Kk6555kYp7LSKXjcwLyKnyR UoEEKcVExQIDAQABo4HKMIHHMA8GA1UdDwEB/wQFAwMHMAAwHwYDVR0jBBgwFoAUpySwPsWD7wQO UHZLGDLnylbRLLowGQYDVR0gBBIwEDAOBgwrBgEEAV4BMQYBBwEwOQYDVR0fBDIwMDAuoCygKoYo aHR0cDovL2NybC5ub2tpYS5jb20vTm9raWElMjBCSSUyMENBLmNybDAeBgNVHREEFzAVgRNtaW5q dW4ueGlAbm9raWEuY29tMB0GA1UdDgQWBBT0labkEeHb+MXx39Wx4H1KJgf2STANBgkqhkiG9w0B AQUFAAOCAQEAJiZTEBjCBAv4ZXf5o7q2H2uFWgJunBWzUXnaxzagytxwbDipb2koUKtYKqgPhqXA icX0sEHQaxB5X5GM/Y7msU1Z4czyZgT9RfKYfJv2BrqIKV5XtadNVXgE1zOUYlqVlEJs770rWOWY ekGeRp+nLOiGFtnN6+WP66os4zUvLX5Xfh4QidXVhIdjnOJAsjC6DY9SWm9T6zboPaqD1yGtGCDz nU3Vy1JvbPTkiZR/kFp9/GiozZIWc6vb/gQQfJ9YaVT+QfN9tbB+4976q8cnw1DQNYe8FeeFLYvS 9LS7irDbcXxO3c8tdNrMw1BUbK8oMEQtCs63kqsCJAO4DYiPyzCCA/swggLjoAMCAQICEAYysTmt jQng3A6B+4epBWwwDQYJKoZIhvcNAQEFBQAwMzELMAkGA1UEBhMCRkkxDjAMBgNVBAoTBU5va2lh MRQwEgYDVQQDEwtOb2tpYSBCSSBDQTAeFw0xMTA2MjAwMzQ2MzNaFw0xMzA2MTkwMzQ2MzNaME8x DjAMBgNVBAoMBU5va2lhMQ8wDQYDVQQLDAZQZW9wbGUxGDAWBgoJkiaJk/IsZAEBDAgxMDM0OTMy MTESMBAGA1UEAwwJWGkgTWluanVuMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArTWZ u3XCp7AnRzEQv2VXvuq3UlTWJBM1XOJ+tBo+X2iOD+Uu9qApVTQj7chrGw6Rl5sxukHY24Q0uyUO NUcCXBBZuHbggbDr5kwTeIHPUqv0Kc8ACjc6QlfgGhT4ZSE/H7QuagayYCdjiBlV9V8z3N3M0Cjm 0bIcgTTttXm3Zj9asP0XcXv23NXjpeYpWp+KzweXnkh2CdOeB8GaZo6hTKKT213JW9tYQsSeYDqM t4M6IaIkMmIpafGSa+h6UxaGKkNAMJb6V+htd39mZCytgpzaagIEN4xC30SPmwMhbHkHJ8IG7Pst NHnb7w37pRI3YaPP4aHePc7rVtR2469qEwIDAQABo4HuMIHrMB8GA1UdIwQYMBaAFKcksD7Fg+8E DlB2Sxgy58pW0Sy6MBkGA1UdIAQSMBAwDgYMKwYBBAFeATEGAQYDMDkGA1UdHwQyMDAwLqAsoCqG KGh0dHA6Ly9jcmwubm9raWEuY29tL05va2lhJTIwQkklMjBDQS5jcmwwIwYDVR0lBBwwGgYIKwYB BQUHAwIGBFUdJQAGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIHgDAeBgNVHREEFzAVgRNtaW5qdW4u eGlAbm9raWEuY29tMB0GA1UdDgQWBBTPcXdeCJw64yJynSvaBChgXaKs2zANBgkqhkiG9w0BAQUF AAOCAQEAGUgJYtg8DjKiAdSxgf/DLMPVCUmFHbaNG8DdlWUL6gJ6lhZ/0CF00i8utrTqMoDS4M43 g328vgzkOwn4+eXgX48uGX3yG4OOoWsorPCveW27g2sg7uG5kAznxXQ1ngeNE5kTEsNuYN2XVLNC Yj4rSWshH79d1mDQG7f3drRSddjvOOG1e1J7/Xes0c/mLzK+WZBHligxNsqPYH+4V72VtPpZ9Oir vRnZefNWB8lNtZEzV4/YzBt/JVCbF4m1URvf9QDjCxWX56iUTO+o70abhWy41rVb5sT1WpX6mXim 7MDV2G3Hh3B5q0OTXHsaLThbPT7xsHlby7te6dSexgQdhTGCAuwwggLoAgEBMEcwMzELMAkGA1UE BhMCRkkxDjAMBgNVBAoTBU5va2lhMRQwEgYDVQQDEwtOb2tpYSBCSSBDQQIQBjKxOa2NCeDcDoH7 h6kFbDAJBgUrDgMCGgUAoIIBejAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ BTEPFw0xMTA5MjMwNzQyNDVaMCMGCSqGSIb3DQEJBDEWBBSgtlG85V5Adp9eZHr5uB8UwOm5mTBX BgkrBgEEAYI3EAQxSjBIMDMxCzAJBgNVBAYTAkZJMQ4wDAYDVQQKEwVOb2tpYTEUMBIGA1UEAxML Tm9raWEgQkkgQ0ECEQCCRcc7N/RSv891nO+7x9ntMFkGCyqGSIb3DQEJEAILMUqgSDAzMQswCQYD VQQGEwJGSTEOMAwGA1UEChMFTm9raWExFDASBgNVBAMTC05va2lhIEJJIENBAhEAgkXHOzf0Ur/P dZzvu8fZ7TBnBgkqhkiG9w0BCQ8xWjBYMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTAN BgkqhkiG9w0BAQEFAASCAQAksmC+o9pCPcguuJiVhceLsYEM8feAUPup2LfG4AKNc9NygofMTnb/ MQEaKBAYNoNkI4Y0LHgkXxN8D2Uv0Bw1psuUtgxWf6rydnM/7ZK0GSUaTvQCJffjHmLPinRiBpAx mN7TZV5fK02G4WDOmL10IgzWOwtZQMCHiCS7swAn69b4EqPgdZudd6e9mlR3Z7eU5qeX/kMFO1f1 4ATAEYF+1AEYO2nLMeRYSQ6nnhLdRHayQh22ioPifHa6cyJ1eCAnL/CjdoOZ55l2inAQ/IDTJON2 AUkRiMMwCHSovVM5etYmz49tFxfVXizUgqLdTlEdo+Id0prouHs4HzPi3umAAAAAAAAA ------=_NextPart_000_004C_01CC7A07.702BCC20-- From teemu.savolainen@nokia.com Fri Sep 23 01:35:46 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5757021F8BBD for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 01:35:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.33 X-Spam-Level: X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[AWL=-0.331, BAYES_00=-2.599, J_CHICKENPOX_52=0.6] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kweDtTNsxenw for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 01:35:45 -0700 (PDT) Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 33AFD21F8BB0 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 01:35:44 -0700 (PDT) Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8N8aZx0006204 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 11:38:15 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 23 Sep 2011 11:38:00 +0300 Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 23 Sep 2011 10:38:00 +0200 Received: from 008-AM1MPN1-036.mgdnok.nokia.com ([169.254.6.138]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0339.002; Fri, 23 Sep 2011 10:37:53 +0200 From: To: <6lowpan@ietf.org> Thread-Topic: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) Thread-Index: Acx5yvTkcMWcQYBsTaWQK+YNfIuQUA== Date: Fri, 23 Sep 2011 08:37:53 +0000 Message-ID: <916CE6CF87173740BC8A2CE44309696202F2F0A5@008-AM1MPN1-036.mgdnok.nokia.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Company Confidential;Project=None; x-titus-version: 3.3.8.1 x-headerinfofordlp: None x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IiXSGa0NTRVWCWxcDyDa8OeCbhCTsrdpbgiM7AO5K1kcagJeDOF5YAj3DDoSz/c07l17+ssoDcq9HBNiUUtaxW7HTD6GwjUo28EaOfWUjoPR4jaHP7KMJLU06HtDW/bcY9OcmSwNeAWfud2krbHZ9AuOcI46YzUfRtm+f4JotHF8o48zbbhDSLo3vRH+76BJAXEKQP1qR5fe2kvp1LsmHmfhRa3/fKeeVD0Uf/xLn01o2yrymZOVnE3cCos8hlYMJFfi9EKrd4cXMym725Gqrkk= x-originating-ip: [10.162.93.230] Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_01C1_01CC79E5.3A6C9CD0" MIME-Version: 1.0 X-OriginalArrivalTime: 23 Sep 2011 08:38:00.0390 (UTC) FILETIME=[1A07A660:01CC79CC] X-Nokia-AV: Clean Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over BT-LE draft) X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 08:35:46 -0000 ------=_NextPart_000_01C1_01CC79E5.3A6C9CD0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable (just joined this list) I do not believe normative text about from where 6LBR gets prefixes it = uses to number BT-LE network is mandatory for "IPv6 over BT-LE" = document. A tool for obtaining prefixes, which can be used on BT-LE = network, is used on 6LBR's "non-BT-LE" WAN interface and hence has = nothing to do with BT-LE. That said, the 6LBR could utilize multitude of tools, for example: - DHCPv6 Prefix Delegation is a possibility when 6LBR's WAN interface is = cellular and ISP providers DHCPv6 Prefix Delegation service. Also if WAN = is fixed network, then the fixed-line ISP may also provide DHCPv6 PD = services - IPv6 Neighbor Discovery Proxy technology is also possibility, in which = case 6LBR "bridges" the (/64) prefix it has on WAN (cellular) interface = to BT-LE network - Prefix generated as described by 6to4 is possibility if 6LBR has only = public IPv4 address in its WAN interface (it can use that to build IPv6 = prefix) - Autogenerated ULA prefix is also possibility, if only "site local" = communication is required - NAT66 is possibility, although very evil of course=E2=98=BA In that = case 6LBR would advertise e.g. autogenerated ULA prefix for BT-LE and = then NAT communications using local addresses to public IPv6 - Static prefixes could be used, and those could be configured manually = or provided via some provisioning system=20 And of course if only local communications are needed (6LBR acts as = proxy), then of course no prefix is needed at all and communications = with link-local addresses is enough. And so forth, i.e. the 6LBR can get the prefixes from the source best = suited for the deployment scenario at hand. Maybe it would be worth = clarifying that the exact tool 6LBR uses is out of scope of this = document? In 3GPP based cellular accesses the handsets will prefer DHCPv6 Prefix = Delegation (standardized in 3GPP Release-10 but could be used sooner as = well), but if DHCPv6 PD is not supported by handset or network, then ND = Proxy is the likeliest technology to choose. In 3GPP access the phone = gets at least one /64 for its WAN interface, which can be shared locally = as well. For 3GPP addressing details please see: draft-ietf-v6ops-3gpp-eps-07 = section 5. Best regards, Teemu >-----Original Message----- >From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On=20 >Behalf Of Xi Minjun (Nokia-NRC/Beijing) >Sent: 23 September, 2011 10:43 >To: esko.dijk@philips.com; Nieminen Johanna.1 (Nokia-NRC/Helsinki);=20 >cabo@tzi.org >Cc: 6lowpan@ietf.org >Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over = >BT-LE >draft) > >Sorry about that, I misunderstood your question. I have no idea about=20 >which prefix should be generated by the 6LBR, which is really one big = issue. >-- >Best Regards, >Minjun, Xi >Nokia Research Center > >-----Original Message----- >From: ext Dijk, Esko [mailto:esko.dijk@philips.com] >Sent: Thursday, September 22, 2011 10:59 PM >To: Xi Minjun (Nokia-NRC/Beijing); Nieminen Johanna.1=20 >(Nokia-NRC/Helsinki); cabo@tzi.org >Cc: 6lowpan@ietf.org >Subject: RE: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over = >BT-LE >draft) > >Hello Minjun, > >I don't see an issue in IPv6 address configuration in 6LNs / section = 3.2.1. >Rather the question is how the 6LBR (phone) obtains IP prefix(es). I=20 >was curious whether a cellular operator would provide either > 1) an IPv6 prefix (which the phone could further use for prefix=20 >distribution into the LoWPAN) > 2) an IPv6 address (in which case the phone needs some other=20 >mechanism to obtain an IPv6 prefix - see below) > >Quote from draft-ietf-6lowpan-nd: > > The 6LBRs are responsible for managing the prefix(es) assigned to = the > 6LoWPAN, using manual configuration, DHCPv6 Prefix Delegation > [RFC3633], or other mechanisms. In an isolated LoWPAN a ULA > [RFC4193] prefix SHOULD be generated by the 6LBR. > >If more is known how this is going to work eg for the topology in Fig=20 >5, we could consider to write it in the I-D. > >Esko > >-----Original Message----- >From: minjun.xi@nokia.com [mailto:minjun.xi@nokia.com] >Sent: Thursday 22 September 2011 15:53 >To: Dijk, Esko; johanna.1.nieminen@nokia.com; cabo@tzi.org >Cc: 6lowpan@ietf.org >Subject: Re: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over = >BT-LE >draft) > >Esko, >DHCPv6 for 6LoWPAN network. > >In the current version of I-D, there's one chapter (3.2.1) describing >"IPv6 Address Configuration", which mentioned "Stateless=20 >autoconfiguration". >Stateless autoconfiguration is defined in RFC4862, which is different=20 >from "stateful autoconfiguration" (aka DHCPv6). > >Compared with 6LoWPAN over BT-LE, draft-ietf-6lowpan-nd has defined the = >mechanism to configure IPv6 addresses for 6LoWPAN over 802.15.4. In=20 >draft- ietf-6lowpan-nd-17, there're several assumptions for 6lowpan-nd. = >It says "All nodes in the network have an EUI-64 interface identifier=20 >in order to do address auto-configuration and detect duplicate = addresses." >Also, draft-ietf-6lowpan-nd introduces the Address Registration=20 >mechanism and the optional DAD mechanism. DHCPv6 is not optimized for=20 >low-power and lossy networks including 802.15.4 and BT-LE. > >I think it is necessary to make the "IPv6 address configuration" for=20 >6LoWPAN over BT-LE clear in the future revision. > >Thank you! > >-- >Best Regards, >Minjun, Xi >Nokia Research Center > > > > > >On 9/19/11 9:54 PM, "ext Dijk, Esko" wrote: > >>Dear BT-LE authors, all, >> >>I haven't done a detailed review but I have one technical=20 >>comment/question. The typical case in the I-D is a BT-LE mobile phone, = >>connected to the internet, acting as a 6LBR and distributing an IP=20 >>prefix to 6LNs. Is it the intention that an IP prefix for the 6LoWPAN=20 >>can be obtained by the phone via DHCPv6 ? If so would an ISP support=20 >>this for a phone connected to their 3G network? >> >>Obtaining an IP prefix by the 6LBR seems necessary to enable routing=20 >>from a host on the internet to a 6LN. >> >>regards, >>Esko >> >> >>Esko Dijk >> >>Philips Corporate Technologies, Research High Tech Campus 34,=20 >>Eindhoven, The Netherlands esko.dijk@philips.com >> >> >> >> >>-----Original Message----- >>From: 6lowpan-bounces@ietf.org [mailto:6lowpan-bounces@ietf.org] On=20 >>Behalf Of Carsten Bormann >>Sent: Friday 9 September 2011 14:43 >>To: 6lowpan@ietf.org >>Subject: [6lowpan] Ready for WGLC? (Re: Latest version of IPv6 over=20 >>BT-LE >>draft) >> >>6LoWPANners, >> >>we are now looking at the third WG version (-02) of this draft. >> >>Are we ready to do a working-group last-call on this? >> >>-- if you see something major that needs to be done before this is=20 >>ready, please speak up now. >> (If you have technical comments, or maybe some editorial=20 >>suggestions, these are also useful at this point, although there also=20 >>will be time to comment in the actual WGLC.) >> >>-- conversely, if you have reviewed the document and like it, please=20 >>do speak up (and please do say what you have specifically looked at). >> >>Of course, we don't want to go into a WGLC with glaring omissions (I=20 >>gather Appendix A is not really a necessary part of this spec), and we = >>also don't want to go into WGLC if the working group hasn't been able=20 >>to review the document or, worse, if nobody actually cares. >> >>Please respond to this message by Sep 16. >> >>Gruesse, Carsten >> >>_______________________________________________ >>6lowpan mailing list >>6lowpan@ietf.org >>https://www.ietf.org/mailman/listinfo/6lowpan >> >>The information contained in this message may be confidential and=20 >>legally protected under applicable law. The message is intended solely = >>for the addressee(s). If you are not the intended recipient, you are=20 >>hereby notified that any use, forwarding, dissemination, or=20 >>reproduction of this message is strictly prohibited and may be=20 >>unlawful. If you are not the intended recipient, please contact the=20 >>sender by return e-mail and destroy all copies of the original = message. >> >>_______________________________________________ >>6lowpan mailing list >>6lowpan@ietf.org >>https://www.ietf.org/mailman/listinfo/6lowpan > > >The information contained in this message may be confidential and=20 >legally protected under applicable law. The message is intended solely=20 >for the addressee(s). If you are not the intended recipient, you are=20 >hereby notified that any use, forwarding, dissemination, or=20 >reproduction of this message is strictly prohibited and may be=20 >unlawful. If you are not the intended recipient, please contact the=20 >sender by return e-mail and destroy all copies of the original message. ------=_NextPart_000_01C1_01CC79E5.3A6C9CD0 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIOuzCCAzYw ggIeoAMCAQICBDpVqdkwDQYJKoZIhvcNAQEFBQAwKTEOMAwGA1UEChMFTm9raWExFzAVBgNVBAMT Dk5va2lhICBSb290IENBMB4XDTAxMDEwNTExMDUwNVoXDTE2MDEwMjExMDUwNVowKTEOMAwGA1UE ChMFTm9raWExFzAVBgNVBAMTDk5va2lhICBSb290IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A MIIBCgKCAQEAsrTy8gLmr4LYvp0khVUVHw7ascdl+Cjr+yI5MlZ6J/U6Qsvkiqthgqq8rPcLV0P1 92TfBr27VgKEeCaZe0icS1jC2spM/wRv3j2WxdkKxb9kDJtuCNJaRBqvi5vGTHB15nmEmKuL5f3i rAxeHqPjgS496oWcudzFT1e7Xrc/gWGFYd72+/ykIFXjWOMZv6QpxD8x1hLPyh2YVXRk9U7N7pvm RQNX29g4SCFJY2BBIa5JPlwIF8Nc9IePaC/E/2M4tGMtiOOZlm99EoL7N0hJZtFSvUwdCBud/viH 4DgsKGjNkNKi6pAHc9IaXB6tIykcoYp+L+oe/3+cuEJaCj1EKwIDAQABo2YwZDASBgNVHRMBAf8E CDAGAQH/AgEEMB0GA1UdDgQWBBSNjfefoQ0AITLvqe0iruA79NB9sDAfBgNVHSMEGDAWgBSNjfef oQ0AITLvqe0iruA79NB9sDAOBgNVHQ8BAf8EBAMCAYYwDQYJKoZIhvcNAQEFBQADggEBAIGEPql2 TALyKi/h1J+Mh5XolAtYppcSOLMtBkoA7ZovGBDNvl0VbZs8AAojJqkUoWBB+L6DKyl/jKhNfKcu rWRGRyj7pnbxrKLsI3gmWNWkyo2b60wJwe9fqPD5ZQy3oEiMit9l0Ba6il/k2GqYopUCNMa7mfeb E2LeBy5ChYMiCi97UQSJvAdzEYylTJw8Awc6AiM2Ve5N+XxsmKgNf/2A/5IJ3EZZ+wFRmkI4062A oNU302rqAt0HH88jzoUF4AfYHWl6HpYhGXFbcX44rHINyPmFBRxLYIFJ6ZWUr/mXpL/e6rqFtNWO kV6UoJND7OVZkbLh7F1+lcqXRU8TPBMwggOHMIICb6ADAgECAgRBtbHpMA0GCSqGSIb3DQEBBQUA MCkxDjAMBgNVBAoTBU5va2lhMRcwFQYDVQQDEw5Ob2tpYSAgUm9vdCBDQTAeFw0wNjAzMzAwOTU3 MTFaFw0xNjAxMDIxMTA1MDVaMDMxCzAJBgNVBAYTAkZJMQ4wDAYDVQQKEwVOb2tpYTEUMBIGA1UE AxMLTm9raWEgQkkgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDtFCg3QEjSCg6T IUxoWsNwELh8bBNiUQPCPmg8c2DHQYXWWCSCMb+S0Fvh1qqI1xt+XnzyFq+5eqzGzDj4UaBcG+d9 qxrCFly8sHyoPTryyPrR0EI2UUDWwfS6ojhqgwghRqo8G38TjFusyBtLub/5L6yvWYSOHD+JcB+q VM2fbkArPYK4Ydv8WG/DbHjGn0gKq0zwpVZKI/gCK/QALYvte02NXseqvY9/GOyLtjy3Z8erFv71 KKTq+gxI/7DK55pJf3PoD+kT4kyGm6EF9DTdK4ojMdar17uyX0IOZz/4vkkF0d+60nmnLX63FJPA jUyB0HUNJ32NXDo9UsM38aoNAgMBAAGjgawwgakwDwYDVR0TAQH/BAUwAwEB/zARBgNVHSAECjAI MAYGBFUdIAAwDgYDVR0PAQH/BAQDAgGGMFQGA1UdIwRNMEuAFI2N95+hDQAhMu+p7SKu4Dv00H2w oS2kKzApMQ4wDAYDVQQKEwVOb2tpYTEXMBUGA1UEAxMOTm9raWEgIFJvb3QgQ0GCBDpVqdkwHQYD VR0OBBYEFKcksD7Fg+8EDlB2Sxgy58pW0Sy6MA0GCSqGSIb3DQEBBQUAA4IBAQAC3lEUplDlVNOT Pjz/XFezXx2bV2XbCFindhA3F815Egi55H6/cYezEjoP4QLNEGGl2I3aLvkn5A0T8I4pbiFPhIiu B/frbbGg6k6GjQLe/bFQ8F1mAOOR+GyneKZFPfzaRV0jiIR9QqnMXTf8RvKkCJyFj10MZVsLIy/Y uBkzeP3JhzDhUdtPfwmJN6ZbIhH5uR/2BwAGtgQknb8WX3I4wnhWtMUxB8XmayayYs8qWYeIiVkI FV+sLTkWUWVvvKUjyakBpbAW2vUP84DYsJ8TL1YefNjf/nIOByMcORLuV/1gPjyv00qJbcB59AA+ iXe3zIo8QNcgXG0uPQQFmrGDMIID5DCCAsygAwIBAgIQMH5apak8lEy6LmLlLsJy8TANBgkqhkiG 9w0BAQUFADAzMQswCQYDVQQGEwJGSTEOMAwGA1UEChMFTm9raWExFDASBgNVBAMTC05va2lhIEJJ IENBMB4XDTExMDkwNjA1NTIwNFoXDTE0MDkwNjA1NTIwNFowVjEOMAwGA1UECgwFTm9raWExDzAN BgNVBAsMBlBlb3BsZTEYMBYGCgmSJomT8ixkAQEMCDEwMDI0Njc2MRkwFwYDVQQDDBBTYXZvbGFp bmVuIFRlZW11MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAshEsmw6Yiz6XWX26oF+I s5fsfE1OfCjOelclmtqCiIgXND5klkNOBs2d4ZGzgD9mN+XnTZnOTh249c2WxPBugf12DCcDmBAJ gL+VuWUJVBTE5NRchm/O8nZnZsRFst+gAC9/Juykh4+EYewZ7QbpnlwW7hNpj8eH+rMr+OZHKzdp KTftgVjmuF4JJ/cPMQUjL8SuGj+zBW6IWPOZdqkEMtf7Pr8kkYbZsh0SgJ0ceRHZ7Uc06mB/y+C1 UnJPxehTTdu8tpCjdzXgBw/H2uuW1J3qdHbCfbuDILql8V8RiZKubcZLhdsD3Jvj8qK0DGWBJa6x p90q5p3pLE8LvAeCgQIDAQABo4HQMIHNMA4GA1UdDwEB/wQEAwIEMDAfBgNVHSMEGDAWgBSnJLA+ xYPvBA5QdksYMufKVtEsujAZBgNVHSAEEjAQMA4GDCsGAQQBXgExBgEHAzA5BgNVHR8EMjAwMC6g LKAqhihodHRwOi8vY3JsLm5va2lhLmNvbS9Ob2tpYSUyMEJJJTIwQ0EuY3JsMCUGA1UdEQQeMByB GnRlZW11LnNhdm9sYWluZW5Abm9raWEuY29tMB0GA1UdDgQWBBQTRzvZsgmQrAGCeuzdHTGAC6Jg UzANBgkqhkiG9w0BAQUFAAOCAQEACmPVsdi07pjK5gDa+W5JlE2C74kVVsB8alBqfioYeR5At2FG B7sua4Dz5H7TJMpZ1jYFeI+zjexD5f+beY2IlV15lMoWD+5e38QlLYjwfe2LAyvdzBKXW0e0U6Bt p78ft4gyVak1X+Db+ebR+FNHUOMNhm+yK3w9sy5ZQzBFusIx4OgxGvcZhyhmd9WjipSTalgPwgqV Ju2aPADCG++OEXmgEWRLsR4yNopkgK4ftVqrN5uUtLs83qdeXTRcNRiET1IOx5zmYFZ6q3gjKIx5 iyuxcDeYas93vVHUcaRRYpsoby5CHq7Z/j/TQhtqO/knWuxLFFiCUgdGKMKrRkg29DCCBAowggLy oAMCAQICEQCBvi+p+bA/dBtBtybwA6YYMA0GCSqGSIb3DQEBBQUAMDMxCzAJBgNVBAYTAkZJMQ4w DAYDVQQKEwVOb2tpYTEUMBIGA1UEAxMLTm9raWEgQkkgQ0EwHhcNMTEwOTA2MDU1MDM0WhcNMTMw OTA1MDU1MDM0WjBWMQ4wDAYDVQQKDAVOb2tpYTEPMA0GA1UECwwGUGVvcGxlMRgwFgYKCZImiZPy LGQBAQwIMTAwMjQ2NzYxGTAXBgNVBAMMEFNhdm9sYWluZW4gVGVlbXUwggEiMA0GCSqGSIb3DQEB AQUAA4IBDwAwggEKAoIBAQDFPmbRVwuo52v+h6xnQUqokAx2xsHjmPBniEkzgtgBNJsFi838ATEg 1zsx+VotoJg7hMijcrQfpTAgW6gpLGnlmw5QQswrNK1zleOHb4pA5JguU3WhVKFkAH/6/2EU2k/9 m8Pb/gwP55cYg80R6fRmbdsWKhseXF/1isW/rJcWLmIYDg/rXfo3ixqtT9MroAMiuoXnb0ij1L2d Jj64LDp3Ld8Jo0qZzk3Fj4apo8PBd8eAH6HloVBJkxQcwAnv561A+Xi1GHZ2mafRYJGO+1uBDwyd g/8ybEXXA4MKo8lPKjBebYBUFvz80DBA/Lq74UysXkG23BSulcG4xQSYGlyzAgMBAAGjgfUwgfIw HwYDVR0jBBgwFoAUpySwPsWD7wQOUHZLGDLnylbRLLowGQYDVR0gBBIwEDAOBgwrBgEEAV4BMQYB BgQwOQYDVR0fBDIwMDAuoCygKoYoaHR0cDovL2NybC5ub2tpYS5jb20vTm9raWElMjBCSSUyMENB LmNybDAjBgNVHSUEHDAaBggrBgEFBQcDAgYEVR0lAAYIKwYBBQUHAwQwDgYDVR0PAQH/BAQDAgeA MCUGA1UdEQQeMByBGnRlZW11LnNhdm9sYWluZW5Abm9raWEuY29tMB0GA1UdDgQWBBTGhbTJF0EX iagjymQo6GIuSQeRVDANBgkqhkiG9w0BAQUFAAOCAQEAqai6TxZ/BlMHZIhJNPriBPXkQhUlBkGA buJZ5sVm1HIQhWN8elZKjjJdHi1qWEKhMg7yHjEMZsyV8XAZzK0UnOqkpUnt+jnVkNZ9O7/jRtyK f4WUtq5jErc8Hlv4bbGFRHk1T7AuLLE52r1lYOdmoibnQp03QtlDvHUNa68G7jvzThJhieB7U1xh vH3yy0ktaVnWEgAylqf9yIUFjnqau5R6cE1Xo57IYPk/KitX0YF+OigEI/bOQVMi+fze93ZsAOJv /z6g/NGemvUgl5YSdX0uPQK6kEHf/sp/nZyUWWQ7OjtVSqkq2YuYEueQFxTfafl+78GWqgm6W/Bl 32laYzGCAuswggLnAgEBMEgwMzELMAkGA1UEBhMCRkkxDjAMBgNVBAoTBU5va2lhMRQwEgYDVQQD EwtOb2tpYSBCSSBDQQIRAIG+L6n5sD90G0G3JvADphgwCQYFKw4DAhoFAKCCAXgwGAYJKoZIhvcN AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwOTIzMDgzNzUyWjAjBgkqhkiG9w0B CQQxFgQUzfsY74xRv5OjVrtEQGICVXNj/y0wVgYJKwYBBAGCNxAEMUkwRzAzMQswCQYDVQQGEwJG STEOMAwGA1UEChMFTm9raWExFDASBgNVBAMTC05va2lhIEJJIENBAhAwflqlqTyUTLouYuUuwnLx MFgGCyqGSIb3DQEJEAILMUmgRzAzMQswCQYDVQQGEwJGSTEOMAwGA1UEChMFTm9raWExFDASBgNV BAMTC05va2lhIEJJIENBAhAwflqlqTyUTLouYuUuwnLxMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZI hvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC AgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMA0GCSqGSIb3DQEBAQUABIIBAE8YUPeWdIBr2GxU5wuJ xYO+tZ218Tuga5vvQBgQIAkv0B75M8ZJ3RPZQV7zzfC6Hf6jnq5KJcJZvQaWRfpllsN0OMERb7kZ nWl4LAc/It3v5vdlH3QwVhnk6SEI+ffHJksYkAdZPxevnzs9HbsD6iavozYKr2Z1ZVUOVyQl77Di 2BOR4Dk1WeXIQMV8orj11GgyfDoLrSM5sQ37ujqlAhTaoHygT1fsxLk2Ms50xyAv5KYZWYKH1MEe h9nS0h5GqzHDMXH3jEnQt6Md3qClcg3u5NA6mapHY/0IFMLM61Vv/63R0545luHGDcaPnHR7kEgq WHESUqynF2vroOQekqgAAAAAAAA= ------=_NextPart_000_01C1_01CC79E5.3A6C9CD0-- From rgm@labs.htt-consult.com Fri Sep 23 10:33:23 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D78BE21F8CEB for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 10:33:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.58 X-Spam-Level: X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZif60tADUwz for <6lowpan@ietfa.amsl.com>; Fri, 23 Sep 2011 10:33:23 -0700 (PDT) Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id 5C04121F8CE9 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 10:33:23 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id 0AB3E62A87 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 17:35:37 +0000 (UTC) X-Virus-Scanned: amavisd-new at localhost Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sc647NjyhkB1 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 13:35:26 -0400 (EDT) Received: from nc2400.htt-consult.com (nc2400.htt-consult.com [208.83.67.155]) (Authenticated sender: rgm@labs.htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPA id CB73762A76 for <6lowpan@ietf.org>; Fri, 23 Sep 2011 13:35:26 -0400 (EDT) Message-ID: <4E7CC35E.10805@labs.htt-consult.com> Date: Fri, 23 Sep 2011 13:35:26 -0400 From: Robert Moskowitz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Thunderbird/3.1.12 MIME-Version: 1.0 To: 6lowpan <6lowpan@ietf.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [6lowpan] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 17:33:24 -0000 This week the PAR for KMP passed within 802.15: https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-protocol-par.doc https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc In the PAR we are requesting the creation of a Recommended Practice that will be identified as 802.15.8. Next step is to get IEEE 802 approval which will be at the Atlanta meeting week prior to IETF. For all the current documents for the KMPIG: https://mentor.ieee.org/802.15/documents?is_group=0kmp In particular https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.ppt GIves the latest thoughts on how the shim will work and how the document will be structured. As for 6lowpan and pre-802.15.4e devices, I will work on and Internet Draft and welcome any partner authors. From johanna.1.nieminen@nokia.com Mon Sep 26 02:41:58 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94EC821F84F9 for <6lowpan@ietfa.amsl.com>; Mon, 26 Sep 2011 02:41:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.849 X-Spam-Level: X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJMvGU0pNsml for <6lowpan@ietfa.amsl.com>; Mon, 26 Sep 2011 02:41:57 -0700 (PDT) Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id BCE6821F84B5 for <6lowpan@ietf.org>; Mon, 26 Sep 2011 02:41:56 -0700 (PDT) Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da02.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p8Q9i0eD006081; Mon, 26 Sep 2011 12:44:37 +0300 Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 26 Sep 2011 12:43:33 +0300 Received: from 008-AM1MMR1-003.mgdnok.nokia.com (65.54.30.58) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 26 Sep 2011 11:43:33 +0200 Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.167]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.01.0339.002; Mon, 26 Sep 2011 11:43:32 +0200 From: To: Thread-Topic: [6lowpan] Latest version of IPv6 over BT-LE draft Thread-Index: Acxj7bwqMeJce9kfQvayEwuvlbMVbANK7JmAAAfCxjABYqOPgAFbTYNA Date: Mon, 26 Sep 2011 09:43:32 +0000 Message-ID: <5FA713B99ACAA6478C065A155E206B460A510D@008-AM1MPN1-043.mgdnok.nokia.com> References: <5FA713B99ACAA6478C065A155E206B4608E013@008-AM1MPN1-043.mgdnok.nokia.com> <20110912085852.GA39547@elstar.local> <5FA713B99ACAA6478C065A155E206B4609483E@008-AM1MPN1-043.mgdnok.nokia.com> <20110919135531.GA4103@elstar.local> In-Reply-To: <20110919135531.GA4103@elstar.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.21.23.136] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 26 Sep 2011 09:43:33.0756 (UTC) FILETIME=[C1BCEBC0:01CC7C30] X-Nokia-AV: Clean Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Sep 2011 09:41:58 -0000 Hi, We have agreed that BT 4.0 will be included in the list of normative refere= nces even though all features are not required.=20 Johanna >-----Original Message----- >From: ext Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs- >university.de] >Sent: 19 September, 2011 16:56 >To: Nieminen Johanna.1 (Nokia-NRC/Helsinki) >Cc: 6lowpan@ietf.org >Subject: Re: [6lowpan] Latest version of IPv6 over BT-LE draft > >On Mon, Sep 12, 2011 at 10:41:42AM +0000, johanna.1.nieminen@nokia.com >wrote: >> Hi, >> >> That specification is very broad and not necessarily all features are >normative. >> > >One can discuss whether its normative or not, but having no reference at a= ll to >BT 4.0 in the references section seems somewhat odd as far as I am >concerned. > >/js > >-- >Juergen Schoenwaelder Jacobs University Bremen gGmbH >Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany >Fax: +49 421 200 3103 From czhou@cisco.com Tue Sep 27 20:51:44 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0D821F8CBD for <6lowpan@ietfa.amsl.com>; Tue, 27 Sep 2011 20:51:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.832 X-Spam-Level: X-Spam-Status: No, score=-0.832 tagged_above=-999 required=5 tests=[AWL=1.766, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LuSIYGwkt6es for <6lowpan@ietfa.amsl.com>; Tue, 27 Sep 2011 20:51:43 -0700 (PDT) Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id AA89521F8CAD for <6lowpan@ietf.org>; Tue, 27 Sep 2011 20:51:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=czhou@cisco.com; l=5696; q=dns/txt; s=iport; t=1317182071; x=1318391671; h=mime-version:subject:date:message-id:from:to; bh=d6yPQlkRB0FsbELITuttKYWXx8vyFkYEDkXlB3NbLfs=; b=SPZvX9ERWyU1lK92YW2pcHiL7Wr9WKcMbJmk2lYe2HAOTGk8LHWA6jb5 jYC2DjALqQWKPr6dMTNAmPsavWgUkw+1cp6Wc+MqAMfHE/TrIQ8LJAQpQ VpKHtWagEvhc9lHo1JmCjjYnml9atOeMH1FEFaIIJvr6DNMgSO/1TWDbC Q=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArIIAIiZgk6rRDoI/2dsb2JhbABBgk2Wc4cvhxV4gVUBAQMSAQkRAzgjASoGGAdXAQQbGqEHgSYBnh6GK2AEh3KRC4wn X-IronPort-AV: E=Sophos;i="4.68,453,1312156800"; d="scan'208,217";a="4696945" Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 28 Sep 2011 03:54:31 +0000 Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p8S3sUwU030705 for <6lowpan@ietf.org>; Wed, 28 Sep 2011 03:54:30 GMT Received: from xmb-rcd-208.cisco.com ([72.163.62.215]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 27 Sep 2011 22:54:30 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 x-cr-hashedpuzzle: A3W9 A5Ly Bkmu CYDi DNYT EdTZ E6aK FGq2 Fa8t Fxnh H1WD ISC6 Is/C Iuf7 Jfz2 KP06; 1; NgBsAG8AdwBwAGEAbgBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {373D9DA7-865F-499F-A711-8EBBAC9B30BE}; YwB6AGgAbwB1AEAAYwBpAHMAYwBvAC4AYwBvAG0A; Wed, 28 Sep 2011 03:54:27 GMT; SABvAHcAIAB0AG8AIABhAHMAawAgAGEAIABwAHIAZQBzAGUAbgB0AGEAdABpAG8AbgAgAHQAaQBtAGUAIABzAGwAbwB0ACAAaQBuACAAYwBvAG0AaQBuAGcAIABJAEUAVABGACAAYwBvAG4AZgAgAGkAbgAgAFQAYQBpAHAAZQBpAD8A MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CC7D92.5323DBD9" x-cr-puzzleid: {373D9DA7-865F-499F-A711-8EBBAC9B30BE} Content-class: urn:content-classes:message Date: Tue, 27 Sep 2011 22:54:27 -0500 Message-ID: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to ask a presentation time slot in coming IETF conf in Taipei? Thread-Index: Acx9klG9HdPOyiBPS3SkHn75FJoI4Q== From: "Chao Zhou (czhou)" To: <6lowpan@ietf.org> X-OriginalArrivalTime: 28 Sep 2011 03:54:30.0471 (UTC) FILETIME=[5364BD70:01CC7D92] Subject: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 03:51:44 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CC7D92.5323DBD9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, there =20 We're planning to give a presentation in 6lowpan area in next IETF conference but couldn't find our schedule or time slot. How to apply for it? Can anyone give some suggestion? =20 Thanks. -Chao ------_=_NextPart_001_01CC7D92.5323DBD9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi, there

 

We’re planning to give a presentation in = 6lowpan area in next IETF conference but couldn’t find our schedule or time = slot. How to apply for it? Can anyone give some suggestion?

 

Thanks.

-Chao

------_=_NextPart_001_01CC7D92.5323DBD9-- From cabo@tzi.org Wed Sep 28 04:15:07 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CC421F8BE7 for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 04:15:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.582 X-Spam-Level: X-Spam-Status: No, score=-106.582 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAUAsYwuWJH8 for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 04:15:06 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 7E80321F8BBF for <6lowpan@ietf.org>; Wed, 28 Sep 2011 04:15:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p8SBHfYH027944; Wed, 28 Sep 2011 13:17:41 +0200 (CEST) Received: from [10.0.1.3] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 7C05A23F; Wed, 28 Sep 2011 13:17:41 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=windows-1252 From: Carsten Bormann In-Reply-To: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> Date: Wed, 28 Sep 2011 13:17:40 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> To: "Chao Zhou (czhou)" X-Mailer: Apple Mail (2.1244.3) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 11:15:07 -0000 > We=92re planning to give a presentation in 6lowpan area in next IETF = conference but couldn=92t find our schedule or time slot. How to apply = for it? Can anyone give some suggestion? Hi Chao, the 6LoWPAN WG is not meeting in Taipei. There also is, in general, no plan to take on new work within this = particular WG. This, of course, does not mean that there won't be additional work in = this space =97 quite to the contrary. Just not likely in the existing = organizational context of this WG. As you know, the right way to bring an idea to the IETF is to write an = Internet-Draft. (Even if there were a 6LoWPAN slot in Taipei, the chairs would generally = require an Internet-Draft for a meeting slot.) Once we have that, we = may be able to find a meeting of a different WG that might provide a way = to discuss the work. Or we might be able to progress it outside of = face-to-face meetings, as we are doing with the Bluetooth-Low-Energy = (BT-LE) work right now. So, in any case, my recommendation is to write a draft, and if that = creates interest within the purview of the 6LoWPAN WG, we will find a = way forward. Gr=FC=DFe, Carsten From rgm@labs.htt-consult.com Wed Sep 28 07:28:33 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBB221F8C5B for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 07:28:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.581 X-Spam-Level: X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNBmMic70E4e for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 07:28:32 -0700 (PDT) Received: from klovia.htt-consult.com (klovia.htt-consult.com [208.83.67.149]) by ietfa.amsl.com (Postfix) with ESMTP id A7B7321F8C0E for <6lowpan@ietf.org>; Wed, 28 Sep 2011 07:28:32 -0700 (PDT) Received: from localhost (unknown [127.0.0.1]) by klovia.htt-consult.com (Postfix) with ESMTP id A593662B7A; Wed, 28 Sep 2011 14:30:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at localhost Received: from klovia.htt-consult.com ([127.0.0.1]) by localhost (klovia.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RevJiibOMKca; Wed, 28 Sep 2011 10:30:38 -0400 (EDT) Received: from nc2400.htt-consult.com (nc2400.htt-consult.com [208.83.67.155]) (Authenticated sender: rgm@labs.htt-consult.com) by klovia.htt-consult.com (Postfix) with ESMTPA id C136B62ABA; Wed, 28 Sep 2011 10:30:38 -0400 (EDT) Message-ID: <4E832F8E.1050700@labs.htt-consult.com> Date: Wed, 28 Sep 2011 10:30:38 -0400 From: Robert Moskowitz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.20) Gecko/20110817 Fedora/3.1.12-1.fc14 Thunderbird/3.1.12 MIME-Version: 1.0 To: Carsten Bormann References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> In-Reply-To: <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> Content-Type: multipart/alternative; boundary="------------030004060208070104000208" Cc: "Chao Zhou \(czhou\)" , 6lowpan@ietf.org Subject: [6lowpan] 802.15 KMP -- was: Re: How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 14:28:34 -0000 This is a multi-part message in MIME format. --------------030004060208070104000208 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 09/28/2011 07:17 AM, Carsten Bormann wrote: >> We’re planning to give a presentation in 6lowpan area in next IETF conference but couldn’t find our schedule or time slot. How to apply for it? Can anyone give some suggestion? > Hi Chao, > > the 6LoWPAN WG is not meeting in Taipei. > There also is, in general, no plan to take on new work within this particular WG. > > This, of course, does not mean that there won't be additional work in this space — quite to the contrary. Just not likely in the existing organizational context of this WG. > > As you know, the right way to bring an idea to the IETF is to write an Internet-Draft. On a related note, a PAR for adding Key Management to 802.15 is advancing and we expect its approval at the November 802 meeting (the week before IETF). The work for 15.4 will rely on the Information Element and Multipurpose frame of 15.4e. However, 6lowpan COULD allocate a frameID (? or whatever the RFC calls the data header field) for KMP and we could have a simple method mirroring the 4e model but for 6lowpan pre-4e. I was asked about this in Quebec, and I DO plan on writing an ID for this. I could have a rough cut for November, but it will be tracking the 802.15 work (which btw most likely will be 802.15.8 as it will apply to 15.6 and 15.7 as well) so it will take a bit to finish. What value would MAC KMP serve IETF? Keying for the MAC to secure Neighbor discovery. Security for roll. Its value for core may be minimal: for core over single hop only or one KMP for all levels (MAC, IP, Session (DTLS)). So this will be available for 6lowpan discussions, but probably you will end up waiting until Paris for a full presentation. Or come to Jacksonville in January to work it out in 802.15! BTW, I need an editor. I have an interested, experienced 802.15 editor that needs funding. So either someone to help with the funding of an experienced editor or someone to step forward to take on the editing. I do NOT see this (802.15.8) to be a major document. > (Even if there were a 6LoWPAN slot in Taipei, the chairs would generally require an Internet-Draft for a meeting slot.) Once we have that, we may be able to find a meeting of a different WG that might provide a way to discuss the work. Or we might be able to progress it outside of face-to-face meetings, as we are doing with the Bluetooth-Low-Energy (BT-LE) work right now. > > So, in any case, my recommendation is to write a draft, and if that creates interest within the purview of the 6LoWPAN WG, we will find a way forward. > > Grüße, Carsten > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan > -- Robert Moskowitz Senior Technical Advisor Security & Standards Verizon Business Systems C:248-219-2059 F:248-968-2824 E:robert.moskowitz@verizonbusiness.com There's no limit to what can be accomplished if it doesn't matter who gets the credit --------------030004060208070104000208 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit On 09/28/2011 07:17 AM, Carsten Bormann wrote: 
We’re planning to give a presentation in 6lowpan area in next IETF conference but couldn’t find our schedule or time slot. How to apply for it? Can anyone give some suggestion?

Hi Chao,

the 6LoWPAN WG is not meeting in Taipei.
There also is, in general, no plan to take on new work within this particular WG.

This, of course, does not mean that there won't be additional work in this space — quite to the contrary.  Just not likely in the existing organizational context of this WG.

As you know, the right way to bring an idea to the IETF is to write an Internet-Draft.

On a related note, a PAR for adding Key Management to 802.15 is advancing and we expect its approval at the November 802 meeting (the week before IETF).  The work for 15.4 will rely on the Information Element and Multipurpose frame of 15.4e.  However, 6lowpan COULD allocate a frameID (? or whatever the RFC calls the data header field) for KMP and we could have a simple method mirroring the 4e model but for 6lowpan pre-4e.

I was asked about this in Quebec, and I DO plan on writing an ID for this.  I could have a rough cut for November, but it will be tracking the 802.15 work (which btw most likely will be 802.15.8 as it will apply to 15.6 and 15.7 as well) so it will take a bit to finish.

What value would MAC KMP serve IETF?  Keying for the MAC to secure Neighbor discovery.  Security for roll.  Its value for core may be minimal:  for core over single hop only or one KMP for all levels (MAC, IP, Session (DTLS)).

So this will be available for 6lowpan discussions, but probably you will end up waiting until Paris for a full presentation.

Or come to Jacksonville in January to work it out in 802.15!

BTW, I need an editor.  I have an interested, experienced 802.15 editor that needs funding.  So either someone to help with the funding of an experienced editor or someone to step forward to take on the editing.  I do NOT see this (802.15.8) to be a major document.

(Even if there were a 6LoWPAN slot in Taipei, the chairs would generally require an Internet-Draft for a meeting slot.)  Once we have that, we may be able to find a meeting of a different WG that might provide a way to discuss the work.  Or we might be able to progress it outside of face-to-face meetings, as we are doing with the Bluetooth-Low-Energy (BT-LE) work right now.

So, in any case, my recommendation is to write a draft, and if that creates interest within the purview of the 6LoWPAN WG, we will find a way forward.

Grüße, Carsten

_______________________________________________
6lowpan mailing list
6lowpan@ietf.org
https://www.ietf.org/mailman/listinfo/6lowpan

--
Standard Robert Moskowitz
Senior Technical Advisor
Security & Standards
Verizon Business Systems
C:      248-219-2059
F:      248-968-2824
E:      robert.moskowitz@verizonbusiness.com

There's no limit to what can be accomplished if it doesn't matter who gets the credit
--------------030004060208070104000208-- From czhou@cisco.com Wed Sep 28 11:22:35 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24E91F0CCE for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 11:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.421 X-Spam-Level: X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[AWL=1.178, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRIPDa24vwDI for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 11:22:35 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id CF2331F0CCD for <6lowpan@ietf.org>; Wed, 28 Sep 2011 11:22:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=czhou@cisco.com; l=1783; q=dns/txt; s=iport; t=1317234322; x=1318443922; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=gg/SXa0KMD9Q15gXftweeeiYNOxTMlcILBP+/2ups5Y=; b=iahXbHXd5oXCUYUa4Vyz611ycvV/piRdECGZdPhS6904w8y3bqtZeZCA 1qmRlQ+FSwCuWbJKXlMvUrRpig4cxe019YmLVjr8vfEshTxQKlTR6QKpQ IS7gK2VgmcV39lW5YHnpJXdLvCJBQUu3aPW7HvqZTl6NGypYRTQFqMzW7 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap8AANplg06tJXHB/2dsb2JhbABCmQqPAniBUwEBAQECARIBHTgRBQcEAgEIDgMEAQELBhcBBgFFCQgBAQQTCBqHVpoUAZ4nhithBIdCMJEOjCg X-IronPort-AV: E=Sophos;i="4.68,456,1312156800"; d="scan'208";a="24693086" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-7.cisco.com with ESMTP; 28 Sep 2011 18:25:21 +0000 Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id p8SIPLXR030539; Wed, 28 Sep 2011 18:25:21 GMT Received: from xmb-rcd-208.cisco.com ([72.163.62.215]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 28 Sep 2011 13:25:21 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Sep 2011 13:25:20 -0500 Message-ID: <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com> In-Reply-To: <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? Thread-Index: Acx90EKpf/MoYW4FQY+NfYD+y0/NNwAO01bg References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> From: "Chao Zhou (czhou)" To: "Carsten Bormann" X-OriginalArrivalTime: 28 Sep 2011 18:25:21.0877 (UTC) FILETIME=[FBA89050:01CC7E0B] Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 18:22:35 -0000 Hi Carsten, Thank you for your info. We do have a draft which is = "draft-wang-6lowpan-scheduling-requirements-00". We're hoping to bring = interest in this area through the presentation in the coming conference. = We're planning to submit the second version soon. In this case, is that = possible to make a slot? Thanks. -Chao -----Original Message----- From: Carsten Bormann [mailto:cabo@tzi.org]=20 Sent: Wednesday, September 28, 2011 7:18 PM To: Chao Zhou (czhou) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming = IETF conf in Taipei? > We're planning to give a presentation in 6lowpan area in next IETF = conference but couldn't find our schedule or time slot. How to apply for = it? Can anyone give some suggestion? Hi Chao, the 6LoWPAN WG is not meeting in Taipei. There also is, in general, no plan to take on new work within this = particular WG. This, of course, does not mean that there won't be additional work in = this space - quite to the contrary. Just not likely in the existing = organizational context of this WG. As you know, the right way to bring an idea to the IETF is to write an = Internet-Draft. (Even if there were a 6LoWPAN slot in Taipei, the chairs would generally = require an Internet-Draft for a meeting slot.) Once we have that, we = may be able to find a meeting of a different WG that might provide a way = to discuss the work. Or we might be able to progress it outside of = face-to-face meetings, as we are doing with the Bluetooth-Low-Energy = (BT-LE) work right now. So, in any case, my recommendation is to write a draft, and if that = creates interest within the purview of the 6LoWPAN WG, we will find a = way forward. Gr=FC=DFe, Carsten From alper.yegin@yegin.org Wed Sep 28 11:33:45 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6615A21F8D50; Wed, 28 Sep 2011 11:33:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cx-D79SZ5Qu4; Wed, 28 Sep 2011 11:33:44 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 9370321F8D39; Wed, 28 Sep 2011 11:33:44 -0700 (PDT) Received: from [192.168.2.109] (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0M3z0U-1QquD81qCI-00rlIO; Wed, 28 Sep 2011 14:36:32 -0400 Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Alper Yegin In-Reply-To: <4E7CC30C.10305@htt-consult.com> Date: Wed, 28 Sep 2011 21:36:27 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> References: <4E7CC30C.10305@htt-consult.com> To: Robert Moskowitz X-Mailer: Apple Mail (2.1244.3) X-Provags-ID: V02:K0:rS3d/j+wg8RFC4PS5+afQy4uxcdI7CTPdzueABIvEzW wj08MUGKxc+kiuUsbaUfzr1tMwCYp2yOE2HIk/iioxRNHr1jBv fbdkYQhtl1vHAim3isFnrsb2N7wfLbq6gEzZOsNABPx61RKGxB whc/E5ZB5C/6vGKv7Zs26x1iDDehmPa70nmi96hCwPVlofwuEY kIUVmNUmBpzhycO63hRU1kb1rGFOH2Qi14sStyXKBBpEKFQWdp sS6NTcOMxAVpwVRu4OHyf/PH+I9rYoa+Rx5wRkP3DShV6DxMp+ j+HfI4xO0LUXK+30aSL//s/xvnR1DFpnHB4jDjoQHQ/wvXwxRb TiViEOh3nOmKY9uKktDetuvj+C5NaII/7pFHuqD6l8lmTEkygm dLGZv7uXtwzaw== Cc: 6lowpan@ietf.org, saag@ietf.org Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 18:33:45 -0000 Hi Bob, As you know, Zigbee Alliance has already adopted EAP/PANA for network = access authentication and key agreement for Smart Energy Profile 2.0. Is the problem you are seeking to solve the same problem, or a different = one? Thanks. Alper On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote: > This week the PAR for KMP passed within 802.15: >=20 > = https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-pr= otocol-par.doc > = https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc >=20 > In the PAR we are requesting the creation of a Recommended Practice = that will be identified as 802.15.8. >=20 > Next step is to get IEEE 802 approval which will be at the Atlanta = meeting week prior to IETF. >=20 > For all the current documents for the KMPIG: >=20 > https://mentor.ieee.org/802.15/documents?is_group=3D0kmp >=20 > In particular >=20 > = https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.pp= t >=20 > GIves the latest thoughts on how the shim will work and how the = document will be structured. >=20 > _______________________________________________ > saag mailing list > saag@ietf.org > https://www.ietf.org/mailman/listinfo/saag From cabo@tzi.org Wed Sep 28 12:31:25 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9735E1F0CDA for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 12:31:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.249 X-Spam-Level: X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocNov2SmHs0z for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 12:31:25 -0700 (PDT) Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id A1DBA1F0CF8 for <6lowpan@ietf.org>; Wed, 28 Sep 2011 12:31:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p8SJY3xv005578; Wed, 28 Sep 2011 21:34:03 +0200 (CEST) Received: from [192.168.217.112] (p5489B8D1.dip.t-dialin.net [84.137.184.209]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2A0994AF; Wed, 28 Sep 2011 21:34:03 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: Carsten Bormann In-Reply-To: <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com> Date: Wed, 28 Sep 2011 21:34:02 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <3D95370E-8D44-4A79-AF0E-80FE4905E163@tzi.org> References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com> To: "Chao Zhou (czhou)" X-Mailer: Apple Mail (2.1244.3) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2011 19:31:25 -0000 On Sep 28, 2011, at 20:25, Chao Zhou (czhou) wrote: > Thank you for your info. We do have a draft which is = "draft-wang-6lowpan-scheduling-requirements-00". We're hoping to bring = interest in this area through the presentation in the coming conference. = We're planning to submit the second version soon. In this case, is that = possible to make a slot? Chao, thanks for the pointer. Leafing through this draft, I have two questions: 1) What is the ultimate disposition you envision for this document? What kind of standards activity will be influenced by this set of = requirements? Or, more specifically, what is the IETF activity you envision that would = have this document as its requirements set? 2) What would be the objective of a face-to-face discussion at this = point? (We don't schedule meeting slots to present things, but to achieve = something.) Given that I'm not aware of an existing IETF activity where this = document would fit, a natural first step would be to first gather = interest in setting up a new activity and then start work on the = pertinent requirements document. A random observation about the I-D:=20 I'm not sure about the purpose of the references. Gruesse, Carsten From ben@blindcreek.com Wed Sep 28 18:16:53 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A7A21F8D5D for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 18:16:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obhmZsDRoIke for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 18:16:52 -0700 (PDT) Received: from wilson.nswebhost.com (wilson.nswebhost.com [209.217.228.58]) by ietfa.amsl.com (Postfix) with ESMTP id EF71721F8B9A for <6lowpan@ietf.org>; Wed, 28 Sep 2011 18:16:47 -0700 (PDT) Received: from [64.74.213.174] (port=52300 helo=[192.168.250.11]) by wilson.nswebhost.com with esmtpa (Exim 4.69) (envelope-from ) id 1R95Hf-0008LJ-P6 for 6lowpan@ietf.org; Wed, 28 Sep 2011 20:19:32 -0500 Message-ID: <4E83C7A6.4020008@blindcreek.com> Date: Wed, 28 Sep 2011 18:19:34 -0700 From: "Benjamin A. Rolfe" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 To: 6lowpan@ietf.org References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> In-Reply-To: <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wilson.nswebhost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - blindcreek.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2011 01:16:53 -0000 There is an obvious difference in scope: The scope of the ZigBee SEP profile is specifically Demand Response and Load Management applications. ZigBee uses IEEE P802.15.4-2003. The scope of the referenced PAR includes all current members of the 802.15 family of standards, which includes 5 distinct MAC and PHY standards (soon to be 6). I'm sure Bob can elaborate further. Hope that helps. Regards -Ben > Hi Bob, > > As you know, Zigbee Alliance has already adopted EAP/PANA for network access authentication and key agreement for Smart Energy Profile 2.0. > > Is the problem you are seeking to solve the same problem, or a different one? > > Thanks. > > Alper > > > > > > On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote: > >> This week the PAR for KMP passed within 802.15: >> >> https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-protocol-par.doc >> https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc >> >> In the PAR we are requesting the creation of a Recommended Practice that will be identified as 802.15.8. >> >> Next step is to get IEEE 802 approval which will be at the Atlanta meeting week prior to IETF. >> >> For all the current documents for the KMPIG: >> >> https://mentor.ieee.org/802.15/documents?is_group=0kmp >> >> In particular >> >> https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.ppt >> >> GIves the latest thoughts on how the shim will work and how the document will be structured. >> >> _______________________________________________ >> saag mailing list >> saag@ietf.org >> https://www.ietf.org/mailman/listinfo/saag > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan > From czhou@cisco.com Wed Sep 28 21:04:01 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F78F21F8C3E for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 21:04:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.716 X-Spam-Level: X-Spam-Status: No, score=-1.716 tagged_above=-999 required=5 tests=[AWL=0.883, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwZrMP-pg4tY for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 21:04:00 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 292E121F8C3D for <6lowpan@ietf.org>; Wed, 28 Sep 2011 21:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=czhou@cisco.com; l=1973; q=dns/txt; s=iport; t=1317269210; x=1318478810; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=h+oQ5Blbmycs4GYbEeGVpJe9sBN2PgxqgPwzqD4vcsY=; b=dCd21772Kjl0iXYuWGU0dIURafoJkT0O2pY/s2bpfg7QcGpl2xzvuuPK nioR7jAFBs/sFm35cjwQ1ky4lL7bnLTXTHlNapKf6Ps8YEf7gDWXB68OB a4TMeii2SNST41IQc6mR5f1DoVViQSjqKc7ecmXZHjY/f1FQ9ycHkvnF0 g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4AADjug06tJXG9/2dsb2JhbABBmQqOfXiBUwEBAQECARIBHQouEQUHBAIBCA4DBAEBCwYXAQYBRQkIAQEEEwgah1aZZAGeKoYrYQSHcpEQjCs X-IronPort-AV: E=Sophos;i="4.68,459,1312156800"; d="scan'208";a="24783731" Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 29 Sep 2011 04:06:47 +0000 Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p8T46lfw010292; Thu, 29 Sep 2011 04:06:47 GMT Received: from xmb-rcd-208.cisco.com ([72.163.62.215]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 28 Sep 2011 23:06:47 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Sep 2011 23:06:45 -0500 Message-ID: <01A021EBB03D534AB5CE4B620B5F82D10443C6B3@XMB-RCD-208.cisco.com> In-Reply-To: <3D95370E-8D44-4A79-AF0E-80FE4905E163@tzi.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? Thread-Index: Acx+FZn9UcHYAxA/T/qo0Mas+I6W2QAReFcw References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com> <3D95370E-8D44-4A79-AF0E-80FE4905E163@tzi.org> From: "Chao Zhou (czhou)" To: "Carsten Bormann" X-OriginalArrivalTime: 29 Sep 2011 04:06:47.0461 (UTC) FILETIME=[35163D50:01CC7E5D] Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2011 04:04:01 -0000 Hi Carsten, What we're trying to explore is the deployment possibility of 6lowpan in industrial control/monitoring environment. There are specific requirements in the industrial control field, like, determinism, real-time, reliability, etc. This is the first document we submit and hope to bring out people's interest and get a general idea of people's perspective. We're planning to submit more follow-on drafts for some detailed discussion. Hope this explains. Thanks. -Chao -----Original Message----- From: Carsten Bormann [mailto:cabo@tzi.org]=20 Sent: Thursday, September 29, 2011 3:34 AM To: Chao Zhou (czhou) Cc: 6lowpan@ietf.org Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei? On Sep 28, 2011, at 20:25, Chao Zhou (czhou) wrote: > Thank you for your info. We do have a draft which is "draft-wang-6lowpan-scheduling-requirements-00". We're hoping to bring interest in this area through the presentation in the coming conference. We're planning to submit the second version soon. In this case, is that possible to make a slot? Chao, thanks for the pointer. Leafing through this draft, I have two questions: 1) What is the ultimate disposition you envision for this document? What kind of standards activity will be influenced by this set of requirements? Or, more specifically, what is the IETF activity you envision that would have this document as its requirements set? 2) What would be the objective of a face-to-face discussion at this point? (We don't schedule meeting slots to present things, but to achieve something.) Given that I'm not aware of an existing IETF activity where this document would fit, a natural first step would be to first gather interest in setting up a new activity and then start work on the pertinent requirements document. A random observation about the I-D:=20 I'm not sure about the purpose of the references. Gruesse, Carsten From alper.yegin@yegin.org Thu Sep 29 12:37:42 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7274F1F0C4F; Thu, 29 Sep 2011 12:37:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjJWwlSpz7df; Thu, 29 Sep 2011 12:37:41 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 851341F0C4E; Thu, 29 Sep 2011 12:37:41 -0700 (PDT) Received: from [192.168.2.109] (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LqhqM-1Qezja2viM-00eRy0; Thu, 29 Sep 2011 15:40:32 -0400 Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Alper Yegin In-Reply-To: <4E83C7A6.4020008@blindcreek.com> Date: Thu, 29 Sep 2011 22:40:27 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <709DC625-A433-4DDC-9505-D9DD7180B93E@yegin.org> References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> <4E83C7A6.4020008@blindcreek.com> To: Benjamin A. Rolfe X-Mailer: Apple Mail (2.1244.3) X-Provags-ID: V02:K0:wvIj2dU+IWQQDr8WVuT8YRc+owYF4q2P61MOu0YjPrM 8yBDHnlqpijJAO6CusNyE/kiKyGCS8FPOXc6r+BF7OZfU74YTk q5EoHGYdBeco0aSNCrITO8+MfCHBhl1RpoZCEl6AOa6GPAZE6x ffHDjN6foaijVpGyMoC9j5/pOLfmx6XH2IU0JczOuiMFQfFWBE qufo+y77PkARZoaBet+WI7TmU5x3wlmTSZu5i9B4SN+WnI1obA RDjFJI3wyWIZnnEZJQfa1T4Oej48/CNs0HBGoR/3Z4jljGj9FB 5FqFLtWtRShkD7IHlPVI9dIqhJ0wAQxKoGEA7zZnOL6voaGJxu 4MxYIPPy/5EgihnbSbhcqp9XT/V8/lL2xl59kKXSKC4R5nPY2h BNvI5v3jXfe5g== Cc: 6lowpan@ietf.org, saag@ietf.org Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2011 19:37:42 -0000 Thank you. I think it'd be useful for IETF community to understand what those 5/6 = distinct standards, and if the KMP being sought would be a generic = solution or specific to each one of them. PANA being used for one of = them already, I wonder whether it applies to the others or not. Any = ideas on that? On Sep 29, 2011, at 4:19 AM, Benjamin A. Rolfe wrote: > There is an obvious difference in scope: The scope of the ZigBee SEP = profile is specifically Demand > Response and Load Management applications. ZigBee uses IEEE = P802.15.4-2003. The scope of the referenced PAR includes all current = members of the 802.15 family of standards, which includes 5 distinct MAC = and PHY standards (soon to be 6). >=20 > I'm sure Bob can elaborate further. >=20 > Hope that helps. >=20 > Regards >=20 > -Ben >=20 >=20 >=20 >=20 >> Hi Bob, >>=20 >> As you know, Zigbee Alliance has already adopted EAP/PANA for network = access authentication and key agreement for Smart Energy Profile 2.0. >>=20 >> Is the problem you are seeking to solve the same problem, or a = different one? >>=20 >> Thanks. >>=20 >> Alper >>=20 >>=20 >>=20 >>=20 >>=20 >> On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote: >>=20 >>> This week the PAR for KMP passed within 802.15: >>>=20 >>> = https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-pr= otocol-par.doc >>> = https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc >>>=20 >>> In the PAR we are requesting the creation of a Recommended Practice = that will be identified as 802.15.8. >>>=20 >>> Next step is to get IEEE 802 approval which will be at the Atlanta = meeting week prior to IETF. >>>=20 >>> For all the current documents for the KMPIG: >>>=20 >>> https://mentor.ieee.org/802.15/documents?is_group=3D0kmp >>>=20 >>> In particular >>>=20 >>> = https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.pp= t >>>=20 >>> GIves the latest thoughts on how the shim will work and how the = document will be structured. >>>=20 >>> _______________________________________________ >>> saag mailing list >>> saag@ietf.org >>> https://www.ietf.org/mailman/listinfo/saag >> _______________________________________________ >> 6lowpan mailing list >> 6lowpan@ietf.org >> https://www.ietf.org/mailman/listinfo/6lowpan >>=20 >=20 > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan From ben@blindcreek.com Thu Sep 29 15:15:02 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33DB21F8B3F for <6lowpan@ietfa.amsl.com>; Thu, 29 Sep 2011 15:15:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.653 X-Spam-Level: X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[AWL=-0.946, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MISSING_HEADERS=1.292] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQgE5EjXGuqb for <6lowpan@ietfa.amsl.com>; Thu, 29 Sep 2011 15:15:01 -0700 (PDT) Received: from wilson.nswebhost.com (wilson.nswebhost.com [209.217.228.58]) by ietfa.amsl.com (Postfix) with ESMTP id 73FB221F8B59 for <6lowpan@ietf.org>; Thu, 29 Sep 2011 15:15:01 -0700 (PDT) Received: from [64.74.213.174] (port=49521 helo=[192.168.250.11]) by wilson.nswebhost.com with esmtpa (Exim 4.69) (envelope-from ) id 1R9OvL-0006FS-Lg for 6lowpan@ietf.org; Thu, 29 Sep 2011 17:17:48 -0500 Message-ID: <4E84EE8F.8000708@blindcreek.com> Date: Thu, 29 Sep 2011 15:17:51 -0700 From: "Benjamin A. Rolfe" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.20) Gecko/20110804 Lightning/1.0b2 Thunderbird/3.1.12 MIME-Version: 1.0 CC: 6lowpan@ietf.org References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> <4E83C7A6.4020008@blindcreek.com> <709DC625-A433-4DDC-9505-D9DD7180B93E@yegin.org> In-Reply-To: <709DC625-A433-4DDC-9505-D9DD7180B93E@yegin.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - wilson.nswebhost.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - blindcreek.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2011 22:15:02 -0000 I can summarize the 802.15 family; Bob will have to speak specifically to the KMP RP and which it will apply to. Each consists of a distinct MAC sub-layer specification and one or more PHY specifications (usually more). 802.15.1 - you will probably know it as Bluetooth (802.15.1 where the "personal" comes from in WPAN); short range, moderate data rate, small networks in both radio SOI and number of devices. Current revision 2005. 802.15.3 - high rate WPAN. The current standard includes a common MAC and multiple PHY layers, including a 2.4GHz PHY operating up to 55Mbps, and a very high rate (up to 5Gbps) PHYs operating in the 60 GHz (mmWave) band. Also small ROI and modest number of devices. The very high rate is being used in consumer applications such as video transport. Initial standard 2003 with amendment 3b published 2005 and amendment 3c published 2009. 802.15.4 - LR-WPAN, first publication in 2003 with a simple MAC and 2 PHYs, one 2.4GHz (OQPSK) and one for the 868 MHz and 915 MHz (BPSK) bands. This is the version called out in ZigBee. Since 2003 there has been a major revision that made significant changes to the MAC and two new PHYs operating in the 868 and 915 bands: OQPSK and ASK. Amendment 4a adds two more PHYs, a UWB PHY in 3 to 10 GHz band, and a CSS PHY in 2.4GHz; Amendment 4c adds PHYs for operating in the 780MHz band in China; Amendment 4d adds a GFSK PHY operating in the 950MHz band in Japan. The current revision is P802.15.4-2011 which includes all of the above amendments on the 2006 revision. Currently there are 3 new amendments nearing completion: Task Group (TG) 4e is adding new features to the MAC; TG4g is adding three new PHYs and a plethora of bands around the world, and is already being used for smart grid and M2M applications; TG4f adds 2 new PHYs for RFID applications. Additional TGs are underway defining even more new PHYs expanding the usefulness of 15.4 even further. Quite a bit has happened since 2003! 802.15.6 - Body Area Networks (or as I like to call it, very personal area networks), with yet another distinct MAC (including security). Currently there are 3 PHYs in the draft. Balloting in progress. 802.15.7 - Visible Light Communications. Approved in 2011. -B > Thank you. > > I think it'd be useful for IETF community to understand what those 5/6 distinct standards, and if the KMP being sought would be a generic solution or specific to each one of them. PANA being used for one of them already, I wonder whether it applies to the others or not. Any ideas on that? > > > > > > > > > On Sep 29, 2011, at 4:19 AM, Benjamin A. Rolfe wrote: > >> There is an obvious difference in scope: The scope of the ZigBee SEP profile is specifically Demand >> Response and Load Management applications. ZigBee uses IEEE P802.15.4-2003. The scope of the referenced PAR includes all current members of the 802.15 family of standards, which includes 5 distinct MAC and PHY standards (soon to be 6). >> >> I'm sure Bob can elaborate further. >> >> Hope that helps. >> >> Regards >> >> -Ben >> >> >> >> >>> Hi Bob, >>> >>> As you know, Zigbee Alliance has already adopted EAP/PANA for network access authentication and key agreement for Smart Energy Profile 2.0. >>> >>> Is the problem you are seeking to solve the same problem, or a different one? >>> >>> Thanks. >>> >>> Alper >>> >>> >>> >>> >>> >>> On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote: >>> >>>> This week the PAR for KMP passed within 802.15: >>>> >>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-management-protocol-par.doc >>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft.doc >>>> >>>> In the PAR we are requesting the creation of a Recommended Practice that will be identified as 802.15.8. >>>> >>>> Next step is to get IEEE 802 approval which will be at the Atlanta meeting week prior to IETF. >>>> >>>> For all the current documents for the KMPIG: >>>> >>>> https://mentor.ieee.org/802.15/documents?is_group=0kmp >>>> >>>> In particular >>>> >>>> https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-15.ppt >>>> >>>> GIves the latest thoughts on how the shim will work and how the document will be structured. >>>> >>>> _______________________________________________ >>>> saag mailing list >>>> saag@ietf.org >>>> https://www.ietf.org/mailman/listinfo/saag >>> _______________________________________________ >>> 6lowpan mailing list >>> 6lowpan@ietf.org >>> https://www.ietf.org/mailman/listinfo/6lowpan >>> >> _______________________________________________ >> 6lowpan mailing list >> 6lowpan@ietf.org >> https://www.ietf.org/mailman/listinfo/6lowpan > From robert.cragie@gridmerge.com Fri Sep 30 05:27:58 2011 Return-Path: X-Original-To: 6lowpan@ietfa.amsl.com Delivered-To: 6lowpan@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67F521F8A57 for <6lowpan@ietfa.amsl.com>; Fri, 30 Sep 2011 05:27:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIumFnW6R+4D for <6lowpan@ietfa.amsl.com>; Fri, 30 Sep 2011 05:27:58 -0700 (PDT) Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id CB40C21F8B20 for <6lowpan@ietf.org>; Fri, 30 Sep 2011 05:27:53 -0700 (PDT) Received: from client-82-26-192-102.pete.adsl.virginmedia.com ([82.26.192.102] helo=[192.168.1.80]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) id 1R9cEj-0001U0-32 for 6lowpan@ietf.org; Fri, 30 Sep 2011 13:30:41 +0100 Message-ID: <4E85B6F9.4020908@gridmerge.com> Date: Fri, 30 Sep 2011 13:32:57 +0100 From: Robert Cragie Organization: Gridmerge Ltd. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0) Gecko/20110922 Thunderbird/7.0 MIME-Version: 1.0 To: 6lowpan@ietf.org References: <4E7CC30C.10305@htt-consult.com> <9F3F4978-B966-4074-B96A-A2C2ED879F6A@yegin.org> <4E83C7A6.4020008@blindcreek.com> In-Reply-To: <4E83C7A6.4020008@blindcreek.com> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050609070705010702060807" X-Authenticated-As: robert.cragie@gridmerge.com Subject: Re: [6lowpan] [saag] Follow up on IEEE 802.15 Key Management X-BeenThere: 6lowpan@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: robert.cragie@gridmerge.com List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Sep 2011 12:27:59 -0000 This is a cryptographically signed message in MIME format. --------------ms050609070705010702060807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Actually, the ZigBee Alliance has adopted PANA/EAP for the ZigBee IP=20 stack, which is a specification of an IPv6 stack using 6lowpan over=20 802.15.4-2006 (not 2003) based on IETF standards. This is independent=20 from the SEP 2.0 application profile, which incidentally uses TLS. At the time of development, there was no EAP transport specified for any = 802.15 standard. The most expedient route for us at the time was to use=20 PANA (RFC 5191), which uses UDP datagrams which are accommodated easily=20 in 6lowpan without requiring any changes. With addition of the PANA=20 relay (RFC 6345), it provides an effective EAP transport, especially=20 where the authentication server is not in direct contact with the=20 joining node. Any EAP transport for 802.15 networks also needs to take=20 this into consideration given the topologies formed in 802.15 networks=20 (well, at least 802.15.4) Robert On 29/09/2011 2:19 AM, Benjamin A. Rolfe wrote: > There is an obvious difference in scope: The scope of the ZigBee SEP=20 > profile is specifically Demand > Response and Load Management applications. ZigBee uses IEEE=20 > P802.15.4-2003. The scope of the referenced PAR includes all current=20 > members of the 802.15 family of standards, which includes 5 distinct=20 > MAC and PHY standards (soon to be 6). > > I'm sure Bob can elaborate further. > > Hope that helps. > > Regards > > -Ben > > > > >> Hi Bob, >> >> As you know, Zigbee Alliance has already adopted EAP/PANA for network = >> access authentication and key agreement for Smart Energy Profile 2.0. >> >> Is the problem you are seeking to solve the same problem, or a=20 >> different one? >> >> Thanks. >> >> Alper >> >> >> >> >> >> On Sep 23, 2011, at 8:34 PM, Robert Moskowitz wrote: >> >>> This week the PAR for KMP passed within 802.15: >>> >>> https://mentor.ieee.org/802.15/dcn/11/15-11-0613-03-0kmp-key-manageme= nt-protocol-par.doc=20 >>> >>> https://mentor.ieee.org/802.15/dcn/11/15-11-0665-03-0kmp-kmp-5c-draft= =2Edoc=20 >>> >>> >>> In the PAR we are requesting the creation of a Recommended Practice=20 >>> that will be identified as 802.15.8. >>> >>> Next step is to get IEEE 802 approval which will be at the Atlanta=20 >>> meeting week prior to IETF. >>> >>> For all the current documents for the KMPIG: >>> >>> https://mentor.ieee.org/802.15/documents?is_group=3D0kmp >>> >>> In particular >>> >>> https://mentor.ieee.org/802.15/dcn/11/15-11-0650-00-0kmp-kmp-for-802-= 15.ppt=20 >>> >>> >>> GIves the latest thoughts on how the shim will work and how the=20 >>> document will be structured. >>> >>> _______________________________________________ >>> saag mailing list >>> saag@ietf.org >>> https://www.ietf.org/mailman/listinfo/saag >> _______________________________________________ >> 6lowpan mailing list >> 6lowpan@ietf.org >> https://www.ietf.org/mailman/listinfo/6lowpan >> > > _______________________________________________ > 6lowpan mailing list > 6lowpan@ietf.org > https://www.ietf.org/mailman/listinfo/6lowpan > --------------ms050609070705010702060807 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP3jCC BIowggNyoAMCAQICECf06hH0eobEbp27bqkXBwcwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6 hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu 9mIwFIws6wIDAQABo4HhMIHeMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/ BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9BZGRU cnVzdEV4dGVybmFsQ0FSb290LmNybDA2oDSgMoYwaHR0cDovL2NybC5jb21vZG8ubmV0L0Fk ZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAZ2IkRbyispgCi 54fBm5AD236hEv0e8+LwAamUVEJrmgnEoG3XkJIEA2Z5Q3H8+G+v23ZF4jcaPd3kWQR4rBz0 g0bzes9bhHIt5UbBuhgRKfPLSXmHPLptBZ2kbWhPrXIUNqi5sf2/z3/wpGqUNVCPz4FtVbHd WTBK322gnGQfSXzvNrv042n0+DmPWq1LhTq3Du3Tzw1EovsEv+QvcI4l+1pUBrPQxLxtjftz Mizpm4QkLdZ/kXpoAlAfDj9N6cz1u2fo3BwuO/xOzf4CjuOoEwqlJkRl6RDyTVKnrtw+ymsy XEFs/vVdoOr/0fqbhlhtPZZH5f4ulQTCAMyOofK7MIIFGjCCBAKgAwIBAgIQbRnqpxlPajMi 5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcw FQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VS Rmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBa Fw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5 MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NY X2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqi QfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBT bJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YX WEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30i Y9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSd JnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MA4GA1UdDwEB /wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYEVR0gADBYBgNVHR8E UTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGll bnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRoMGYwPQYIKwYBBQUH MAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVudF9DQS5jcnQw JQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQEFBQAD ggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjBMCjf y/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T 4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrU yTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lE uJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggYuMIIFFqAD AgECAhBcMVDbxC2oy5hyHl/adO9mMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEb MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNh dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDkwMjAwMDAwMFoXDTE0MDkwMTIzNTk1 OVowggE3MQswCQYDVQQGEwJHQjEQMA4GA1UEERMHV0Y0IDRXQTEXMBUGA1UECBMOV2VzdCBZ b3Jrc2hpcmUxEjAQBgNVBAcTCVdha2VmaWVsZDEUMBIGA1UECRMLR3JhbmdlIE1vb3IxHzAd BgNVBAkTFjg5IEdyZWVuZmllbGQgQ3Jlc2NlbnQxFzAVBgNVBAoTDkdyaWRtZXJnZSBMdGQu MTQwMgYDVQQLEytJc3N1ZWQgdGhyb3VnaCBHcmlkbWVyZ2UgTHRkLiBFLVBLSSBNYW5hZ2Vy MR8wHQYDVQQLExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRYwFAYDVQQDEw1Sb2JlcnQgQ3Jh Z2llMSowKAYJKoZIhvcNAQkBFhtyb2JlcnQuY3JhZ2llQGdyaWRtZXJnZS5jb20wggEiMA0G CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxOGq8t5ZTVDVkmadv7ZRBLA5ApaiTcDUzCTn zYB2/BoBDIEWWI/InSRcmq3A0Ghm+T7dYmvRADllGv4nTHexdWlzFp2iM/Yc3PLWCyAO0gYb yW2hTi+ZfUDwFOU4hRP4+Dyn9tKu7FXS/PQJHyGjaGxHRmLm9T6tAo2ZuC59uRaGVCcwRiOS d6axwtB/DVhnP3S1rrt2g0O6MXLr5fojToemO52AxjHxt2w1LnFUUXC4EDV6o1Ctr7EvOEI5 5f088H/Mrryp02GueLdY9gb0SFK3gPOT7EjP2GPvCtRkhVcNM+xjyptRIFWnCbMjmUIc+DO6 sfU4rtbCCkNKyXmnAgMBAAGjggHVMIIB0TAfBgNVHSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBb vHnFezAdBgNVHQ4EFgQUEI5c0f6UObxT2DLdvdtG+vG8qCswDgYDVR0PAQH/BAQDAgWgMAwG A1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0w OwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5u ZXQvQ1BTMFcGA1UdHwRQME4wTKBKoEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9E T0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEB BHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50 QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov L29jc3AuY29tb2RvY2EuY29tMCYGA1UdEQQfMB2BG3JvYmVydC5jcmFnaWVAZ3JpZG1lcmdl LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAPpv87QuQ9q+RHhmeirGDQB3szd24Obi7N+uVfh5y CrnoJx3B37dNrLPsTB6PfTChUyZMqQD80pFoJ3TBUz3yx4X+hmNco7ujVIfbuKBGcZJaMKhZ ex3AkZ9ltie9wgiGGzEmgI81t5JHsLQ8AUMqw/fGsnIwcyWMgmyhFtm79+dg3IVaH05d/t9g k4aYoMoCFJptQZ+Fju6a9T139hOqjTZDpjMLt3jM80bVrvkC4dIRyF/oZ0qrJwbfwjnL2OUN ph9eymhLc+VM0Ih5k41s5IxmB+2c0RUqr5JbK0WrIb/z53Cmb9rXYox7HknyIfBpQqP77Y7a sAU2MMOpel4RijGCBAwwggQIAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0Eg TGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2Vj dXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMAkGBSsOAwIaBQCgggI4MBgGCSqGSIb3 DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDkzMDEyMzI1N1owIwYJKoZI hvcNAQkEMRYEFBjP46fSO69YPYYWz+BOso/NmykbMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZI AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr DgMCBzANBggqhkiG9w0DAgIBKDCBuQYJKwYBBAGCNxAEMYGrMIGoMIGTMQswCQYDVQQGEwJH QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD VQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50 aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMIG7BgsqhkiG 9w0BCRACCzGBq6CBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3 BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBD QQIQXDFQ28QtqMuYch5f2nTvZjANBgkqhkiG9w0BAQEFAASCAQAnhDJsLjd2/LiUYeYdkpl/ iJThoHJTHFzol/tKi/Ko37XAnenWjAkfseF4vtgSYBGoVOTn6v3ZcvG68QaDeRGqvqaGwhp2 8qd4FDKDhYmehjBYQ6XgynEb3LqzE1daCvlu5YaVQWDESrBLy8fwg7EgEYzCDJSiXCQNvay5 gjZNksrScg1fdEegzcdmu4mkcztVa8aG1XEDUP11emkF4raHN+5hDpgSFImNVcZ8Kh2e66Gc ENHqg72DPR2V88DZeW0Wx0Ja6CSbSUcwezuiu/M15V8/k+A5/6uVgbLquy0yIk8k6Xez8G9G 5ug3y1uTX76Y+QObE+6hDbznmFEZ4NZVAAAAAAAA --------------ms050609070705010702060807--