References from draft-xie-v6ops-ipv6-development-chinatelecom
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 127 |
References Referenced by |
normatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 4787 |
Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
References Referenced by |
Best Current Practice | normatively references | |
RFC 6144 |
Framework for IPv4/IPv6 Translation
References Referenced by |
Informational | normatively references | |
RFC 6333 |
Dual-Stack Lite Broadband Deployments Following IPv4 Exhaustion
References Referenced by |
Proposed Standard | normatively references | |
RFC 7219 |
SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7596 |
Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
References Referenced by |
Proposed Standard | normatively references | |
RFC 7599 |
Mapping of Address and Port using Translation (MAP-T)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8200 |
Internet Protocol, Version 6 (IPv6) Specification
References Referenced by |
Internet Standard | normatively references | |
STD 86 |
References Referenced by |
normatively references |