References from draft-ietf-softwire-unified-cpe
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| BCP 26 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3315 |
Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
| RFC 6333 |
Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6334 |
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-Stack Lite
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7341 |
DHCPv4-over-DHCPv6 (DHCP 4o6) Transport
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7596 |
Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7597 |
Mapping of Address and Port with Encapsulation (MAP-E)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7598 |
DHCPv6 Options for Configuration of Softwire Address and Port-Mapped Clients
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7599 |
Mapping of Address and Port using Translation (MAP-T)
References Referenced by |
Proposed Standard | informatively references |