FFmpeg Servers and Ffmpeg Hosting

Section 1: Introduction
Although the Internet IPv4 protocol was to provide effective service over 20 years
but the new protocol IPv6 offers greater efficiency, and have enough
level addresses IP, greater safety and mobility. In fact, it is useful to assess the benefits we can get the IPv6 protocol over the protocol IPv4. We can upgrade existing IPv4 infrastructure to the next generation Internet Protocol (IPv6) and get the benefits of transition mechanisms.
When IPv4 was designed, most networks have only a few nodes, low bandwidth, high latency and high error rates. The most common applications at the time, FTP, e-mail and so on. In the early 1990s, the computer industry has expanded with the advent of personal computers (PC) market. Also developed the Internet and e-commerce or electronic commerce began. Market demand was the main factor in the Internet revolution. The rapid growth of the Internet were discovered in the early 1990s, was
shows that the IPv4 address space will be completed before the end of the century. In this
sense, some mechanisms that Network Address Translator (NAT), extending the life of IPv4, but it was not a reasonable solution. Today, the market looks quite different than it was in 1980. While FTP and e-mail is very popular today, but new applications like video conferencing, voice-over-IP, e-commerce, Mobile, and etc, has led to the Internet
Engineering Task Force (IETF) to find a new protocol to the Internet, which we call the IPv6.
IPv4 and IPv6 are incompatible protocols. Therefore, the transition to the new protocol would not be painless, and will involve significant costs for service providers and customers. Comparing the costs of transition to non-shift operation or use of IPv4, supporting new services that can help us find the best time to begin the transition process. Each time you start the transition there will be no single "flag days" when all the IPv4 network is transformed into a network of IPv6. On the level of Internet, the transition will be a long
process with the two protocols will coexist for many years. To facilitate the transition has the IETF (Internet Engineering Task Force) set up a working group convened ngtrans (Transition Next Generation) to identify mechanisms to support interoperability between IPv4 and IPv6. In particular, the team has focused on two major problems:
? How IPv6 terminals communicate with the terminals IPv4.
? How to implement IPv6 through an IPv4 network to IPv6 ?islands' associated with IPv4-based Internet to communicate.
This second problem, which is extremely important during the initial phase of IPv6
dissemination, should be incorporated in future reciprocal problem: how to transport
IPv4 to IPv6. However, the discussion of this issue was postponed for the presence of IPv6 to achieve an important point on the Internet.
Work on these problems led to the development of a range of transition, which were aimed at a specific range of uses and applications.
Section 2: IP Overview
Internet Protocol is a set of techniques used by many hosts for transmitting data over
Internet. The current version of Internet protocol is IPv4, which gives a 32-bit address system.
Internet Protocol is a "best effort", which means that no packet of information sent
guaranteed to reach its destination in the same condition it was sent. Often other
protocols used in parallel with the Internet Protocol data, for various reasons
Another must have extremely high fidelity.
Each unit is connected to a network, whether a local area network (LAN) or the Internet,
a file number of Internet. This address is used to identify the product unique to all other devices connected to the network expansion.
2nd 1: Features for IP
IP is a connectionless protocol. This means that he has no idea from one job or session.
Each package is treated as an entity in itself. IP is rather like a postal worker sorting
letters. I do not care if a package is one a lot. This only schedules
packages, one by one, the next point on the route of delivery.
IP is also unconcerned about whether a packet reaches its final destination, or
packets in the original series. No information on a package to
identified as part of a sequence or belonging to a particular task. Therefore, IP
We can tell if the packets were lost or taken off. IP
unreliable protocol. Mechanisms to ensure that data sent will arrive correct and intact provided by higher-level protocols in the suite.
2nd 2: IP Routing
How, then, an IP packet addressed to a computer across the planet to find
route to their destination? The basic mechanism is very simple.
For a local network, each state sees every packet sent by any other country on the LAN.
Normally I would do just the package, addressed to himself, or if
destination is the broadcast address.
The router is different. The router examines each packet, and compares the destination
address with a list of addresses maintained in memory. If it finds an exact match, the
forwards the packet to an address associated with the entry table. It
Associated address, the other network in a point-to-point connection, or
It can be the address of the router next-hop.
If your router does not find a match showing in the table again, this time looking
match for only the network ID portion of the address. Again, if a match is found,
Packages sent to the address associated with this item.
If a match has not yet been found, the router looks to see if a default next hop address
present. If this is the package sent there. If no default address is present, the router sends
ICMP "host unreachable" or "Network unreachable" message to the sender. About
You see this message, it usually indicates that a router failure at some point in
network.
The hard work part of a router is not how it routes packets, but how to create the
board. In the simplest case, the router table is static: it is loaded from a file at startup.
This is sufficient for simple networking. Not even need a special piece of kit for
, because routing functionality is built into IP.
Dynamic routing is more complex. The router table accumulates from transmission
Messages ICMP Router solicitation, in which other routers respond. Routing Protocol
used to find the shortest path to a location. Routes are regularly updated to
depending on traffic conditions and access to a route. But details of how
All this work is outside the scope of this report.
2nd 3: The Future of the Internet
As we can see the Internet will have serious problems a few years. Thanks to
extraordinary growth and restrictions on construction and equipment, is
problems when no more free addresses available for connecting to new hosts or
award of a new entity. At that time, some new web servers set up, no
Most users can sign up for internet service providers and some new machines can be created to access the internet or participate in online games.
There have been various solutions to the problem. A very popular method is to
It returns a global unique address to each computer user, but rather to map
the "private" addresses, and several machines behind an official, worldwide
unique address. This technique is called "Network Address Translation or NAT. The
have problems because the engines behind the global address list could not be addressed,
and as a result, open relationships with those used in online games
Peer-to-peer networks, etc., is possible.
Another approach to the problem of Internet addresses key is to get rid
old Internet protocol with its limited capacity to cope and use a new
protocols that do not have these restrictions. The report, actually a series
protocol used by devices connected to the Internet version now called
TCP / IP (Transmission Control Protocol, Internet Protocol), and version 4 now
use has all the problems described above.
Jump to a different protocol version that has these problems, of course,
required for a new version is available. Indeed, there is a better version.
Version 6 of Internet Protocol (IPv6), allows future studies on the address bar
and create other functions such as privacy, encryption, and better support for
laptops and.
Assuming a basic understanding of how the current IPv4, this report aims
as an introduction to protocol IPv6. Changes in forms of address and name
Resolution covered. After that will be shown how to use IPv6 with a simple, but —
effective transition mechanism called 6to4.
Section 3: IPv6 vs. IPV4
When people say to migrate from IPv4 to IPv6, the question often hear, "Why?".
There are indeed some good reasons to move to the new version:
? Larger address space
? Mobile Support
? Embedded Security
3rd 1: Bigger address space
The biggest address space offered by IPv6 is the most obvious improvement is
IPv4. While the architecture of the Internet today is based on 32-bit wide addresses, the new
version has 128-bit technology available to deal with. Base address of the enlarged
space, solutions that NAT is not used anymore. This allows full, unlimited IP IP connectivity for today based machines as well as future mobile devices such as PDAs and mobile phones will all benefit from full access to IP over GPRS and UMTS.
3rd 2: Mobility
When mentioning mobile devices and IP, it is important to note that a specific protocol
required to support the movement and implementation of this protocol known as "Mobile
IP is one of the requirements for each stack IPv6. So if we have IPv6, would
Supports roaming between different networks, the global notification when
leave one network and enter another. Support for roaming is possible
IPv4 too, but there are a number of obstacles to be jumped to get things
work. With IPv6, there is no need for this as support for mobility was one of the
Planning for IPv6.
3rd 3: Security
In addition to support for mobility, security was another requirement for the successor
Current version of Internet Protocol. As a result, IPv6 protocol stacks required for
include IPsec. IPsec can be validated, encryption and compression of IP traffic.
With the exception of application layer protocols such as SSL or SSH, all IP traffic between two
nodes can not be customizing applications. The advantage is that all
program on a machine can benefit from encryption and authentication, and
policies can be set per-host (or even per-network) basis, not under / service.
Section 4: IPv6
The features of IPv6 in this section.
4th 1: The multiple addresses
In IPv4, the state usually has an IP number for each network or any machine
If the IP stack supports. Only very rare applications like web servers result
machines with more than a number of IP.
In IPv6, is different. For each interface is not only a globally unique IP
address, but there are two other addresses of interest: The link local address,
and site-local address. The link-local address has a prefix fe80:: / 64, and
The bits built by the host interface address EUI64. The link-local address used
To contact the hosts and routers on the same network addresses only
visible or accessible to different subnets. If desired, the choice of either
with global addresses assigned by the supplier, or use site-local addresses. [16]
Site-local addresses assigned network address fec0:: / 10, and subnets and hosts
can be treated just like to providers dedicated network. The only difference is that
addresses are not visible to outside machines, as is another
networks and their site-local addresses to different physical networks. As with 10 s 8
network in IPv4, site-local addresses may be used but should not. For IPv6, the
most common hosts assigned to a local connection and a global address IP. Site-local
Addresses are quite rare today, and not a substitute for the unique in the world
address, if global connectivity is required.
4th 2: Multiple
In IP land, there are three ways to talk to a host: unicast, broadcast and multicast. The
common way to talk about a host of talking directly with a unicast address.
In unicast IPv4 address is "normal" IP address on a single computer;
all tracks assigned address. The broadcast address is used to treat all hosts at the same
IP subnet has the network bits to the network address and all the pieces that hosts the "1"
which can easily be done using the subnet mask, and some work later. Multicast addresses are used to achieve a number of computers in the same multicast group, which can be machines spread across the Internet. Cameras should be multicast groups
specifically to join and there are special numbers used for IPv4 multicast addresses, allocated from the subnet 224 / 8. Multicast is used in both IPv4, and only a few programs that use. In IPv6, unicast addresses are used in the same way as in IPv4, no surprise there all
network and host bits assigned to identify the target network and machine.
Broadcasting is no longer available in IPv6, how it was in IPv4, where multicasting comes into play. Addresses FF:: / 8 network is reserved for multicast applications, and there are two special multicast addresses replacing addresses broadcast by IPv4. One is the "all routers" multicast address, the other is for "all hosts".
The details of IPv6 is generally the method proposed in RFC of the IETF, but chose a platform for conducting the test using the Microsoft Windows 2003. Because of early development, IPv6 protocol stack on Windows 2003 still has many problems, such as issues of fragmentation, there is no support
for IPSec, a local security, etc. …
Microsoft has two different applications both of IPv6 stack for Windows NT 5th 0 and Windows 2003. The old chimney, known as "The Microsoft Research IPv6 Release 1. 4 ", working in both NT 4. 0 and Win2K, the newest batch, called
"The Microsoft IPv6 Technology Preview for Windows 2003" operating environment to Windows 2003. Both stacks requires an existing IPv4 stack previously installed.
Once installed, while ensuring the environment of Windows, support for IPv6, the
creates an entirely new set of routines as "ping6", "tracert6", which is the same
the "ping" and "tracert", but work on the new IPv6 stack. The good part for the implementation of IPv6 is created by Microsoft is that the built-in IPv6 creates the Winsock2 API. ???? ???????? ??? ?? ?????????? ??????? ???????????? ??????????? ???? ?? ?????????? ??? ????????, ??????, ????????? ? ????,
? ??? ???? ??????????????? ??? ?????? ?? ???????? ?????? IPv4 ?????? ??????? ?? ??????
? ?? ????? ??? ?????? ????????? IPv6 ??????.
? ?????????? Internet ?????? 6 ???? ?????????? ?? ??? ?????????? ?????????? ??? ?????????
? ?????????? (IPv4) ??? ??, ???? ??????????????, ????????? ?? ?? ?????? IPv4 ??? ?????? ??????? ????????. IPv6 ???? ?????????? ??? ?? ????????? ??? ????????? ?? ???????????? ???????, ???? ?? ???? ??? ?????? ??? ???????????? ????????? ??? ?? ???????? ???? ??? ????????? ??????? ???????????, ?? ???? 128-????????? bit ??? ??????? FFFF: FFFF: FFFF: FFFF, ??? ?? ??????????? ???
? 340,282,366,920938,463,463,374,607,431,768,211,456 ????????? ???????????. ???? ?????? 1, ???????? ?? ????? ?? ????? ??? IPv6 ???????? IPv4.
? IPv6 header ????? ????? ????? ??? ????? ??? ??????? ??????? 40 bytes. ?? ?????
? IPv6 header ???????????? ????????? ????????.
? ?? ????? ???? ??????????? IPv6 ?????:
? ?????? – ?? 4 bit ??? ???????????????? ??? ?? ?????????? ???? ?????? ??? IP ??? ???? ??????? ?? 6.
? Traffic Class – ????????? ??? ???? ? ??? ????????????? ??? ??????? IPv6. ?? ??????? ????? ??? ????????
? ????? 8 bits. ?? ????? ??????????? ?????????? ???? ?? IPv4 ????? ???
? ???????? ?????.
? Flow Label – ??????? ??? ???? ?? ?????? ?????? ?? ??? ???????????? ????????? ??? ???????
? ?????? ???? ????? ??? ??????????, ??? ??????? ?????? ???????????? ??? ???? ??????????? IPv6
? ????????????. ?? ??????? ????? ??? ?????? ????? 20 bits. ? Flow Label ??????????????? ??? ??-????????
? ?????????, ???? ??????? ??? ??????????? ?? ?????????? ????? (???? ??? ??????). ???
? ?????????? ?????????? router, ? ???????? ???? Label ??????? ?? 0. ?????? ?? ???????? ????????? ???? ?????? ???? ????? ??? ??????????, ? ????? ?????????????? ??? ????????? ?? ???????? ???? ????????. ??????? ?????? ????? – ????????? ?? ???????? ??? ???????? ??????? ??. ?? ??????? ????? ??? ?????? ????? 16 bit. ??????? ?????? ????? ????? ???????????? ??? ???????????? ??? ???????? ??? ???????? ????????? PDU. ?? 16 bits, ??? ??????? ?????? ?? IPv6 ????? 65.535 bytes ?????? ?? ?????????????. ??? ???? ???????? ??????? ??? ??? 65.535 bytes ????? ?? ??????? ?????? ??? ?????? ????? ??????? ?? 0 ??? Jumbo Payload ??????? ??????????????? ???? Hop-by-Hop Options header ????????.
? ??????? Header – ??????? ???? ??? ????? ???????? ???????? (??? ???????) ? ??? ???????????
? ??? ??????? ?????? PDU (???? ?? TCP, UDP, ? ICMPv6). ?? ??????? ????? ??? ?????? ????? 8
? bits. ???? ???????? ??? ??????? ?????????? ???????? ??? ?????????? ??? ?????????, ??? ????
? ????? ??? ???????????????? ???? ????? ?????????? IPv4 ??????????????? ???.
? ???????? Header – Zero ? ???????????? ????????? ???????? ?????? ?? ????? ???????? ??? ?????
? ???????? ?????????. ??? ????? Next Header ???? ??????????? IPv6 ??????? ??? ??????? ????????
? header. ???? ?? ???? ???????? ???????? ????? ??? ???? ????? Next Header ??? ???????
? ??????? header ????????. ???????? ????????? ???????? ??????? ?? ??????? ?????? ???????????
? (?.?. TCP, UDP, ? ICMPv6) ??? ??????????? ??? ??????? ?????? ??????????? ????????? ???????.
? IPv6 header ??? ????????? ???????? ?????????????? ?? ???????? IPv4 ???????? IP ?? ????????. ? ??? ????? ??????????? ????????? IPv6 ????????? ?? ????????? ??? ?? ???????????? ??? ??????????? ??????? ??? ?????????. ?? ???????? ?? ??? ???????? ???? ???????? IPv4, IPv6 headers ???????? ??? ????? ??????? ??????? ??? ?????? ?? ????????? ??? ?? ??????????? ??? ?? ???????? ??? ?????????
? ??? ??????????? ??? ??? ??????????? IPv6.
? Hop ???? – ?????????? ?? ??????? ?????? ??? ?????? ???? ??? ????? ?? ?????? IPv6 ?????? ??
? ?????? ?????? ????????? ??? ?????????. ?? ??????? ????? ??? ?????? ????? 8 bits. ? Hop Limit ????? ????????
? ??? ????? IPv4 TTL ????? ??? ?? ??? ??? ??????? ????? ???????? ????? ?? ?? ?????
? (?? ????????????) ??? ?? ?????? ????? ???? ??? ???????????. ???? ?? Hop ???? ????? 0, ?
? ?????? ???????????? ??? ?? ?????? ICMP ????????????? ?? ???-????????? ????.
? ??????????? ????????? ?????????? ? ????????? IPv6 ??? ??????? ?????????. ?? ??????? ????? 128 bit.
? ????????? ?????????? – ??????????? ?? ????????? IPv6 ??? ????????? ????????. The
? ?? ??????? ????? ??? ????? ????? 128 bit. ???? ???????????? ???????????, ? ?????????? ????????? ???? ??????? ??? ?? ??????
? ????????? ??????????.
? ??????, ??? ??? ???????????? ???????? ???????? ????? ???????, ? ????????? ?????????? ?????? ??
? ??????????? ??? ??????? ??????????? ??????? ??? ????? ???????? ????.
? ????? 5: Transition ??????????
? ???? ?? IPv6 ????? ?????? ??????? ?? ????????, ????? ???????? ??? ?? ???? ??? ??? ??????????
? Internet, ?????? ?? ??????. ??? ???? ?? ???? ?? ??????? ?? ?????? ??? ?????????? ?? 12,
? ?????????? ??? ???????? ???????, ??????????????????? ????????????, ????????? ??????????, … ??? ????????
? ????????? ??? ???? ???? 6 ??? ????????? ??? ??? ?? ???? ???? ??? ?????.
? ???? ????? ??????????, ????? ?? ??????? ??????????? ??????? ??? ?, ?? ????? ??????,
? ?????? ?? ????? ???? ???? ?????, ??? ???? ?????? ??? ?????????? ???? ???? ??? ?? ????? ??? ??????.
? ??????????? ???????? ???????? ??????? ????? ??????????, ????? ?????? ?? ?????? ???? ?? ????????
? ???? ??? 10 ?????? ???????. ??????? ??? ???? ??????????? ????????? ????? ?? ????:
? Dual Stack
? Siit? – ????????? IP / ICMP ???????????
? AIIH – ???????? ??????????? IPv4 ?? IPv6 Global Hosts
? NAT – ?????????? ??????????? – ???? ????????? ??? DNS ??????, ??? ???? ???? ??? ???????? ???????????
? ??????? Broker – ????? ???????? ???????? ????? ??????????? ??? ????????, ???? ???? ?????????? ??????????, ??? ??? ??????????
? 6-??-4 ?????????? – ???????? ????????? ???????? ??? IPv4 ??????? ??? ?? ??????? ??? 6-??-4 ??????
? IPv4 ?? IPv6 tunneling – ????????? ?? ????? ??? ??????????? ???????? ???? ??????????? ????????
? o Host-Host Tunneling
? o Router-Router Tunneling
? o Host-router ??? ??????????? Tunneling
? 5?? 1: Dual Stack:
? ? ?????? ??????? ??? ?? ????????? ?? ????? ??????????? ????? ? ???????? ????? ?????? IP,
? ???? ???? ??? ????????, server, router ? ???? ???????? ??? ?????????? ??? ??????????? ?? ??????? IP ?????? ?? ??????????? ??? ??????????. ?? ????? ??? ????? ???????????? ?????? IPv6 ??????????
? ?????, ??? ??? ????????? IPv4/IPv6 ??? ?????? ?? ???????????? ?? IPv4-???? ????????? ?????? ?? ????? ??? ?? IPv4. ???? ? ?????????? ??? ????? ????????? ??????? ??? ???? ???????????? ??? servers, ????? ????????? ??? ??? ?????????? ??? ?????????? ??? ??? ????? ????????? ???????? ??? ???????. ??????, ?? ????? ??????????? ????? ??? ??????? ????? ? ?????? ?? ??????????
? ??? ????-?????? ?????????? ?? ????? ??????? ????????????, ? ????? ??????? ??? ????? ???????? ??? ??????????? ?????????. ????????, ? ??????????? ????? ??? ?????? ??????? ?? ??????? ??? ?? ????? ?????? ???? ? ?????????? ???? ??????????? ?????? ?? ?????? ??? ?? ???? ??????????? IPv4 ??? ?????? ????? ?? ??????????.
? ??? ?? ??????????? ???? ?? ??????????, ?????? ?????? ??? ??? ????????????? ?????? IPv6-???? ?? ?????? ??? ?? ?????? IPv4 ?? ??????????? ???? ???? ??? ????????? end-to-????? ??????????? ?????? ?????????? ?????????? ???????:
? ? ????? ?????? IP ALG ???????? ??? ????????? ?????? ??? ???????? ????????? ?????????? ??? ?????? ?????? ??? ??-?????????? ?????? ??????????????? ??????????? ????????, ???????????? ?? ?? ????? ?????? ???????????.
? ? NAT-PT (Network Address Translator – ?????????? ???????????) ???????? ??? ????????? ?????? ??? ???????? ????????? ??? ?? ????????? ?????????? ??? ?????? ?????? ??? ?? ???????? ??????? ?? ??????? IP.
? ? Dual ?????????? ????????? ????, ? DSTM, ? ????? ????????? ?? ?????????????? ? ????? ?????? IP ?????????? ????????? ?? ??????????? IPv4 ???????????? ???????? ???? ??????????, ??? ? ????? ??? IPv4 ?? IPv6 tunneling ?? ??????? ?? ?????? ?????? IPv6 ??????? ???????? ???? ????????? IPv4 ??????.
? ?? ??? ????? ?? ?????????? ????????? ????? ??? ????? ????????? ??? ????????? ?????????? ??? ???????????? ??? ?? ?????????? ??? ???????? ??????? IPv4, ?????? ??? ????????? ??????????? ??? ?? ??????. ?? ??? ?? ?????????? ??? ?? IPv4 ????? ?????? ??? ??? ?????? ?? ????? ??? ????? ? ???????? ??? IPv6 ????? ???????? ???????? ??? ?? ???????????? ? ????????? IPv4 ??? IPv6, ??? ?? ????? ?? ????????? ?????????? ???????? ??????? ?? ?? IPv6.
? IPv6 ???????? ?? ??? ???????? ??? ????????????? ??? ?? ??????? ???? ??? ??????? ??????????? ?????????? IPv4, ???? ?????? ??? ?????????? ??? ??? ????????? ??? ???????????, ??? ?????? ??????? ?? ??? ????? ?????? ????????? ????????.
? ????? ?????? ?? ?? ????????? ?????????? IPv4 ??? IPv6 ??????????. ????? ??????? ??? ???????????? / ????????? ??????????? ??? ??????????, ??? ?? IPv6 ??????????? ????? ?????? ??? ????? ?? ???????? ??????????.
? ??? ?????? ?????? ?????? ?????????? ????????? ????? ?? ????? ? ???????? ??? ??? ?????? ??? ??
? ????. ???? ???????? ????????? ??? ?????????? TCP / IP ?????????? ??????? ??? ??? WAN ???????????? ??????, ??? ????????, ???????????? ????????? ??? ????? ??????????, ???? ?? ???????????? ????????? ??????????? ???, ?????, ??? ????????? ???????? ???????????? ?????????. ???? ?? ?????? ???? ?????????? ??? ?? IPv6 ??? ?????????? IPv4, ? ?????????? ?? ????? ????? ??????? ?????????? ??????? ?? ???? ??????????? ??? ??? ???????? ??? ?????????? ????
? ?????????.
? ??? ???? ?????????? ????? ? ????? ??? ???????? ??? ?? ???????? ???? ??????????? ???? ?? ??? ????. ????????
? ?? IPv6 ?????? ??? ?? ???????????? ???? ?? ?????? IPv4 ?? ????????????? ???? ??? ??????? ??? ??? ????? ????? ???????????? ?? IPv6.
? ????? ????????, ???? ?? ?????????? Network Address Translation (NAT-PT)
? ???? ??????????? ?????? IPv6 ?? ?????? IPv4. ?? ???????? ????? ????????? ????? ???
? ????????? ??? IPv4 NAT, ?????? ?? ?????????? ??? ????? ???????????? ?????? ?????????. ???????? ????????? ???????????? ?? ??????????????? ?? ????????? ????. ??????????????? ?????? ?????? ??? ???????? ??????????? ????? ??????????? ?? ??????????????? ?? NAT-PT.
? ?? ????? ??? ?????? ?? ??????????? ?? ?????? ?? ????? ?? ??? ????? ??????-mode ??? ??? ???????? ?????????
? ?????????? IPv4 ??? ?????? ??? ??????. ??? ??? ????????, ??? ???????? ????? ????????? ??? ????????????? ??? ?? IPv6-???? ????????????, ???? ???????? ????? ????????? ??? ??????????? ?? ????? ?????? ?????. ??? ??????????? ??????? ??? Microsoft, ??? ??????????, ???? ??? ????? ?????? ????????????? ??? ????????? ??? ?????????? ?????????? ??? ???? ???????????. ?? ?? ??????, ?? ?????? ????????????? ????????????? ?? ????? ??? ?????? ??????? ??? ?? ??????????????? ?? ???? ??? ???????????. ?? ?????? ?????? ??
? ??????? ??? ? ?????????? ?????? ?????? ??? ????? ? ?????? ?????????. ??? ?????? ?? ??????? ??? ? ??????
? ???????? ??? IPv6 ????? ? ??????? ??????????.
? Dual ?????? IPv4/IPv6
? ???? ?? ???????? ??? ????????? ??? 1990 ?? ?????? ??? ??????????????? ? ????? "Switch ???? ????????, ???????? ???? ??????. "?? ?? ??????, ??????, ?? ????????? ??? ???????????? ??? ??? ????????? ???????. ??? ?? IPv6 ?????????? ???? ?? ??? ????? ?? ????? ?????? ?????? ???? ????????, ?????? ???? ??????. "
? 5?? 2: IPv6 ?? IPv4 tunneling:
? IPv4 ?? IPv6 tunneling ????? ???? ??? ???? ???????????? ?????????? ????????? ??? ?? ????? ??? ?? IPv6
? ????????? / ?????? ??????? ?? ????????? ?????? ????, ??? ??????????? ?? ?? ????????? ?????? IPv4 ?? ??? ???????????? ??????? ????????? ????????? ????????. ???? ? ??????? ????? ?????? IPv6 ????????? ?? ?????? IPv4 ??? ??? ???????? ????????????? ???? ??? ??????? IPv4 ?? ???????? ?????? IPv4 ???? ????????. ??? ????? ??? ?????? ??? ???? ?? ??????
? decapsulated ?? ?? ?????? ?????? IPv6.
? ?? ???????? ????? ?????? ?????? ?????????????? ??? ?????????? ???????????:
? ???? encapsulating ??? datagram ????? TTL ??? ????????? ???????? IP ??? decremented
? ???? ?? ? ??????? ????? ??????????? ?? ?? ????????? ??? ?????????????????, ? ??????
? ????????? ???????? TTL ??? ???? ??????? ???? ?? ???????? encapsulation. ??? ?? ????????? TTL ??
? ????????? ???????? IP ????? ?????, ?? datagram ???????????? ??? ??? ICMP Time Exceeded ?????? ??????????? ???? ?????????.
? ?? ?? ??????, ???? ???????? encapsulator ??? ????? ??? ?????? ????????? ?? TTL = 0.
? ?????????? ??? IPv4 ?? IPv6:
? o ???????????? IPv4 ??????? ??? ?????????.
? o ????? ?????? ?????????????? ??? IPv6.
? o ??????? ??? ????? ??? ?????? ?????????? ??? ?? ???????? ?????? ???? ??? ??????????? 41 (?? ??).
? ???????? ??? ????? ????????: ??????????? ??? ????????. ??????????? ???????? IPv6 ??????? ?????????? ??? ??? ??? ???? ??? ????????, ??? ?? ????????? ???????? ?????????????? ???????? ?? ???? ?? ????????? ?????????? ?????????? ??? ?? ?????????. ???????? tunneling ???????? ???????????? ?????????? ?? ???????? ?? ???????
? ????????? ????????, ???? ???????? ???????? ?? ???????? ?????????? ??????????? ??????? ??? ????
? ??????????? ??????, ??? ???????????? ???? ???????? ???????? ???? ????? ???????????.
? ????? ???????, ???? ??????????????, ???????? ??? ??? ???????? ??? ??????????? ????????. ??? ??????????, ?? ???????? ???????? ??? ????? ?????? ?? ????? ????? ????? ??????????? ???? ??? ????????? ????????, ??? ????? ??? ????????? ??? ?????? ????????? ??? ????????. ????? ??? ?????????? ??????? ???? ???????????? ??? ?? ??????????? ?? ?????? nonauthenticated ????????????. ????? ??????
? ??????? ?? ???????? ??????? ?????? ?? ??? ?????? ?????? ??? ???????? ??? ?? ????????? ?????? ??? ??????????? ??? ???????. Tunneling ?????????? ??????????? ???? ?????? ?? ??????? ?? ?????? ?? ????????????? ??? ??????? ??? ????? firewalls ??? ?? ??????????? ??? ??????, ??? ????? ?? ??? ???????. ????????? IP ?????????? 41 (IPv6 ????????? ?? IPv4) ???? ???? ??????? ?????????? IPv4 ??? ????? ? ????????
? ????????. ????? ??? ?? ?????????? ???? "IPv6 ????????? ?? ?????? ??????????? ?????" ?????? ???? ??? ??????? ??????????.
? ???????? ?? ?????? ??????? ?? ??????? ??? ?? ??????????????? ???????? ??? ????????. ???????? ?? ?????? ?????? ?? ?????????? ???? ? ??????? IPv6 ????????? ??? ???????? ???? ??? ????? IPv6. ????????, ?? ????? ???? ??? ?????????? ??????????, ??? ??? ???????????? ??????????? ?? ??? ?????????? ?????? ??? ???????? ?? ????? ??? ????????.
? ???????? tunneling ??????? ??? ?????????? ???????????? ??????? ??? ?????? ?? ??????????????? ?? SNMP. ???????? tunneling ????????, ???? ? 6-4 ?????? 2002:: / 16 ???????????, ?? ????? ???????? ??? ?? ?????? ?? ??????????? ?? ?????? ??? ?????, ??? ??????? ??? ????????? ??? IPv6.
? ?????? ??? ??? ????????? ???????? ??????????? ?????? ?? ???? ?? ?????????? multicast ??????????? ??? ??? ??????? ?? ?????????? ??? IPv4 NAT ??? ???? ??? ?????????.
? ??? ??? ??????? ????? ?? ????????? ???? ?? ??? ????? ????????????, ?? ????????? ???????? ???????
? ??????? ?? ????????? ?????????? ????????????, ???? ??? ? OSPF. ???? ?? ????????? ??????? ?? ??? ???????????? ?????? ??? ??????????? ????????? ?????????? BGP, ?.??..
? ???? ????????? ??? ??????, ??? ???? ICMP ?????? ?????? ?? ???????, ??????????? ?? ?????????? ?? ??????????? ????? ????? ?????????.
? ?? ??????? ???? ???????????, ???? ?? / ????? ? ?????????? ??? ??????? ????????? ??????? ??
? ???? ??? ??? ????? ??? ????????, ????? ? ?????? ???? ? ????.
? IPv6 tunneling ????????? ? ??????????? iSeries ?? ???????? ?? ?? IPv6 ??????? (hosts ??? routers) ???? ?????? IPv4. Tunneling ?????? ???????????? ?????? IPv6 ? ?????? ?? ???????????? ??? ??? ?????????? ??????? IPv4. Tunneling ????????? ?????????? IPv4 ??? IPv6 ?? ????????????, ??? ?? ?? ?????? ??? ?????????? ??????????
? ???????? ??? IPv6 ??? ? ????????? ??? ???????? ?? ?? IPv4.
? ??? ??????? ??????????? ??? ??? ?????? ?????? (IPv4 ??? IPv6) ?????? ?? ??? ?????? IPv4. ???? ?????? ??????? ?????? ????????? ?? ?????????? ???????????? ???? ?? IPv4 ??? ???????????? IPv6. ??? ??? ?? ???-?????? ??????? ???? ???? ??? ???????? IPv6 ??????? ??? ??????????? IPv4 ??????? (????????) ???? ?????? IPv6, ??? ??????? ??? ?? ??????? ??? ?? ???? ???????? ?????????? IPv4 ???? ??? ??????????? ??????. ???????????? IPv4 ????????? ?? ?????????? ??? ??????? ??????. ??? ??? ???? ?????? ??? ????????, ??? ?????-?????? ????? ??????????? ???????? ???????? IP ??? IPv6 ?????? (decapsulates) ??? ?? ??????? ???? ?????? ????????? ??? ?? ??????? IPv6.
? IPv6 tunneling ??? ??? ????????? ??????? ???????????, ?? ?????? ????? ????????? ???????. ????????? ??????? ???????? ???????? Tunneling IPv6 ?? ???? ????? ?? ??? routable ????????? IPv4, ? ????? ??????????? ?? IPv6 ????????. ????? ?? ?????? ?????? ?? ?????????? ??????????, ?????? ???? ?????? ????? IPv4 ? ?? ???? ????????????? ?????.
? ????????? ????????? ???????? ????? ??????-????-??????. ??? ?? ????????? ??? ??????????? ????? ??? ????? ??? ????????
? ??????, ?????? ?? ?????????? ??? ??????? ?????? ?????? ??? ???????? (????????? IPv4), ???? 124? 10? 10? 150, ??? ? ?????? ????????? IPv6, ???? 1080:0:0:0:8:800:200 c: 417a. Vi m?ste ocks? skapa en IPv6-rutt f?r att m?jligg?ra trafik till sig genom tunneln. N?r vi skapa rutten, kommer vi att definiera en av tunnelns fj?rrkontroll endpoints (IPv4
? adress) eftersom rutten n?sta hop. Vi kan konfigurera ett obegr?nsat antal endpoints
? f?r ett obegr?nsat antal tunnlar.
? 5. 2? 1: Host-to-Host Tunneling
? I v?rd till v?rd tunneling metod, inkapsling sker vid k?llan v?rd och ecapsulation g?rs p? destination v?rd. S? tunneln skapas mellan tv? v?rdar st?der b?de IPv4 och travar IPv6. S? p? detta s?tt inkapslade datapaket skickas genom tunneln ?ver IPv4-n?tverk.
? B?de v?rdar med dubbla skorsten kapslar in paketen av IPv6 i IPv4-paket och s?nder ?ver n?tet som IPv4-paket utnyttja alla de egenskaper och dirigering mekanismer f?r IPv4. With this transition mechanism, it is possible to support IPv6 simply by upgrading the end hosts protocol stacks to IPv6 while leaving the IPv4
? infrastructure unchanged.
? 5?? 2? 2 : Router-to-Router Tunneling
? In router to router tunneling mechanism, encapsulation is done at edge router of
? originating host and decapsulation is done in the same way at edge router of destined host. The tunnel is created in between two edge routers supporting both IPv4 and IPv6 stacks. Therefore, the end hosts can support native IPv6 protocol stack while the edge routers create the tunnels and handle the encapsulation and decapsulation in order to transmit the packets over the existing IPv4 infrastructure.
? The IPv6 datagrams are forwarded from host to edge routers while encapsulation takes place at the router level; similarly at the other end, the reverse process takes place. In this method, both edge routers need to support dual stacks and established a tunnel prior to transmission.
? 5?? 2? 3 : Host-to-Router Tunneling
? In host to router tunneling mechanism, encapsulation is done at originating host and
? decapsulation is done in the same way at edge router of destined host and vice versa.
? The tunnel is created in between one host and one edge router both of them supporting both IPv4 and IPv6 stacks. So in this way encapsulated datagrams are sent through the tunnel over the existing IPv4 network. The same process can happen the other way around, from one edge router to an end host.
? The tunnel is therefore established between the host and the router. In this method one
? dual stack supporting router and one dual stack supporting host is required.
? 5?? 3 : Overlay Tunnels for IPv6
? Overlay tunneling encapsulates IPv6 packets in IPv4 packets for delivery across an
? IPv4 infrastructure (a core network or the Internet). By using overlay tunnels, we can
? communicate with isolated IPv6 networks without upgrading the IPv4 infrastructure
? between them. Overlay tunnels can be configured between border routers or between
? a border router and a host; however, both tunnel endpoints must support both the IPv4
? and IPv6 protocol stacks as we can see in figure
? 4 . Cisco IOS IPv6 supports the
? following types of overlay tunneling mechanisms:
? ? Manual
? ? Generic routing encapsulation (GRE)
? ? IPv4-compatible
? ? 6to4
? ? Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)
? Note Overlay tunnels reduce the maximum transmission unit (MTU) of an interface
? by 20 octets (assuming the basic IPv4 packet header does not contain optional fields).
? A network using overlay tunnels is difficult to troubleshooting. Therefore, overlay tunnels connecting isolated IPv6 networks should not be considered as a final IPv6 network architecture. The use of overlay tunnels should be considered as a transition technique toward a network that supports both the IPv4 and IPv6 protocol stacks or just the IPv6 protocol stack .
? 5?? 5 : GRE/IPv4 Tunnel Support for IPv6 Traffic
? IPv6 traffic can be carried over IPv4 GRE tunnels using the standard GRE tunneling technique that is designed to provide the services necessary to implement any standard point-to-point encapsulation scheme. As in IPv6 manually configured tunnels, GRE tunnels are links between two points, with a separate tunnel for each
? link. The tunnels are not tied to a specific passenger or transport protocol, but in this
? case carry IPv6 as the passenger protocol with the GRE as the carrier protocol and
? IPv4 or IPv6 as the transport protocol.
? The primary use of GRE tunnels is for stable connections that require regular secure
? communication between two edge routers or between an edge router and an end system. The edge routers and the end systems must be dual-stack implementations.
? GRE has a protocol field that identifies the passenger protocol. GRE tunnels allow
? Intermediate System-to-Intermediate System (IS-IS) or IPv6 to be specified as a passenger protocol, which allows both IS-IS and IPv6 traffic to run over the same tunnel. If GRE did not have a protocol field, it would be impossible to distinguish whether the tunnel was carrying IS-IS or IPv6 packets. The GRE protocol field is why
? it is desirable that you tunnel IS-IS and IPv6 inside GRE.
? 5?? 6 : GRE/CLNS Tunnel Support for IPv4 and IPv6 Packets GRE tunneling of IPv4 and IPv6 packets through CLNS networks enables Cisco CLNS Tunnels (CTunnels) to interoperate with networking equipment from other vendors. The optional GRE services defined in header fields, such as checksums, keys, and sequencing, are not supported. Any packet received requesting such
? services will be dropped.
? 5?? 7 : Automatic 6to4 Tunnels
? An automatic 6to4 tunnel allows isolated IPv6 domains to be connected over an IPv4 network to remote IPv6 networks. The key difference between automatic 6to4 tunnels and manually configured tunnels is that the tunnel is not point-to-point; it is point-to-multipoint. In automatic 6to4 tunnels, routers are not configured in pairs because they treat the IPv4 infrastructure as a virtual nonbroadcast multiaccess (NBMA) link. The
? IPv4 address embedded in the IPv6 address is used to find the other end of the automatic tunnel.
? An automatic 6to4 tunnel may be configured on a border router in an isolated IPv6 network, which creates a tunnel on a per-packet basis to a border router in another IPv6 network over an IPv4 infrastructure. The tunnel destination is determined by the IPv4 address of the border router extracted from the IPv6 address that starts with the prefix 2002::/16, where the format is 2002:border-router-IPv4-address::/48. Following the embedded IPv4 address are 16 bits that can be used to number networks within the
? site. The border router at each end of a 6to4 tunnel must support both the IPv4 and IPv6 protocol stacks. 6to4 tunnels are configured between border routers or between a border router and a host.
? The simplest deployment scenario for 6to4 tunnels is to interconnect multiple IPv6 sites, each of which has at least one connection to a shared IPv4 network. This IPv4 network could be the global Internet or a corporate backbone. The key requirement is that each site have a globally unique IPv4 address; the Cisco IOS software uses this address to construct a globally unique 6to4/48 IPv6 prefix. As with other tunnel
? mechanisms, appropriate entries in a Domain Name System (DNS) that map between hostnames and IP addresses for both IPv4 and IPv6 allow the applications to choose the required address.
? 5?? 8 : Automatic IPv4-Compatible IPv6 Tunnels
? Automatic IPv4-compatible tunnels use IPv4-compatible IPv6 addresses. IPv4-compatible IPv6 addresses are IPv6 unicast addresses that have zeros in the high-order 96 bits of the address, and an IPv4 address in the low-order 32 bits. They can be written as 0:0:0:0:0:0:A. B. C. D or ::A. B. C. D, where "A. B. C. D" represents the
? embedded IPv4 address.
? The tunnel destination is automatically determined by the IPv4 address in the low-
? order 32 bits of IPv4-compatible IPv6 addresses. The host or router at each end of an IPv4-compatible tunnel must support both the IPv4 and IPv6 protocol stacks. IPv4-compatible tunnels can be configured between border-routers or between a border-router and a host. Using IPv4-compatible tunnels is an easy method to create tunnels
? for IPv6 over IPv4, but the technique does not scale for large networks.
? IPv4-compatible tunnels were initially supported for IPv6, but are being deprecated. Cisco recommends that you use the IPv6 ISATAP tunneling technique.
? Section 6 : IPV6 Network potential problems
? 6? 1 : Poor IPv6 Network Performance:
? Most applications on dual stack nodes will try IPv6 destinations first by default due
? to the Default Address Selection mechanism. If the IPv6 connectivity to those
? destinations is poor while the IPv4 connectivity is better , the IPv6 traffic experiences higher latency, lower throughput, or more lost packets than IPv4 traffic, applications will still communicate over IPv6 at the expense of network
? performance. There is no information available to applications in this case to advise them to try another destination address. An example of such a situation is a node which obtains IPv4 connectivity natively through an ISP, but whose IPv6 connectivity is obtained through a configured tunnel whose other endpoint is
? topologically such that most IPv6 communication is done through triangular IPv4 paths. Operational experience on the 6bone shows that IPv6 RTT's are poor in such situations. An example of such a network is an enterprise network that has both IPv4 and IPv6 routing within the enterprise and has a firewall configured to allow some IPv4 communication,but no IPv6 ommunication.
? 6? 2 : Security Problems in IPV6 over IPV4:
? Enabling IPv6 on a host implies that the services on the host may be open to IPv6 communication. If the service itself is insecure and depends on a security policy enforced somewhere else on the network (such as in a firewall), then there is
? potential for new attacks against the service.
? A firewall may not be enforcing the same policy for IPv4 as for IPv6 traffic, which could be due to misconfiguration of the firewall. One possibility is that the firewall could have more relaxed policy for IPv6, perhaps by letting all IPv6 packets pass through, or by letting all IPv4 protocol packets pass through. In this scenario, the dual stack hosts within the protected network could be subject to different attacks than for IPv4. Even if a firewall has a stricter policy or identical policy for IPv6 traffic than for
? IPv4 (the extreme case being that it drops all IPv6 traffic), IPv6 packets could go through the network untouched if tunneled over a transport layer. This could open the host to direct IPv6 attacks. It should be noted that IPv4 packets can also be tunneled, so this is not a new security concern for IPv6. Firewalls must be
? deliberately and properly configured.
? A similar problem could exist for virtual private network (VPN) software. A VPN could protect all IPv4 packets but transmit all others onto the local subnet unprotected. At least one widely used VPN behaves this way. This is problematic
? on a dual stack host that has IPv6 enabled on its local network. It establishes its VPN link and attempts to communicate with destinations that resolve to both IPv4 and IPv6 addresses. The destination address selection mechanism prefers the IPv6 destination so the application sends packets to an IPv6 address. The VPN doesn't know about IPv6, so instead of protecting the packets and sending them to the
? remote end of the VPN, it passes such packets in the clear to the local network.
? This is problematic for a number of reasons. The first is that if the node has a default IPv6 route, the packets will be forwarded off-link to an unknown destination.
? Another is if no legitimate router is on-link and the node makes the on-link, the packets will simply be sent onto the local link to be potentially viewed by a node spoofing the destination. A third is if a rogue IPv6 router exists on-link. In that case the malicious node will simply be sent all IPv6 packets in the clear.
? 6? 3 : Finding problems in TCP/IP using IPV6:
? In this part I want to describe the techniques and tools that we can use to help identify
? a problem at successive layers of the Transmission Control Protocol/Internet Protocol
? (TCP/IP) protocol stack that is using an Internet Protocol version 6 (IPv6) Internet layer in Microsoft Windows XP , Windows Server 2003 or Windows Vista.
? Depending on the type of problem, we might do one of the following:
? -Starting from the bottom of the stack and move up.
? -Starting from the top of the stack and move down.
? The following sections are organized from the top of the stack and describe how to:
? -Verify IPv6 connectivity
? -Verify Domain Name System (DNS) name resolution for IPv6 addresses
? -Verify IPv6-based TCP connections
? We can also use Network Monitor to capture IPv6 traffic Although not specified in the following sections, to troubleshoot many problems with IPv6-based communications. Network Monitor is provided with Microsoft Systems Management Server and as an optional network component with Windows Server 2003. However, to correctly interpret the display of IPv6 packets in Network Monitor, we must have
? detailed knowledge of the protocols included in each packet.
? 7? 3?? 1 : Manage Configuration
? To manually configure IPv6 addresses, use the netsh interface ipv6 set address command. In Windows Vista, we can manually configure IPv6 addresses from the properties of the Internet Protocol Version 6 (TCP/IPv6) component, available from the Network Connections folder. In most cases, we do not need to manually configure
? IPv6 addresses because they are automatically assigned for hosts through IPv6 address auto-configuration.
? Also to make changes to the configuration of IPv6 interfaces, we use the netsh interface ipv6 set interface command. To add the IPv6 addresses of DNS servers, use the netsh interface ipv6 add dnsserver command.
? 7? 3?? 2 : Verify Reachability
? To verify reachability with a local or remote destination, try the following:
? ?Check and flush the neighbor cache? . Similar to the Address Resolution Protocol (ARP) cache, the neighbor cache stores recently resolved link-layer addresses. To display the current contents of the neighbor cache, use the netsh interface ipv6 show neighbors command.
? Section 7 : Conclusion
? There are some of mechanisms for network administrators to transition their networks
? from IPv4 to IPv6. The transition technologies I have presented are robust to slowly and incrementally transitioning groups of networks, as well as mixed protocol support of hosts within individual networks.
? My recommendation is using tunneling IPV6 over IPV4 as much as possible to Simplify communications between IPv6 hosts.
? I recommend first using tunneling to support both IPv4 and IPv6 applications, then slowly transitioning to pure IPV6 infrastructure. I believe this gradual process will support legacy systems until they are totally replaced, and this will ready the intranet for an IPv6 internet by the time of IPv4 address exhaustion.
? Microsoft has more software that has no IPv6 support, but alternatives are available and everything still works on IPv4. It will take some time before everything has IPv6 support, until than both IPv6 and IPv4 can coexist together without any problems. Therefore it is advisable to implement IPv6 as much as possible,
? because sooner or later the migration from IPv4 to IPv6 has to be made. Important when deciding to implement IPv6 is to plan everything very carefully. Especially when it comes to services it is important to know whether or not the services installed and configured in your situation are capable of handling IPv6.
? Internet service providers may wait till there are enough IPv6 applications to deploy IPv6 networks, and application developers may wait for the IPv6 network to be deployed first. It is up to servers and application developers to take
? more and more IPv6 into consideration and also all the business sectors to consider migrating to IPv6, and not waiting for others to be the firsts.
? Of course, if everyone waits until the last minute, it could end up costing much
? more not just to engineer the transition, but in the cost of the disruption to what has become a crucial part of our economic and social infrastructure.
? As I wrote a common dual-stack migration strategy is to make the transition from the
? core to the edge. This involves enabling two TCP/IP protocol stacks on the WAN core
? routers, then perimeter routers and firewalls, then the server-farm routers and finally
? the desktop access routers. After the network supports IPv6 and IPv4 protocols, the
? process will enable dual protocol stacks on the servers and then the edge computer Systems.
? In my opinion it is not difficult to implement IPv6 in an IPv4 environment and if there
? are any hesitations left, this report shows that migration can go without difficulties.
? The transition from IPv4 to IPv6 will be a larger task for the industry. It will affect nearly all networked applications, end-systems, frastructure systems, and network architectures.
? The conversion to IPv6 has no specific timeline.
? However, as noted upper, the rate of IPv4 address using is rapidly decreasing.
? Section 9 : References
? [1] Borella, M. ; Grabelsky, D. ; Lo, J. ; Taniguchi, K. Realm "Specific IP Protocol Specification. " . IJCSNS International Journal of Computer Science and Network Security . http://tools. ietf. org/html/rfc3103 March 2007
? [2] Sawant, A. " IPv6 Features and Migration from IPv4. " In Bechtel Telecommunications Technical Journal, January 2004. from www. bechteltelecoms. com/docs/bttj_v2/Article8. pdf
? [3] T. Chown. " Considerations for IPv6 Tunneling Solutions. ". International Journal of Foundations of Computer Science (IJFCS). April 2004. University of Southampton
? [4] China Internet Information Center. "Statistical Survey Report on the Internet Development in China. ". from http://www. cnnic. net. cn/uploadfiles/pdf/2007/2/14/200607. pdf January 2007
? [5] S. Daniel Park, "IPv6 Tunnel End-point Automatic Discovery Mechanism". IJCSNS International Journal . (Sep 2004).
? [6] Nevil Brownless, NeTraMet, . ? Observations of IPv6 traffic on a 6to4 relay?
? IJCSA, International Journal of computer science and application . http://portal. acm. org/citation. cfm?id=1052821 . (Jan 2005)
? [7] Daniele Muscetta , ? Connecting to an IPv6 Tunnel Broker ? . IJCSNS International Journal . (2005)
? [8] Wright, A. ? Internet Adoption Slowing But Dependence on It Continues to Grow. ?. from http://www. ipsosna. com/news/pressrelease. cfm?id=3030 March 29, 2006
? [9] Barlow, J. ? IPv6 HandsOn ? IJCSA, International Journal of computer science and application . December 2006
? [10] Tsirtsis, G. ; Srisuresh, P. ? Network Address Translation Protocol Translation (NATPT). ? In InternetDraft, . Retrieved December 2006 from http://tools. ietf. org/html/rfc2766
? [11] Borella, M. ; Montenegro, G. ?Address Sharing with EndtoEnd Security. ? In the Proceedings of the Special Workshop on Intelligence at the Network Edge, December 2006 from https://www. usenix. org/publications/library/proceedings/ine2000/full_papers/borella/borella_html/rsipusenix. html
? [12] Borman, D. ; Deering, S. ; Hinden, R. ? IPv6 Jumbograms. ? . IJCSNS International Journal . December 2006 from http://tools. ietf. org/html/rfc2675
? [13] Carpenter, B. ; Moore, K. ? Connection of IPv6 Domains via IPv4 Clouds. "
? International Journal of Foundations of Computer Science (IJFCS) Decemeber 2006 .
? [14] Hupprich, L. ; Bumatay, M. Global Internet Population Grows an Average of Four Percent YearOverYear. Nielsen//NetRatings. March 2007 from http://phx. corporateir. net/phoenix. zhtml?c=82037&p=irolnewsArticle&ID=538993&highlight=
? [15] [RFC4607] H. Holbrook and B. Cain, "Source-Specific Multicast for IP", Cisco RFC 4607, August 2006.
? [16] IPv6 Task Force, U. S. Department of Commerce. ? Technical and Economic Assessment of Internet Protocol Version 6 (IPv6). ? January 2006. from http://www. ntia. doc. gov/ntiahome/ntiageneral/ipv6/final/ipv6final. pdf
? [17] Metz, C. ; Hagino, J. ? IPv4Mapped Addresses on the Wire Considered Harmful. ? International Journal of Foundations of Computer Science (IJFCS), December 2006 .
? [18] Professor Peter Kirstein, Dr. Tim Chown ?Why a new Internet Protocol??, UKIPV6 Task Force Journal . (2006).
? [19] Pekka Savola. CSC/FUNET, Finland .
? ? Observations of IPv6 Traffic on a 6to4 Relay. ?IJCSA, International Journal of computer science and application. (Sep 2007).
? [20] Microsoft, ? Microsoft?s Objectives for IPV6 Tunneling? http://technet. microsoft. com/en-us/library/bb726951. aspx (2007),
? [21] [RFC4795] B. Aboba, D. Thaler, L. Esibov, "Link-local Multicast Name
? zesolution (LLMNR)", HongKong Computer Society journal. January 2007.
? [22] Raymond A. Plzak, ?ARIN Board Advises Internet Community on Migration to IPv6. ? International Journal of Foundations of Computer Science (IJFCS). (May 2007)
? [23] Jeroen van Nieuwenhuizen ( 2007 ). Setting up IPv6 . Project Phoenix The Legend
? M. Rahman, Ph. D, Andrew Schaumberg (2007). Transitioning Networks from IPv4 to IPv6. University Plaza, Platteville, USA .
? [24] IANA. ? IPv4 Address Report. ? International Journal of Foundations of Computer Science (IJFCS) . (March 2007) from http://www. potaroo. net/tools/ipv4/index. html