Defining the Role and Function of IETF Protocol Parameter Registry Operators
draft-ietf-iasa2-rfc6220bis-03

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

• Versions
• 00
• 01
• 02
• 03

Internet Architecture Board(IAB)                       D. McPherson, Ed.
Internet-Draft                                           O. Kolkman, Ed.
Obsoletes: 6220 (if approved)                                       ISOC
Intended status: Informational                           J. Klensin, Ed.
Expires: June 13, 2019
                                                          G. Huston, Ed.
                                                                   APNIC
                                                                     IAB
                                                       December 10, 2018

   Defining the Role and Function of IETF Protocol Parameter Registry
                               Operators
                     draft-ietf-iasa2-rfc6220bis-03

Abstract

   Many Internet Engineering Task Force (IETF) protocols make use of
   commonly defined values that are passed in messages or packets.  To
   ensure consistent interpretation of these values between independent
   implementations, there is a need to ensure that the values and
   associated semantic intent are uniquely defined.  The IETF uses
   registry functions to record assigned protocol parameter values and
   their associated semantic intentions.  For each IETF protocol
   parameter, it is current practice for the IETF to delegate the role
   of Protocol Parameter Registry Operator to a nominated entity.  This
   document provides a description of, and the requirements for, these
   delegated functions.

[Cover Note]

   [The IASA2 WG asks the IAB to publish this replacement for RFC 6220.
   This document is changed for alignment with the new structure for the
   IETF Administrative Support Activity (IASA). ]

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

McPherson, et al.         Expires June 13, 2019                 [Page 1]
Internet-Draft         Role of Registry Operators          December 2018

   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 June 13, 2019.

Copyright Notice

   Copyright (c) 2018 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
   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.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Roles and Responsibilities Concerning IETF Protocol Parameter
       Registries  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Protocol Parameter Registry Operator Role . . . . . . . .   4
     2.2.  IAB Role  . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.3.  IESG Role . . . . . . . . . . . . . . . . . . . . . . . .   8
     2.4.  Role of the IETF Trust  . . . . . . . . . . . . . . . . .   8
     2.5.  Role of the IETF Administration Limited         Liability
           Company . . . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Miscellaneous Considerations  . . . . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Informative References  . . . . . . . . . . . . . . . . . . .  10
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  11
   Appendix B.  IAB members  . . . . . . . . . . . . . . . . . . . .  11
   Appendix C.  Document Editing Details . . . . . . . . . . . . . .  11
     C.1.  Version Information . . . . . . . . . . . . . . . . . . .  12
       C.1.1.  draft-iab-iasa2-rfc6220-00  . . . . . . . . . . . . .  12
       C.1.2.  draft-iab-iasa2-rfc6220-01  . . . . . . . . . . . . .  12
       C.1.3.  draft-iab-iasa2-rfc6220-02  . . . . . . . . . . . . .  12
       C.1.4.  draft-iab-iasa2-rfc6220-03  . . . . . . . . . . . . .  12
     C.2.  RCS information . . . . . . . . . . . . . . . . . . . . .  13
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

McPherson, et al.         Expires June 13, 2019                 [Page 2]