One document matched: draft-arberg-pppoe-iana-00.txt

PPP Extensions Working Group
Internet Draft                                              Peter Arberg
                                                        Redback Networks
Intended status: Best Current Practice 
Expiration Date: April 2006                              Vince Mammoliti
                                                           Cisco Systems


                                                            October 2005





           IANA Considerations for PPP over Ethernet (PPPoE)

                    draft-arberg-pppoe-iana-00.txt


Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups. Note that other
   groups may also distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


Copyright Notice

   Copyright (C) The Internet Society (2005).


Abstract

   This document describes the IANA considerations for the PPP over 
   Ethernet (PPPoE) protocol.





Arberg                    Expires April 2006                    [Page 1]

Internet Draft        draft-arberg-pppoe-iana-00.txt        October 2005


Table of Contents

   1. Introduction.............................................    2
     1.1 Terminology...........................................    2
     1.2 Specification of Requirements.........................    2
   2. IANA Considerations......................................    3
     2.1 Recommended Registration Policies.....................    3
     2.2 Reserved PPPoE TAG Values.............................    3
   3. Security Considerations..................................    4
   4. Normative References.....................................    4
     4.1 Informative References................................    4
   5. Author's Address.........................................    4
   6. Full Copyright Statement.................................    5
   7. Intellectual Property Statement..........................    5


1. Introduction

   This document provides guidance to the Internet Assigned Numbers
   Authority (IANA) regarding the registration of values related to 
   the PPP over Ethernet Protocol (PPPoE), defined in [RFC2516], in
   accordance with BCP 26, [RFC2434].  It also reserves PPPoE TAG
   values that are or have been in use on the Internet.


1.1 Terminology

   The following terms are used here with the meanings defined in
   BCP 26:  "name space", "assigned value", "registration".

   The following policies are used here with the meanings defined in
   BCP 26: "Private Use", "First Come First Served", "Expert Review",
   "Specification Required", "IETF Consensus", "Standards Action".


1.2 Specification of Requirements

   In this document, several words are used to signify the requirements
   of the specification.  These words are often capitalized.  The key
   words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
   "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document
   are to be interpreted as described in [RFC2119].










Arberg                    Expires April 2006                    [Page 2]

Internet Draft        draft-arberg-pppoe-iana-00.txt        October 2005


2. IANA Considerations

   The PPPoE protocol as defined in [RFC2516] defines one name space 
   that requires registration, the PPPoE TAG.


2.1 Recommended Registration Policies

   IANA needs to set up a registry of "PPPoE TAG Values". These are
   16-bit values. PPPoE TAG values already in use are specified as 
   reserved in this document, all other TAG values between 0 and 65535 
   are to be assigned by IANA, using the "First Come First Served" 
   policy defined in [RFC2434]. 

   A TAG-Name and a point of contact MUST be provided for any assignment 
   from this registry.

   If a specification description exists, a reference to this SHOULD
   also be provided.


2.2 Reserved PPPoE TAG Values

   TAG Value            TAG Name                         Reference
   --------------       -------------------------        ---------
   0       0x0000       End-Of-List                      [RFC2516]
   
   257     0x0101       Service-Name                     [RFC2516]
   258     0x0102       AC-Name                          [RFC2516]
   259     0x0103       Host-Uniq                        [RFC2516]
   260     0x0104       AC-Cookie                        [RFC2516]
   261     0x0105       Vendor-Specific                  [RFC2516]
   262     0x0106       Credits                          [BERRY]
   263     0x0107       Metrics                          [BERRY]
   264     0x0108       Sequence Number                  [BERRY]

   272     0x0110       Relay-Session-Id                 [RFC2516]
   273     0x0111       HURL                             [CARREL]
   274     0x0112       MOTM                             [CARREL]
   
   288     0x0120       PPP-Max-Payload                  [ARBERG]
   289     0x0121       IP_Route_Add                     [CARREL]
   
   513     0x0201       Service-Name-Error               [RFC2516]
   514     0x0202       AC-System-Error                  [RFC2516]
   515     0x0203       Generic-Error                    [RFC2516]
   





Arberg                    Expires April 2006                    [Page 3]

Internet Draft        draft-arberg-pppoe-iana-00.txt        October 2005


3. Security Considerations

   This document focuses on IANA considerations, and does not have 
   security considerations.


4. Normative References

   [RFC2119]      Bradner, S., "Key words for use in RFCs to Indicate
                  Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2434]      Narten, T. and H. Alvestrand, "Guidelines for Writing
                  an IANA Considerations Section in RFCs", BCP 26, RFC
                  2434, October 1998.

   [RFC2516]      Mamakos L., Lidl K., Evarts J., Carrel D., Simone D., 
                  Wheeler R., "A Method for Transmitting PPP Over 
                  Ethernet (PPPoE)", RFC 2516, February 1999


4.1 Informative References

   [CARREL]       Carrel D., Simone D., Ho C., Stoner T., "Extensions 
                  to a Method for Transmitting PPP Over Ethernet 
                  (PPPoE)", work in progress.

   [BERRY]        Berry B., Holgate H., "PPP Over Ethernet (PPPoE) 
                  Extensions for Credit Flow and Link Metrics", 
                  work in progress.

   [ARBERG]       Arberg P., Kourkouzelis D., Duckett M., Anschutz T., 
                  Moisand J., "Accommodating an MTU/MRU greater than 
                  1492 in PPPoE", work in progress.


5. Author Information

   Peter Arberg 
   Redback Networks, Inc.
   300 Holger Way
   San Jose, CA 95134
   USA
   Email: parberg@redback.com

   Vince Mammoliti
   Cisco Systems, Inc.
   181 Bay Street, Suite 3400
   Toronto, Ontario, M5J 2T3
   Canada
   EMail: vince@cisco.com


Arberg                    Expires April 2006                    [Page 4]

Internet Draft        draft-arberg-pppoe-iana-00.txt        October 2005


6. Full Copyright Statement

   Copyright (C) The Internet Society (2005).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


7. Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr@ietf.org.


Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.






Arberg                    Expires April 2006                    [Page 5]