Without consulting my co-author, here's my personal suggestion for
a change to the draft. There's just time to submit an update before
the cutoff, if people respond immediately.
OLD
In recent years, web browsers have evolved considerably and now
accept and parse many forms of input that are not a formal URI.
Examples of this include host names, search items, bookmarks, search
history, etc. For example the Google Chrome browser now calls the
"address bar" the "omnibox" [chrome]. The authors believe it is
feasible, and very convenient for users, if browsers also allow (in
addition to the formal URI syntax defined in this document) a syntax
that will enable cut and paste. For example:
http://[fe80::a%en1]
It seems that modern browsers can be adapted to parse this because it
is inside of the "[" "]"'s. This would permit the output of commands
like ping6 -w ff02::1%en1 to be "cut and pasted" into a browser
address bar. Consequently this document recommends that browsers
support this syntax in addition to the formal URI syntax defined
above.
NEW
In recent years, web browsers have evolved considerably and now
accept and parse many forms of input that are not a formal URI.
Examples of this include host names, search items, bookmarks, search
history, etc. For example the Google Chrome browser now calls the
"address bar" the "omnibox" [chrome]. Thus, it seems that browsers
can take a pragmatic approach to literal addresses including ZoneIDs.
Unfortunately there is no way to resolve the discrepancy between
the two approaches mentioned above (raw "%" versus "%25") and
therefore we recommend general implementation of the new "-" syntax
defined by this document. This will allow simple "cut and paste"
between tools such as "ping6" and browser address bars.
Brian
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
