datatracker.ietf.org
Sign in
Version 5.6.3, 2014-09-19
Report a bug

Layer Two Tunneling Protocol (L2TP) Internet Assigned Numbers Authority (IANA) Considerations Update
RFC 3438

Document type: RFC - Best Current Practice (December 2002; No errata)
Also Known As BCP 68
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 3438 (Best Current Practice)
Responsible AD: Thomas Narten
IESG Note: published
Send notices to: <mark@townsley.net>

Network Working Group                                        W. Townsley
Request for Comments: 3438                                 Cisco Systems
BCP: 68                                                    December 2002
Category: Best Current Practice

                  Layer Two Tunneling Protocol (L2TP)
    Internet Assigned Numbers Authority (IANA) Considerations Update

Status of this Memo

   This document specifies an Internet Best Current Practices for the
   Internet Community, and requests discussion and suggestions for
   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document describes updates to the Internet Assigned Numbers
   Authority (IANA) considerations for the Layer Two Tunneling Protocol
   (L2TP).

Table of Contents

   1. Introduction.............................................    1
     1.1 Terminology...........................................    2
   2. IANA Considerations......................................    2
     2.1 Control Message AVPs..................................    3
     2.2 Message Type AVP Values...............................    3
     2.3 Result Code AVP Values................................    3
     2.4 Remaining Values......................................    3
   3. Normative References.....................................    3
   4. Security Considerations..................................    4
   5. Acknowledgements.........................................    4
   6. Author's Address.........................................    4
   7. Full Copyright Statement.................................    5

1. Introduction

   This document provides guidance to the Internet Assigned Numbers
   Authority (IANA) regarding the registration of values related to the
   Layer Two Tunneling Protocol (L2TP), defined in [RFC2661], in
   accordance with BCP 26, [RFC2434].

Townsley                 Best Current Practice                  [Page 1]
RFC 3438                L2TP IANA Considerations           December 2002

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".

2. IANA Considerations

   L2TP [RFC2661] defines a number of "magic" numbers to be maintained
   by the IANA.  This section updates the criteria to be used by the
   IANA to assign additional numbers in each of these lists.

   Each of the values identified in this document that require a
   registration criteria update are currently maintained by IANA and
   have a range of values from 0 to 65 535, of which a very small number
   have been allocated (the maximum number allocated within any one
   range is 46) [L2TP-IANA].  Given the nature of these values, it is
   not expected that any will ever run into a resource allocation
   problem if registration allocation requirements are relaxed from
   their current state.

   The recommended criteria changes for IANA registration are listed in
   the following sections.  In one case, the registration criteria is
   currently defined as First Come First Served and should be made more
   strict, others are defined as IETF Consensus and need to be relaxed.
   The relaxation from IETF Consensus is motivated by specific cases in
   which values that were never intended to be vendor-specific have had
   to enter early field trials or be released in generally available
   products with vendor-specific values while awaiting documents to be
   formalized.  In most cases, this results in products that have to
   support both the vendor-specific value and IETF value indefinitely.

   For registration requests where a Designated Expert should be
   consulted, the responsible IESG Area Director should appoint the
   Designated Expert.

   For registration requests requiring Expert Review, the Designated
   Expert should consult relevant WGs as appropriate (e.g., the l2tpext
   WG at the time of this writing).

   The basic guideline for the Expert Review process will be to approve
   the assignment of a value only if there is a document being advanced
   that clearly defines the values to be assigned, and there is active

Townsley                 Best Current Practice                  [Page 2]
RFC 3438                L2TP IANA Considerations           December 2002

   implementation development (perhaps entering early field or

[include full document text]