Browse Prior Art Database

Network Address Translation - Protocol Translation (NAT-PT) (RFC2766)

IP.com Disclosure Number: IPCOM000003364D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 18 page(s) / 47K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Tsirtsis: AUTHOR [+2]

Abstract

This document specifies an IPv4-to-IPv6 transition mechanism, in addition to those already specified in [TRANS]. This solution attempts to provide transparent routing, as defined in [NAT-TERM], to end-nodes in V6 realm trying to communicate with end-nodes in V4 realm and vice versa. This is achieved using a combination of Network Address Translation and Protocol Translation. The scheme described does not mandate dual-stacks (i.e., IPv4 as well as V6 protocol support) or special purpose routing requirements (such as requiring tunneling support) on end nodes. This scheme is based on a combination of address translation theme as described in [NAT-TERM] and V6/V4 protocol translation theme as described in [SIIT].

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group G. Tsirtsis

Request for Comments: 2766 BT

Category: Standards Track P. Srisuresh

Campio Communications

February 2000

Network Address Translation - Protocol Translation (NAT-PT)

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This document specifies an IPv4-to-IPv6 transition mechanism, in

addition to those already specified in [TRANS]. This solution

attempts to provide transparent routing, as defined in [NAT-TERM], to

end-nodes in V6 realm trying to communicate with end-nodes in V4

realm and vice versa. This is achieved using a combination of Network

Address Translation and Protocol Translation. The scheme described

does not mandate dual-stacks (i.e., IPv4 as well as V6 protocol

support) or special purpose routing requirements (such as requiring

tunneling support) on end nodes. This scheme is based on a

combination of address translation theme as described in [NAT-TERM]

and V6/V4 protocol translation theme as described in [SIIT].

Acknowledgements

Special thanks to Pedro Marques for reviewing an earlier version of

this memo. Also, many thanks to Alan O'Neill and Martin Tatham, as

the mechanism described in this document was initially developed

through discussions with them.

Table of Contents

1. Introduction.................................................. 2

2. Terminology................................................... 3

2.1 Network Address Translation (NAT)......................... 4

2.2 NAT-PT flavors............................................ 4

2.2.1 Traditional-NAT-PT................................... 4

2.2.2 Bi-directional-NAT-PT................................ 5

2.3 Protocol Translation (PT)................................. 5

2.4 Application Level Gateway (ALG)........................... 5

2.5 Requirements.............................................. 5

3. Traditional-NAT-PT operation (V6 to V4)....................... 6

3.1 NAT-PT Outgoing Sessions.................................. 6

3.2 NAPT-PT Outgoing Sessions................................. 7

4. Use of DNS-ALG for Address assignment......................... 8

4.1 V4 Address Assignment for Incoming Connections (V4 to V6). 9

4.2 V4 Address Assignment for Outgoing Connections (V6 to V4). 11

5. Protocol Translation Detail...