IETF Logo Mail Archive

Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt

Samita Chakrabarti <samita.chakrabarti@ericsson.com> Sat, 18 July 2015 22:31 UTC

Return-Path: <samita.chakrabarti@ericsson.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0191A0078 for <6lo@ietfa.amsl.com>; Sat, 18 Jul 2015 15:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qAv5S1-c_JGe for <6lo@ietfa.amsl.com>; Sat, 18 Jul 2015 15:31:52 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 294AA1A1A5B for <6lo@ietf.org>; Sat, 18 Jul 2015 15:31:52 -0700 (PDT)
X-AuditID: c6180641-f794d6d000001dfb-e3-55aa6bfb2e60
Received: from EUSAAHC002.ericsson.se (Unknown_Domain [147.117.188.78]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id B5.C7.07675.BFB6AA55; Sat, 18 Jul 2015 17:08:43 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC002.ericsson.se ([147.117.188.78]) with mapi id 14.03.0210.002; Sat, 18 Jul 2015 18:31:50 -0400
From: Samita Chakrabarti <samita.chakrabarti@ericsson.com>
To: "paduffy@cisco.com" <paduffy@cisco.com>, "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt
Thread-Index: AdC4UzCPfoTixixXT5Sqp0lO5gesdgBE9PQAABAAMyAAE+zfUwHDeOng
Date: Sat, 18 Jul 2015 22:31:50 +0000
Message-ID: <ECA43DA70480A3498E43C3471FB2E1F022229185@eusaamb103.ericsson.se>
References: <ECA43DA70480A3498E43C3471FB2E1F01C39990C@eusaamb103.ericsson.se> <CAO6tK45NVtbN4gON+fcQA=xzzV0Wd00Jqgo78i6LP5QV_j71Sg@mail.gmail.com> <ECA43DA70480A3498E43C3471FB2E1F01C39B48B@eusaamb103.ericsson.se> <CAO6tK474ga37g29Ope8XxsPB67iBpsSAsPhXqXfMcyvCm6_+xg@mail.gmail.com> <559DE950.3080805@cisco.com>
In-Reply-To: <559DE950.3080805@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOLMWRmVeSWpSXmKPExsUyuXSPn+7v7FWhBr/7jS2apwhYXL9UYdG5 4hWzA7PHlN8bWT0W9Fh5LFnykymAOYrLJiU1J7MstUjfLoEr4/6VtawFy4Uq7rQfZGpgbOTv YuTkkBAwkTh38TMLhC0mceHeerYuRi4OIYGjjBKf1reyQzjLGSVuztjBDFLFJmAl0dG7hx3E FhHwkrizZitTFyMHB7OArcS8PWYgYWEBR4kTX6exQJQ4SWyaeZcNwnaTuH2uB8xmEVCVaOro YQFp5RXwlZi7WwZi1T4miWmd38F6OQU0JZZcXMcIYjMCHff91BomEJtZQFzi1pP5TBBHC0gs 2XOeGcIWlXj5+B8rhK0kMef1NWaIeh2JBbs/sUHY2hLLFr4Gi/MKCEqcnPmEZQKj2CwkY2ch aZmFpGUWkpYFjCyrGDlKi1PLctONDDcxAmPmmASb4w7GBZ8sDzEKcDAq8fA+qFoZKsSaWFZc mXuIUZqDRUmcV9ovL1RIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD446lhXaP2r3llIpjmX7z aT40rQu03nqud6OyLfvFFZ5z/FeE5J8IM2yd2G/I7ObDffBLi8MJRVmxY9dW3cuQe7/q9PmW 73lVpzV0BGbUyjTk3z91O9h333kjrRMd8Rd8Gg82LDPI3Omckb/4lpTdlpSVlSJynd9E5zwp 1t7oOMUzQ3bnBsUbSizFGYmGWsxFxYkAqaX4cXoCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/5aJW_1iTRWetTuCtt6j8zcI67G0>
Cc: "Thierry LYS (thierry.lys@erdf.fr)" <thierry.lys@erdf.fr>
Subject: Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Jul 2015 22:31:56 -0000

Hi Paul,

Thanks for your suggestion. We will revisit the ESC bytes allocation proposal based on various suggestions.
As for G3-PLC usage of 6lowpan usage,  here is some explanation provided by Thierry on the list:



From: Thierry LYS [mailto:thierry.lys@erdf.fr] 
Sent: Tuesday, May 19, 2015 3:11 PM
To: Samita Chakrabarti
Cc: 6lo@ietf.org; cabo@tzi.org; cedric-2.lavenu@edf.fr
Subject: RE: [6lo] Possible 6LoWPAN dispatch type deprecation and re-use for route over purposes

Hello Samita, 

Please find my answer below: 

> ESC dispatch header is used in G3-PLC for 2 types of commands : the mesh-under routing and the bootstrapping. 
We do use 6LOWPAN_IPHC and ESC headers in the same frame during the bootstrapping phase. 

> ESC dispatch header is placed after 6LOWPAN_IPHC header. ESC is always located in last position. 

Best regards, 
Thierry 

-------------

-Samita
-----Original Message-----
From: 6lo [mailto:6lo-bounces@ietf.org] On Behalf Of Paul Duffy
Sent: Wednesday, July 08, 2015 8:24 PM
To: 6lo@ietf.org
Subject: Re: [6lo] draft-chairs-6lo-dispatch-iana-registry-00.txt

On 7/8/2015 4:48 PM, Jonathan Hui wrote:
> Finally, I'll reiterate that I think we should think carefully about 
> simply giving a whole swath of the ESC namespace to G3-PLC.  One 
> possibility is to have an encoding that can carry something like an 
> OUI, allowing third parties to define whatever they want without any 
> further coordination with the IETF.  IEEE 802.15.4e-2012 IEs have a 
> form that can carry OUIs.

I agree with Jonathan's statements re: this draft.  The G3 assignments represents more that 10% of the available extension types, and I see little justification for that.

Alternatives include a dispatch value assigned for "organization extension" with the subsequent frame containing an OUI, PEN, etc. then the org defined payload.  Let the extending organization manage their own number space and frame definition.  Or the mentioned approach of 4e's Information Element.

I'm also curious, given G3 is asking for 31 Extension Types ... what parts of RFC-ed 6LoWPAN are they actually using?

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

v2.23.0 | Report a Bug | By Email