Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries
draft-ietf-idr-bgp-ls-registry-01

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01

IDR Group                                                      A. Farrel
Internet-Draft                                        Old Dog Consulting
Updates: 7752 (if approved)                                 May 21, 2020
Intended status: Standards Track
Expires: November 22, 2020

Updates to the Allocation Policy for the Border Gateway Protocol - Link
                  State (BGP-LS) Parameters Registries
                   draft-ietf-idr-bgp-ls-registry-01

Abstract

   RFC 7752 defines Border Gateway Protocol - Link State (BGP-LS).  IANA
   created a registry consistent with that document called the "Border
   Gateway Protocol - Link State (BGP-LS) Parameters Registry" with a
   number of sub-registries.  The allocation policy applied by IANA for
   those policies is "Specification Required" as defined in RFC 8126.

   This document updates RFC 7752 by changing the allocation policy for
   all of the registries to "Expert Review" and by updating the guidance
   to the Designated Experts.

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 https://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 November 22, 2020.

Copyright Notice

   Copyright (c) 2020 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Farrel                  Expires November 22, 2020               [Page 1]
Internet-Draft           BGP-LS Registry Update                 May 2020

   publication of this document.  Please review these documents
   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Guidance for Designated Experts . . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4

1.  Introduction

   Border Gateway Protocol - Link State (BGP-LS) [RFC7752] requested
   IANA to create a registry consistent called the "Border Gateway
   Protocol - Link State (BGP-LS) Parameters Registry" with a number of
   sub-registries.  The allocation policy applied by IANA for those
   policies is "Specification Required" as defined in [RFC8126].

   The "Specification Required" policy requires evaluation of any
   assignment request by a "Designated Expert" and guidelines for any
   such experts are given in section 5.1 of [RFC7752].  In addition,
   this policy requires "the values and their meanings must be
   documented in a permanent and readily available public specification,
   in sufficient detail so that interoperability between independent
   implementations is possible" [RFC8126].  Further, the intention
   behind "permanent and readily available" is that "a document can
   reasonably be expected to be findable and retrievable long after IANA
   assignment of the requested value" [RFC8126].

   It is often considered that it is the responsibility of the
   Designated Expert to make a determination as to whether a
   specification meets the requirement to be permanent and readily
   publicly available.  A degree of contention arises in this case
   because Internet-Drafts are now permanently archived in the IETF&s
   tools archive, yet each such document is marked with a piece of
   boilerplate text as follows that brings doubt about its suitability
   as a permanent record:

      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

Farrel                  Expires November 22, 2020               [Page 2]