Entering IPv6 Zone Identifiers in User Interfaces
draft-ietf-6man-zone-ui-08

Yes

Erik Kline

No Objection

Gorry Fairhurst

No Record

Andy Newton
Deb Cooley
Gunter Van de Velde
Jim Guichard
Ketan Talaulikar
Mahesh Jethanandani
Mike Bishop
Mohamed Boucadair
Orie Steele
Paul Wouters
Roman Danyliw
Éric Vyncke

Summary: Needs 8 more YES or NO OBJECTION positions to pass.

Erik Kline
Yes
Gorry Fairhurst
No Objection
Comment (2025-03-24) Sent 
Thank you for this work to improve the use of zone identifiers.

1. The document provides only a small number of RFC2119 requirements. It might be more clear to organise the normative list of items in section 5 in a bulleted list:
- Ideally, ...
- If ...
- If ...

2. Please consider adding text on the challenge for browser configuration. In particular, it could be useful to provide slightly more context on the problem with RFC6874. From draft-schinazi-httpbis-link-local-uri-bcp, I understand:

The solution in [RFC6874] requires the browser to treat the zone
identifier as part of the origin in some contexts (such as when
determining uniqueness of a name), but not in others (such as when
sending the Host header on the wire). This significantly increases
implementation complexity and security risks.

A version of this text might help alert people that a solution for a browser might require various considerations.

3. Please also consider the issues raised in the TSV ART review and SECDIR review to discuss whether anything more can be said about a browser method to specify a zone identifier.
Andy Newton
No Record
Deb Cooley
No Record
Gunter Van de Velde
No Record
Jim Guichard
No Record
Ketan Talaulikar
No Record
Mahesh Jethanandani
No Record
Mike Bishop
No Record
Mohamed Boucadair
No Record
Orie Steele
No Record
Paul Wouters
No Record
Roman Danyliw
No Record
Éric Vyncke
No Record