Updates to IS-IS TLV Codepoints Registry
draft-ietf-isis-tlv-codepoints-01

The information below is for an old version of the document
Document Type Active Internet-Draft (isis WG)
Last updated 2014-08-12
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Christian Hopps
Shepherd write-up Show (last changed 2014-07-14)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Needs 6 more YES or NO OBJECTION positions to pass.
Responsible AD Alia Atlas
Send notices to isis-chairs@tools.ietf.org, draft-ietf-isis-tlv-codepoints@tools.ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state None
Networking Working Group                                     L. Ginsberg
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                         August 12, 2014
Expires: February 13, 2015

                Updates to IS-IS TLV Codepoints Registry
                 draft-ietf-isis-tlv-codepoints-01.txt

Abstract

   This document recommends some editorial changes to the IANA IS-IS TLV
   Codepoints registry to more accurately document the state of the
   protocol.  It also sets out new guidelines for Designated Experts to
   apply when reviewing allocations from the registry.

Requirements Language

   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 RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

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

   This Internet-Draft will expire on February 13, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Ginsberg                Expires February 13, 2015               [Page 1]
Internet-Draft             isis-tlv-codepoints               August 2014

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IS Neighbor sub-TLV Registry  . . . . . . . . . . . . . . . .   3
   3.  Prefix Reachability sub-TLV Registry  . . . . . . . . . . . .   3
   4.  Guidance for Designated Experts . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informational References  . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The IS-IS TLV Codepoints registry was created by [RFC3563] and
   extended by [RFC6233].  The assignment policy for the registry is
   "Expert Review" as defined in [RFC5226].  As IS-IS related documents
   are developed, the codepoints required for the protocol extensions
   are reviewed by the Designated Experts and added to the IANA managed
   registry.  As these documents are published as RFCs, the registries
   are updated to reference the relevant RFC.

   In the case of TLVs supporting prefix advertisement, currently
   separate sub-TLV registries are maintained for each TLV.  These
   registries need to be combined into a common sub-TLV registry similar
   to what has been done for neighbor advertisement TLVs.
Show full document text