Re: [Pppext] small draft to update iana rules in PPP BAP/BACP

Jari Arkko <jari.arkko@piuha.net> Sat, 05 September 2009 09:47 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77F483A6817 for <pppext@core3.amsl.com>; Sat, 5 Sep 2009 02:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level:
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzT0LAv72cDk for <pppext@core3.amsl.com>; Sat, 5 Sep 2009 02:47:43 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 668A33A67FE for <pppext@ietf.org>; Sat, 5 Sep 2009 02:47:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8EAEED6270; Sat, 5 Sep 2009 12:48:02 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7-v+6eddNl9; Sat, 5 Sep 2009 12:48:02 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 11729D6246; Sat, 5 Sep 2009 12:48:02 +0300 (EEST)
Message-ID: <4AA233D1.5030902@piuha.net>
Date: Sat, 05 Sep 2009 12:48:01 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: William Allen Simpson <william.allen.simpson@gmail.com>
References: <4A9F722B.6070508@piuha.net> <20090904064923.GC22860@juniper.net> <4AA0D674.5000509@piuha.net> <4AA0E2B4.2000500@gmail.com>
In-Reply-To: <4AA0E2B4.2000500@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "pppext@ietf.org" <pppext@ietf.org>
Subject: Re: [Pppext] small draft to update iana rules in PPP BAP/BACP
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Sep 2009 09:47:44 -0000

Bill,

> My preference would be to rename:
>
> Updated IANA Allocation Guidelines for PPP documents
>
> And rigorously walk through every PPP-related RFC, looking for missing
> or inconsistent IANA information.

Are you volunteering? :-) I'm asking serioulsy, because I think we 
should do a walkthrough and find out what other missing information 
there might be.
.
> Should BAP be the only one missing its allocations, then maybe just 
> update
> IANA without bothering to write yet another RFC....

I know this RFC is a borderline case in terms of real-world usefulness. 
I do believe, however, that the registries need to be kept up to date 
and correct even for older protocols. And my personal preference is to 
issue significant registry updates only through RFCs. Most of the effort 
in writing this draft has gone into getting the various registries 
correct (whether they should or should not contain 0 - vendor specific, 
for instance. It took a while for me and James to get that right. This 
needs to be done anyway, and I guess I'm still hoping that the remaining 
IETF publication process for simple RFCs is a very efficient one :-) Or 
at least it has been for some of the past RFCs that we have written on 
similar IANA updates.

Jari