Skip to main content

References to RFC 7597

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.

Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.

Document Title Status Type Downref
RFC 7618
As draft-ietf-softwire-map
Dynamic Allocation of Shared IPv4 Addresses
References Referenced by
Proposed Standard normatively references
RFC 7678 Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions
References Referenced by
Proposed Standard normatively references
RFC 8389 Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)
References Referenced by
Proposed Standard normatively references
RFC 8512 A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)
References Referenced by
Proposed Standard normatively references
RFC 8585 Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service
References Referenced by
Informational normatively references
RFC 8676 YANG Modules for IPv4-in-IPv6 Address plus Port (A+P) Softwires
References Referenced by
Proposed Standard normatively references
RFC 9313 Pros and Cons of IPv6 Transition Technologies for IPv4-as-a-Service (IPv4aaS)
References Referenced by
Informational normatively references
RFC 9386 IPv6 Deployment Status
References Referenced by
Informational normatively references
draft-ietf-v6ops-framework-md-ipv6only-underlay Framework of Multi-domain IPv6-only Underlay Network and IPv4-as-a-Service
References Referenced by
informatively references
RFC 7596 Lightweight 4over6: An Extension to the Dual-Stack Lite Architecture
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 informatively references
RFC 7599 Mapping of Address and Port using Translation (MAP-T)
References Referenced by
Proposed Standard informatively references
RFC 7620
As draft-ietf-softwire-map
Scenarios with Host Identification Complications
References Referenced by
Informational informatively references
RFC 7703 Experience with Testing of Mapping of Address and Port Using Translation (MAP-T)
References Referenced by
Informational informatively references
RFC 7721 Security and Privacy Considerations for IPv6 Address Generation Mechanisms
References Referenced by
Informational informatively references
RFC 8026 Unified IPv4-in-IPv6 Softwire Customer Premises Equipment (CPE): A DHCPv6-Based Prioritization Mechanism
References Referenced by
Proposed Standard informatively references
RFC 8114 Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
References Referenced by
Proposed Standard informatively references
RFC 8219 Benchmarking Methodology for IPv6 Transition Technologies
References Referenced by
Informational informatively references
RFC 8517 An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective
References Referenced by
Informational informatively references
RFC 8539 Softwire Provisioning Using DHCPv4 over DHCPv6
References Referenced by
Proposed Standard informatively references
RFC 8658 RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
References Referenced by
Proposed Standard informatively references
RFC 9066 Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home
References Referenced by
Proposed Standard informatively references
RFC 9099 Operational Security Considerations for IPv6 Networks
References Referenced by
Informational informatively references