I'm doing a presentation on how the internet works, and I'm wondering if there is even such a thing as a private IPV6 address. If so, what does a private IPV6 address looks like?
IPV6 Address – What Does a Private IPV6 Address Look Like?
ipip addressipv6
Related Solutions
The IPv6 address is the network address assigned to the interface of the tunnel. I don't know where you came up with the /128
because that is used for something like a loopback.
Specifies the IPv6 network assigned to the interface and enables IPv6 processing on the interface.
Something like this from the Cisco documentation:
Example: Configuring 6to4 Tunnels
The following example configures a 6to4 tunnel on a border router in an isolated IPv6 network. The IPv4 address is 192.168.99.1, which translates to the IPv6 prefix of 2002:c0a8:6301::/48. The IPv6 prefix is subnetted into 2002:c0a8:6301::/64 for the tunnel interface: 2002:c0a8:6301:1::/64 for the first IPv6 network, and 2002:c0a8:6301:2::/64 for the second IPv6 network. The static route ensures that any other traffic for the IPv6 prefix 2002::/16 is directed to tunnel interface 0 for automatic tunneling.
interface GigabitEthernet0/0/0
description IPv4 uplink
ip address 192.168.99.1 255.255.255.0
!
interface GigabitEthernet1/0/0
description IPv6 local network 1
ipv6 address 2002:c0a8:6301:1::1/64
!
interface GigabitEthernet2/0/0
description IPv6 local network 2
ipv6 address 2002:c0a8:6301:2::1/64
!
interface Tunnel0
description IPv6 uplink
no ip address
ipv6 address 2002:c0a8:6301::1/64
tunnel source GigabitEthernet0/0/0
tunnel mode ipv6ip 6to4
!
ipv6 route 2002::/16 tunnel 0
RFC 5952 gives you the canonical IPv6 format. That is explained in the RFC itself:
This document defines a canonical textual representation format.
and
4. A Recommendation for IPv6 Text Representation
A recommendation for a canonical text representation format of IPv6 addresses is presented in this section.
There are people who incorrectly call a fully uncompressed (eight words of four hexadecimal digits each) the canonical format but the RFC refer to this as conventional notation.
When zero words are replaced with ::
it is a compressed address format, and when used with IPv4 notation, such as ::ffff:10.11.12.13
it is a mixed, or compressed and mixed, address format.
Edit based on the question edit:
There is no official name for the IPv6 notation, but RFC 5952, among others, refers to it as hexadecimal
notation.
Even the IPv4 address notation commonly called dotted-decimal
notation is not really in any RFC defining IPv4. It is mentioned in RFC 3795, Survey of IPv4 Addresses in Currently Deployed IETF Application Area Standards Track and Experimental Documents, an informational RFC which specifically states:
This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
In conclusion, there is no official name for the general IPv6 format, and you may call it whatever you wish. I think it is important to distinguish between the various IPv6 address formats. My company has a requirement to use the RFC 5952 canonical format rather than the conventional format.
Note: I left the rest of my answer in as useful information.
Best Answer
IPv6 does not have Private addresses the way IPv4 does. There once was IPv6 Site Local addressing (
fec0::/10
), but that was deprecated in favor of Unique Local Addressing (fc00::/7
). ULA goes a long way to solving the problem presented by IPv4 Private addressing where it is very common for different sites to use the same Private addressing.With ULA, the addressing is divided into two different parts:
fc00::/8
is reserved for future use, presumably by a Global authority to assignfd00::/8
is available for local assignment, with certain restrictions, such as the next 40 bits must be randomly assigned in order to achieve a large degree of uniqueness.The uniqueness goes a long way to prevent the problem with connecting sites that have overlapping addressing. This is a common problem with IPv4 Private addressing. Companies that merge will almost surely have overlapping IPv4 addressing, and another kludge is necessary until one or both companies can readdress (a giant project that can last years).
Having said all that. There is no NAT standard for IPv6* the way there is for IPv4. For use on the public Internet, hosts are assigned Global IPv6 addresses, which restores the end-to-end paradigm of the original IP design that IPv4 NAPT breaks.
*There is an experimental RFC for IPv6 NAT, but it is a one-to-one NAT with restrictions to preserve the IP end-to-end paradigm. The RFC forbids NAPT, which is the common NAT variant used for IPv4.