idnits 2.17.1 draft-birrane-dtn-adm-ion-bpadmin-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 42 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 2125 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 Bundle Protocol Agent Application Data Model 9 draft-birrane-dtn-adm-ion-bpadmin-00 11 Abstract 13 This document describes the Application Data Model (ADM) for the 14 administration of Bundle Protocol (BP) ION 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. ION BP Admin ADM JSON Encoding . . . . . . . . . . . . . . . 5 59 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 61 6.1. Informative References . . . . . . . . . . . . . . . . . 14 62 6.2. Normative References . . . . . . . . . . . . . . . . . . 14 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 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 The ION Bundle Protocol Administration ADM contains all of the 75 functionality that is required for the configuration and management 76 of BP on the local ION node. 78 1.1. Technical Notes 80 o This document describes Version 0.0 of the ION BP Admin ADM. 82 o The Asynchronous Resource Identifier (ARI) for this ADM is NOT 83 correctly set. A sample ARI is used in this version of the 84 specification and MAY change in future versions of this ADM until 85 an ARI registry is established. This notice will be removed at 86 that time. 88 o Agent applications MAY choose to ignore the name, description, or 89 other annotative information associated with the component 90 definitions within this ADM where such items are only used to 91 provide human-readable information or are otherwise not necessary 92 to manage a device. 94 1.2. Scope 96 This ADM specifies those components of the Asynchronous Management 97 Model (AMM) common to the configuration and management of Bundle 98 Protocol in ION. 100 Any Manager software implementing this ADM MUST perform the 101 responsibilities of an AMA Manager as outlined in 102 [I-D.birrane-dtn-adm] as they relate to the objects included in this 103 document. 105 Any Agent software implementing this ADM MUST perform the 106 responsibilities of an AMA Agent as outlined in [I-D.birrane-dtn-adm] 107 as they relate to the objects included in this document. 109 1.3. Requirements Language 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119 [RFC2119]. 115 2. Structure and Design of this ADM 117 The BP Admin ADM's structure is in accordance to 118 [I-D.birrane-dtn-adm]. This ADM contains metadata, table templates, 119 and controls. Table Templates are column templates that will be 120 followed by any instance of this table available in the network. 121 They may not be created dynamically within the network by Managers. 122 Controls are predefined and sometimes parameterized opcodes that can 123 be run on an Agent. Controls are preconfigured in Agents and 124 Managers as part of ADM support. There are no variables, report 125 templates, constants, macros, edd, or operators in this ADM at this 126 time. The contents of this ADM are derived from the main functions 127 and data that are needed to configure and manage BP in accordance 128 with (WHICH VERSION OF BP). 130 All ADMs have metadata that includes the name, namespace, and version 131 of the ADM as well as the name of the organization that is issuing 132 that particular ADM. This is important for identification purposes 133 of the ADMs and to ensure version control. The table templates and 134 controls in this ADM deal with inducts, outducts, schemes, and 135 protocols, the most important things needed for the proper 136 administration of Bundle Protocol. 138 3. Naming and Identification 140 This section outlines the namespaces used to uniquely identify ADM 141 objects in this specification. 143 3.1. Namespace and Nicknames 145 In accordance with [I-D.birrane-dtn-adm], every ADM is assigned a 146 moderated Namespace. In accordance with [I-D.birrane-dtn-amp], these 147 namespaces may be enumerated for compactness. The namespace and ADM 148 identification for these objects is defined as follows. 150 +-----------------+------------------+ 151 | Identifier | Value | 152 +-----------------+------------------+ 153 | Namespace | DTN/ION/bpadmin/ | 154 | | | 155 | ADM Enumeration | 5 | 156 +-----------------+------------------+ 158 Table 1: Namespace Information 160 Given the above ADM enumeration, in accordance with 161 [I-D.birrane-dtn-amp], the following AMP nicknames are defined. 163 +----------+------------------------------+ 164 | Nickname | Collection | 165 +----------+------------------------------+ 166 | 100 | DTN/ION/bpadmin/Const | 167 | | | 168 | 101 | DTN/ION/bpadmin/Ctrl | 169 | | | 170 | 102 | DTN/ION/bpadmin/Edd | 171 | | | 172 | 103 | DTN/ION/bpadmin/Mac | 173 | | | 174 | 104 | DTN/ION/bpadmin/Oper | 175 | | | 176 | 105 | DTN/ION/bpadmin/Rptt | 177 | | | 178 | 107 | DTN/ION/bpadmin/Tblt | 179 | | | 180 | 109 | DTN/ION/bpadmin/Var | 181 | | | 182 | 110 | DTN/ION/bpadmin/Mdat | 183 | | | 184 | 111-119 | DTN/ION/bpadmin/Reserved | 185 +----------+------------------------------+ 187 Table 2: ION BP ADM Nicknames 189 4. ION BP Admin ADM JSON Encoding 191 The following is the JSON encoding of the Bundle Protocol Admin 192 Application Data Model: 194 { 195 "Mdat": [ 196 { 197 "name": "name", 198 "type": "STR", 199 "value": "ion_bp_admin", 200 "description": "The human-readable name of the ADM." 201 }, 202 { 203 "name": "namespace", 204 "type": "STR", 205 "value": "DTN/ION/bpadmin", 206 "description": "The namespace of the ADM" 207 }, 208 { 209 "name": "version", 210 "type": "STR", 211 "value": "v0.0", 212 "description": "The version of the ADM" 213 }, 214 { 215 "name": "organization", 216 "type": "STR", 217 "value": "JHUAPL", 218 "description": "The name of the issuing organization of the ADM" 219 } 220 ], 221 "Edd": [ 222 { 223 "name": "bp_version", 224 "type": "STR", 225 "description": "Version of installed ION BP Admin utility." 226 } 227 ], 228 "Tblt": [ 229 { 230 "name": "endpoints", 231 "columns": [ 232 {"type":"STR","name":"scheme_name"}, 233 {"type":"STR","name":"endpoint_nss"}, 234 {"type":"UINT","name":"app_pid"}, 235 {"type":"STR","name":"recv_rule"}, 236 {"type":"STR","name":"rcv_script"} 237 ], 238 "description": "Local endpoints, regardless of scheme name." 239 }, 240 { 241 "name": "inducts", 242 "columns": [ 243 {"type":"STR","name":"protocol_name"}, 244 {"type":"STR","name":"duct_name"}, 245 {"type":"STR","name":"cli_control"} 246 ], 247 "description": "Inducts established locally for the indicated CL 248 protocol." 249 }, 250 { 251 "name": "outducts", 252 "columns": [ 253 {"type":"STR","name":"protocol_name"}, 254 {"type":"STR","name":"duct_name"}, 255 {"type":"UINT","name":"clo_pid"}, 256 {"type":"STR","name":"clo_control"}, 257 {"type":"STR","name":"max_payload_length"} 258 ], 259 "description": "If protocolName is specified, this table lists all 260 outducts established locally for the indicated CL protocol. 261 Otherwise, it lists all locally established outducts, regardless 262 of their protocol." 263 }, 264 { 265 "name": "protocols", 266 "columns": [ 267 {"type":"STR","name":"name"}, 268 {"type":"UINT","name":"payload_bpf"}, 269 {"type":"UINT","name":"overhead_bpf"}, 270 {"type":"UINT","name":"nominal_data_rate"} 271 ], 272 "description": "Convergence layer protocols that can currently be 273 utilized at the local node." 274 }, 275 { 276 "name": "schemes", 277 "columns": [ 278 {"type":"STR","name":"scheme_name"}, 279 {"type":"UINT","name":"fwd_pid"}, 280 {"type":"STR","name":"fwd_cmd"}, 281 {"type":"UINT","name":"admin_app_pid"}, 282 {"type":"STR","name":"admin_app_cmd"} 283 ], 284 "description": "Declared endpoint naming schemes." 285 }, 286 { 287 "name": "egress_plans", 288 "columns": [ 289 {"type":"STR","name":"scheme_name"}, 290 {"type":"UINT","name":"fwd_pid"}, 291 {"type":"STR","name":"fwd_cmd"}, 292 {"type":"UINT","name":"admin_app_pid"}, 293 {"type":"STR","name":"admin_app_cmd"} 294 ], 295 "description": "Declared endpoint naming schemes." 296 } 297 ], 298 "Ctrl": [ 299 { 300 "name": "endpoint_add", 301 "parmspec": [ 302 {"type":"STR","name":"endpoint_id"}, 303 {"type":"UINT","name":"type"}, 304 {"type":"STR","name":"rcv_script"} 305 ], 306 "description": "Establish DTN endpoint named endpointId on the local 307 node. The remaining parameters indicate what is to be done when 308 bundles destined for this endpoint arrive at a time when no 309 application has the endpoint open for bundle reception. If type is 310 'x', then such bundles are to be discarded silently and immediately. 311 If type is 'q', then such bundles are to be enqueued for later 312 delivery and, if recvScript is provided, recvScript is to be 313 executed." 314 }, 315 { 316 "name": "endpoint_change", 317 "parmspec": [ 318 {"type":"STR","name":"endpoint_id"}, 319 {"type":"UINT","name":"type"}, 320 {"type":"STR","name":"rcv_script"} 321 ], 322 "description": "Change the action taken when bundles destined for this 323 endpoint arrive at a time when no application has the endpoint open 324 for bundle reception." 325 }, 326 { 327 "name": "endpoint_del", 328 "parmspec": [{"type":"STR","name":"endpoint_id"}], 329 "description": "Delete the endpoint identified by endpointId. The 330 control will fail if any bundles are currently pending delivery to 331 this endpoint." 332 }, 333 { 334 "name": "induct_add", 335 "parmspec": [ 336 {"type":"STR","name":"protocol_name"}, 337 {"type":"STR","name":"duct_name"}, 338 {"type":"STR","name":"cli_control"} 339 ], 340 "description": "Establish a duct for reception of bundles via the 341 indicated CL protocol. The duct's data acquisition structure is 342 used and populated by the induct task whose operation is initiated 343 by cliControl at the time the duct is started." 344 }, 345 { 346 "name": "induct_change", 347 "parmspec": [ 348 {"type":"STR","name":"protocol_name"}, 349 {"type":"STR","name":"duct_name"}, 350 {"type":"STR","name":"cli_control"} 351 ], 352 "description": "Change the control used to initiate operation of the 353 induct task for the indicated duct." 354 }, 355 { 356 "name": "induct_del", 357 "parmspec": [ 358 {"type":"STR","name":"protocol_name"}, 359 {"type":"STR","name":"duct_name"} 360 ], 361 "description": "Delete the induct identified by protocolName and 362 ductName. The control will fail if any bundles are currently 363 pending acquisition via this induct." 364 }, 365 { 366 "name": "induct_start", 367 "parmspec":[ 368 {"type":"STR","name":"protocol_name"}, 369 {"type":"STR","name":"duct_name"} 370 ], 371 "description": "Start the indicated induct task as defined for the 372 indicated CL protocol on the local node." 373 }, 374 { 375 "name": "induct_stop", 376 "parmspec":[ 377 {"type":"STR","name":"protocol_name"}, 378 {"type":"STR","name":"duct_name"} 379 ], 380 "description": "Stop the indicated induct task as defined for the 381 indicated CL protocol on the local node." 382 }, 383 { 384 "name": "init", 385 "description": "Until this control is executed, Bundle Protocol is not 386 in operation on the local ION node and most bpadmin controls will 387 fail." 388 }, 389 { 390 "name": "manage_heap_max", 391 "parmspec": [ 392 {"type":"UINT","name":"max_database_heap_per_acquisition"} 393 ], 394 "description": "Declare the maximum number of bytes of SDR heap space 395 that will be occupied by any single bundle acquisition activity 396 (nominally the acquisition of a single bundle, but this is at the 397 discretion of the convergence-layer input task). All data acquired 398 in excess of this limit will be written to a temporary file pending 399 extraction and dispatching of the acquired bundle or bundles. The 400 default is the minimum allowed value (560 bytes), which is the 401 approximate size of a ZCO file reference object; this is the minimum 402 SDR heap space occupancy in the event that all acquisition is into 403 a file." 404 }, 405 { 406 "name": "outduct_add", 407 "parmspec": [ 408 {"type":"STR","name":"protocol_name"}, 409 {"type":"STR","name":"duct_name"}, 410 {"type":"STR","name":"clo_command"}, 411 {"type":"UINT","name":"max_payload_length"} 412 ], 413 "description": "Establish a duct for transmission of bundles via the 414 indicated CL protocol. the duct's data transmission structure is 415 serviced by the outduct task whose operation is initiated by 416 CLOcommand at the time the duct is started. A value of zero for 417 maxPayloadLength indicates that bundles of any size can be 418 accomodated; this is the default." 419 }, 420 { 421 "name": "outduct_change", 422 "parmspec": [ 423 {"type":"STR","name":"protocol_name"}, 424 {"type":"STR","name":"duct_name"}, 425 {"type":"STR","name":"clo_control"}, 426 {"type":"UINT","name":"max_payload_length"} 427 ], 428 "description": "Set new values for the indicated duct's payload size 429 limit and the control that is used to initiate operation of the 430 outduct task for this duct." 431 }, 432 { 433 "name": "outduct_del", 434 "parmspec":[ 435 {"type":"STR","name":"protocol_name"}, 436 {"type":"STR","name":"duct_name"} 437 ], 438 "description": "Delete the outduct identified by protocolName and 439 ductName. The control will fail if any bundles are currently 440 pending transmission via this outduct." 441 }, 442 { 443 "name": "outduct_start", 444 "parmspec":[ 445 {"type":"STR","name":"protocol_name"}, 446 {"type":"STR","name":"duct_name"} 447 ], 448 "description": "Start the indicated outduct task as defined for the 449 indicated CL protocol on the local node." 450 }, 451 { 452 "name": "egress_plan_block", 453 "parmspec": [{"type":"STR","name":"plan_name"}], 454 "description": "Disable transmission of bundles queued for 455 transmission to the indicated node and reforwards all non-critical 456 bundles currently queued for transmission to this node. This may 457 result in some or all of these bundles being enqueued for 458 transmission to the psuedo-node limbo." 459 }, 460 { 461 "name": "egress_plan_unblock", 462 "parmspec": [{"type":"STR","name":"plan_name"}], 463 "description": "Re-enable transmission of bundles to the indicated 464 node and reforwards all bundles in limbo in the hope that the 465 unblocking of this egress plan will enable some of them to be 466 transmitted." 467 }, 468 { 469 "name": "outduct_stop", 470 "parmspec":[ 471 {"type":"STR","name":"protocol_name"}, 472 {"type":"STR","name":"duct_name"} 473 ], 474 "description": "Stop the indicated outduct task as defined for the 475 indicated CL protocol on the local node." 476 }, 477 { 478 "name": "protocol_add", 479 "parmspec": [ 480 {"type":"STR","name":"protocol_name"}, 481 {"type":"UINT","name":"payload_bytes_per_frame"}, 482 {"type":"UINT","name":"overhead_bytes_per_frame"}, 483 {"type":"UINT","name":"nominal_data_rate"} 484 ], 485 "description": "Establish access to the named convergence layer 486 protocol at the local node. The payloadBytesPerFrame and 487 overheadBytesPerFrame arguments are used in calculating the 488 estimated transmission capacity consumption of each bundle, to 489 aid in route computation and congesting forecasting. The 490 optional nominalDataRate argument overrides the hard coded 491 default continuous data rate for the indicated protocol for 492 purposes of rate control. For all promiscuous prototocols-that 493 is, protocols whose outducts are not specifically dedicated to 494 transmission to a single identified convergence-layer protocol 495 endpoint- the protocol's applicable nominal continuous data 496 rate is the data rate that is always used for rate control over 497 links served by that protocol; data rates are not extracted 498 from contact graph information. This is because only the induct 499 and outduct throttles for non-promiscuous protocols (LTP, TCP) 500 can be dynamically adjusted in response to changes in data rate 501 between the local node and its neighbors, as enacted per the 502 contact plan. Even for an outduct of a non-promiscuous protocol 503 the nominal data rate may be the authority for rate control, 504 in the event that the contact plan lacks identified contacts 505 with the node to which the outduct is mapped." 506 }, 507 { 508 "name": "protocol_del", 509 "parmspec": [{"type":"STR","name":"protocol_name"}], 510 "description": "Delete the convergence layer protocol identified by 511 protocolName. The control will fail if any ducts are still locally 512 declared for this protocol." 513 }, 514 { 515 "name": "protocol_start", 516 "parmspec": [{"type":"STR","name":"protocol_name"}], 517 "description": "Start all induct and outduct tasks for inducts and 518 outducts that have been defined for the indicated CL protocol on 519 the local node." 520 }, 521 { 522 "name": "protocol_stop", 523 "parmspec": [{"type":"STR","name":"protocol_name"}], 524 "description": "Stop all induct and outduct tasks for inducts and 525 outducts that have been defined for the indicated CL protocol on 526 the local node." 527 }, 528 { 529 "name": "scheme_add", 530 "parmspec": [ 531 {"type":"STR","name":"scheme_name"}, 532 {"type":"STR","name":"forwarder_control"}, 533 {"type":"STR","name":"admin_app_control"} 534 ], 535 "description": "Declares an endpoint naming scheme for use in endpoint 536 IDs, which are structured as URIs: schemeName:schemeSpecificPart. 537 forwarderControl will be executed when the scheme is started on this 538 node, to initiate operation of a forwarding daemon for this scheme. 539 adminAppControl will also be executed when the scheme is started on 540 this node, to initiate operation of a daemon that opens a custodian 541 endpoint identified within this scheme so that it can recieve and 542 process custody signals and bundle status reports." 543 }, 544 { 545 "name": "scheme_change", 546 "parmspec": [ 547 {"type":"STR","name":"scheme_name"}, 548 {"type":"STR","name":"forwarder_control"}, 549 {"type":"STR","name":"admin_app_control"} 550 ], 551 "description": "Set the indicated scheme's forwarderControl and 552 adminAppControl to the strings provided as arguments." 553 }, 554 { 555 "name": "scheme_del", 556 "parmspec": [{"type":"STR","name":"scheme_name"}], 557 "description": "Delete the scheme identified by schemeName. The 558 control will fail if any bundles identified in this scheme are 559 pending forwarding, transmission, or delivery." 560 }, 561 { 562 "name": "scheme_start", 563 "parmspec": [{"type":"STR","name":"scheme_name"}], 564 "description": "Start the forwarder and administrative endpoint tasks 565 for the indicated scheme task on the local node." 566 }, 567 { 568 "name": "scheme_stop", 569 "parmspec": [{"type":"STR","name":"scheme_name"}], 570 "description": "Stop the forwarder and administrative endpoint tasks 571 for the indicated scheme task on the local node." 572 }, 573 { 574 "name": "start", 575 "description": "Start all schemes and all protocols on the local 576 node." 577 }, 578 { 579 "name": "stop", 580 "description": "Stop all schemes and all protocols on the local node." 581 }, 582 { 583 "name": "watch", 584 "parmspec":[ 585 {"type":"UINT","name":"status"}, 586 {"type":"UINT","name":"activity_spec"} 587 ], 588 "description": "Enable/Disable production of a continuous stream of 589 user selected Bundle Protocol activity indication characters. A 590 watch parameter of 1 selects all BP activity indication characters, 591 0 deselects allBP activity indication characters; any other 592 activitySpec such as acz~ selects all activity indication characters 593 in the string, deselecting all others. BP will print each selected 594 activity indication character to stdout every time a processing 595 event of the associated type occurs: a new bundle is queued for 596 forwarding, b bundle is queued for transmission, c bundle is popped 597 from its transmission queue, m custody acceptance signal is 598 recieved, w custody of bundle is accepted, x custody of bundle is 599 refused, y bundle is accepted upon arrival, z bundle is queued for 600 delivery to an application, ~ bundle is abandoned (discarded) on 601 attempt to forward it, ! bundle is destroyed due to TTL expiration, 602 & custody refusal signal is recieved, # bundle is queued for 603 re-forwarding due to CL protocol failures, j bundle is placed in 604 'limbo' for possible future reforwarding, k bundle is removed from 605 'limbo' and queued for reforwarding, $ bundle's custodial 606 retransmission timeout interval expired." 607 } 608 ] 609 } 611 5. IANA Considerations 613 At this time, this protocol has no fields registered by IANA. 615 6. References 617 6.1. Informative References 619 [I-D.birrane-dtn-ama] 620 Birrane, E., "Asynchronous Management Architecture", 621 draft-birrane-dtn-ama-07 (work in progress), June 2018. 623 6.2. Normative References 625 [I-D.birrane-dtn-adm] 626 Birrane, E., DiPietro, E., and D. Linko, "AMA Application 627 Data Model", draft-birrane-dtn-adm-02 (work in progress), 628 June 2018. 630 [I-D.birrane-dtn-amp] 631 Birrane, E., "Asynchronous Management Protocol", draft- 632 birrane-dtn-amp-04 (work in progress), June 2018. 634 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 635 Requirement Levels", BCP 14, RFC 2119, 636 DOI 10.17487/RFC2119, March 1997, 637 . 639 Authors' Addresses 641 Edward J. Birrane 642 Johns Hopkins Applied Physics Laboratory 644 Email: Edward.Birrane@jhuapl.edu 646 Evana DiPietro 647 Johns Hopkins Applied Physics Laboratory 649 Email: Evana.DiPietro@jhuapl.edu 651 David Linko 652 Johns Hopkins Applied Physics Laboratory 654 Email: David.Linko@jhuapl.edu