Bill,
(B
(B Interestingly enough, part of this question brings up
(Ban issue with using "_". In the question below, at least
(Bfor my E-Mail reader, I cannot see the "_" in the URL below
(Bbecause the entire URL is underlined.
(B
(B "http://[fe80::1_de0]/"
(B
(B Using "_" introduces a "human readibility" problem. I
(Bmentioned this at the meeting...
(B
(B--
(BEric
(B
(B-----Original Message-----
(BFrom: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
(B[EMAIL PROTECTED]
(BSent: Wednesday, March 30, 2005 11:57 AM
(BTo: Bill Fenner
(BCc: ipv6@ietf.org
(BSubject: Re: Move forward with scoped literal URI format?
(B
(B
(B>>>>> On Wed, 30 Mar 2005 06:56:15 -0800,
(B>>>>> Bill Fenner <fenner@research.att.com> said:
(B
(B>> Then the browser (parser) implementation would first extract
(B>> "fe80::1_de0" and pass it to getaddrinfo(3) for converting it to an
(B>> IPv6 address. So far, so good, but then the browser would also need
(B>> to modify the entire URL to:
(B>>
(B>> http://[fe80::1]/
(B>>
(B>> before sending it to the web server on the home router
(B
(B> This part of the URL is already parsed out before it's sent -
(B> the GET argument in this case is just "/"; and the "Host:" header
(B> would contain fe80::1. Since it already had to parse it out to hand
(B> it to getaddrinfo, I don't see the problem with reusing that parsed
(B> result in the HTTP transaction.
(B
(BI'm not sure if we are synchronized...please let me check the
(Bscenario. What I wanted to say is:
(B
(B1. assume we type "http://[fe80::1_de0]/" in "the URL bar" of the
(B browser.
(B2. then the browser parser parses the entire URL and extracts
(B "fe80::1_de0" and (the trailing) "/" by recognizing "[" and "]" as
(B delimiters.
(B3. the parser passes "fe80::1_de0" to getaddrinfo(), and gets a
(B sockaddr_in6 structure (whose sin6_addr member is "fe80::1" and
(B sin6_scope_id member is the link ID corresponding to interface
(B "de0"). The browser uses the sockaddr_in6 structure with
(B connect(2) to connect to the remote web server.
(B4. the parser parses "fe80::1_de0" further, and decomposes the string
(B to "fe80::1" and "de0" by recognizing "_" as the delimiter.
(B5. when the connection is established, the browser sets "Host:" to
(B "fe80::1" (extracted from "fe80::1_de0" in step 4).
(B
(BIs this okay so far? And if so, are you saying that the parsing in
(Bstep 4 is not a problem since the parser already has to parse the
(Binput in step 2?
(B
(B JINMEI, Tatuya
(B Communication Platform Lab.
(B Corporate R&D Center, Toshiba Corp.
(B [EMAIL PROTECTED]
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(Bipv6@ietf.org
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(Bipv6@ietf.org
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
