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,H. Alvestrand +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
Citations
More filters
Best Current Practice for Communications Services in Support of Emergency Calling
James Polk,Brian Rosen +1 more
TL;DR: This memo describes best current practice on how devices, networks, and services using IETF protocols should use such standards to make emergency calls.
Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful Restart
Reshad Rahman,Arun Satyanarayana +1 more
TL;DR: This document describes extensions to the Resource Reservation Protocol (RSVP) Graceful Restart mechanisms defined in RFC 3473 that enable the recovery of RSVP signaling state based on the Path message last sent by the node being restarted.
ReportDOI
Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
TL;DR: This document specifies the DOTS signal channel, a protocol for signaling the need for protection against Distributed Denial-of- Service (DDoS) attacks to a server capable of enabling network traffic mitigation on behalf of the requesting client.
Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
TL;DR: This document defines extensions to GMPLS routing and signaling protocols so as to support the operation of Generalized Multi Protocol Label Switching Multi- Layer/Multi- Region Networks.
Address Resolution for Instant Messaging and Presence
TL;DR: This document provides guidance for locating the resources associated with URIs that employ two Universal Resource Identifier schemes: 'im' for instant inboxes and 'pres' for PRESENTITIES.
References
More filters
Key words for use in RFCs to Indicate Requirement Levels
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
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,T. Li +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
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)
IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers 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.
S. Bradner,V. Paxson +1 more