Re: [Roll] FW: Revised Early Allocation for draft-ietf-roll-trickle-mcast
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 24 May 2013 20:50 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 6ABC511E8136 for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.326
X-Spam-Level:
X-Spam-Status: No, score=-2.326 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLpRWtphiv99 for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:50:20 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 2967C11E8132 for <roll@ietf.org>; Fri, 24 May 2013 13:50:19 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OKoHrk009130; Fri, 24 May 2013 21:50:17 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OKoFLm009110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 21:50:15 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Ulrich Herberg' <ulrich@herberg.name>, 'roll WG' <roll@ietf.org>
References: <20130524200446.9059.78064.idtracker@ietfa.amsl.com> <075c01ce58bc$93866f00$ba934d00$@olddog.co.uk> <CAK=bVC_nibqpZE4FvKqEvWdvkn9fmW9xS85X4gRkboVQ7ho-Rw@mail.gmail.com>
In-Reply-To: <CAK=bVC_nibqpZE4FvKqEvWdvkn9fmW9xS85X4gRkboVQ7ho-Rw@mail.gmail.com>
Date: Fri, 24 May 2013 21:50:14 +0100
Message-ID: <076c01ce58c0$4b5945f0$e20bd1d0$@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: AQHuT8k/wbyMhRnnvyd/g4chVJ/kSwLhyxINAup/EAaYpn01MA==
Content-Language: en-gb
Subject: Re: [Roll] FW: Revised Early Allocation for draft-ietf-roll-trickle-mcast
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk, Routing Over Low power and Lossy networks <roll@ietf.org>
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, 24 May 2013 20:50:27 -0000
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:ulrich@herberg.name] > Sent: 24 May 2013 21:31 > To: adrian@olddog.co.uk; 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 <adrian@olddog.co.uk> wrote: > > FYI > > > >> -----Original Message----- > >> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of > IESG > >> Secretary > >> Sent: 24 May 2013 21:05 > >> To: iana@iana.org > >> Cc: iesg@ietf.org > >> 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 > > Roll@ietf.org > > https://www.ietf.org/mailman/listinfo/roll
- [Roll] FW: Revised Early Allocation for draft-iet… Adrian Farrel
- Re: [Roll] FW: Revised Early Allocation for draft… Ulrich Herberg
- Re: [Roll] FW: Revised Early Allocation for draft… Adrian Farrel
- Re: [Roll] FW: Revised Early Allocation for draft… Ulrich Herberg
- Re: [Roll] Revised Early Allocation for draft-iet… Ralph Droms
- Re: [Roll] FW: Revised Early Allocation for draft… Adrian Farrel
- Re: [Roll] Revised Early Allocation for draft-iet… Ulrich Herberg