RFC 4787

E546374

RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RFC 4787 canonical 1

Statements (49)

Predicate Object
instanceOf IETF RFC
standards document
addresses ICMP handling by NATs
NAT hairpinning support
NAT mapping and filtering consistency
NAT traversal issues for UDP
fragmentation handling by NATs
interoperability of NATs with UDP-based applications
port preservation behavior
appliesTo IPv4 NAT
area Transport
BCPNumber BCP 127 NERFINISHED
category Best Current Practice
defines behavioral requirements for NAT devices
requirements for endpoint-independent filtering
requirements for endpoint-independent mapping
requirements for hairpinning behavior
requirements for port assignment behavior
requirements for timer handling for UDP mappings
terminology for NAT behaviors
focusesOn NAT behavioral requirements
Network Address Translation
unicast UDP traffic
goal improve interoperability of NATs with UDP applications
standardize NAT behavior for unicast UDP
hasSuccessor RFC 5382 NERFINISHED
RFC 5508 NERFINISHED
RFC 7857 NERFINISHED
intendedFor designers of NAT devices
implementers of NAT devices
network operators
language English
obsoletedBy RFC 7857 NERFINISHED
obsoletes none
protocol UDP
publishedBy Internet Engineering Task Force
surface form: IETF

Internet Engineering Task Force
publisher RFC Editor NERFINISHED
relatedTo RFC 5382
RFC 5508 NERFINISHED
RFC 7857 NERFINISHED
scope unicast traffic
series Request for Comments NERFINISHED
status Best Current Practice
stream Internet Engineering Task Force
surface form: IETF
title Network Address Translation (NAT) Behavioral Requirements for Unicast UDP NERFINISHED
updatesBehaviorOf NAT devices
workingGroup BEHAVE NERFINISHED
Behavior Engineering for Hindrance Avoidance (BEHAVE) NERFINISHED

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.

RFC 6146 updates RFC 4787