IETF Logo Mail Archive

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

Ulrich Herberg <ulrich@herberg.name> Fri, 24 May 2013 20:57 UTC

Return-Path: <ulrich@herberg.name>
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 E0F5111E8132 for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 4OlAdhHxsOtn for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:57:57 -0700 (PDT)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2736321F8FA3 for <roll@ietf.org>; Fri, 24 May 2013 13:57:57 -0700 (PDT)
Received: by mail-vb0-f54.google.com with SMTP id f13so3446021vbg.27 for <roll@ietf.org>; Fri, 24 May 2013 13:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QRjMQnppSXKvcPk34AY5T3DiH2jAJyjwVUCHlC7rFdk=; b=T4z3OMRi41CXRVHE8aKi4ABhb1Rf2FllJVytIHJ2Ovv8x6QqZ/cixqoAaHWPItfzk4 4b/lQA3Q1rcFZAhrG3RkJ+z2vbe0WnFDvJozwiTxpKrgBLzcXaM4RKQBdC7I+xcScOJS soEK2HOBmm0MbUHBYwFM1NcCGBUWy7Vt6t/Qk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=QRjMQnppSXKvcPk34AY5T3DiH2jAJyjwVUCHlC7rFdk=; b=GUcrAsH22sWkEZwLBiHRTKia5YKtM6COhRDD7Rv3/CJfIrDMcbHQkIRmEqTm8Q7w7b ncTdkyjopwI76KqhIg8/C1KmOqCGe3sPkFVjtrirNfaTSR/uROP6/LmdwLK5iD+Kp3q1 MEPLNFtVM4j+aVkeoxdo2WVmU0G5xlVPb20iAOF3oIqURs/PfUnFfdvl/TALSQdzydke ni6m856tW/mElf/8j5Gc2ATXJz7aGKTXCisIiVBXh7CR/DUzDmJ1AKX+pVtZLzohJ5u9 k3pMI4EIX0UJTYGpDPk6P1CMP/HZRz0+nqYnIdrPJsGPEJQXDzNNmkeE6ghfc5btTYA7 rO3A==
MIME-Version: 1.0
X-Received: by 10.220.53.138 with SMTP id m10mr9763777vcg.29.1369429076384; Fri, 24 May 2013 13:57:56 -0700 (PDT)
Received: by 10.220.195.134 with HTTP; Fri, 24 May 2013 13:57:56 -0700 (PDT)
In-Reply-To: <076c01ce58c0$4b5945f0$e20bd1d0$@olddog.co.uk>
References: <20130524200446.9059.78064.idtracker@ietfa.amsl.com> <075c01ce58bc$93866f00$ba934d00$@olddog.co.uk> <CAK=bVC_nibqpZE4FvKqEvWdvkn9fmW9xS85X4gRkboVQ7ho-Rw@mail.gmail.com> <076c01ce58c0$4b5945f0$e20bd1d0$@olddog.co.uk>
Date: Fri, 24 May 2013 13:57:56 -0700
Message-ID: <CAK=bVC_4bMsQ0SZwV8MqtWwJ_XsrXND0hkDNFXeVKaC1uV_6JQ@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
To: adrian@olddog.co.uk
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQmD0J+9yf2H6L3Ym0XYJsfKMAJGJokBPp+Uc+jUTupTKH4OnHhxkOitr6k8TxQ6veaJy2Wl
Cc: roll WG <roll@ietf.org>
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: 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:57:58 -0000

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.

Regards
Ulrich

On Fri, May 24, 2013 at 1:50 PM, Adrian Farrel <adrian@olddog.co.uk> 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: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
>

v2.23.0 | Report a Bug | By Email