RFC 5207: NAT and Firewall Traversal Issues of Host Identity Protocol (HIP) Communication

The Host Identity Protocol (HIP) changes the way in which two Internet hosts communicate. One key advantage over other schemes is that HIP does not require…

Read RFC 5207 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2663: IP Network Address Translator (NAT) Terminology and Considerations
Normative reference — RFC 4423: Host Identity Protocol (HIP) Architecture
Normative reference — RFC 5201: Host Identity Protocol
Normative reference — RFC 3948: UDP Encapsulation of IPsec ESP Packets
Informative reference — RFC 4303: IP Encapsulating Security Payload (ESP)
Informative reference — RFC 3234: Middleboxes: Taxonomy and Issues
Informative reference — RFC 3489: STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
Informative reference — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Informative reference — RFC 5206: End-Host Mobility and Multihoming with the Host Identity Protocol
Informative reference — RFC 4091: The Alternative Network Address Types (ANAT) Semantics for the Session Description Protocol (SDP) Grouping Framework
Informative reference — RFC 5190: Definitions of Managed Objects for Middlebox Communication

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap
Informatively referenced by — RFC 7402: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol (HIP)
Informatively referenced by — RFC 6538: The Host Identity Protocol (HIP) Experiment Report