RFC4380

Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)

We propose here a service that enables nodes located behind one or more IPv4 Network Address Translations (NATs) to obtain IPv6 connectivity by tunneling packets over UDP; we call this the Teredo service. Running the service requires the help of "Teredo servers" and "Teredo relays". The Teredo servers are stateless, and only have to manage a small fraction of the traffic between Teredo clients; the Teredo relays act as IPv6 routers between the Teredo service and the "native" IPv6 Internet. The relays can also provide interoperability with hosts using other transition mechanisms such as "6to4". [STANDARDS TRACK]

pozycje od 4 do 4 z 53, strona 4 z 53

< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 > >>

RFC 4380                         Teredo                    February 2006


2.  Definitions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   This specification uses the following definitions:

2.1.  Teredo Service

   The transmission of IPv6 packets over UDP, as defined in this memo.

2.2.  Teredo Client

   A node that has some access to the IPv4 Internet and wants to gain
   access to the IPv6 Internet.

2.3.  Teredo Server

   A node that has access to the IPv4 Internet through a globally
   routable address, and is used as a helper to provide IPv6
   connectivity to Teredo clients.

2.4.  Teredo Relay

   An IPv6 router that can receive traffic destined to Teredo clients
   and forward it using the Teredo service.

2.5.  Teredo IPv6 Service Prefix

   An IPv6 addressing prefix that is used to construct the IPv6 address
   of Teredo clients.

2.6.  Global Teredo IPv6 Service Prefix

   An IPv6 addressing prefix whose value is 2001:0000:/32.

2.7.  Teredo UDP Port

   The UDP port number at which Teredo servers are waiting for packets.
   The value of this port is 3544.

2.8.  Teredo Bubble

   A Teredo bubble is a minimal IPv6 packet, made of an IPv6 header and
   a null payload.  The payload type is set to 59, No Next Header, as
   per [RFC2460].  The Teredo clients and relays may send bubbles in
   order to create a mapping in a NAT.

Huitema                     Standards Track                     [Page 4]

pozycje od 4 do 4 z 53, strona 4 z 53

< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 > >>

RFC4380

Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)

Książki warte uwagi