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

Ignacio Goyret <igoyret@alcatel-lucent.com> Fri, 04 September 2009 02:45 UTC

Return-Path: <igoyret@alcatel-lucent.com>
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 9CCE73A681E for <pppext@core3.amsl.com>; Thu, 3 Sep 2009 19:45:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 f+nwDqUMlNAx for <pppext@core3.amsl.com>; Thu, 3 Sep 2009 19:45:19 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 1A06E3A63CB for <pppext@ietf.org>; Thu, 3 Sep 2009 19:45:19 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id n8416JMR015342; Thu, 3 Sep 2009 20:06:19 -0500 (CDT)
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [135.140.53.169]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n8416IFE001201; Thu, 3 Sep 2009 20:06:18 -0500 (CDT)
Received: from igoyret-c1.alcatel-lucent.com (dhcp-135-140-27-183 [135.140.27.183]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id n8416H60007097; Thu, 3 Sep 2009 18:06:18 -0700
Message-Id: <200909040106.n8416H60007097@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 03 Sep 2009 18:05:05 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: Ignacio Goyret <igoyret@alcatel-lucent.com>
In-Reply-To: <4A9F722B.6070508@piuha.net>
References: <4A9F722B.6070508@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
Cc: 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: Fri, 04 Sep 2009 02:45:20 -0000

At 10:37 AM 9/3/2009 +0300, Jari Arkko wrote:

>http://www.ietf.org/id/draft-arkko-pppext-bap-ianafix-00.txt
>
>Comments appreciated. I promise that at least this draft is shorter and simpler than most others :-)

Hi Jari,
Just a couple of minor comments on the "PPP BAP Link Type" option.
It may be useful to IANA to mention that this is actually
a bit field and that each entry defines one bit.

Although RFC2125 allows defining more bits for this field,
the interoperability of such a choice would probably be questionable.
May be the text should include some sort of discouragement to
adding more bits beyond the defined ones.

Finally, the bit positions are opposite of the usual: bit 0 is
actually the low order bit. This is very confusing, but this is
also how it is in the original RFC. Too bad it wasn't fixed
back then.

Cheers,-Ignacio