Each device that participates in networking activities must hold a alone IP reference. Network services that use TCP/IP place other web hosts by utilizing IP references. The IP reference provides the exact location of a host device on a web. If the cyberspace protocol determines that a finish reference is on the local web, it transmits the package straight to the web host. If it is determined that the finish IP reference is non on the local web, the cyberspace protocol looks for a path to a distant host. An reference on the local web is a local reference and on non on the local web is a distant reference. If a path is found, the package is sent utilizing that path. If no path is found, so the package is sent to the default gateway for the beginning host. A gateway connects webs utilizing different communicating protocols.
An IP reference includes a web identifier and a host identifier. The web identifier is used to place the web where the host is located. All systems that are on the same physical web must hold the same web identifier. The host identifier identifies a workstation, waiter, router, or other host within a web. The reference assigned to each host must be alone to the web identifier.
The 128-bit IPv6 reference is divided into 16-bit boundaries. The 16-bit blocks are so converted to a 4-digit hexadecimal figure, separated by colons. This representation is called colon-hexadecimal. This is in contrast to 32-bit IPv4 reference represented in the dotted-decimal format, divided into 8-bit boundaries, and so converted to its denary equivalent, and separated by periods.
IPv6 references do non necessitate to be configured manually. Unlike in IPv4, DHCP is non used in IPv6 to configure IP references and subnet masks automatically. The link-local range of an IPv6 reference is ever configured automatically. Addresss with other Scopess, for illustration planetary, are configured by router advertizements.
Inactive and Dynamic Addresses
A inactive IP reference is an reference that does non alter over clip unless altered manually. It is used when an IP reference or web location has to stay the same systematically. A good illustration of this would be a web waiter. If you go to www.google.co.uk you are truly traveling to the IP reference of 220.127.116.11. If this were to alter it would non be possible to entree Google.co.uk unless you knew the new IP reference or until Google updated their DNS records.
A Dynamic IP reference is an reference that changes every clip the device connects to a web and is assigned an IP reference. It is largely normally used when a consistent IP reference is non necessary. Dynamic IPaa‚¬a„?s are used in big webs where computing machines are often reconfigured, or where a limited figure of IP reference are available to portion between many computing machines.
IPv6 Unicast Addresses
IPv6 Unicast references are generically structured as a two portion reference: a 64-bit Topology portion, used by routers to send on a package to its intended finish web, and a 64-bit Interface Identifier, that identifies a peculiar terminal point.
There are several types of unicast references in IPv6 unicast: planetary unicast, link-local unicast, and unique-local unicast. There are besides some special-purpose subtypes of planetary unicast, for illustration IPv6 addresses with embedded IPv4 addresses or Loopback reference. Extra reference types or subtypes may be defined in the hereafter.
Elementss of a Unicast Address
Prefix – e.g. FC00: :/7 is a prefix to place Local IPv6 unicast references.
Global IDs are 40-bit planetary identifiers used to make a globally alone prefix
Subnet IDs are 16-bit identifiers used to place a subnet within the site
Interface ID is a 64-bit Interface identifier that indicates the interface of a node
Global Unicast Addresses of this type are designed to be aggregated or summarized to bring forth an efficient routing substructure. They are the IPv6 equivalent of public IPv4 references. Unlike the current IPv4-based Internet, which has the mixture of both level and hierarchal routing, IPv6 has been designed from the land up to back up hierarchal addressing and routing. Global unicast references are globally routable and approachable on the IPv6 subdivision of the Internet. The part of the Internet over which the planetary unicast reference is alone is the full IPv6 Internet.
IPv6 planetary unicast references are assigned from the prefix 2000: :/3. Global unicast reference assignments are made to Regional Internet Registries, and the reference blocks that have been assigned are registered in the IANA IPv6 Global Unicast Address Assignment Registry. All other reference prefixes are presently unallocated, and should non be seen in the beginning or finish reference of an IPv6 package in the context of planetary routing.
F: Network Design – COMP09022Network Design CourseworkGUA.png
Link-local references are web references that are intended merely for communications within one section of a local web or a point-to-point connexion. Link-locals allow turn toing hosts without utilizing a globally-routable reference prefix. Routers will non send on a package with link-local references.
Link-local references are frequently used for web reference constellation when there is no external beginning of web turn toing information is available. This addressing is accomplished by the host operating system utilizing a procedure called stateless reference car constellation. This is possible in both IPv4 and in IPv6.
IPv6 hosts automatically delegate their interfaces a alone reference based on the IEEE 802 MAC reference.
F: Network Design – COMP09022Network Design CourseworkLLA.png
Unique Local Addresses
Unique Local Addresses are similar to the private reference infinite in IPv4. This address infinite is intended to hold the same range as planetary reference but that equates to an endeavor environment. Unique local references are assigned from the prefix FD00: :/8, utilizing a self-assigned Global ID, where the Local spot is set to 1. The Global ID is non certain to be alone, and there is no signifier of address enrollment. Packages with these references in the beginning or finish Fieldss are non intended to be routed in the public Internet, but are intended to be routed in a site. The reference prefix FC00: :/8, with the local spot set to 0, is presently undefined.
A former criterion proposed the usage of “ site-local ” references in the fec0: :/10 scope, but due to concerns about scalability and the hapless definition of what constitutes a site, its usage has been deprecated since September 2004
F: Network Design – COMP09022Network Design CourseworkULA.png
Global Unicast Address Considerations
No important considerations are necessary if the organisation has an address infinite assignment and a individual prefix is deployed.
A multi-homed site may deploy references from two or more Service Provider assigned IPv6 reference ranges. Here, the web Administrator must hold consciousness on where and how these scopes are used on the multi-homed substructure environment.
The nature of the use of multiple prefixes may depend on the ground for multi-homing ( e.g. resiliency failover, burden reconciliation, policy-based routing, or multi-homing during an IPv6 renumbering event )
IPv6 introduces improved support for multi-addressed hosts through the IPv6 default reference choice methods.
A multi-homed host may therefore hold two references, one per prefix ( supplier ) , and choice beginning and finish references.
However multi-homing besides has some operative and administrative loads besides taking multiple references per interface
Local Link Addresses Considerations
Link-Local references are designed to be used for turn toing on a individual nexus
By and large for the intents of automatic reference constellation, neighbour find, or when no routers are present.
Routers should non send on any packages with Link-Local beginning or finish references to other links.
alone merely on one physical nexus
ne’er routed even within peculiar organisation
non globally alone
non alone even within peculiar organisation
used for particular characteristics of IPv6 like car constellation
Unique Local Addresses Considerations
Provides Local IPv6 prefixes that can be used independently of any provider-based IPv6 unicast reference allotments. This is utile for sites that are non ever connected to the Internet or sites that want to hold a distinguishable prefix that can be used to place traffic inside of the site.
Applications can handle these references in the same mode as any other type of planetary IPv6 unicast references.
Sites can be merged without renumbering of the Local IPv6 addresses.
Sites can alter their provider-based IPv6 unicast reference without interrupting any communicating within the Local IPv6 addresses.
Has a good known prefix that allows for easy filtering at site boundary.
Can be used for in-site Virtual Private Networks.
If accidently leaked outside of a site via routing or DNS, there is no struggle with other references.
It is non possible to route Local IPv6 prefixes on the planetary Internet. Consequentially, it is necessary to hold the default behavior of site boundary line routers to filtrate these references.
There is an highly low chance of non-unique locally assigned references. This hazard can be ignored for all practical intents, but it still leads to a theoretical hazard of colliding references.
The Unique Local Address format is recommended for several grounds:
Allows webs to be combined or in private interconnected without making any address struggles or necessitating renumbering of interfaces utilizing these prefixes
If by chance leaked outside of a web via routing or DNS, there is no struggle with any other references
ISP independent and can be used for communications inside of a web without holding any lasting or intermittent Internet connectivity
Well known prefix to let for easy filtering at web boundaries
In pattern, applications may handle these references like planetary scoped references
is designed for Addressing isolated webs
Persistent local-context references ( independent of provider-based references )
VPN ( Virtual Private Network ) – styled interconnectedness of local web contexts
Private references in footings of routing range
Global references in footings of singularity