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

[L.Wood at surrey.ac.uk]

I think it would be useful to reversibly:

- take GSCID + link identifier (number) + IPv6 local prefix (sub-prefix) and generate link-local IPv6 address for the spacecraft interface.

- take given link-local IPv6 address and figure out which interface (link interface) and which spacecraft (GSCID) you're talking to across a link.

(Yes, this could be done with more authentication/more reliably at higher layers, with more long-distance back-and-forths to give you the same information. I doubt the anonymity-providing features of link-local addressing will be useful for spacecraft for a loooong time to come.)

L.

<http://www.ee.surrey.ac.uk/Personal/L.Wood/><L.Wood at surrey.ac.uk>



-----Original Message-----
From: Marc Blanchet [mailto:marc.blanchet at viagenie.ca]
Sent: Sun 2006-12-24 13:53
To: Wood L Dr (Electronic Eng)Electronic Eng)
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)
 
Le 06-12-23 à 11:09, Lloyd Wood a écrit :

> At Friday 22/12/2006 23:36 -0500, Marc Blanchet wrote:
>
>> Le 06-12-22 à 20:40, Ivancic, William D. (GRC-RCN0) a écrit :
>>
>>> Marc,
>>>
>>> If one is speaking global addressing you are correct.  However, we
>>> are speaking link-local addressing
>>
>> of course, that was the thread. So I guess I did not understand what
>> Lloyd was referring to for "an allocated IPv6 space". link-local is a
>> defined allocated IPv6 space: fe80::
>
> and that's a big space. So do the GSCIDs exist in a part of that,  
> or what?

it could. nothing prevents it.

Marc.


>
> L.
>
>
>
>> Marc.
>>
>>> 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.
>>
>> -----
>> IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca
>>
>>

-----
IPv6 book: Migrating to IPv6, Wiley, 2006, http://www.ipv6book.ca



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-csi/attachments/20061224/3da7b790/attachment.htm