RFC 7084: Basic Requirements for IPv6 Customer Edge Routers
In plain English — editorial summary, not part of the RFC
This document specifies requirements for an IPv6 Customer Edge (CE) router. Specifically, the current version of this document focuses on the basic provisioning of an IPv6 CE router and the provisioning of IPv6 hosts attached to it. The document also covers IP transition technologies. Two transition technologies in RFC 5969's IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) and RFC 6333's Dual-Stack Lite (DS-Lite) are covered in the document. The document obsoletes RFC 6204.
Document record
- Document ID
- RFC7084
- Published
- November 2013
- Authors
- H. Singh; W. Beebee; C. Donley; B. Stark
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 21
- Also known as
- —
- Obsoletes:
- RFC 6204
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 7678Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional SolutionsCurrent
October 2015
- RFC 6324Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed MitigationsCurrent
August 2011
- RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent
July 2015
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 6334Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack LiteCurrent
August 2011
- RFC 7857Updates to Network Address Translation (NAT) Behavioral RequirementsCurrent
April 2016
- RFC 8026Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization MechanismCurrent
November 2016
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
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?