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

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
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
Precedence: list
Reply-To: adrian@olddog.co.uk

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