Many users are currently located behind NAT NAT's which prohibit the usage of proto-41 IPv6 in IPv4 tunnels [RFC3056] unless they manually reconfigure their NAT setup which in some cases is impossible as the NAT cannot be configured to forward proto-41 [RFC1933] to a specific host. There might also be cases when multiple endpoints are behind the same NAT, when multiple NATs are used or when the user has no control at all over the NAT setup. This is an undesired situation as it limits the deployment of IPv6 [RFC3513], which was meant to solve the problem of the disturbance in end to end communications caused by NATs, which where created because of limited address space in the first place. IPv6, or Internet Protocol version 6, is a network layer standard; i. ...
This problem can be solved easily by tunneling the IPv6 packets over either UDP, TCP or even SCTP. Taking into consideration that multiple separate endpoints could be behind the same NAT and/or that the public endpoint can change on the fly, there is also a need to identify the endpoint that certain packets are coming from and endpoints need to be able to change e.g. source addresses of the transporting protocol on the fly while still being identifiable as the same endpoint. The protocol described in this document is independent of the transport and payload's protocol. An example could be IPv6-in-UDP-in-IPv4, which is a typical setup that can be used by IPv6 Tunnel Brokers. The abbreviation UDP can refer to: User Datagram Protocol Usenet Death Penalty Ulster Democratic Party Uridine-diphosphate, cf. ... TCP is an abbreviation of: Transmission Control Protocol Thermal conversion process, another name for thermal depolymerization Top Cow Productions Tool Center Point of a robot A number of chemical substances: Trichlorophenol, a fungicide Trichlorophenylmethyliodosalicyl, a germicide, see TCP (antiseptic) Tricresylphosphate, a lubricant, gasoline additive, plasticizer, and flame retardant Two Component... SCTP, or Stream Control Transmission Protocol is a transport layer protocol defined in 2000 by the IETF. The protocol is defined in RFC 2960, and an introductory text is provided by RFC 3286. ...
The type of identity used by an AYIYA tunnel is negotiated either manually or automatically outside of this protocol, these fields are included to allow verification of the type and also to allow multiple types to be used by one receiver at the same time.
AYIYA is capable of crossing any NAT because an AYIYA receiver uses the AYIYA port as the source port and the address that received the initial AYIYA packet from the client as a source address, Restricted Cone NATs, Port-Restricted Cone NATs and Symmetric NATs can be traversed.
AYIYA could be used in a mobility situation for tunneling its Home Address back to the Home Agent, thus acting as a normal tunnel situation and for the Remote Host it seems the communication is happening directly.
9.1 Using AYIYA for IPv6 Tunnel Brokers The main scenario where AYIYA is intended to be used is for solving the problem where an IPv4 host is behind a NAT and wants to tunnel to a Tunnel Server [RFC3056].
The AYIYA packet includes an identity, thus the endpoint address of the client does not need to be known and the tunnel can be brought and kept up at wish by the user when its client notifies the Tunnel Server of its existence by sending AYIYA packets.
Massar Expires January 5, 2005 [Page 22] Internet-Draft AYIYA: Anything In Anything July 2004 9.4 Mobility using AYIYAAYIYA could be used in a mobility situation for tunneling its Home Address back to the Home Agent, thus acting as a normal tunnel situation and for the Remote Host it seems the communication is happening directly.
Feeds |
Contact