Move Kerberos protocol parameter registries to IANA
draft-ietf-kitten-kerberos-iana-registries-04

Document Type Active Internet-Draft (kitten WG)
Last updated 2017-03-30
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                              T. Yu
Internet-Draft                                   MIT Kerberos Consortium
Updates: rfc4120 (if approved)                            March 30, 2017
Intended status: Standards Track
Expires: October 1, 2017

          Move Kerberos protocol parameter registries to IANA
             draft-ietf-kitten-kerberos-iana-registries-04

Abstract

   The Keberos 5 network authentication protocol has several numeric
   protocol parameters.  Most of these parameters are not currently
   under IANA maintenance.  This document requests that IANA take over
   the maintenance of the remainder of these Kerberos parameters.

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 October 1, 2017.

Copyright Notice

   Copyright (c) 2017 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
   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.

Yu                       Expires October 1, 2017                [Page 1]
Internet-Draft          Kerberos IANA registries              March 2017

1.  Requirements Notation

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

2.  Introduction

   The Keberos 5 network authentication protocol[RFC4120][RFC1510] has
   several numeric protocol parameters.  This document requests that
   IANA take over the maintenance of the Kerberos protocol parameters
   that are not currently under IANA maintenance.  Several instances of
   number conflicts in Kerberos implementations could have been
   prevented by having IANA registries for those numbers.  This document
   updates [RFC4120].

3.  General registry format

   Unless otherwise specified, each Kerberos protocol number registry
   will have the following fields: "number", "name", "reference", and
   "comments".

   The name must begin with a lowercase letter, and must consist of
   ASCII letters, digits, and hyphens.  Two or more hyphens must not
   appear directly adjacent to each other.  A hyphen must not appear at
   the end of a name.  It is preferred that words in a name be separated
   by hyphens, and that all of the letters be lowercase.

   (These rules are consistent with the lexical rules for an ASN.1
   valuereference or identifier.  Where the constraints are stricter
   than the ASN.1 lexical rules, they make it easier to systematically
   transform the names for use in implementation languages.)

   Names for numeric parameter values have no inherent meaning in the
   Kerberos protocol, but they can guide choices for internal
   implementation symbol names and for user-visible non-numeric
   representations.  When written in English prose in specifications, or
   when used as symbolic constants in implementation languages (e.g., C
   preprocessor macros), it is common to transform the name into all
   uppercase letters, and possibly to replace hyphens with underscores.

4.  General registration procedure

   This document requests that the IESG establish a pool of Kerberos
   experts who will manage the Kerberos registries using these
   guidelines.  The IESG may wish to consider including the set of
   designated IANA experts for existing Kerberos IANA registries as
   candidates for this pool.

Yu                       Expires October 1, 2017                [Page 2]
Show full document text