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

Operation of the IP Flow Information Export (IPFIX) Protocol on IPFIX Mediators

TL;DR: This document specifies the operation of the IP Flow Information Export (IPFIX) protocol specific to IPFIX Mediators, including Template and Observation Point management, timing considerations, and other Mediator-specific concerns.

Sieve Email Filtering: Extension for Notifications

TL;DR: This draft describes an extension to the Sieve mail filtering language that allows users to give specific rules for how and when notifications should be sent, and clarifies that a notification mechanism can treat some URI parameters as an error.

Mixed Security Mode for the Two-Way Active Measurement Protocol (TWAMP)

Al Morton, +1 more
TL;DR: This memo describes a simple extension to TWAMP - the Two-Way Active Measurement Protocol, which adds the option to use different security modes in the TWAMP-Control and TWamp-Test protocols simultaneously.

YANG data model for BGP Segment Routing Extensions

TL;DR: This document defines a YANG data model that can be used to configure and manage Segment Routing extensions in BGP.

FCAST: Object Delivery for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) Protocols

TL;DR: This document introduces the FCAST reliable object (e.g., file) delivery application, designed to operate either on top of the underlying Asynchronous Layered Coding (ALC) / Layering Coding Transport (LCT) reliable multicast transport protocol or the NACK- Oriented Reliable Multicast (NORM) transport protocol.
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)