interface identifier (was: [Sis-csi] No call today)

[Ivancic, William D. (GRC-RCN0)]

Marc,

If one is speaking global addressing you are correct.  However, we are speaking link-local addressing where anything goes so long as you are not using someone else's link-local address (oh yeah - don't forget security - that always  messes up what looked like a good solution!)


Will

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Lab 216-433-2620
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic 
 

> -----Original Message-----
> From: Marc Blanchet [mailto:marc.blanchet at viagenie.ca] 
> Sent: Friday, December 22, 2006 1:59 PM
> To: Lloyd Wood
> Cc: Ivancic, William D. (GRC-RCN0); Keith Hogie; Mezu, 
> Okechukwu A. (GRC-RCN0); sis-csi at mailman.ccsds.org
> Subject: Re: interface identifier (was: [Sis-csi] No call today)
> 
> 'f
> Le 06-12-22 à 13:41, Lloyd Wood a écrit :
> 
> > At Thursday 21/12/2006 14:18 -0600, Ivancic, William D. \(GRC-RCN0
> > \) wrote:
> >
> >
> >
> >> If one wanted to go throught the trouble, I guess one 
> could specify a 
> >> standardized mechanism for CCSDS for configuring unique link local 
> >> IPv6 addressed based on Spacecraft ID of some other space-unique 
> >> identifier.
> >
> >
> > What would it take to produce a unique address from GSCID, 
> interface 
> > identification
> 
> a document that describes that.
> 
> > and (presumably) an allocated IPv6 space?
> 
> you meant address space for the network part? currently, you 
> get it from your upstream provider or directly from the 
> registries. Of course, in the process of planning a 
> deployment, address space would have to be looked up, but I'm 
> not sure that needs to be taken care in the ccsds "protocol" profile.
> 
> Marc.
> 
> >
> > L.
>