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
Independent Submissions to the RFC Editor
John C. Klensin,David G. Thaler +1 more
TL;DR: This document discusses the Independent Submission model and some reasons why it is important, and describes editorial and processing norms that can be used for Independent Submissions as the community goes forward into new relationships between the IETF community and its primary technical publisher.
Mutual Authentication Protocol for HTTP
TL;DR: This scheme provides true mutual authentication between an HTTP client and an HTTP server using password-based authentication using the user's encrypted password.
The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Option
Ted Lemon,Mark Stapp +1 more
TL;DR: An authentication suboption for the Dynamic Host Configuration Protocol Relay Agent Information Option is defined, containing a keyed hash in its payload, which supports data integrity and replay protection for relayed DHCP messages.
Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) Parameters
TL;DR: This document details the parameters of the Aggregate Server Access Protocol (ASAP) and Endpoint Handlespace Redundancy Protocol (ENRP) protocols defined within the Reliable Server Pooling (RSerPool) architecture.
Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations Status of This Memo
TL;DR: This memo defines an Experimental Protocol for the Internet community that is designed to accelerate IP handover between wireless access routers and the ICMP subtype extension format for Seamoby.
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