IETF Logo Mail Archive

Re: [6lo] Draft wording for liaison statement

Kerry Lynn <kerlyn@ieee.org> Tue, 21 July 2015 16:54 UTC

Return-Path: <kerlyn2001@gmail.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 532941AC42C for <6lo@ietfa.amsl.com>; Tue, 21 Jul 2015 09:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjYUROMZJjOq for <6lo@ietfa.amsl.com>; Tue, 21 Jul 2015 09:54:53 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 928A81B2FDC for <6lo@ietf.org>; Tue, 21 Jul 2015 09:54:47 -0700 (PDT)
Received: by lblf12 with SMTP id f12so120003354lbl.2 for <6lo@ietf.org>; Tue, 21 Jul 2015 09:54:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=s4mmHRuDePunsCZ7+fZ3TtMND2gHbI/dQ60rW/EWgks=; b=k84YJyb2WP+d7hKX4Kgk3AA97UQfebzHUf5EID9OxR9y/eZopu/WIu/4PtqKpYG5Xd WYhYFsDEFaSlipuQJTE9C/muqERMtaPr8cdMuU3C8hMfVK2surZLllcooOrnQ/XxEhzn 6UXBYh0UYBoYWgjVbjd/Uu1oVwfvVbLPNlWvL4PMWEnVlSCx8iBE/Gycu1ubV8GwV4j3 lDzKQg2UoCKOaYH/A5SjhdwaiY4blkOSpwZyTYAXQdf9IekzuAB66ZhY5cAZ2pFJKHz8 1rgs8Hg41UiDp8GnD5qW8YMdytL4OgygB2t23StTNnFR9xpRSsX2+oVtH4v/dmt1nLdo VEag==
MIME-Version: 1.0
X-Received: by 10.152.30.4 with SMTP id o4mr33124315lah.74.1437497686119; Tue, 21 Jul 2015 09:54:46 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.25.87.7 with HTTP; Tue, 21 Jul 2015 09:54:46 -0700 (PDT)
In-Reply-To: <55AE5B96.7030407@gmail.com>
References: <C67ABF34-1468-4580-B1CB-236000DF6A85@gmail.com> <55AE5B96.7030407@gmail.com>
Date: Tue, 21 Jul 2015 12:54:46 -0400
X-Google-Sender-Auth: rIih3xphk3qIPkf5S-YlnDKxPkc
Message-ID: <CABOxzu1gqo3B3OMv-ZaRWwjg4SU1Sndq6oz7NjRn-scU4X9_kQ@mail.gmail.com>
From: Kerry Lynn <kerlyn@ieee.org>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary="089e0160b436f25bac051b65825c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/31akdAa6LPpagaBb_XtJg1_RAtI>
Cc: "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6lo] Draft wording for liaison statement
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: Tue, 21 Jul 2015 16:54:55 -0000

On Tue, Jul 21, 2015 at 10:47 AM, Alexandru Petrescu <
alexandru.petrescu@gmail.com> wrote:

>
>
> Le 21/07/2015 12:34, Ralph Droms a écrit :
>
>> We held a hum regarding the content of a liaison statement to send to
>> ITU-T SG15 in response to the recent liaison statement from SG15.  The
>> WG has been asked to respond by Friday.  Included below is a rough
>> transcription of the words I used in the hum yesterday.  Scott, Samita,
>> Gabriel, James and I will write up the final liaison statement for
>> transmission to SG-15 on Friday.  If you have any comments on the
>> *content* (not the specific language, which we will likely rewrite) of
>> the text, please comment to the list by Thursday.
>>
>> -----
>>
>> The IETF will not change the definitions of the code points specified in
>> RFC 4944 and RFC 6282, as published in IANA registry "IPv6 Low Power
>> Personal Area Network Parameters"
>> <
>> http://www.iana.org/assignments/_6lowpan-parameters/_6lowpan-parameters.xhtml
>> >,
>> in such a way as to affect the ITU-T G.9903 and G.9905 specifications.
>>
>
> I agree, it is neutral enough.
>
> But I dont understand why is IANA reserving anything below the IP layer?
>
> Provided there is an explanation for it that I missed (sorry), I dont
> understand why IANA is not reserving something for the IPv6 Base Header
> altogether - a simple plain IPv6 Base Header uncompressed.?
>
> <kel>
Isn't that what the 01 000001 Dispatch Value bit pattern is for?  Or are you
talking about another name space?

Kerry
</kel>

>  The IETF 6lo working group offers to collaborate with ITU-T SG15 in
>> establishing a new registry for the code points following the ESC
>> dispatch code.  This new registry will be populated at the time of its
>> establishment with the Command ID values as defined in G.9903 and G.9905.
>>
>
> I can agree to it.  But I still need to understand why IANA needs to
> control this.
>
> Alex
>
>
>
>>
>>
>>
>> _______________________________________________
>> 6lo mailing list
>> 6lo@ietf.org
>> https://www.ietf.org/mailman/listinfo/6lo
>>
>>
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo
>

v2.23.0 | Report a Bug | By Email