scispace - formally typeset
Open Access

Guidelines for Writing an IANA Considerations Section in RFCs Status of this Memo This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.

T. Narten, +1 more
Reads0
Chats0
TLDR
In this article, the authors discuss issues that should be considered in formulating a policy for assigning values to a name space and provide guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.
Abstract
Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication algorithm for IPSec). To insure that such quantities have consistent values and interpretations in different implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for the IANA to manage a given name space prudently, it needs guidelines describing the conditions under which new values can be assigned. If the IANA is expected to play a role in the management of a name space, the IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA.

read more

Content maybe subject to copyright    Report

Citations
More filters

An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework

TL;DR: This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection, and media recording) and allows other dialog languages to be used and the package also defines elements for auditing package capabilities andIVR dialogs.

A DNS RR Type for Lists of Address Prefixes (APL RR)

P. Koch
TL;DR: This document specifies a new DNS RR type "APL" for address prefix lists, which is primarily used to translate domain names into IPv4 addresses using A RRs (Resource Records).

Forwarding and Control Element Separation (ForCES) Logical Functional Block (LFB) Subsidiary Management

TL;DR: This document introduces the SM LFB class, an L FB class that specifies the configuration parameters of an FE, and provides manipulation of debug mechanisms along with a general purpose attribute definition to describe configuration information.

A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)

TL;DR: This specification defines a Uniform Resource Name (URN) namespace for the Global System for Mobile Communications Association (GSMA) and a Namespace Specific String (NSS) for the International Mobile station Equipment Identity (IMEI) as well as an associated parameter for the international Mobile station equipment Identity and Software Version number (IMEISV).

PB-TNC: A Posture Broker (PB) Protocol Compatible with Trusted Network Connect (TNC)

TL;DR: This document specifies PB-TNC, a Posture Broker Protocol identical to the Trusted Computing Group's IF-TNCCS 2.0 protocol, and evaluates it against the requirements defined in the NEA Requirements specification.
References
More filters

Key words for use in RFCs to Indicate Requirement Levels

S. Bradner
TL;DR: This document defines these words as they should be interpreted in IETF documents as well as providing guidelines for authors to incorporate this phrase near the beginning of their document.

Security Architecture for the Internet Protocol

R. Atkinson
TL;DR: This document describes an updated version of the "Security Architecture for IP", which is designed to provide security services for traffic at the IP layer, and obsoletes RFC 2401 (November 1998).

A Border Gateway Protocol 4 (BGP-4)

Yakov Rekhter, +1 more
TL;DR: This document, together with its companion document, "Application of the Border Gateway Protocol in the Internet", define an inter- autonomous system routing protocol for the Internet.

Internet Protocol

J. Postel
TL;DR: Along with TCP, IP represents the heart of the Internet protocols and has two primary responsibilities: providing connectionless, best-effort delivery of datagrams through an internetwork; and providing fragmentation and reassembly of data links to support data links with different maximum transmission unit (MTU) sizes.
Journal ArticleDOI

A security architecture for the Internet protocol

TL;DR: The design, rationale, and implementation of a security architecture for protecting the secrecy and integrity of Internet traffic at the Internet Protocol (IP) layer, which includes a modular key management protocol, called MKMP, is presented.
Related Papers (5)