ccsds 131.0-b-2

More documents

Recommendations

Info

CCSDS RECOMMENDED STANDARD FOR TM SYNCHRONIZATION AND CHANNEL CODINGANNEX BSECURITY, SANA, AND PATENT CONSIDERATIONS(INFORMATIVE)B1SECURITY CONSIDERATIONSB1.1 SECURITY BACKGROUNDIt is assumed that security is provided by encryption, authentication methods, and accesscontrol to be performed at higher layers (application and/or transport layers). Mission andservice providers are expected to select from recommended security methods, suitable to thespecific application profile. Specification of these security methods and other securityprovisions is outside the scope of this Recommended Standard. The coding layer has theobjective of delivering data with the minimum possible amount of residual errors. An LDPC,Reed-Solomon, or other code with CRC code must be used to insure that residual errors aredetected and the frame flagged. There is an extremely low probability of additionalundetected errors that may escape this scrutiny. These errors may affect the encryptionprocess in unpredictable ways, possibly affecting the decryption stage and producing dataloss, but will not compromise the security of the data.B1.2 SECURITY CONCERNSSecurity concerns in the areas of data privacy, authentication, access control, availability ofresources, and auditing are to be addressed in higher layers and are not related to thisRecommended Standard. The coding layer does not affect the proper functioning of methodsused to achieve such protection at higher layers, except for undetected errors, as explainedabove.The physical integrity of data bits is protected from channel errors by the coding systemsspecified in this Recommended Standard. In case of congestion or disruption of the link, thecoding layer provides methods for frame re-synchronization.B1.3 POTENTIAL THREATS AND ATTACK SCENARIOSAn eavesdropper can receive and decode the codewords, but will not be able to get to theuser data if proper encryption is performed at a higher layer. An interferer could affect theperformance of the decoder by congesting it with unwanted data, but such data would berejected by the authentication process. Such interference or jamming must be dealt with atthe Physical Layer and through proper spectrum regulatory entities.CCSDS <strong>131.0</strong>-B-2 Page B-1 August 2011
CCSDS RECOMMENDED STANDARD FOR TM SYNCHRONIZATION AND CHANNEL CODINGB1.4 CONSEQUENCES OF NOT APPLYING SECURITYThere are no specific security measures prescribed for the coding layer. Thereforeconsequences of not applying security are only imputable to the lack of proper securitymeasures in other layers. Residual undetected errors may produce additional data loss whenthe link carries encrypted data.B2SANA CONSIDERATIONSThe recommendations of this document do not require any action from SANA.B3PATENT CONSIDERATIONSB3.1 TURBO CODINGImplementers should be aware that a wide class of Turbo codes is covered by a patent byFrance Télécom and Télédiffusion de France under US Patent 5,446,747 and its counterpartsin other countries.Potential user agencies should direct their requests for licenses to:Mr. Christian HamonCCETT GIE/CVP4 rue du Clos CourtelBP59, 35512 CESSON SEVIGNE Cedex, FranceTel: +33 2 99 12 48 05, Fax: +33 2 99 12 40 98E-mail: christian.hamon@cnet.francetelecom.frB3.2 LDPC CODINGImplementers should be aware that the 1/2-, 2/3-, and 4/5-rate codes are covered by USPatent 7,343,539. Potential user agencies should direct their requests for licenses to:Office of Technology TransferCalifornia Institute of Technology1200 E. California Blvd., Mail Code 210-85Pasadena, CA 91125Tel: +1 626 395 3822, +1 626 577 2528E-mail: Vieregg@Caltech.eduCCSDS <strong>131.0</strong>-B-2 Page B-2 August 2011
Page 1 and 2:
Recommendation for Space Data Syste
Page 3 and 4:
CCSDS RECOMMENDED STANDARD FOR TM S
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22: CCSDS RECOMMENDED STANDARD FOR TM S
Page 71: CCSDS RECOMMENDED STANDARD FOR TM S
show all

ccsds 131.0-b-2

Create successful ePaper yourself

Delete template?

Save as template?