Re: [IPv6] Request for WG adoption call for draft-carpenter-6man-zone-ui

[Brian E Carpenter <[e-mail]>]

On 19-Apr-24 11:43, Michael Richardson wrote:
> 
> I have read draft-carpenter-6man-zone-ui.  I agree with adopting it.
> (note that anyone may call for adoption. chairs consult by tradition)
> 
> I did not know about this NMEA use case. Interesting.
> I don't think the wireshark example is good/accurate, but perhaps the goal is
> to show a category of tool.  Note that pcapng files can contain captured
> traffic from multiple interfaces (not so for pcap), so in theory one might
> need to qualify a filter.

Yes, exactly. I wanted to do that quite recently, when playing with mDNS on
a host with multiple interfaces. We can rephrase, of course.

(Off topic: the business of interface selection in Wireshark is quite messy
in Windows, because interfaces on Windows turn out to have a variety of names,
and the result of if_indextoname() is not what you might expect.)

> 
>>    Open Issue: This specification effectively extends RFC 4007.  Should
>>    this be recorded as a formal update to RFC 4007?
> 
> Yes.

Noted.

> 
>>    An implementation should not include ASCII NULL characters in a zone
>>    identifier string as this could cause inconsistencies in subsequent
>>    string processing.
> 
> Do we need to repeat that it's limited to 7-bit alphanumber?
> (Do we say this in 4007? probably. but, worth repeating here)
> I assume *$%43 is not valid as a zone ID.

RFC4007 says basically nothing except "The precise format and semantics of additional strings is implementation dependent."

So no, it isn't limited to ASCII, or UTF-8, or anything at all, by the current spec. Personally I think that should be fixed, but as part of a serious revision of RFC4007, not in this rather modest draft.

    Brian