References from draft-cui-softwire-pet-framework
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 |
|---|---|---|---|---|
| RFC 1702 |
Generic Routing Encapsulation over IPv4 networks
References Referenced by |
Informational | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2529 |
Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2765 |
Stateless IP/ICMP Translation Algorithm (SIIT)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2766 |
Network Address Translation - Protocol Translation (NAT-PT)
References Referenced by |
Historic | normatively references | |
| RFC 2767 |
Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)
References Referenced by |
Informational | normatively references | |
| RFC 2893 |
Transition Mechanisms for IPv6 Hosts and Routers
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3089 |
A SOCKS-based IPv6/IPv4 Gateway Mechanism
References Referenced by |
Informational | normatively references | |
| RFC 3338 |
Dual Stack Hosts Using "Bump-in-the-API" (BIA)
References Referenced by |
Experimental | normatively references | |
| RFC 4213 |
Basic Transition Mechanisms for IPv6 Hosts and Routers
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5565 |
Softwire Mesh Framework
References Referenced by |
Proposed Standard | normatively references |