Great, got it.
-Mar.
On Wed, Sep 08, 2010 at 11:53:12AM -0400, Jon Smirl wrote:
> On Wed, Sep 8, 2010 at 11:43 AM, Jon Smirl wrote:
> >> "For example, the Interface Identifier for an Ethernet interface whose
> >> built-in address is, in hexadecimal,
>
> Interface Identifier != MAC address. It i
On Wed, Sep 8, 2010 at 11:43 AM, Jon Smirl wrote:
>> "For example, the Interface Identifier for an Ethernet interface whose
>> built-in address is, in hexadecimal,
Interface Identifier != MAC address. It is a two step process.
For Ethernet (48b) MAC addresses.
34-56-78-9A-BC-DE
First conve
On Wed, Sep 8, 2010 at 11:43 AM, Jon Smirl wrote:
> On Wed, Sep 8, 2010 at 10:40 AM, Mariano Alvira wrote:
>> On Wed, Aug 11, 2010 at 01:35:44AM +0400, Dmitry Eremin-Solenikov wrote:
>>> On 8/11/10, Mariano Alvira wrote:
>>>
>>> Please refer to the part 'Restricted encapsulated values'.
>>>
>>>
On Wed, Sep 8, 2010 at 10:40 AM, Mariano Alvira wrote:
> On Wed, Aug 11, 2010 at 01:35:44AM +0400, Dmitry Eremin-Solenikov wrote:
>> On 8/11/10, Mariano Alvira wrote:
>>
>> Please refer to the part 'Restricted encapsulated values'.
>>
>> IMO you should have generated EUI-64 directly from OUI/exti
On Wed, Aug 11, 2010 at 01:35:44AM +0400, Dmitry Eremin-Solenikov wrote:
> On 8/11/10, Mariano Alvira wrote:
>
> Please refer to the part 'Restricted encapsulated values'.
>
> IMO you should have generated EUI-64 directly from OUI/extid
> EUI-48 -> EUI-64 is really meant for cases where manufact
