NAT Port Mapping Protocol (NAT-PMP) is a network protocol for establishing network address translation (NAT) settings and port forwarding configurations automatically without user effort.[1] The protocol automatically determines the external IPv4 address of a NAT gateway, and provides means for an application to communicate the parameters for communication to peers. Apple introduced NAT-PMP in 2005 by as part of the Bonjour specification, as an alternative to the more common ISO Standard Internet Gateway Device Protocol implemented in many NAT routers. The protocol was published as an informational Request for Comments (RFC) by the Internet Engineering Task Force (IETF) in RFC 6886.
NAT-PMP runs over the User Datagram Protocol (UDP) and uses port number 5351 on the server, whilst port 5350 is used on the client, as per spec. It has no built-in authentication mechanisms because forwarding a port typically does not allow any activity that could not also be achieved using STUN methods. The benefit of NAT-PMP over STUN is that it does not require a STUN server and a NAT-PMP mapping has a known expiration time, allowing the application to avoid sending inefficient keep-alive packets.
NAT-PMP is the predecessor of the Port Control Protocol (PCP).
YouTube Encyclopedic
-
1/3Views:74 30557 65710 554
-
Port Forwarding Explained
-
MicroNugget: What is N.A.T. (Network Address Translation)
-
NAT Explained | Overload, Dynamic & Static
Transcription
See also
- Port Control Protocol (PCP)
- Internet Gateway Device Protocol (UPnP IGD)
- Universal Plug and Play (UPnP)
- NAT traversal
- STUN
- Zeroconf
References
- ^ NAT Port Mapping Protocol (NAT-PMP). IETF. April 1, 2013. doi:10.17487/RFC6886. RFC 6886.
 | This computer networking article is a stub. You can help Wikipedia by expanding it. |
 | This article about Apple Inc. is a stub. You can help Wikipedia by expanding it. |
This page was last edited on 31 May 2024, at 03:00