W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2011

Re: IPv6 and draft-petersson-forwarded-for

From: Andreas Petersson <andreas@sbin.se>
Date: Tue, 26 Apr 2011 15:01:13 +0200
To: "Dan Wing" <dwing@cisco.com>
Cc: <draft-petersson-forwarded-for@tools.ietf.org>, <ietf-http-wg@w3.org>
Message-ID: <20110426150113.47b78a39@hetzer>
On Mon, 25 Apr 2011 22:14:58 -0700
"Dan Wing" <dwing@cisco.com> wrote:

> Andreas, Martin,
> 
> The relevant ABNF to construct an IPv6 address is:
> 
>        node = nodename [":" node-port]
>        node-port = port | obfport
>        nodename = IPv4address | IPv6address |
>                    "unknown" | "hidden" | obfnode
>        IPv6address = addr6 | "[" addr6 "]"
> 
> which could result in something like 2001:db8::5555, which has an ambiguous
> meaning -- it could be "2001:db8 port 5555", or simply the IPv6 address
> "2001:db8::5555" (without the node-port).
> 
> The simplest fix is to require the "[]" characters around an IPv6 address,
> similar to how HTTP is constructed (RFC3986), like this:
>        IPv6address = "[" addr6 "]"
> 
> -d
> 
> 
> 

Hi,

Yes, [] around the address is required in the draft in textual form if
port is present, this will be changed in the next version of the draft
where [] will be required independent of the presence of port.

Beside that, should the BNF for IPv6 be borrowed from RFC3986?
PHK suggested to use the RFC5952, I think that looks good but it lacks
a BNF-description.


rgds,
 Andreas Petersson
Received on Tuesday, 26 April 2011 13:01:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:40 GMT