[Sis-dtn] CCSDS Notification -- Renew / Retire / Update SCPS-TP specification in CCSDS

Burleigh, Scott C (312B) scott.c.burleigh at jpl.nasa.gov
Mon Feb 1 16:12:23 UTC 2016 

I would agree with either renewing or retiring the SCPS-TP specification.  If there were some potential advantage – and no recurring cost – in retaining it as “active” I’d renew it.  But I don’t know of any advantage at this point, and there is the small recurring cost of revisiting it every few years, so retiring it seems like the best option.

Scott

From: sis-dtn-bounces at mailman.ccsds.org [mailto:sis-dtn-bounces at mailman.ccsds.org] On Behalf Of Pitts, Robert L. (MSFC-EO50)[HOSC SERVICES CONTRACT]
Sent: Monday, February 1, 2016 6:26 AM
To: Vint Cerf <vint at google.com>; Scott, Keith L (9730-Affiliate) <kscott at mitre.org>
Cc: scps-interest at mailman.ccsds.org; sis-dtn at mailman.ccsds.org; sis-cfdpv1 at mailman.ccsds.org
Subject: RE: [Sis-dtn] CCSDS Notification -- Renew / Retire / Update SCPS-TP specification in CCSDS

I believe I concur with Vint.  Emeritus is appropriate (silver) but expending effort that could be better served elsewhere would be inappropriate.

Lee

From: sis-dtn-bounces at mailman.ccsds.org<mailto:sis-dtn-bounces at mailman.ccsds.org> [mailto:sis-dtn-bounces at mailman.ccsds.org] On Behalf Of Vint Cerf
Sent: Monday, February 01, 2016 8:12 AM
To: Scott, Keith L.
Cc: scps-interest at mailman.ccsds.org<mailto:scps-interest at mailman.ccsds.org>; sis-dtn at mailman.ccsds.org<mailto:sis-dtn at mailman.ccsds.org>; sis-cfdpv1 at mailman.ccsds.org<mailto:sis-cfdpv1 at mailman.ccsds.org>
Subject: Re: [Sis-dtn] CCSDS Notification -- Renew / Retire / Update SCPS-TP specification in CCSDS

if these older protocols are not operational and if there are no plans to deploy them, it seems to me that retaining the documentation in some kind of retired or emeritus status is appropriate.

v


On Mon, Feb 1, 2016 at 8:57 AM, Scott, Keith L. <kscott at mitre.org<mailto:kscott at mitre.org>> wrote:
Greetings,

The SCPS-TP specification is again overdue for reconfirmation within CCSDS.  At this time we have the opportunity to:

  1.  RENEW the specification for another 5 years — essentially leaving it as-is.
  2.  RETIRE the specification to ‘silver<http://public.ccsds.org/publications/SilverBooks.aspx>’ status — it will remain accessible via the CCSDS website but will no longer be considered an ‘active’ CCSDS Specification

     *   We did this already with the SCPS-NP<http://public.ccsds.org/publications/archive/713x0b1s.pdf>, SCPS-SP,<http://public.ccsds.org/publications/archive/713x5b1sc1.pdf> and SCPS-FP<http://public.ccsds.org/publications/archive/717x0b1s.pdf> protocols.
     *   SCPS-TP is not used in any known space missions.

  1.  UPDATE the specification — make changes to it.

     *   Note that updating the specification would require securing resources from two CCSDS member agencies, which would be very difficult unless there is a compelling need.
CCSDS has maintained the SCPS-TP specification mainly as a service to the terrestrial community using it.  As noted above, SCPS-TP has not been deployed in space missions and within CCSDS is being supplanted by the combination of TCP and the IP suite (where the IP suite can function well) and the BP suite (where the IP suite doesn’t function well).

The activity of determining what to do with the specification will be undertaken by the SIS area and discussed briefly during the SIS-DTN portion of the Spring meetings in Cleveland week of 4 April.

What I am interested in now are opinions from the community as to the three options above.  In particular, does anyone see a need for CCSDS to maintain the ‘active’ status of SCPS-TP?  Again, retiring the specification within CCSDS will NOT cause it to disappear, NOR will it change the fact that the TCP options that implement the signaling for SCPS-TP will remain defined in IANA.

V/r,



—keith


Dr. Keith Scott                                                                        Office: +1.703.983.6547<tel:%2B1.703.983.6547>
Chief Engineer, J86A                                                             Fax:      +1.703.983.7142<tel:%2B1.703.983.7142>
Communications Network Engineering & Analysis Email:  kscott at mitre.org<mailto:kscott at mitre.org>
The MITRE Corporation<http://www.mitre.org/>
M/S H300
7515 Colshire Drive
McLean, VA 22102

Area Director, CCSDS<http://www.ccsds.org/> Space Internetworking Services<http://cwe.ccsds.org/sis/default.aspx>

MITRE self-signs its own certificates.  Information about the MITRE PKI Certificate Chain is available from http://www.mitre.org/tech/mii/pki/

[cid:image001.png at 01D15CC8.47072440]<http://www.mitre.org/>



_______________________________________________
Sis-dtn mailing list
Sis-dtn at mailman.ccsds.org<mailto:Sis-dtn at mailman.ccsds.org>
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn



--
New postal address:
Google
1875 Explorer Street, 10th Floor
Reston, VA 20190
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20160201/dbea30a1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2755 bytes
Desc: image001.png
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20160201/dbea30a1/attachment.png>

More information about the SIS-DTN mailing list