Anything In Anything
Encyclopedia : A : AN : ANY : Anything In Anything
| Layer | Protocols |
|---|---|
| Application | DNS, TLS/SSL, TFTP, FTP, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP, SNMP, SSH, TELNET, BitTorrent, RTP, rlogin, … |
| Transport | TCP, UDP, DCCP, SCTP, IL, RUDP, |
| Network | IP (IPv4, IPv6), ICMP, IGMP, ARP, RARP, … |
| Link | Ethernet, Wi-Fi, Token ring, Point-to-Point Protocol>PPP, SLIP, FDDI, ATM, DTM, Frame Relay, SMDS, … |
Anything In Anything or AYIYA is a draft tunnelling protocol.
Many users are currently located behind NATs 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.
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.
| Bits 0 - 7 | 8 - 15 | 16 - 23 | 24 - 31 | |||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0 | Identity Type | SignatureType | Next Header | Reserved | ||||||||||||||||||||||||||||
| 32 | Epoch Time | |||||||||||||||||||||||||||||||
| Identity | ||||||||||||||||||||||||||||||||
| Signature | ||||||||||||||||||||||||||||||||
For IPv6 over IPv4-UDP operation, as in general use, the Identity is the IPv6 Address of the endpoint (16 bytes) and the signature is a SHA1 hash (20 bytes). The header is then a total of 32 + 16 + 20 = 68 bytes.
More details on the [SixXS] site: [AYIYA]
From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.