>________________________________
> From: Kerry Lynn <kerlyn2...@gmail.com>
>To: Tomoyuki Sahara <sah...@surt.net>
>Cc: 6man <ipv6@ietf.org>
>Sent: Friday, November 18, 2011 3:53 AM
>Subject: Re: Link-local IPv6 addresses in URIs
>
>
>
>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 some comments:
>>
>> - An interface name may be longer than 4 characters. But I know we should
>> have some limit so I suggest 15 because it's maximum length of interface
>> name on *BSD and Linux systems.
>>
>> - 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
>>
>> - Can we have a dot in interface name? On Linux systems, VLAN interfaces
>> have one. An example in the draft above has "%pvc1.3" (may be an ATM
>> interface?).
>>
>>
>Thanks for the reference. I'll take a look at it before revising the ABNF
>again.
Hi,
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 link eth0 name eth0-8 type vlan id 8
ip link add link eth0 name eth0+9 type vlan id 9
ip link add link eth0 name eth0_10 type vlan id 10
ip link add link eth0 name eth0,11 type vlan id 11
ip link add link eth0 name eth0:::12 type vlan id 12
ip link add link eth0 name eth0.+- type vlan id 13
Thanks,
Francois-Xavier
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
