<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: interface identifier (was: [Sis-csi] No call today)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=2>I think it would be useful to reversibly:<BR>
<BR>
- take GSCID + link identifier (number) + IPv6 local prefix (sub-prefix) and generate link-local IPv6 address for the spacecraft interface.<BR>
<BR>
- take given link-local IPv6 address and figure out which interface (link interface) and which spacecraft (GSCID) you're talking to across a link.<BR>
<BR>
(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.)<BR>
<BR>
L.<BR>
<BR>
<<A HREF="http://www.ee.surrey.ac.uk/Personal/L.Wood/">http://www.ee.surrey.ac.uk/Personal/L.Wood/</A>><L.Wood@surrey.ac.uk><BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Marc Blanchet [<A HREF="mailto:marc.blanchet@viagenie.ca">mailto:marc.blanchet@viagenie.ca</A>]<BR>
Sent: Sun 2006-12-24 13:53<BR>
To: Wood L Dr (Electronic Eng)Electronic Eng)<BR>
Cc: Ivancic, William D. (GRC-RCN0); Keith Hogie; Mezu, Okechukwu A. (GRC-RCN0); sis-csi@mailman.ccsds.org<BR>
Subject: Re: interface identifier (was: [Sis-csi] No call today)<BR>
<BR>
Le 06-12-23 à 11:09, Lloyd Wood a écrit :<BR>
<BR>
> At Friday 22/12/2006 23:36 -0500, Marc Blanchet wrote:<BR>
><BR>
>> Le 06-12-22 à 20:40, Ivancic, William D. (GRC-RCN0) a écrit :<BR>
>><BR>
>>> Marc,<BR>
>>><BR>
>>> If one is speaking global addressing you are correct. However, we<BR>
>>> are speaking link-local addressing<BR>
>><BR>
>> of course, that was the thread. So I guess I did not understand what<BR>
>> Lloyd was referring to for "an allocated IPv6 space". link-local is a<BR>
>> defined allocated IPv6 space: fe80::<BR>
><BR>
> and that's a big space. So do the GSCIDs exist in a part of that, <BR>
> or what?<BR>
<BR>
it could. nothing prevents it.<BR>
<BR>
Marc.<BR>
<BR>
<BR>
><BR>
> L.<BR>
><BR>
><BR>
><BR>
>> Marc.<BR>
>><BR>
>>> where anything goes so long as you are not using someone else's<BR>
>>> link-local address (oh yeah - don't forget security - that always<BR>
>>> messes up what looked like a good solution!)<BR>
>>><BR>
>>><BR>
>>> Will<BR>
>>><BR>
>>> ******************************<BR>
>>> William D. Ivancic<BR>
>>> Phone 216-433-3494<BR>
>>> Fax 216-433-8705<BR>
>>> Lab 216-433-2620<BR>
>>> Mobile 440-503-4892<BR>
>>> <A HREF="http://roland.grc.nasa.gov/~ivancic">http://roland.grc.nasa.gov/~ivancic</A><BR>
>>><BR>
>>><BR>
>>>> -----Original Message-----<BR>
>>>> From: Marc Blanchet [<A HREF="mailto:marc.blanchet@viagenie.ca">mailto:marc.blanchet@viagenie.ca</A>]<BR>
>>>> Sent: Friday, December 22, 2006 1:59 PM<BR>
>>>> To: Lloyd Wood<BR>
>>>> Cc: Ivancic, William D. (GRC-RCN0); Keith Hogie; Mezu,<BR>
>>>> Okechukwu A. (GRC-RCN0); sis-csi@mailman.ccsds.org<BR>
>>>> Subject: Re: interface identifier (was: [Sis-csi] No call today)<BR>
>>>><BR>
>>>> 'f<BR>
>>>> Le 06-12-22 à 13:41, Lloyd Wood a écrit :<BR>
>>>><BR>
>>>>> At Thursday 21/12/2006 14:18 -0600, Ivancic, William D. \(GRC-RCN0<BR>
>>>>> \) wrote:<BR>
>>>>><BR>
>>>>><BR>
>>>>><BR>
>>>>>> If one wanted to go throught the trouble, I guess one<BR>
>>>> could specify a<BR>
>>>>>> standardized mechanism for CCSDS for configuring unique link <BR>
>>>>>> local<BR>
>>>>>> IPv6 addressed based on Spacecraft ID of some other space-unique<BR>
>>>>>> identifier.<BR>
>>>>><BR>
>>>>><BR>
>>>>> What would it take to produce a unique address from GSCID,<BR>
>>>> interface<BR>
>>>>> identification<BR>
>>>><BR>
>>>> a document that describes that.<BR>
>>>><BR>
>>>>> and (presumably) an allocated IPv6 space?<BR>
>>>><BR>
>>>> you meant address space for the network part? currently, you<BR>
>>>> get it from your upstream provider or directly from the<BR>
>>>> registries. Of course, in the process of planning a<BR>
>>>> deployment, address space would have to be looked up, but I'm<BR>
>>>> not sure that needs to be taken care in the ccsds "protocol" <BR>
>>>> profile.<BR>
>>>><BR>
>>>> Marc.<BR>
>>>><BR>
>>>>><BR>
>>>>> L.<BR>
>><BR>
>> -----<BR>
>> IPv6 book: Migrating to IPv6, Wiley, 2006, <A HREF="http://www.ipv6book.ca">http://www.ipv6book.ca</A><BR>
>><BR>
>><BR>
<BR>
-----<BR>
IPv6 book: Migrating to IPv6, Wiley, 2006, <A HREF="http://www.ipv6book.ca">http://www.ipv6book.ca</A><BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>