Vijay-

The only thing I could find is that it's just standard practice to use FF
FE.. For example, if you use privacy extensions then there is no FF FE
because its address is hashed right? I think it's just a 16 bit filler for a
MAC 48..  See below from the IEEE:

http://standards.ieee.org/regauth/oui/tutorials/EUI64.html

Even RFC 4291 didn't really go into much detail either..
http://www.ietf.org/rfc/rfc4291.txt

Anyone else have any thoughts?  I also included the NAv6TF in the
discussion..



010100110110010101101101011100000110010101110010001000000100011001101001

Jeremy Duncan

DTRA (BE-BIC)
INFOSEC 3, IPv6 Architect
Command Information
Office: (703) 767-6167
Cell: (703) 598-1193

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Vijayrajan ranganathan
Sent: Wednesday, June 24, 2009 1:09 AM
To: [email protected]
Subject: Implementation specific Interface-ID

Hi Everyone,

I have an ethernet interface for which I am defining the Interface-ID in a
different manner.

For an ethernet interface with MAC "34-56-78-9A-BC-DE", I am defining the
Interface-ID to be "34-56-78-xy-zw-9A-BC-DE" instead of
"36-56-78-FF-FE-9A-BC-DE"

where x,y,z,w are my implementation-defined octets.

Note:
1. I am fine with a locally-unique Interface-ID 2. The solicited-node
multicast address i'll generate for a given unicast/anycast address based on
this Interface-ID is the same as that for RFC 2464 based Interface-ID.


Assuming I make this change in an IPv6 stack which conforms to RFCs

2464 - Transmission of IPv6 Packets over Ethernet Networks
3513 - Internet Protocol Version 6 (IPv6) Addressing Architecture
4861 - Neighbor Discovery for IP version 6 (IPv6)
4862 - IPv6 Stateless Address Autoconfiguration 3810 - Multicast Listener
Discovery Version 2 (MLDv2) for IPv6

After this change, will I still conform to these RFCs??


Thanks & Regards
Vijay
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Attachment: smime.p7s
Description: S/MIME cryptographic signature

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to