RFC 3769: Requirements for IPv6 Prefix Delegation
In plain English — editorial summary, not part of the RFC
This document describes requirements for how IPv6 address prefixes should be delegated to an IPv6 subscriber's network (or "site"). This memo provides information for the Internet community.
Document record
- Document ID
- RFC3769
- Published
- June 2004
- Authors
- S. Miyakawa; R. Droms
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4068Fast Handovers for Mobile IPv6Obsoleted
July 2005
- RFC 4140Hierarchical Mobile IPv6 Mobility Management (HMIPv6)Obsoleted
August 2005
- RFC 4291IP Version 6 Addressing ArchitectureUpdated
February 2006
- RFC 4294IPv6 Node RequirementsObsoleted
April 2006
- RFC 4311IPv6 Host-to-Router Load SharingCurrent
November 2005
- RFC 4429Optimistic Duplicate Address Detection (DAD) for IPv6Updated
April 2006
- RFC 4620IPv6 Node Information QueriesCurrent
August 2006
- RFC 4640Problem Statement for bootstrapping Mobile IPv6 (MIPv6)Current
September 2006
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?