At the IETF meeting in Minneapolis, I talked about the URI format for
scoped addresses, described in
http://www.ietf.org/internet-drafts/draft-fenner-literal-zone-01.txt
square bracket does not fit the RFC3986 abnf anyways. therefore,
i do not think addition of v6. or use
Ten years ago with the very first communications between two independent
implementations, IPv6 became reality (*)!
(*) according to the IETF credo about running code (cf RFC 3160 section 7),
the first demonstrated interoperability is the real birth of IPv6.
[EMAIL PROTECTED]
PS: here is the log
square bracket does not fit the RFC3986 abnf anyways. therefore,
i do not think addition of v6. or use of _ would really help.
Please look again at the IP-Literal and IPvFuture productions.
i would say we should stick to current
Then the browser (parser) implementation would first extract
fe80::1_de0 and pass it to getaddrinfo(3) for converting it to an
IPv6 address. So far, so good, but then the browser would also need
to modify the entire URL to:
http://[fe80::1]/
before sending it to the web server on the home
On Wed, 30 Mar 2005 06:56:15 -0800,
Bill Fenner fenner@research.att.com said:
Then the browser (parser) implementation would first extract
fe80::1_de0 and pass it to getaddrinfo(3) for converting it to an
IPv6 address. So far, so good, but then the browser would also need
to modify the
You're right, we were out of sync;
3. the parser passes fe80::1_de0 to getaddrinfo(), and gets a
sockaddr_in6 structure (whose sin6_addr member is fe80::1 and
sin6_scope_id member is the link ID corresponding to interface
de0). The browser uses the sockaddr_in6 structure with
Bill,
(B
(BInterestingly 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
On Wed, 30 Mar 2005 09:18:15 -0800,
Bill Fenner fenner@research.att.com said:
3. the parser passes fe80::1_de0 to getaddrinfo(), and gets a
sockaddr_in6 structure (whose sin6_addr member is fe80::1 and
sin6_scope_id member is the link ID corresponding to interface
de0). The browser uses
On Wed, Mar 30, 2005 at 06:53:12AM -0800, Bill Fenner wrote:
i would say we should stick to current
http://[fe80::1%fxp0]:80/index.html
This is not the current notation, neither the grammar in rfc 2732 nor rfc
3986 permits it, and rfc 3986 explicitly mentions zones as not
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Version 6 Working Group Working Group of
the IETF.
Title : Considerations on M and O Flags of IPv6 Router
Advertisement
Author(s) : S. Park, et al.
square bracket does not fit the RFC3986 abnf anyways. therefore,
i do not think addition of v6. or use of _ would really help.
Please look again at the IP-Literal and IPvFuture productions.
i would say we should stick to current
11 matches
Mail list logo
