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 define the syntax for *any* address format and restrict it to fe80::/10 by a SHOULD. I'm inclined towards the latter, in case some other use case shows up later. > > 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. Seems reasonable. > > - 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 That's RFC 4007 now. > > - 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?). Yes, we can use the character set "unreserved" from the URI syntax which is defined by unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" Brian -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
