[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [RRG] IEEE EUI-64 as an Identifier format

To: "'RJ Atkinson'" <rja@extremenetworks.com>, "'IRTF Routing RG'" <rrg@psg.com>
Subject: RE: [RRG] IEEE EUI-64 as an Identifier format
From: "Tony Li" <tony.li@tony.li>
Date: Tue, 8 Jul 2008 13:17:18 -0700
In-reply-to: <CA535E63-1ACA-4FC1-9732-5BCB16A8CF69@extremenetworks.com>
References: <CA535E63-1ACA-4FC1-9732-5BCB16A8CF69@extremenetworks.com>
Reply-to: <tony.li@tony.li>

 

|So the EUI-64 format seems like a pretty practical one to use
|for an IPv6 or IPv6-like environment.


Agreed.  The ability escape to a crypto-generated ID seems like a sufficient
mitigation, IMHO.

Tony


--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg

Follow-Ups:
- Re: [RRG] IEEE EUI-64 as an Identifier format
  - From: "William Herrin" <bill@herrin.us>
- Re: [RRG] IEEE EUI-64 as an Identifier format
  - From: Dino Farinacci <dino@cisco.com>

References:
- [RRG] IEEE EUI-64 as an Identifier format
  - From: RJ Atkinson <rja@extremenetworks.com>

Prev by Date: RE: [RRG] perceived privacy issue
Next by Date: Re: [RRG] IEEE EUI-64 as an Identifier format
Previous by thread: [RRG] IEEE EUI-64 as an Identifier format
Next by thread: Re: [RRG] IEEE EUI-64 as an Identifier format
Index(es):
- Date
- Thread