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

Document Type Expired Internet-Draft (iasa2 WG)
Last updated 2019-06-13 (latest revision 2018-12-10)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-iasa2-rfc6220bis-03.txt

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.

Authors

Danny McPherson (dmcpherson@verisign.com)
Olaf Kolkman (kolkman@isoc.org)
John Klensin (john+ietf@jck.com)
Geoff Huston (gih@apnic.net)
IAB (iab@iab.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)