[SIS-CFDPV1] CCSDS Notification -- Renew / Retire / Update SCPS-TP specification in CCSDS

[Chris.Taylor at esa.int]

Keith, from and ESA viewpoint we would vote for retiring the books. They can remain silver in perpetuity and thus available if we should need them. 
Regards
//ct
Sent from my iPad

> On 1 Feb 2016, at 14:58, Scott, Keith L. <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:
> RENEW the specification for another 5 years — essentially leaving it as-is.
> RETIRE the specification to ‘silver’ 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, SCPS-SP, and SCPS-FP protocols.
> SCPS-TP is not used in any known space missions.
> 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
> Chief Engineer, J86A                                                            
> Fax:      +1.703.983.7142
> Communications Network Engineering & Analysis
> Email:  kscott at mitre.org
> The MITRE Corporation
> M/S H300
> 7515 Colshire Drive
> McLean, VA 22102
>  
> Area Director, CCSDS Space Internetworking Services
>  
> MITRE self-signs its own certificates.  Information about the MITRE PKI Certificate Chain is available from http://www.mitre.org/tech/mii/pki/
> <6B72C8A7-BF57-46DC-B33A-CAE20825E097.png>
> 
> 

This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-cfdpv1/attachments/20160202/7bb144cc/attachment.html>