Similar Posts

Subscribe
Notify of
5 Answers
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
KarlRanseierIII
1 year ago

Firstly, because it is fixed that way, and secondly, because I only know the length of the word and could inflate it to the total length if :: occurs twice in two places with different weightings.

ChrisCat1, UserMod Light

One or more successive blocks whose value 0 can be represented by “:” in a shortened manner.

If you have the “:” but at several in one address you can not necessarily say how many 0-en were in the respective places.

Example:

1111:0000:1111:0000:0000:0000:111111

If you cut both areas where there are several blocks with the value 0, the following would come out: 1111::111111::1111
Here it is no longer possible to see how long the two blocks were, so that the actual address can no longer be determined.
The following addresses would therefore be possible:

1111:0000:0000:0000:111111:0000:111111
1111:0000:0000:111111:0000:111111
1111:0000:1111:0000:0000:0000:111111
1111:0000:111111:0000:0000:0000:0000:111111

In order to prevent this, only one place may be shortened.

GuteAntwort2021
1 year ago

I never understood why you don’t just

1111:::1111::::1111

can do. This would eliminate the problem and still allow the cut.

tschaefer2023
1 year ago

This would make the rules for writing IPv6 addresses even more complex. This is why

1111:0:0:1111::111111 If I have not counted myself, it is no longer

jo135
1 year ago

https://datatracker.ietf.org/doc/html/rfc5952#section-2.2

The “:” can only appear once in an address.

Analogous to the previous versions of this RFC.

Why is that? Why do you know how many zeros have been replaced?