zero suppression vs compression in addresses

Gert Doering gert at space.net
Sun May 17 17:30:59 CEST 2009


Hi,

On Sun, May 17, 2009 at 03:45:09PM +0100, michael.dillon at bt.com wrote:
> The point is that the text representation of IPv6 addresses
> might be about to change, so if you are writing code to
> read IPv6 text format addresses, you probably want to 
> accept the format defined in this draft. Unless of course,
> there is some fundamental flaw in which case you might 
> want to communicate that to the author of the draft.

The whole point of this draw is the *output* format of an IPv6 address
(and it's using fairly weak language, like "should" instead of "SHOULD",
at that).

Input parsers need to understand every possible representation, as long
as it's syntactically correct.  This draft doesn't change what is to be
considered a syntactically correct representation, so for a *reader*,
it is just not very relevant.

Gert Doering
        -- NetMaster
-- 
Total number of prefixes smaller than registry allocations:  128645

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279


More information about the ipv6-ops mailing list