Re: [Gen-art] Re: Gen-art review of draft-bberry-pppoe-credit-04.txt

Brian E Carpenter <brc@zurich.ibm.com> Tue, 03 January 2006 13:56 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtmeE-00042I-DP; Tue, 03 Jan 2006 08:56:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtmeC-00042D-Hj for gen-art@megatron.ietf.org; Tue, 03 Jan 2006 08:56:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25963 for <gen-art@ietf.org>; Tue, 3 Jan 2006 08:55:03 -0500 (EST)
Received: from mtagate4.uk.ibm.com ([195.212.29.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtmjP-0003pg-VW for gen-art@ietf.org; Tue, 03 Jan 2006 09:01:44 -0500
Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id k03Dt9i9056590 for <gen-art@ietf.org>; Tue, 3 Jan 2006 13:55:13 GMT
Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k03Dt9FI190722 for <gen-art@ietf.org>; Tue, 3 Jan 2006 13:55:09 GMT
Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id k03Dt8cm005477 for <gen-art@ietf.org>; Tue, 3 Jan 2006 13:55:09 GMT
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id k03Dt7jK005448; Tue, 3 Jan 2006 13:55:08 GMT
Received: from zurich.ibm.com (sig-9-145-135-150.de.ibm.com [9.145.135.150]) by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id OAA68542; Tue, 3 Jan 2006 14:54:59 +0100
Message-ID: <43BA8231.8090906@zurich.ibm.com>
Date: Tue, 03 Jan 2006 14:54:57 +0100
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Mark Townsley <townsley@cisco.com>
Subject: Re: [Gen-art] Re: Gen-art review of draft-bberry-pppoe-credit-04.txt
References: <43B57671.6050609@dial.pipex.com> <43B9650E.3020405@cisco.com>
In-Reply-To: <43B9650E.3020405@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: hholgate@cisco.com, Margaret Wasserman <margaret@thingmagic.com>, bberry@cisco.com, gen-art@ietf.org, James Carlson <james.d.carlson@sun.com>
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Mark Townsley wrote:
> 
> Focusing on one point (authors, please respond to the other issues 
> directly)
> 
> Elwyn Davies wrote:
> 
>>  Even were it to be published I am unclear why this document should be
>>  Informational. It is documenting a proposed extension to a standard
>>  (although, if the authors wished, it could have made use of the
>>  existing Vendor-specific tag and then it would legitimately have been
>>  an Informational document on that front - the new message types are
>>  another matter) and as such ought to be aiming for PS.
> 
> 
> This document is extending PPPoE, which by no means is a standard of any 
> kind. I'm not sure what status other than Informational I could ask for 
> here.

You can't, but that leads to another question - why isn't PPoE a standards
track protocol? I blinked back when that happened, apparently. It seems
to me we need to address that question before thinking about PPoE extensions.
(As far as I understand it, this draft extendes the PPoE code number space,
not a general PPP code space.)
> 
>>
>>  Assuming this document is approved, it needs an IANA considerations
>>  section. I think that it effectively creates two registries for
>>  PPPoE discovery message ids and discovery option tags which (AFAICS)
>>  weren't setup by RFC2516 although the TAG registry is implicit in the
>>  wording of RFC2516.

I don't know the history of 2516 but it seems to be a poster child for why
we require IANA Considerations sections now.
>>
> 
> We intend to ask for an IANA space for the PPPoE tag registry. For this, 
> and other PPPoE extensions.
> 
> draft-arberg-pppoe-iana-00.txt

That covers the tags but not the codes. RFC 2516 defines 8-bit codes
like 0x09 and draft-bberry adds several more like 0x0A. So I think that
field needs a registry too.

In any case, since you agree that this needs an IANA registry, it can't be
an RFC Editor submission, period.

     Brian




_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art