References from draft-sunq-v6ops-contents-transition
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 | ||
draft-wing-behave-http-ip-address-literals |
Coping with IP Address Literals in HTTP URIs with IPv6/IPv4 Translators
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 2629 |
Writing I-Ds and RFCs using XML
References Referenced by |
Informational | informatively references | |
RFC 4213 |
Basic Transition Mechanisms for IPv6 Hosts and Routers
References Referenced by |
Proposed Standard | normatively references | |
RFC 6052 |
IPv6 Addressing of IPv4/IPv6 Translators
References Referenced by |
Proposed Standard | normatively references | |
RFC 6144 |
Framework for IPv4/IPv6 Translation
References Referenced by |
Informational | normatively references | |
RFC 6145 |
IP/ICMP Translation Algorithm
References Referenced by |
Proposed Standard | normatively references | |
RFC 6146 |
Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
References Referenced by |
Proposed Standard | normatively references | |
RFC 6154 |
IMAP LIST Extension for Special-Use Mailboxes
References Referenced by |
Proposed Standard | normatively references | |
RFC 6219 |
The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition
References Referenced by |
Informational | normatively references |