On Wed, 1 May 2019, Juergen Schoenwaelder wrote:
The basic disconnect here may be that for me the prefix is the value
while for you the value is the prefix plus the unused bits.
My disconnect is what the server should do when it encounters a value
where the bits are non-zero.
Where is the text that tells the server implementor whether to throw an
error when client commits non-zero bits, or to just throw the bits away
and store the value in the canonical format?
(Even for the case of simple signed integers, it depends on my internal
number representation whether normalizing +7 to 7 causes a change of
the internal representation or not.)
I think this example is not relevant to this discussion. +7 and 7 doesn't
change any integer backend representation. It's the same value.
Again, I have no problem with the server throwing away the bits at commit
time, I just want it to be clear from the specs that this is the correct
behaviour and what the server should do when the above text is not true:
"The IPv6 address should have all bits that do not belong
to the prefix set to zero."
Throw an error or "fix it"? It seems it should "fix it", so we should have
text that reflects this. I have no idea where this text should go, though.
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
