Re: [Roll] Request for IESG approval of early allocation for HBH code point
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 14 December 2012 11:24 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD7F21F853D for <roll@ietfa.amsl.com>; Fri, 14 Dec 2012 03:24:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxV7SJsfwGsP for <roll@ietfa.amsl.com>; Fri, 14 Dec 2012 03:24:06 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id E3CEB21F853C for <roll@ietf.org>; Fri, 14 Dec 2012 03:24:00 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBEBNvK3029926; Fri, 14 Dec 2012 11:23:57 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBEBNu57029915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Dec 2012 11:23:56 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>
References: <30489.1355451277@obiwan.sandelman.ca>
In-Reply-To: <30489.1355451277@obiwan.sandelman.ca>
Date: Fri, 14 Dec 2012 11:23:54 -0000
Message-ID: <00b401cdd9ed$80ac6270$82052750$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKL3otY+tHaMq3yh8PLWOhpaapgn5acHVHA
Content-Language: en-gb
Cc: roll@ietf.org, draft-ietf-roll-trickle-mcast@tools.ietf.org
Subject: Re: [Roll] Request for IESG approval of early allocation for HBH code point
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 11:24:07 -0000
Thanks Michael, This looks like a reasonable request to me. I have put it on the agenda for IESG consideration at the next telechat on Thursday 20th. If anyone has any issues of concerns please speak soon. Adrian > -----Original Message----- > From: mcr@obiwan.sandelman.ca [mailto:mcr@obiwan.sandelman.ca] On Behalf > Of Michael Richardson > Sent: 14 December 2012 02:15 > To: Adrian Farrel > Cc: roll@ietf.org; draft-ietf-roll-trickle-mcast@tools.ietf.org > Subject: Request for IESG approval of early allocation for HBH code point > > > Adrian, > > The ROLL WG is in the process of finalizing the details of the > draft-ietf-roll-trickle-mcast. In this document there is an IANA > request: > > 8. IANA Considerations > > The Trickle Multicast option requires an IPv6 Option Number. > > HEX act chg rest > --- --- --- ----- > C 01 0 TBD > > The first two bits indicate that the IPv6 node MUST discard the > packet if it doesn't recognize the option type, and the third bit > indicates that the Option Data MUST NOT change en-route. > > Implementers in the ZigBee IP need this value set sooner rather than > later in order to do interoperability testing. > > The need for the allocation will not change even if the precise layout > of one or two bits in the option is not yet fully agreed to. > > The registraty is at: > http://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xml > and is entitled "Destination Options and Hop-by-Hop Options". > > The registry says: > Registration Procedures > IESG Approval, IETF Consensus or Standards Action > > so while it does not support early approval, it does support IESG > Approval. > > We would therefore ask the IESG to please allocate this hop-by-hop > option. > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > IETF ROLL WG co-chair. http://datatracker.ietf.org/wg/roll/charter/
- Re: [Roll] Request for IESG approval of early all… Adrian Farrel