On 2012-02-05 02:20, Brian Haberman wrote: > On 2/4/12 2:11 AM, JINMEI Tatuya / 神明達哉 wrote: >> At Fri, 3 Feb 2012 21:01:32 +0100, >> "t.petch"<[email protected]> wrote: >> >>> My exposure to zoneids started with the installation of Windows 2000 >>> Servers, but there was no SNMP involved there; I cannot recall if >>> URI were in use, I think not, and the ids I saw were, I think, numeric. >>> >>> I did see that RFC4007 says that >>> " Implementations choosing to follow the >>> recommended basic API [10] will want to restrict their index values >>> to those that can be represented by the sin6_scope_id field of the >>> sockaddr_in6 structure." >>> but I am not sure what that means, in terms of character set. >> >> (I've not read the the uri-zoneid draft, but anyway) In terms of >> RFC4007 zone indices are primarily numeric numbers. Only in the >> textual representation of<address>%<zone_id>, and only optionally for >> convenience, the zone_id part can be a more human-understandable form, >> such as an network interface name that can uniquely identify the >> corresponding zone in the context of<address>%<zone_id>. > > The zone ID information included in the InetAddressIPv6z object in RFC > 4001 was modeled after the description of the zone ID in RFC 4007. As > Jinmei points out, the user friendly name is mapped to an easily indexed > interface number to determine the actual zone. > > Regards, > Brian
Exactly, and obviously in a URI it will be the user friendly name. The mapping is a host-specific function. Brian C -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
