[Sis-dtn] [EXT] RE: LTP vs LTPv2

[Tomaso.deCola at dlr.de]

Hi Keith,

I agree with your point on troubles in maintaining two books and the fact that this will imply the same treatment for BPv7. Then whether agencies are happy to refer to a silver book rather than a blue book is a bit question mark in my opinion. I remember we decided a few years ago not to silverize SCPS-TP exactly because there were activities or usage of the corresponding blue book.
We can certainly bring this matter to the next CESG meeting, although I fear that there might be no strict decision in this regard, since I think there is no specific rule again either approaches and the hot potato could be sent back to WG.

Regards,

Tomaso
From: Dr. Keith L Scott <kscott at mitre.org>
Sent: Freitag, 8. Oktober 2021 15:52
To: Cola, Tomaso de <Tomaso.deCola at dlr.de>; marc.sanchez.net at jpl.nasa.gov
Cc: sis-dtn at mailman.ccsds.org
Subject: Re: [EXT] RE: LTP vs LTPv2

I don't like it, but I propose that the WG move forward with developing the book and you bring up the new-version vs. new-book issue to the CESG.

Reasons I don't like the two-book solution:


  *   So now we're maintaining two versions of LTP, which version are folks supposed to choose for missions going forward?  They'll choose the one with flight heritage, right?
  *   We'll have to do the same thing with BPv7
  *   There's a version number in the header; receivers will know what was sent.
  *   The book as Silver is still reference-able.  If folks have systems they're building to the current (v1) book, they can switch to referencing the silver book.
  *   Why don't we do that with ALL CCSDS books, backward-compatible or not?

--keith


From: Tomaso.deCola at dlr.de<mailto:Tomaso.deCola at dlr.de> <Tomaso.deCola at dlr.de<mailto:Tomaso.deCola at dlr.de>>
Date: Friday, October 8, 2021 at 4:19 AM
To: marc.sanchez.net at jpl.nasa.gov<mailto:marc.sanchez.net at jpl.nasa.gov> <marc.sanchez.net at jpl.nasa.gov<mailto:marc.sanchez.net at jpl.nasa.gov>>, Dr. Keith L Scott <kscott at mitre.org<mailto:kscott at mitre.org>>
Cc: sis-dtn at mailman.ccsds.org<mailto:sis-dtn at mailman.ccsds.org> <sis-dtn at mailman.ccsds.org<mailto:sis-dtn at mailman.ccsds.org>>
Subject: [EXT] RE: LTP vs LTPv2
Then probably we should better keep two books, one with the "old LTP" for which we'll do some pink sheets to fix some inconsistencies and another one (the new LTP). In such a away we could have two versions of LTP available, similarly to IPv4 and IPv6 in IETF. Probably we may have to slightly change the title of the books (v1 and v2?) to have a clear demarcation between the two version of the protocols and avoid any ambiguity.
@Scott, Keith L.<mailto:kscott at mitre.org>:what do you think?

Tomaso

From: SIS-DTN <sis-dtn-bounces at mailman.ccsds.org<mailto:sis-dtn-bounces at mailman.ccsds.org>> On Behalf Of Sanchez Net, Marc (US 332H) via SIS-DTN
Sent: Donnerstag, 7. Oktober 2021 00:21
To: sis-dtn at mailman.ccsds.org<mailto:sis-dtn at mailman.ccsds.org>
Subject: [Sis-dtn] LTP vs LTPv2

All,

I had to leave today's meeting early. Did we reach consensus on how to proceed?

Also, I will note that some colleagues at JPL (I have similar concerns) do not really like the idea of turning the current version of LTP into a silver book. The problem is that, by definition, a silver book implies that a protocol is deprecated or obsolete, but several systems that are being built today use BPv6+LTP or BPv7+LTP and thus might be in operation for a long time. So, essentially, we are "telling" industry that they have developed an already obsolete standard?

Best,
-----------------------------------------------------------------------------------------------------------------------
Marc Sanchez Net
Telecommunications Engineer
Jet Propulsion Laboratory
Office: (818) 354-1650<tel:(818)%20393-5840> | Email: marc.sanchez.net at jpl.nasa.gov<mailto:marc.sanchez.net at jpl.nasa.gov>
-----------------------------------------------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20211008/b4b9533a/attachment-0001.htm>