idnits 2.17.1 draft-birrane-dtn-adm-ltp-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** There are 13 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([I-D.birrane-dtn-adm]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 2, 2018) is 2118 days in the past. Is this intentional? Checking references for intended status: Experimental ---------------------------------------------------------------------------- == Outdated reference: A later version (-06) exists of draft-birrane-dtn-adm-02 == Outdated reference: A later version (-08) exists of draft-birrane-dtn-amp-04 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Delay-Tolerant Networking E. Birrane 3 Internet-Draft E. DiPietro 4 Intended status: Experimental D. Linko 5 Expires: January 3, 2019 Johns Hopkins Applied Physics Laboratory 6 July 2, 2018 8 Licklider Transmission Protocol Agent Application Data Model 9 draft-birrane-dtn-adm-ltp-00 11 Abstract 13 This document describes the Application Data Model (ADM) for a 14 Licklider Transmission Protocol Agent (LTPA) in compliance with the 15 template provided by [I-D.birrane-dtn-adm]. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on January 3, 2019. 34 Copyright Notice 36 Copyright (c) 2018 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Technical Notes . . . . . . . . . . . . . . . . . . . . . 2 53 1.2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.3. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 2. Structure and Design of this ADM . . . . . . . . . . . . . . 3 56 3. Naming and Identification . . . . . . . . . . . . . . . . . . 4 57 3.1. Namespace and Nicknames . . . . . . . . . . . . . . . . . 4 58 4. LTP Agent ADM JSON Encoding . . . . . . . . . . . . . . . . . 5 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 61 6.1. Informative References . . . . . . . . . . . . . . . . . 13 62 6.2. Normative References . . . . . . . . . . . . . . . . . . 13 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 65 1. Introduction 67 An Application Data Model (ADM) provides a guaranteed interface for 68 the management of an application or protocol in accordance with the 69 Asynchronous Management Architecture (AMA) defined in 70 [I-D.birrane-dtn-ama]. The ADM described in this document complies 71 with the ADM Template provided in [I-D.birrane-dtn-adm] as encoded 72 using the JSON syntax. 74 Licklider Transmission Protocol Agents (LTPAs) are software instances 75 that implement functionality required by the Licklider Transmission 76 Protocol [RFC5326]. LTP is a convergence layer protocol. There is 77 no flow control or congestion control in LTP. LTP must run either 78 over UDP or directly over a link layer protocol. Because of this, 79 LTP cannot be used in every situation. This LTP Agent ADM provides 80 the set of information necessary to provide retransmission based 81 reliability on challenged networks, focusing on the information that 82 an agent on a network implementing LTP would need in order to run 83 correctly. 85 1.1. Technical Notes 87 o This document describes Version 0.0 of the LTP Agent ADM. 89 o The AMM Resource Identifier (ARI) for this ADM is NOT correctly 90 set. A sample ARI is used in this version of the specification 91 and MAY change in future versions of this ADM until an ARI 92 registry is established. This notice will be removed at that 93 time. 95 o Agent applications MAY choose to ignore the name, description, or 96 other annotative information associated with the component 97 definitions within this ADM where such items are only used to 98 provide human-readable information or are otherwise not necessary 99 to manage a device. 101 1.2. Scope 103 This ADM specifies those components of the Asynchronous Management 104 Model (AMM) common to the management of any instance of a LTP Agent. 106 Any Manager software implementing this ADM MUST perform the 107 responsibilities of an AMA Manager as outlined in 108 [I-D.birrane-dtn-adm] as they relate to the objects included in this 109 document. 111 Any Agent software implementing this ADM MUST perform the 112 responsibilities of an AMA Agent as outlined in [I-D.birrane-dtn-adm] 113 as they relate to the objects included in this document. 115 1.3. Requirements Language 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 119 document are to be interpreted as described in RFC 2119 [RFC2119]. 121 2. Structure and Design of this ADM 123 The LTP Agent ADM's structure is in accordance to 124 [I-D.birrane-dtn-adm]. This ADM contains metadata, edd, report 125 templates, and controls. Externally Defined Data (EDD) are values 126 that are calculated external to the ADM system. Controls are 127 predefined and sometimes parameterized opcodes that can be run on an 128 Agent. Report Templates are ordered sets of data descriptions that 129 show how values will be represented in a corresponding report. There 130 are no variables, table templates, macros, or operators in this ADM 131 at this time. The contents of this ADM are derived from the main 132 functions and data that an agent needs to run LTP RFC 5326 [RFC5326]. 134 The Metadata that is present in this document is common to all ADMs. 135 All ADMs have metadata that includes the name, namespace, and version 136 of the ADM as well as the name of the organization that is issuing 137 that particular ADM. This is important for identification purposes 138 of the ADMs and to ensure version control. The main idea identified 139 in LTP that is present in this ADM is a span of potential LTP data 140 interchange between engines(nodes on a network that use LTP). 142 3. Naming and Identification 144 This section outlines the namespaces used to uniquely identify ADM 145 objects in this specification. 147 3.1. Namespace and Nicknames 149 In accordance with [I-D.birrane-dtn-adm], every ADM is assigned a 150 moderated Namespace. In accordance with [I-D.birrane-dtn-amp], these 151 namespaces may be enumerated for compactness. The namespace and ADM 152 identification for these objects is defined as follows. 154 +-----------------+---------------+ 155 | Identifier | Value | 156 +-----------------+---------------+ 157 | Namespace | DTN/ltp_agent | 158 | | | 159 | ADM Enumeration | 3 | 160 +-----------------+---------------+ 162 Table 1: Namespace Information 164 Given the above ADM enumeration, in accordance with 165 [I-D.birrane-dtn-amp], the following AMP nicknames are defined. 167 +----------+------------------------------+ 168 | Nickname | Collection as an ARI | 169 +----------+------------------------------+ 170 | 60 | DTN/ltp_agent/Const | 171 | | | 172 | 61 | DTN/ltp_agent/Ctrl | 173 | | | 174 | 62 | DTN/ltp_agent/Edd | 175 | | | 176 | 63 | DTN/ltp_agent/Mac | 177 | | | 178 | 64 | DTN/ltp_agent/Oper | 179 | | | 180 | 65 | DTN/ltp_agent/Rptt | 181 | | | 182 | 67 | DTN/ltp_agent/Tblt | 183 | | | 184 | 69 | DTN/ltp_agent/Var | 185 | | | 186 | 70 | DTN/ltp_agent/Mdat | 187 | | | 188 | 71-79 | DTN/ltp_agent/Reserved | 189 +----------+------------------------------+ 191 Table 2: LTP ADM Nicknames 193 4. LTP Agent ADM JSON Encoding 195 { 196 "Mdat": [ 197 { 198 "name": "name", 199 "type": "STR", 200 "value": "ltp_agent", 201 "description": "The human-readable name of the ADM." 202 }, 203 { 204 "name": "namespace", 205 "type": "STR", 206 "value": "DTN/ltp_agent", 207 "description": "The namespace of the ADM." 208 }, 209 { 210 "name": "version", 211 "type": "STR", 212 "value": "v0.0", 213 "description": "The version of the ADM." 214 }, 215 { 216 "name": "organization", 217 "type": "STR", 218 "value": "JHUAPL", 219 "description": "The name of the issuing organization of the ADM." 220 } 221 ], 222 "Edd": [ 223 { 224 "name": "span_remote_engine_nbr", 225 "type": "UINT", 226 "parmspec": [{"type":"UINT","name":"ltp_span"}], 227 "description": "The remote engine number of this span." 228 }, 229 { 230 "name": "span_cur_expt_sess", 231 "type": "UINT", 232 "parmspec": [{"type":"UINT","name":"ltp_span"}], 233 "description": "Expected sessions on this span." 234 }, 235 { 236 "name": "span_cur_out_seg", 237 "type": "UINT", 238 "parmspec": [{"type":"UINT","name":"ltp_span"}], 239 "description": "The current number of outbound segments for this 240 span." 241 }, 242 { 243 "name": "span_cur_imp_sess", 244 "type": "UINT", 245 "parmspec": [{"type":"UINT","name":"ltp_span"}], 246 "description": "The current number of import segments for this span." 247 }, 248 { 249 "name": "span_cur_in_seg", 250 "type": "UINT", 251 "parmspec": [{"type":"UINT","name":"ltp_span"}], 252 "description": "The current number of inbound segments for this span." 253 }, 254 { 255 "name": "span_reset_time", 256 "type": "UVAST", 257 "parmspec": [{"type":"UINT","name":"ltp_span"}], 258 "description": "The last time the span counters were reset." 259 }, 260 { 261 "name": "span_out_seg_q_cnt", 262 "type": "UINT", 263 "parmspec": [{"type":"UINT","name":"ltp_span"}], 264 "description": "The output segment queued count for the span." 265 }, 266 { 267 "name": "span_out_seg_q_bytes", 268 "type": "UINT", 269 "parmspec": [{"type":"UINT","name":"ltp_span"}], 270 "description": "The output segment queued bytes for the span." 271 }, 272 { 273 "name": "span_out_seg_pop_cnt", 274 "type": "UINT", 275 "parmspec": [{"type":"UINT","name":"ltp_span"}], 276 "description": "The output segment popped count for the span." 277 }, 278 { 279 "name": "span_out_seg_pop_bytes", 280 "type": "UINT", 281 "parmspec": [{"type":"UINT","name":"ltp_span"}], 282 "description": "The output segment popped bytes for the span." 283 }, 284 { 285 "name": "span_out_ckpt_xmit_cnt", 286 "type": "UINT", 287 "parmspec": [{"type":"UINT","name":"ltp_span"}], 288 "description": "The output checkpoint transmit count for the span." 289 }, 290 { 291 "name": "span_out_pos_ack_rx_cnt", 292 "type": "UINT", 293 "parmspec": [{"type":"UINT","name":"ltp_span"}], 294 "description": "The output positive acknowledgement received count 295 for the span." 296 }, 297 { 298 "name": "span_out_neg_ack_rx_cnt", 299 "type": "UINT", 300 "parmspec": [{"type":"UINT","name":"ltp_span"}], 301 "description": "The output negative acknowledgement received count 302 for the span." 303 }, 304 { 305 "name": "span_out_cancel_rx_cnt", 306 "type": "UINT", 307 "parmspec": [{"type":"UINT","name":"ltp_span"}], 308 "description": "The output cancelled received count for the span." 309 }, 310 { 311 "name": "span_out_ckpt_rexmit_cnt", 312 "type": "UINT", 313 "parmspec": [{"type":"UINT","name":"ltp_span"}], 314 "description": "The output checkpoint retransmit count for the span." 315 }, 316 { 317 "name": "span_out_cancel_xmit_cnt", 318 "type": "UINT", 319 "parmspec": [{"type":"UINT","name":"ltp_span"}], 320 "description": "The output cancel retransmit count for the span." 321 }, 322 { 323 "name": "span_out_complete_cnt", 324 "type": "UINT", 325 "parmspec": [{"type":"UINT","name":"ltp_span"}], 326 "description": "The output completed count for the span." 327 }, 328 { 329 "name": "span_in_seg_rx_red_cnt", 330 "type": "UINT", 331 "parmspec": [{"type":"UINT","name":"ltp_span"}], 332 "description": "The input segment received red count for the span." 333 }, 334 { 335 "name": "span_in_seg_rx_red_bytes", 336 "type": "UINT", 337 "parmspec": [{"type":"UINT","name":"ltp_span"}], 338 "description": "The input segment received red bytes for the span." 339 }, 340 { 341 "name": "span_in_seg_rx_green_cnt", 342 "type": "UINT", 343 "parmspec": [{"type":"UINT","name":"ltp_span"}], 344 "description": "The input segment received green count for the span." 345 }, 346 { 347 "name": "span_in_seg_rx_green_bytes", 348 "type": "UINT", 349 "parmspec": [{"type":"UINT","name":"ltp_span"}], 350 "description": "The input segment received green bytes for the span." 351 }, 352 { 353 "name": "span_in_seg_rx_redundant_cnt", 354 "type": "UINT", 355 "parmspec": [{"type":"UINT","name":"ltp_span"}], 356 "description": "The input segment received redundant count for the 357 span." 358 }, 359 { 360 "name": "span_in_seg_rx_redundant_bytes", 361 "type": "UINT", 362 "parmspec": [{"type":"UINT","name":"ltp_span"}], 363 "description": "The input segment received redundant bytes for the 364 span." 365 }, 366 { 367 "name": "span_in_seg_rx_mal_cnt", 368 "type": "UINT", 369 "parmspec": [{"type":"UINT","name":"ltp_span"}], 370 "description": "The input segment malformed count for the span." 371 }, 372 { 373 "name": "span_in_seg_rx_mal_bytes", 374 "type": "UINT", 375 "parmspec": [{"type":"UINT","name":"ltp_span"}], 376 "description": "The input segment malformed bytes for the span." 377 }, 378 { 379 "name": "span_in_seg_rx_unk_sender_cnt", 380 "type": "UINT", 381 "parmspec": [{"type":"UINT","name":"ltp_span"}], 382 "description": "The input segment unknown sender count for the span." 383 }, 384 { 385 "name": "span_in_seg_rx_unk_sender_bytes", 386 "type": "UINT", 387 "parmspec": [{"type":"UINT","name":"ltp_span"}], 388 "description": "The input segment unknown sender bytes for the span." 389 }, 390 { 391 "name": "span_in_seg_rx_unk_client_cnt", 392 "type": "UINT", 393 "parmspec": [{"type":"UINT","name":"ltp_span"}], 394 "description": "The input segment unknown client count for the span." 395 }, 396 { 397 "name": "span_in_seg_rx_unk_client_bytes", 398 "type": "UINT", 399 "parmspec": [{"type":"UINT","name":"ltp_span"}], 400 "description": "The input segment unknown client bytes for the span." 401 }, 402 { 403 "name": "span_in_seg_stray_cnt", 404 "type": "UINT", 405 "parmspec": [{"type":"UINT","name":"ltp_span"}], 406 "description": "The input segment stray count for the span." 408 }, 409 { 410 "name": "span_in_seg_stray_bytes", 411 "type": "UINT", 412 "parmspec": [{"type":"UINT","name":"ltp_span"}], 413 "description": "The input segment stray bytes for the span." 414 }, 415 { 416 "name": "span_in_seg_miscolor_cnt", 417 "type": "UINT", 418 "parmspec": [{"type":"UINT","name":"ltp_span"}], 419 "description": "The input segment miscolored count for the span." 420 }, 421 { 422 "name": "span_in_seg_miscolor_bytes", 423 "type": "UINT", 424 "parmspec": [{"type":"UINT","name":"ltp_span"}], 425 "description": "The input segment miscolored bytes for the span." 426 }, 427 { 428 "name": "span_in_seg_closed_cnt", 429 "type": "UINT", 430 "parmspec": [{"type":"UINT","name":"ltp_span"}], 431 "description": "The input segment closed count for the span." 432 }, 433 { 434 "name": "span_in_seg_closed_bytes", 435 "type": "UINT", 436 "parmspec": [{"type":"UINT","name":"ltp_span"}], 437 "description": "The input segment closed bytes for the span." 438 }, 439 { 440 "name": "span_in_ckpt_rx_cnt", 441 "type": "UINT", 442 "parmspec": [{"type":"UINT","name":"ltp_span"}], 443 "description": "The input checkpoint receive count for the span." 444 }, 445 { 446 "name": "span_in_pos_ack_tx_cnt", 447 "type": "UINT", 448 "parmspec": [{"type":"UINT","name":"ltp_span"}], 449 "description": "The input positive acknolwedgement transmitted 450 count for the span." 451 }, 452 { 453 "name": "span_in_neg_ack_tx_cnt", 454 "type": "UINT", 455 "parmspec": [{"type":"UINT","name":"ltp_span"}], 456 "description": "The input negative acknolwedgement transmitted 457 count for the span." 458 }, 459 { 460 "name": "span_in_cancel_tx_cnt", 461 "type": "UINT", 462 "parmspec": [{"type":"UINT","name":"ltp_span"}], 463 "description": "The input cancel transmitted count for the span." 464 }, 465 { 466 "name": "span_in_ack_retx_cnt", 467 "type": "UINT", 468 "parmspec": [{"type":"UINT","name":"ltp_span"}], 469 "description": "The input acknolwedgement retransmit count for 470 the span." 471 }, 472 { 473 "name": "span_in_cancel_rx_cnt", 474 "type": "UINT", 475 "parmspec": [{"type":"UINT","name":"ltp_span"}], 476 "description": "The input cancel receive count for the span." 477 }, 478 { 479 "name": "span_in_complete_cnt", 480 "type": "UINT", 481 "parmspec": [{"type":"UINT","name":"ltp_span"}], 482 "description": "The input completed count for the span." 483 } 484 ], 485 "Rptt": [ 486 { 487 "name": "endpointReport", 488 "parmspec": [{"type":"UINT","name":"ltp_span"}], 489 "definition": [ 490 "DTN/ltp_agent/edd.span_remote_engine_nbr();", 491 "DTN/ltp_agent/edd.span_cur_expt_sess();", 492 "DTN/ltp_agent/edd.span_cur_out_seg();", 493 "DTN/ltp_agent/edd.span_cur_imp_sess();", 494 "DTN/ltp_agent/edd.span_cur_in_seg();", 495 "DTN/ltp_agent/edd.span_reset_time();", 496 "DTN/ltp_agent/edd.span_out_seg_q_cnt();", 497 "DTN/ltp_agent/edd.span_out_seg_q_bytes();", 498 "DTN/ltp_agent/edd.span_out_seg_pop_cnt();", 499 "DTN/ltp_agent/edd.span_out_seg_pop_bytes();", 500 "DTN/ltp_agent/edd.span_out_ckpt_xmit_cnt();", 501 "DTN/ltp_agent/edd.span_out_pos_ack_rx_cnt();", 502 "DTN/ltp_agent/edd.span_out_neg_ack_rx_cnt();", 503 "DTN/ltp_agent/edd.span_out_cancel_rx_cnt();", 504 "DTN/ltp_agent/edd.span_out_ckpt_rexmit_cnt();", 505 "DTN/ltp_agent/edd.span_out_cancel_xmit_count();", 506 "DTN/ltp_agent/edd.span_out_complete_cnt();", 507 "DTN/ltp_agent/edd.span_in_seg_rx_red_cnt();", 508 "DTN/ltp_agent/edd.span_in_seg_rx_red_bytes();", 509 "DTN/ltp_agent/edd.span_in_seg_rx_green_cnt();", 510 "DTN/ltp_agent/edd.span_in_seg_rx_green_bytes();", 511 "DTN/ltp_agent/edd.span_in_seg_rx_redundant_cnt();", 512 "DTN/ltp_agent/edd.span_in_seg_rx_redundant_bytes();", 513 "DTN/ltp_agent/edd.span_in_seg_rx_mal_cnt();", 514 "DTN/ltp_agent/edd.span_in_seg_rx_mal_bytes();", 515 "DTN/ltp_agent/edd.span_in_seg_rx_unk_sender_cnt();", 516 "DTN/ltp_agent/edd.span_in_seg_rx_unk_sender_bytes();", 517 "DTN/ltp_agent/edd.span_in_seg_rx_unk_client_cnt();", 518 "DTN/ltp_agent/edd.span_in_seg_rx_unk_client_bytes();", 519 "DTN/ltp_agent/edd.span_in_seg_stray_cnt();", 520 "DTN/ltp_agent/edd.span_in_seg_stray_bytes();", 521 "DTN/ltp_agent/edd.span_in_seg_miscolor_cnt();", 522 "DTN/ltp_agent/edd.span_in_seg_miscolor_bytes();", 523 "DTN/ltp_agent/edd.span_in_seg_closed_cnt();", 524 "DTN/ltp_agent/edd.span_in_seg_closed_bytes();", 525 "DTN/ltp_agent/edd.span_in_ckpt_rx_cnt();", 526 "DTN/ltp_agent/edd.span_in_pos_ack_tx_cnt();", 527 "DTN/ltp_agent/edd.span_in_neg_ack_tx_cnt();", 528 "DTN/ltp_agent/edd.span_in_cancel_tx_cnt();", 529 "DTN/ltp_agent/edd.span_in_ack_retx_cnt();", 530 "DTN/ltp_agent/edd.span_in_cancel_rx_cnt();", 531 "DTN/ltp_agent/edd.span_in_complete_cnt();" 532 ], 533 "description": "This is all known endpoint information" 534 } 535 ], 537 "Ctrl": [ 538 { 539 "name": "reset", 540 "parmspec": [{"type":"UINT","name":"ltp_span"}], 541 "description": "Resets the counters associated with the engine and 542 updates the last reset time for the span to be the time when this 543 control was run." 544 }, 545 { 546 "name": "list_engines", 547 "description": "Lists all remote engine IDs." 548 } 549 ] 550 } 551 5. IANA Considerations 553 At this time, this protocol has no fields registered by IANA. 555 6. References 557 6.1. Informative References 559 [I-D.birrane-dtn-ama] 560 Birrane, E., "Asynchronous Management Architecture", 561 draft-birrane-dtn-ama-07 (work in progress), June 2018. 563 6.2. Normative References 565 [I-D.birrane-dtn-adm] 566 Birrane, E., DiPietro, E., and D. Linko, "AMA Application 567 Data Model", draft-birrane-dtn-adm-02 (work in progress), 568 June 2018. 570 [I-D.birrane-dtn-amp] 571 Birrane, E., "Asynchronous Management Protocol", draft- 572 birrane-dtn-amp-04 (work in progress), June 2018. 574 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 575 Requirement Levels", BCP 14, RFC 2119, 576 DOI 10.17487/RFC2119, March 1997, 577 . 579 [RFC5326] Ramadas, M., Burleigh, S., and S. Farrell, "Licklider 580 Transmission Protocol - Specification", RFC 5326, 581 DOI 10.17487/RFC5326, September 2008, 582 . 584 Authors' Addresses 586 Edward J. Birrane 587 Johns Hopkins Applied Physics Laboratory 589 Email: Edward.Birrane@jhuapl.edu 591 Evana DiPietro 592 Johns Hopkins Applied Physics Laboratory 594 Email: Evana.DiPietro@jhuapl.edu 595 David Linko 596 Johns Hopkins Applied Physics Laboratory 598 Email: David.Linko@jhuapl.edu