31.07.2015 Views

network protocols handbook.pdf

network protocols handbook.pdf

network protocols handbook.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

27Protocols GuideTCP/IP - Application Layer ProtocolsProtocol NameNAT: Network Address TranslationProtocol DescriptionBasic Network Address Translation (Basic NAT) is a methodby which IP addresses are mapped from one group to another,transparent to end users. Network Address Port Translation, orNAPT, is a method by which many <strong>network</strong> addresses and theirTCP/UDP ports are translated into a single <strong>network</strong> address andits TCP/UDP ports. Together, these two operations, referred toas traditional NAT, provide a mechanism to connect a realm withprivate addresses to an external realm with globally unique registeredaddresses.The need for IP Address translation arises when a <strong>network</strong>’sinternal IP addresses cannot be used outside the <strong>network</strong> eitherfor privacy reasons or because they are invalid for use outsidethe <strong>network</strong>. Network topology outside a local domain canchange in many ways. Customers may change providers, companybackbones may be reorganized, or providers may mergeor split. Whenever external topology changes with time, addressassignment for nodes within the local domain must also changeto reflect the external changes. Changes of this type can behidden from users within the domain by centralizing changes toa single address translation router. Basic Address Translationallows hosts in a private <strong>network</strong> to transparently access theexternal <strong>network</strong> and enable access to selected local hosts fromthe outside. Organizations with a <strong>network</strong> setup predominantlyfor internal use and with a need for occasional external accessare good candidates for this scheme.There are limitations to using the translation method. It is mandatorythat all requests and responses pertaining to a sessionbe routed via the same NAT router. One way to ascertain thiswould be to have NAT based on a border router that is uniqueto a stub domain, where all IP packets either originated from thedomain or are destined for the domain. There are other ways toensure this with multiple NAT devices.The NAT solution has the disadvantage of taking away the endto-endsignificance of an IP address, and making up for this withan increased state in the <strong>network</strong>. As a result, with a NAT deviceenroute, end-to-end IP <strong>network</strong> level security assured by IPSeccannot be assumed to apply to end hosts. The advantage of thisapproach, however, is that it can be installed without changesto hosts or routers.Protocol StructureNAT is a procedure, not a structured protocol.Related <strong>protocols</strong>IP, IPv6, TCP, UDP, NATPSponsor SourceNAT is defined by IETF (http://www.ietf.org) in RFC 3022.Referencehttp://www.javvin.com/protocol/rfc3022.<strong>pdf</strong>Traditional IP Network Address Translator (Traditional NAT)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!