[Sis-csi] CCSDS Cislunar Telecon tomorrow, 7 Sept

[Marc Blanchet]

Le 06-09-07 à 13:01, Keith Hogie a écrit :

> Marc,
>
>  I agree that it's probably best focus on the CCSDS specific details
> and put the IPv6 details elsewhere.  I also just noticed RFC 4294
> "IPv6 Node Requirements"

look down in the authors section and see who has co-authored it... ;-)

> which runs through lots of the issues you
> mentioned.  But it also has words like "must", "should", and "may"
> that seem to provide some wiggle room for skipping some of the
> options for certain types of links.

however, the purpose of IPv6 Node requirements is different. Anyway,  
right, it is a good reference.

>   I'm not sure we want to
> take advantage of all of the "should" and "may" options and just
> say we won't support them though.  Those features are there for good
> reasons and we may not want to be too quick to drop them without
> doing more analysis of our future space networking needs.

agree.

marc.

>
> Keith Hogie
>
> Marc Blanchet wrote:
>
>> Le 06-09-07 à 12:39, Keith Hogie a écrit :
>>> Marc,
>>>
>>>   You raise some good points about IPv6 over serial links.  I  
>>> think  one
>>> of the most relevant RFCs is RFC 2590 "Transmission of IPv6  
>>> Packets  over Frame Relay Networks".  For IPv4 in space we use  
>>> RFC 2427 (STD  55)
>>> "Multiprotocol Interconnect over Frame Relay".  I haven't read  
>>> all of
>>> RFC 2590 but it looks like it addresses lots of the MTU and address
>>> discovery issues for IPv6 over serial links.
>> as I wrote, for most if not all link-layers, there is an RFC   
>> describing the interaction and the specifics of IPv6 over that  
>> link- layer.
>> a good starter is also the RFC on IPv6 over NBMA networks (RFC2491).
>>>
>>>   We may just want to mention these RFCs to point people at the   
>>> details
>>> of using IP over FR/HDLC over CCSDS links.  Running straight IPv6  
>>> over
>>> CCSDS would require adjustments similar to RFC 2590 to be mapped  
>>> into
>>> CCSDS virtual circuits.
>> we are in strong agreement!
>> Currently, I see the following possibilities (from my point of view):
>> a) keep IP over CCSDS doc as is. not sure that is very good.
>> b) add text to point to other documents (ex: ipv6 over frame  
>> relay).  not sure this is complete.
>> c) reference a future document to be written which describes the  
>> IPv6  over CCSDS specifics. the current IP over CCSDS document  
>> would only  cover the link layer basic stuff (for example, how to  
>> identify an  IPv6 packet in the encap frame) and clearly state  
>> that there is  another document describing the behavior of IPv6   
>> over CCSDS links.
>> d) add text in the IP over CCSDS doc to cover all the topics for  
>> IPv6  over CCSDS.
>> I see c) as the best path, but I'm new here in CCSDS...
>> Marc.
>>>
>
> ----------------------------------------------------------------------
>   Keith Hogie                   e-mail: Keith.Hogie at gsfc.nasa.gov
>   Computer Sciences Corp.       office: 301-794-2999  fax:  
> 301-794-9480
>   7700 Hubble Dr.
>   Lanham-Seabrook, MD 20706  USA        301-286-3203 @ NASA/Goddard
> ----------------------------------------------------------------------



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