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

[Brian Zill <bzill@microsoft.com>]

> (2) Moving the scope id before the address portion:
> 
>     This is problematic since this TC is for both,
>     global and non-global IPv6 addresses. Due to the
>     way DISPLAY-HINTS work (RFC 2579), you can only
>     have optional parts at the end of the underlying
>     OCTET STRING. I also believe that the current
>     version gives a more natural order and leads to
>     fewer special cases since I expect that global
>     IPv6 addresses >> non-global IPv6 addresses.

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

> 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.

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

--Brian