RFC 4007: IPv6 Scoped Address Architecture
In plain English — editorial summary, not part of the RFC
This document specifies the architectural characteristics, expected behavior, textual representation, and usage of IPv6 addresses of different scopes. According to a decision in the IPv6 working group, this document intentionally avoids the syntax and usage of unicast site-local addresses. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4007
- Published
- March 2005
- Authors
- S. Deering; B. Haberman; T. Jinmei; E. Nordmark; B. Zill
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 24
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4014Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information OptionUpdated
February 2005
- RFC 4016Protocol for Carrying Authentication and Network Access (PANA) Threat Analysis and Security RequirementsCurrent
March 2005
- RFC 3993Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
March 2005
- RFC 4022Management Information Base for the Transmission Control Protocol (TCP)Current
March 2005
- RFC 4030The Authentication Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent OptionCurrent
April 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
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?