RFC 7598: DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
In plain English — editorial summary, not part of the RFC
This document specifies DHCPv6 options, termed Softwire46 options, for the provisioning of Softwire46 Customer Edge (CE) devices. Softwire46 is a collective term used to refer to architectures based on the notion of IPv4 Address plus Port (A+P) for providing IPv4 connectivity across an IPv6 network.
Document record
- Document ID
- RFC7598
- Published
- July 2015
- Authors
- T. Mrugalski; O. Troan; I. Farrer; S. Perreault; W. Dec; C. Bao; L. Yeh; X. Deng
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
- Updated by:
- RFC 8539
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 7653DHCPv6 Active LeasequeryCurrent
October 2015
- RFC 7753Port Control Protocol (PCP) Extension for Port-Set AllocationCurrent
February 2016
- RFC 7839Access-Network-Identifier Option in DHCPCurrent
June 2016
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
- RFC 7341DHCPv4-over-DHCPv6 (DHCP 4o6) TransportCurrent
August 2014
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7969Customizing DHCP Configuration on the Basis of Network TopologyCurrent
October 2016
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?