Re: Problem with draft-ops-endpoint-mib-05.txt

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

>>>>> Brian Zill writes:

Brian> I hope you're not saying that the choice of formats should
Brian> depend upon the limitations of some tool somewhere.  To me,
Brian> this just means that the way DISPLAY-HINTS work is broken.

The DISPLAY-HINT goes works with the ordering of the bytes in on the
wire. We need 16 or 20 bytes to represent global and non-global
addresses. The only reasonable way in the current SMIv2 is to have the
optional bytes at the end. Sure, you can call the current SMIv2 (STD
58) broken. But that won't help to solve the problem since it is a
standard. (BTW, even the struct sockaddr_in6 puts the sin6_scope_id
field "behind" the sin6_addr field.)

Please explain the advantages of putting the scope identifier in front
of the IPv6 address and then we can see how we can get out of this
trouble.

>> The delimiter character is not a big deal. It is nothing which
>> defines on the wire behaviour nor is it mandatory to use the
>> DISPLAY-HINT for rendering values.

Brian> If that's the case, maybe the solution is to not specify a
Brian> DISPLAY-HINT for IPv6 addresses until the IPng working group
Brian> decides upon a format.

As I said, it is not only the DISPLAY-HINT. The ordering on the wire
is IMHO more important to agree on here.

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>