Re: [Roll] Revised Early Allocation for draft-ietf-roll-trickle-mcast

[Ralph Droms <[e-mail]>]

On May 24, 2013, at 4:57 PM 5/24/13, Ulrich Herberg <[e-mail]> wrote:

> Adrian,
> 
> thank you very much for the explanation.
> 
> Is there any good reason for early (permanent) allocations? As long as
> a document still changes, this same problem could occur again for
> other drafts in the future.

I'll make an explanation here as I initially submitted the request for an early allocation.

Some early allocations are requested to cooperate with other SDOs that produce documents dependent on IETF documents and code point allocations.  In this specific case, I requested the early allocation on behalf of ZigBee Alliance, which has incorporated a reference to draft-ietf-roll-trickle-mcast in its "ZigBee IP Specification" (ZigBee Public Document 13-002r00; available for free available by request here: http://www.zigbee.org/Specifications/ZigBeeIP/Download.aspx).

An early allocation in a case like this is unusual; the IETF prefers that SDOs wait to publish their own documents until the referenced IETF documents are published (or, at least, in the RFC Editor queue and unlikely to change).  I requested the early allocation as ZA has had a deadline in place for publication of "ZigBee IP Specification" for some time and it seemed to me, at the time I made the request, that draft-ietf-roll-trickle-mcast was unlikely to change the codepoint before publication.

- Ralph

> 
> Regards
> Ulrich
> 
> On Fri, May 24, 2013 at 1:50 PM, Adrian Farrel <[e-mail]> wrote:
>> The general problem with early allocation is that the entry is placed in the
>> IANA registry and from that point onwards folk can rightfully interpret the
>> codepoint as having the meaning documented in the registry. Therefore, there
>> might reasonably be implementations (code or 'just' diagnostic tools like
>> sniffers) that have shipped and that use the old code point.
>> 
>> The way that IANA handle this is that they deprecate and do not claim back until
>> the registry is crowded, allowing as long as possible before re-use.
>> 
>> As it happens, with this registry, there is a preference for allocations based
>> only on the "rest" bits even though the entries are tracked separately on the
>> full 8 bits. Thus, in this case, the new and old codepoints are effectively the
>> same.
>> 
>> For more details on early allocations read RFC 4020 and
>> https://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/
>> 
>> Cheers,
>> Adrian
>> 
>>> -----Original Message-----
>>> From: Ulrich Herberg [mailto:[e-mail]]
>>> Sent: 24 May 2013 21:31
>>> To: [e-mail]; roll WG
>>> Subject: Re: [Roll] FW: Revised Early Allocation for
>> draft-ietf-roll-trickle-mcast
>>> 
>>> Adrian,
>>> 
>>> does "deprecated" mean that this code point is not useable again for
>>> other protocols? Why can't it be "Unassigned" again (since the draft
>>> is not yet published as RFC)?
>>> 
>>> 
>>> Thanks
>>> Ulrich
>>> 
>>> On Fri, May 24, 2013 at 1:23 PM, Adrian Farrel <[e-mail]> wrote:
>>>> FYI
>>>> 
>>>>> -----Original Message-----
>>>>> From: [e-mail] [mailto:[e-mail]] On Behalf Of
>>> IESG
>>>>> Secretary
>>>>> Sent: 24 May 2013 21:05
>>>>> To: [e-mail]
>>>>> Cc: [e-mail]
>>>>> Subject: Revised Early Allocation for draft-ietf-roll-trickle-mcast
>>>>> 
>>>>> IANA is requested to revise the early allocation previously made for
>> draft-ietf-
>>>>> roll-roll-trickle-mcast.
>>>>> 
>>>>> In the "Internet Protocol Version 6 (IPv6) Parameters" registry
>>>>> (http://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xml)
>>>>> in the "Destination Options and Hop-by-Hop Options" sub-registry...
>>>>> 
>>>>> Please revise the entry that reads
>>>>> 0x4D 01 0 01101 Trickle Multicast Option [draft-ietf-roll-trickle-mcast]
>>>>> to read
>>>>> 0x4D 01 0 01101 Deprecated
>>>>> 
>>>>> Please create a new early allocation entry that reads
>>>>> 0x6D 01 1 01101 MPL Option [draft-ietf-roll-trickle-mcast]
>>>> 
>>>> _______________________________________________
>>>> Roll mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/roll
>> 
> _______________________________________________
> Roll mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/roll