RFC 2663:IP Network Address Translator (NAT) Termi...
RFC-Ref

IP Network Address Translator (NAT) Terminology and Considerations


1. Introduction and Overview
2. Terminology and concepts used
2.1. Address realm or realm
2.2. Transparent routing
2.3. Session flow vs. Packet flow
2.4. TU ports, Server ports, Client ports
2.5. Start of session for TCP, UDP and others
2.6. End of session for TCP, UDP and others
2.7. Public/Global/External network
2.8. Private/Local network
2.9. Application Level gateway (ALG)
3. What is NAT?
3.1. Transparent Address Assignment
3.1.1. Static Address assignment
3.1.2. Dynamic Address assignment
3.2. Transparent routing
3.2.1. Address binding
3.2.2. Address lookup and translation
3.2.3. Address unbinding
3.3. ICMP error packet translation
4. Various flavors of NAT
4.1. Traditional NAT (or) Outbound NAT
4.1.1. Basic NAT
4.1.2. Network Address Port Translation (NAPT)
4.2. Bi-directional NAT (or) Two-Way NAT
4.3. Twice NAT
4.4. Multihomed NAT
5. Realm Specific IP (RSIP)
5.1. Realm Specific Address IP (RSA-IP)
5.2. Realm Specific Address and port IP (RSAP-IP)
6. Private Networks and Tunnels
6.1. Tunneling translated packets
6.2. Backbone partitioned private Networks
7. NAT operational characteristics
7.1. FTP support
8. NAT limitations
8.1. Applications with IP-address Content
8.2. Applications with inter-dependent control and data sessions
8.3. Debugging Considerations
8.4. Translation of fragmented FTP control packets
8.5. Compute intensive
9. Security Considerations
10. REFERENCES
11. Authors' Addresses
12. Full Copyright Statement
13. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org