1. SIS_DTN 1 SIS-DTN LTP Protocol Specification May 2010

2. SIS_DTN 2 Agenda Goals of this activity Advance LTP towards Blue Book status Overview of LTP Goals of the protocol How LTP fits in with Internetworking / Bundle Protocol LTP Operation Comments on the specification To Do Implementations exist (Burleigh, Farrell, Ramadas) Write and execute test plan May 2010

3. SIS_DTN 3 BP App LTP Overview LTP sits at roughly layer 2.5 in the ISO stack, providing optionally-reliable communications across a single data link ‘hop’ In the context of CCSDS, LTP is intended to run primarily over the CCSS Encapsulation service For DTN / SSI, LTP serves as a ‘Convergence Layer’ for the Bundle Protocol, providing reliability for 1-hop communications May 2010 LTP User BP CLA LTP CCSDS Encapsulation CCSDS Data Link (e.g. TC/TM, Prox-1, AOS) CCSDS Encapsulation LTP Optionally-Reliable 1-HOP Communications Provides length field and allows LTP blocks to be efficiently packed into underlying frames. CCSDS RF, coding, and modulation BP BP App LTP User BP CLA BP BP App Optionally-reliable multi-hop space internetworking

4. SIS_DTN 4 BP App LTP Overview LTP sits at roughly layer 2.5 in the ISO stack, providing optionally-reliable communications across a single data link ‘hop’ In the context of CCSDS, LTP is intended to run primarily over the CCSS Encapsulation service For DTN / SSI, LTP serves as a ‘Convergence Layer’ for the Bundle Protocol, providing reliability for 1-hop communications May 2010 LTP User BP CLA LTP CCSDS Encapsulation CCSDS Data Link (e.g. TC/TM, Prox-1, AOS) CCSDS Encapsulation LTP Optionally-Reliable 1-HOP Communications Provides length field and allows LTP blocks to be efficiently packed into underlying frames. CCSDS RF, coding, and modulation BP BP App LTP User BP CLA BP BP App Optionally-reliable multi-hop space internetworking

5. SIS_DTN 5 LTP Operation May 2010 Fix me: after CP, EORP loss, retransmit.

6. SIS_DTN 6 The CCSDS LTP Red Book CCSDS Boilerplate Overview Service Specification (extracted from the RFC) RFC5326 (Licklider Transmission Protocol) Any comments on the specification? http://tools.ietf.org/rfc/rfc5326.txt Some LTP parameters are SDNVs (e.g. LTP session #s, checkpoint #s, report serial #s) and may be randomly selected integers – could be really really big (might want to restrict to --- a few bytes) Note: PICS and MIB sections will cover the normatively referenced RFC Security Extensions (RFC5327)? [authentication, cookies] – can omit if running BP over LTP? (use BAB instead) Informative reference to SDNV RFC (pending) Mapping LTP onto lower-layers (Link Service Adaptors for LTP – e.g. for Encap) Issues w/ maximum LTP segment size to deal with underlying layer.e.g. TC (TC is 10 bits of length with no segmentation unless you use the MAP) Options for multiple checkpoints when transmitting (prohibit?) Asynchronously generated report segments (allow or deny these?) May 2010

7. SIS_DTN 7 LTP Segment Format May 2010 Version Number (0x01) Segment Type Flags Session ID (Engine ID of source, session number chosen by sender) Header Extensions Segment Content Trailer Extensions Header Extension CountTrailer Extension Count Header Trailer Control-Byte Extensions 01234567 CTRLEXCFlag1Flag0

8. SIS_DTN 8 Flags May 2010 CTRL EXC Flag 1 Flag 0 Code Nature of segment ---- --- ------ ------ ---- --------------------------------------- 0 0 0 0 0 Red data, NOT {Checkpoint, EORP or EOB} 0 0 0 1 1 Red data, Checkpoint, NOT {EORP or EOB} 0 0 1 0 2 Red data, Checkpoint, EORP, NOT EOB 0 0 1 1 3 Red data, Checkpoint, EORP, EOB 0 1 0 0 4 Green data, NOT EOB 0 1 0 1 5 Green data, undefined 0 1 1 0 6 Green data, undefined 0 1 1 1 7 Green data, EOB 1 0 0 0 8 Report segment 1 0 0 1 9 Report-acknowledgment segment 1 0 1 0 10 Control segment, undefined 1 0 1 1 11 Control segment, undefined 1 1 0 0 12 Cancel segment from block sender 1 1 0 1 13 Cancel-acknowledgment segment to block sender 1 1 1 0 14 Cancel segment from block receiver 1 1 1 1 15 Cancel-acknowledgment segment to block receiver

9. SIS_DTN 9 Backups May 2010

10. SIS_DTN 10 May 2010 Sending LTP Entity Receiving LTP Entity Sending LTP User Receiving LTP User RS CP, EORP RS CP RSReport Segment CPCheckpoint EORPEnd of Red Part Transaction. request SessionStart.indication GSArrival.indications RedPartReception. indication TransmissionSession Complete. indication CP, EORP RS InitialTransmission Complete.indication LTP Block Portion of block to be transmitted reliably. Portion of block to be transmitted unreliably.