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

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

To: "'Dino Farinacci'" <dino@cisco.com>
Subject: RE: [RRG] IEEE EUI-64 as an Identifier format
From: "Tony Li" <tony.li@tony.li>
Date: Tue, 8 Jul 2008 14:58:32 -0700
Cc: "'RJ Atkinson'" <rja@extremenetworks.com>, "'IRTF Routing RG'" <rrg@psg.com>
In-reply-to: <FD1392A5-D7BA-4A65-BF73-1367E867AF8F@cisco.com>
References: <CA535E63-1ACA-4FC1-9732-5BCB16A8CF69@extremenetworks.com> <9D4DBC4686F34D8BBA0C9A6195AD0B0D@ad.redback.com> <FD1392A5-D7BA-4A65-BF73-1367E867AF8F@cisco.com>
Reply-to: <tony.li@tony.li>

 

|However, you get zero aggregation of ID space with EUI-64 
|assignments.  
|Not good for a mapping database.


Not good if you need an ID->locator mapping or ID-><anything> mapping.
However, do we have that need?

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

References:
- [RRG] IEEE EUI-64 as an Identifier format
  - From: RJ Atkinson <rja@extremenetworks.com>
- RE: [RRG] IEEE EUI-64 as an Identifier format
  - From: "Tony Li" <tony.li@tony.li>
- Re: [RRG] IEEE EUI-64 as an Identifier format
  - From: Dino Farinacci <dino@cisco.com>

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