References from draft-liu-softwire-experience-map
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-cordeiro-softwire-experience-mapt |
Experience from MAP-T Testing
References Referenced by |
informatively references | ||
| draft-hazeyama-widecamp-ipv6-only-experience |
Experiences from IPv6-Only Networks with Transition Technologies in the WIDE Camp Autumn 2012
References Referenced by |
informatively references | ||
| draft-ietf-softwire-map |
Mapping of Address and Port with Encapsulation (MAP-E)
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-softwire-map-t |
Mapping of Address and Port using Translation (MAP-T)
References Referenced by |
Proposed Standard | normatively references | |
| draft-xli-softwire-map-testing |
MAP Interoperability Testing Results
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 6144 |
Framework for IPv4/IPv6 Translation
References Referenced by |
Informational | Possible Reference | |
| RFC 6586 |
Experiences from an IPv6-Only Network
References Referenced by |
Informational | informatively references |