From: Brian E Carpenter brian.e.carpen...@gmail.com
To: François-Xavier Le Bail fx.leb...@yahoo.com
Cc: Kerry Lynn kerlyn2...@gmail.com; Tomoyuki Sahara sah...@surt.net;
6man ipv6@ietf.org
Sent: Tuesday, November 22, 2011 10:35 PM
Subject: Re: Link-local IPv6 addresses in URIs
On 2011-11
On 2011-11-19 05:03, François-Xavier Le Bail wrote:
...
In Linux, you can use any character in VLAN interface name :
examples:
ip link add link eth0 name eth0.5 type vlan id 5
ip link add link eth0 name eth0-6 type vlan id 6
ip link add link eth0 name eth0#7 type vlan id 7
ip link add
On 2011-11-18 15:27, Tomoyuki Sahara wrote:
Hi,
That sounds good to me too.
My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
IPv6address rule only as a starting point:
/ FE80:: [ *3( h16 : ) h16 ] [ % 1*4(ALPHA / DIGIT) ]
That's one option; another one is to
On Thu, Nov 17, 2011 at 9:27 PM, Tomoyuki Sahara sah...@surt.net wrote:
Hi,
That sounds good to me too.
My ABNF is pretty rusty, so I offer the following extension to the RFC
3986
IPv6address rule only as a starting point:
/ FE80:: [ *3( h16 : ) h16 ] [ % 1*4(ALPHA / DIGIT) ]
I have
On 11/17/11 9:27 PM, Tomoyuki Sahara wrote:
- FYI, there was an attempt to define textual representation of zone id:
http://tools.ietf.org/html/draft-ietf-ipngwg-scoping-arch-04#section-12
Published as RFC 4007 (http://tools.ietf.org/html/rfc4007).
Regards,
Brian
From: François-Xavier Le Bail fx.leb...@yahoo.com
To: Kerry Lynn kerlyn2...@gmail.com; Tomoyuki Sahara sah...@surt.net
From: Kerry Lynn kerlyn2...@gmail.com
To: Tomoyuki Sahara sah...@surt.net
On Thu, Nov 17, 2011 at 9:27 PM, Tomoyuki Sahara
On Thu, Nov 17, 2011 at 12:13 AM, Carsten Bormann c...@tzi.org wrote:
On Nov 17, 2011, at 13:00, Brian E Carpenter wrote:
Do people agree that this is a reasonable thing to do?
Yes please!
My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
IPv6address rule only as
On 11/17/11 12:00 AM, Brian E Carpenter wrote:
Dear 6man,
Kerry and I talked about this. It seems to me that, given we allow for
IPv6 literals in URIs principally for diagnostic purposes, it is indeed
unfortunate that http://[fe80::206:98ff:fe00:232%tap0] is not
allowed by the formal
Yes from me. Thanks.
Bert
-Original Message-
From: ipv6-boun...@ietf.org [mailto:ipv6-boun...@ietf.org] On Behalf Of Brian E
Carpenter
Sent: Thursday, November 17, 2011 12:00 AM
To: 6man
Cc: Kerry Lynn
Subject: Re: Link-local IPv6 addresses in URIs
Dear 6man,
Kerry and I talked about
Hi,
That sounds good to me too.
My ABNF is pretty rusty, so I offer the following extension to the RFC 3986
IPv6address rule only as a starting point:
/ FE80:: [ *3( h16 : ) h16 ] [ % 1*4(ALPHA / DIGIT) ]
I have some comments:
- An interface name may be longer than 4 characters. But I
Dear 6man,
Kerry and I talked about this. It seems to me that, given we allow for
IPv6 literals in URIs principally for diagnostic purposes, it is indeed
unfortunate that http://[fe80::206:98ff:fe00:232%tap0] is not
allowed by the formal syntax.
This would need to be fixed by a small RFC that
On Nov 17, 2011, at 13:00, Brian E Carpenter wrote:
Do people agree that this is a reasonable thing to do?
Yes please!
I trust that the update spec will explain the for debugging focus and will
have appropriate warning
-- that the link identifiers are node-local names with node-local
Kerry,
On 2011-11-14 18:41, Kerry Lynn wrote:
Greetings,
I've noticed that a bug has re-appeared in Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=700999
In older versions of Firefox (e.g. 3.6.23) it is possible to enter URIs of
the form http://[fe80::206:98ff:fe00:232%tap0] in
13 matches
Mail list logo
