HOME





Mapping Of Address And Port
Mapping of Address and Port (MAP) is a proposal that combines A+P port address translation with the tunneling of legacy IPv4 protocol packets over an ISP's internal IPv6 network. MAP uses the extra bits available in the IPv6 address to contain the extra port range identifier bits of the A+P addressing pair that cannot be encoded directly into the IPv4 address, thus eliminating the need for "port routing" within the carrier network by leveraging the provider's own IPv6 rollout. In effect, MAP is an (almost) stateless alternative to Carrier-grade NAT and DS-Lite that pushes the IPv4 IP address/port translation function (and therefore the maintenance of NAT state) entirely into the existing customer premises equipment IPv4 NAT implementation, thus avoiding the NAT444 and statefulness problems of carrier-grade NAT. See also * DS-Lite * IPv4 Residual Deployment (4rd) IPv4 Residual Deployment (4rd) is an IPv6 transition mechanism for Internet service providers for deployment of In ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


Address Plus Port
The Address plus Port (A+P) within the network layer communications protocol for Internet networking is an experimental approach to the IPv4 address shortage. It is a technique for sharing single IPv4 addresses among several users without using stateful network address translation (NAT) in the carrier network. Normal routing only uses the IPv4 address to identify which host an IP packet is destined for. A+P uses the destination TCP or UDP port in addition to the IP address to extend the range of available host addresses. Each host is assigned a unique range of ports which they set as the source port in outbound packets and which they use to receive inbound traffic. A+P is a stateless alternative to conventional stateful NAT, as the A+P gateway does not need to keep track of every TCP or UDP flow. However, it does require A+P aware software at the end-point, capable of limiting the range of port numbers used for originating connections to its allocated range, either in the end ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


picture info

Carrier-grade NAT
Carrier-grade NAT (CGN or CGNAT), also known as large-scale NAT (LSN), is a type of Network address translation (NAT) for use in IPv4 network design. With CGNAT, end sites, in particular residential networks, are configured with private network addresses that are translated to public IPv4 addresses by middlebox network address translator devices embedded in the network operator's network, permitting the sharing of small pools of public addresses among many end sites. This shifts the NAT function and configuration thereof from the customer premises to the Internet service provider network (though "conventional" NAT on the customer premises will often be used additionally). Carrier-grade NAT is often used for mitigating IPv4 address exhaustion. One use scenario of CGN has been labeled as NAT444, because some customer connections to Internet services on the public Internet would pass through three different IPv4 addressing domains: the customer's own private network, the carrier's ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


picture info

DS-Lite
An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host. To meet its technical criteria, IPv6 must have a straightforward transition plan from the current IPv4. The Internet Engineering Task Force (IETF) conducts working groups and discussions through the IETF Internet Drafts and Request for Comments processes to develop these transition technologies towards that goal. Some basic IPv6 transition mechanisms are defined in RFC 4213. Stateless IP/ICMP Translation Stateless IP/ ICMP Translation (SIIT) translates between the packet header formats in IPv6 and IPv4. The SIIT method defines a class of IPv6 addresse ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]  


IPv4 Residual Deployment (4rd)
IPv4 Residual Deployment (4rd) is an IPv6 transition mechanism for Internet service providers for deployment of Internet Protocol version 6 (IPv6), while maintaining IPv4 service to customers. The protocol and sample applications are specified in RFC 7600. Features IPv4 Residual Deployment has three main features: *Mesh topology: between two endpoints, IPv4 packets take the same direct routes as IPv6 packets. *Shared IPv4 addresses: to deal with the unavoidable IPv4-address shortage, several customers can be assigned a common IPv4 address, with disjoint TCP/UDP port sets assigned to each (an application of the general A+P model of RFC 6346). *Stateless operation: conversions of IPv4 packets into IPv6 packets at domain entry, and the reverse at domain exit, are stateless (i.e., one where ''no per-customer state'' is needed in domain edge nodes). Compared to other IETF-specified mechanisms having the same main features, i.e., MAP-E (RFC 7597, RFC 7598, RFC 2473) and MAP-T (RFC ...
[...More Info...]      
[...Related Items...]     OR:     [Wikipedia]   [Google]   [Baidu]