Re: [6lo] WGLC for draft-ietf-6lo-ethertype-request-00.txt

Paul Duffy <paduffy@cisco.com> Wed, 20 April 2016 20:16 UTC

Return-Path: <paduffy@cisco.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE3E012E20E for <6lo@ietfa.amsl.com>; Wed, 20 Apr 2016 13:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.516
X-Spam-Level:
X-Spam-Status: No, score=-15.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVZHoulwW_3v for <6lo@ietfa.amsl.com>; Wed, 20 Apr 2016 13:16:53 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE26212E2E5 for <6lo@ietf.org>; Wed, 20 Apr 2016 13:16:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13794; q=dns/txt; s=iport; t=1461183413; x=1462393013; h=reply-to:subject:references:to:cc:from:message-id:date: mime-version:in-reply-to; bh=DtCgU6c6SEUM4bVAqH7TeUYbY47iOuAs/4j8brdE8/Y=; b=bTPmVXXRukJ3Ehrv1z5d5K8WdVNyjr33U1wKFnN1C2G8eA5r31HE449w DW7CYwjCzuzhWoaHgNxqOSrUTzOXS7avxg1nqrsxvNWcwqBDkx6Q8m36+ CY0KnR/VbieZaBUycVK4LrDOvdLWF+BIjukfv6Gn5MU2r50dRolFRnUPt k=;
X-IronPort-AV: E=Sophos; i="5.24,510,1454976000"; d="scan'208,217"; a="94066255"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Apr 2016 20:16:53 +0000
Received: from [10.86.242.62] (che-vpn-cluster-2-62.cisco.com [10.86.242.62]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u3KKGqtB005292; Wed, 20 Apr 2016 20:16:52 GMT
References: <ECA43DA70480A3498E43C3471FB2E1F02238F2B1@eusaamb103.ericsson.se>
To: Samita Chakrabarti <samita.chakrabarti@ericsson.com>, "Ralph Droms (rdroms) (rdroms@cisco.com)" <rdroms@cisco.com>
From: Paul Duffy <paduffy@cisco.com>
Organization: Cisco Systems
Message-ID: <5717E3B4.8070901@cisco.com>
Date: Wed, 20 Apr 2016 16:16:52 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <ECA43DA70480A3498E43C3471FB2E1F02238F2B1@eusaamb103.ericsson.se>
Content-Type: multipart/alternative; boundary="------------010804050502000101020202"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/6CBi1VKuw374iX-jmI5MIWrdvvo>
Cc: "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6lo] WGLC for draft-ietf-6lo-ethertype-request-00.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: paduffy@cisco.com
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: Wed, 20 Apr 2016 20:16:57 -0000

Hi Samita

...

On 4/20/2016 1:25 PM, Samita Chakrabarti wrote:
>
> Comments :
>
> ‘Introduction’ section of this draft  indicates a few bullet points on 
> how it might be useful in 802.15.9 and  wifi/Ethernet technologies , 
> but it is not clear to me that if this type is now mandatory for other 
> non-802.15.4  L2 technologies as well.
>
> Can you please add a section on the document on usage with other L2 
> technologies? Or is this draft only limited to Wifi/Ethernet technologies?
>

 From the intro ...

    o  Usage of LoWPAN encapsulation in conjunction with IEEE 802.15.9
       Multiplexed Data Service [IEEE802159 
<https://tools.ietf.org/html/draft-ietf-6lo-ethertype-request-00#ref-IEEE802159>], which provides the ability
       to perform upper layer protocol dispatch for IEEE 802.15.4
       networks.  Wi-SUN Alliance intends to use the 15.9 Multiplexed
       Data Information Element to dispatch LoWPAN encapsulation frames
       to upper stack layers.  As specified in IEEE 802.15.9, dispatch of
       LoWPAN encapsulation frames will require an Ethertype be assigned
       for LoWPAN encapsulation.



> If it applies to other foo L2 technologies, then an explanation is 
> requested  as to when to consider adding this “type” in the solution 
> and whether any existing RFCs( bt-le, lowpanz etc.) require any 
> modification.
>
> Best regards,
>
> -Samita
>
> *From:*Samita Chakrabarti
> *Sent:* Wednesday, April 20, 2016 10:07 AM
> *To:* 6lo@ietf.org
> *Cc:* 6lo-chairs@tools.ietf.org
> *Subject:* WGLC for draft-ietf-6lo-ethertype-request-00.txt
>
> Hello All:
>
> The WG Last Call for the following document starts today.
>
> Please provide your input on improving the document and comments on 
> proceeding towards the next step.
>
> The LC will end on May 4, 2016.
>
> Thank you.
>
> -Samita & Gabriel
>
> >Title           : Assignment of an Ethertype for IPv6 with LoWPAN 
> Encapsulation
>
> > Authors         : Ralph Droms
>
> > Paul Duffy
>
> > Filename        : draft-ietf-6lo-ethertype-request-00.txt
>
> > Pages           : 4
>
> > Date            : 2016-04-18
>
> >
>
> > Abstract:
>
> >   When carried over layer 2 technologies such as Ethernet, IPv6
>
> >   datagrams using LoWPAN encapsulation as defined in RFC 4944 must be
>
> >   identified so the receiver can correctly interpret the encoded IPv6
>
> >   datagram. This document requests the assignment of an Ethertype for
>
> >   that purpose.
>
> >
>
> >
>
> > The IETF datatracker status page for this draft is:
>
> > https://datatracker.ietf.org/doc/draft-ietf-6lo-ethertype-request/
>
> >
>
> > There's also a htmlized version available at:
>
> > https://tools.ietf.org/html/draft-ietf-6lo-ethertype-request-00
>