On 2012-02-04 09:01, t.petch wrote:
> ----- Original Message -----
> From: "Brian E Carpenter" <[email protected]>
> To: "t.petch" <[email protected]>
> Cc: "6man" <[email protected]>
> Sent: Friday, February 03, 2012 8:11 PM
>> Thanks Tom, this is new to me. I don't understand
>> where the 'decimal' hint comes from, given that the
>> practice has always been to use alphanumerics.
>>
>> Does anyone know if this is actually used, and if so, how?
>
> Brian
>
> 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.
Not much, since it's a uint32_t.
"Linux only supports it for link scope addresses, in that case sin6_scope_id
contains the interface index (see netdevice(7)) "
In other words, if it's presented as "eth0" or "foobar99" in a URI,
it will get mapped into an interface number before it goes into a
socket call. That mapping will be o/s and host dependent. At least in Linux,
it's netdevice ioctls that convert between an interface name and its index
number.
"SIOCGIFNAME
Given the ifr_ifindex, return the name of the interface in ifr_name. This
is the only ioctl which returns its result in
ifr_name.
SIOCGIFINDEX
Retrieve the interface index of the interface into ifr_ifindex. "
I assume that the MIB is intended to hold the index, up to 4 bytes long,
not the name.
Brian
>
> Tom Petch
>
>
>> Regards
>> Brian Carpenter
>>
>> On 2012-02-04 02:47, t.petch wrote:
>>> Brian
>>>
>>> Did you look at the INET-ADDRESS-MIB when preparing this? I ask because it
>>> defines [RFC4001] a 4 byte zone index; and a display hint of 'd' is
> decimal:-)
>>> "InetAddressIPv6z ::= TEXTUAL-CONVENTION
>>> DISPLAY-HINT "2x:2x:2x:2x:2x:2x:2x:2x%4d"
>>> DESCRIPTION
>>> "Represents a non-global IPv6 network address, together
>>> with its zone index:
>>>
>>> Octets Contents Encoding
>>> 1-16 IPv6 address network-byte order
>>> 17-20 zone index network-byte order
>>>
>>> The corresponding InetAddressType value is ipv6z(4).
>>>
>>> The zone index (bytes 17-20) is used to disambiguate
>>> identical address values on nodes that have interfaces
>>> attached to different zones of the same scope. The zone index
>>> may contain the special value 0, which refers to the default
>>> zone for each scope.
>>> SYNTAX OCTET STRING (SIZE (20))
>>>
>>> Tom Petch
>>>
>>> ----- Original Message -----
>>> From: "Tomoyuki Sahara" <[email protected]>
>>> To: "6man" <[email protected]>
>>> Sent: Thursday, February 02, 2012 2:48 AM
>>> Subject: Re: Reviews requested: draft-carpenter-6man-uri-zoneid-00.txt
>>>
>>>
>>>> On Wed, Jan 4, 2012 at 11:23 AM, Brian E Carpenter
>>>> <[email protected]> wrote:
>>>>> Representing IPv6 Zone Identifiers in Uniform Resource Identifiers
>>>>>
>>>>> We'd like feedback on this. In particular, which of the two options
>>>>> proposed do people prefer?
>>>> OPTION 2 seems better to me.
>>>> It's easier to implement.
>>>>
>>>>
>>>> Thanks,
>>>> Tomoyuki
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> [email protected]
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>>
>>>>
>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> [email protected]
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>>
>
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
