RFC 2754: RPS IANA Issues
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6254.
Current version: RFC 6254 — Request to Move RFC 2754 to Historic Status
In plain English — editorial summary, not part of the RFC
RPS Security requires certain RPSL objects in the IRR to be hierarchically delegated. The set of objects that are at the root of this hierarchy needs to be created and digitally signed by IANA. This paper presents these seed objects and lists operations required from IANA. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2754
- Published
- January 2000
- Authors
- C. Alaettinoglu; C. Villamizar; R. Govindan
- Status
- HISTORIC
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 6254
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3171IANA Guidelines for IPv4 Multicast Address AssignmentsObsoleted
August 2001
- RFC 5771IANA Guidelines for IPv4 Multicast Address AssignmentsCurrent
March 2010
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 2434Guidelines for Writing an IANA Considerations Section in RFCsObsoleted
October 1998
- RFC 2036Observations on the use of Components of the Class A Address Space within the InternetCurrent
October 1996
- RFC 1917An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANACurrent
February 1996
- RFC 1881IPv6 Address Allocation ManagementCurrent
December 1995
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?