The IPv4 Address Shortage
According to Vint Cerf (the father of IP), the IPv4 32-bit address size of was chosen arbitrarily. IP was a government/academic collaborative experiment, and the current public Internet was never envisioned. The IP paradigm was that each connected device would have a unique IP address (all packets sent between IP devices would be ...
As Ron said, anyone can write a proposal. I have a hard time taking proposals seriously from someone who suggests interconnecting satellites with optical fiber, though.
Also, I can't imagine this actual proposal gaining any momentum, especially due to this note:
All Internet connected hosts must be IPv10 hosts to be able to
communicate regardless the ...
Two things are getting confused here:
classful addressing vs CIDR
Masquerading / NAT
Going from classful addressing to Classless Inter Domain Routing (CIDR) was an improvement that made the address distribution to ISPs and organisations more efficient, thereby also increasing the lifetime of IPv4. In classful addressing an organisation would get one of ...
The layout that we are using for our rollout is:
/48 per customer
/56 per customer site (as a subnet of the other /48)
/126 for all point-to-point links in the core, these are all subnets of a /48 used for all core links
These sizes are mostly taken from the RIPE advisory here.
One of the ideas around IPv6 was to speed up packet forwarding. To that end, several decisions were made. For example, the IPv6 header was greatly simplified and is a fixed length, unlike the variable length IPv4 header. Also, you cannot fragment IPv6 packets along the path, the way you can for IPv4, because packet fragmentation is resource intensive.
MAC addresses only need to be unique in a local broadcast domain, not globally, so re-use of MAC addresses in different networks usually isn't a problem.
The internet isn't one global broadcast domain and thus needs to be divided into many blocks of addresses assigned to different ISP's and each ISP divides his blocks into smaller blocks for different ...
Ron Maupin's answer gives a brilliant overview of the IPv4 shortage, but I'd like to address this part of your question:
Why can't a city (for example) have just one IP address and all homes in this city would just be on a private network of that city. Then this one city would be able to assign addresses from range 0.0.0.1 to 255.255.255.254.
On the face ...
I think the link-local scope was set to /10 simply to "fit in" better with the other scopes, e.g. site-local (before it was replaced with unique local).
Initially I had thought maybe it was to allow the use of many link-local networks on the same link, but RFC 4291 explicitly states that only fe80::/64 may be used.
No, private addressing will not become obsolete. But actually, there are two kinds of private addresses: the Unique Local Addresses (ULAs) and the link-local addresses (LLAs).
There will always be a need for big (i.e. routed) private networks that are not directly connected to the internet. Now, you could argue you don't require a private address space for ...
You must remember that anyone can submit proposals to the IETF, and they are taken seriously, until they are either adopted or die due to lack of interest.
This particular proposal has expired and been renewed by the author several times. It doesn't appear to have much, if any, support, and it doesn't even have a proposed RFC status, e.g. Standards Track. ...
IP address and port pair is called, Socket Address
Pair of socket addresses (10.0.0.1:123, 192.168.0.1:123) may also be called 4-tuple or 5-tuple if the protocol is specified as well (10.0.0.1:123, 192.168.0.1:123 UDP)
The old recommendation was to use /64 everywhere even on P2P links and assign a /48 per site.
Using large, empty subnets on point-to-point links can lead to a number of potential security issues, (see RFC6164,) so it's now best practice to use a /127 for P2P links and /128 for loopbacks.
It's not necessary to give a small customer a /48 although you would ...
Because it's redundant.
All the common link-layer protocols, like Ethernet or WiFi, have their own error checking and error correction mechanisms, so physical transmission errors are already unlikely.
What's left are logic errors in the packet itself. But almost all transport protocols based on IPv6, like TCP or UDP, also have error checking to catch ...
I don't have a full strategy, but here's the rough way I did it at $JOB[-1]:
Get an IPv6 block, either from your existing carrier, or an RIR
You might also want to mark a fc00::/7 (Unique local) block for fully internal subnets if you have an ISP block and may ever need to renumber
Decide on your v6 IGP, IS-IS is still a safer option than OSPFv3, but much ...
With IPv6 you no longer have to worry about allocating space for a given number of hosts. All subnets (other than P2P links) should be assigned as a /64 which gives you a ridiculous number of host addresses. This frees you to focus on other topics such as good network layout & design. (A /48 would give you 65,536 /64 networks)
There are (of course) ...
:: is the unspecified address (0:0:0:0:0:0:0:0), and it is only used in packets as the source address of a host that does not yet have an address and is trying to get an address assigned. What you see in the output means that a process is binding to port 8100 for all destination addresses in the host.
::1 is the loopback address (0:0:0:0:0:0:0:1), and ...
You're late to the game: IPv4 addresses are already exhausted, and have been for a number of years. All the major manufacturers have included IPv6 capability (in varying degrees) in their product for quite some time.
These days it's usually at /48, and it's very unlikely to ever be longer.
There are still AS' filtering longer than /32 though, but they should all have a default at this point (Verizon were a hold-out, but I believe they've given up).
There are also AS' filtering on allocation lengths, so if you got a /32 they might require you advertise it as such (based ...
The mechanism is called Address Resolution Protocol (ARP). Every ethernet IPv4 device ARPs to resolve ethernet mac addresses for target IPs. IP to mac mappings are stored in each device's ARP table (the phone book in your analogy).
To simplify: In most cases, to resolve the MAC address associated with an IP address, you send a broadcast ARP packet (to all ...
The IPv6 documentation prefix (2001:db8:::/32) must be used ONLY for documentation purposes. It means written examples, diagrams, PPT presentations, Textbook explanations, etc.
This range shouldn't be used in practical networks.
There is a "private IP range" of fc00::/7 which should be used for device testing, demos, courses, etc. as per RFC4193
A little precision to earlier responses, based on the RIPE IPv6 training session I had a year ago. Basically their recommendation is to focus on aggregation rather than address space preservation.
That is : don't worry to reserve a large amount of IPs for a Point of Presence even if you only have small amount of subnets here (for now). But you should ...
Some simple guidelines that work most of the time:
Dividing your /29
The standard size of your allocation from RIPE NCC is a /32
A /32 is a well-accepted prefix size in the global routing table
You can get a /29 just by asking for it
Conclusion: Get a /29 and start using the a /32, save the other /32s for when you deploy to other countries, continents etc.
A subnet (network) is really just a collection of contiguous addresses within a binary mask. It is simply a logical way to divide address block. If you run out of addresses in a network (subnet), then you are simply out of addresses in that network. Adding any more hosts would require reclaiming unused addresses, expanding the network (may not be possible), ...
Is “IPv10” a joke or a serious RFC draft?
Both. I guess that bloke is serious and he doesn't get what ridiculous schemes he's proposing. The joke's on him.
The Fiber Satellite proposal is even more ludicrous as it neglects required fiber lengths and totally ignores orbital mechanics.
IETF should block him for trolling.
TL;DR: If you're a consumer/SOHO nothing needs doing. If you're providing services, start planning now while there's no rush and no deadline.
Basically, everything is dual stack these days, meaning it supports IPv4 and IPv6 out of the box. The Internet in general is still operating fully supporting IPv4 as much as possible.
At this point, if you're ...
RFC 4291 provides instructions on how to create the EUI64 address:
Links or Nodes with IEEE 802 48-bit MACs
[EUI64] defines a method to create an IEEE EUI-64 identifier from an
IEEE 48-bit MAC identifier. This is to insert two octets, with
hexadecimal values of 0xFF and 0xFE (see the Note at the end of
appendix), in the middle of the 48-bit MAC (between ...
The first four bits in the IP header are used to store the Protocol version (4 or 6).
The version 5 was assigned to another protocol, the Internet Steam Protocol and so was not available for the successor of IPv4.
Internet Steam Protocol is defined by RFC1819 in which you will find in section 1.2:
Both ST2 and IP apply the same addressing schemes to ...
It will "flap". On the sending host (another host or the gateway/router) there will be an ARP entry for the IP pointing to the MAC address of one of the hosts. Packets will go to one of the hosts, wherever the ARP entry currently points. This will effectively disrupt connectivity for both hosts.
The neighbor discovery protocol will do a ...
You may notice that two least-significant bits of the most-significant byte of a 48-bit MAC address are usually set to 0 (as in all your examples). There are two flags in the most-significant byte of the OUI (Organizationally Unique Identifier, which are the most-significant 24-bits) part of the MAC address:
The least-significant bit is the I/G (Individual/...
Not all types of network interfaces use MAC addresses. MAC addresses are mostly associated with Ethernet, though quite a few other networking standards do use it. However, an IPv6 address can still be assigned to a network interface that doesn't use MAC addresses for Layer 2.
Also of note, a MAC address can be converted to an IPv6 host portion through EUI-...