> > So, I guess the appropriate next step for this work is to > make consensus on this, which mostly equals to my question -1: > > -1. are we okay with forcing URL/URI parsers to understand the > detailed semantics of the scoped address syntax and to strip the > zone ID (+ delimiter) part by itself for the reason because the > parsers would already need to do some extra work for the special > syntax? > (slightly modified based on the discussion so far) >
I modified our URL parser to recognize and parse a URL of the form http://[v6.fe80::1_fxp0]:8081/readme.txt The additional code is straightforward based on my own implementation experience. So my answer to the above question is a "yes". I chose the "_" as the delimiter and as a few other have noted, this character disappears in my mail client. While testing with Firefox, interestingly enough Firefox appears to be the only browser that allows IPv6 address in the HTTP Proxy setting, but the browser actually puts "GET http://[fe80::2b0:d0ff:fe25:689%4]/readme.txt HTTP/1.1 HOST: [fe80::2b0:d0ff:fe25:689%4]" on the wire. I've filed a bug against it. -- Qing -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
