Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism
RFC 8026
Revision differences
Document history
Date | By | Action |
---|---|---|
2016-11-17
|
(System) | IANA registries were updated to include RFC8026 |
2016-11-15
|
(System) | Received changes through RFC Editor sync (created alias RFC 8026, changed title to 'Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism', … Received changes through RFC Editor sync (created alias RFC 8026, changed title to 'Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism', changed abstract to 'In IPv6-only provider networks, transporting IPv4 packets encapsulated in IPv6 is a common solution to the problem of IPv4 service continuity. A number of differing functional approaches have been developed for this, each having their own specific characteristics. As these approaches share a similar functional architecture and use the same data plane mechanisms, this memo specifies a DHCPv6 option, whereby a single instance of Customer Premises Equipment (CPE) can interwork with all of the standardized and proposed approaches to providing encapsulated IPv4-in-IPv6 services by providing a prioritization mechanism.', changed pages to 11, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2016-11-15, changed IESG state to RFC Published) |
2016-11-15
|
(System) | RFC published |