idnits 2.17.1 draft-birrane-dtn-adm-ion-bpadmin-01.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. ** 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 (March 11, 2019) is 1866 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: 2 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: September 12, 2019 Johns Hopkins Applied Physics Laboratory 6 March 11, 2019 8 Bundle Protocol Agent Application Data Model 9 draft-birrane-dtn-adm-ion-bpadmin-01 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 September 12, 2019. 34 Copyright Notice 36 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . 17 60 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 61 6.1. Informative References . . . . . . . . . . . . . . . . . 17 62 6.2. Normative References . . . . . . . . . . . . . . . . . . 18 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 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 "name": "name", 197 "type": "STR", 198 "value": "ion_bp_admin", 199 "description": "The human-readable name of the ADM." 200 }, 201 { 202 "name": "namespace", 203 "type": "STR", 204 "value": "DTN/ION/bpadmin", 205 "description": "The namespace of the ADM" 206 }, 207 { 208 "name": "version", 209 "type": "STR", 210 "value": "v0.0", 211 "description": "The version of the ADM" 212 }, 213 { 214 "name": "organization", 215 "type": "STR", 216 "value": "JHUAPL", 217 "description": "The name of the issuing organization of the ADM" 218 } 219 ], 220 "Edd": [{ 221 "name": "bp_version", 222 "type": "STR", 223 "description": "Version of installed ION BP Admin utility." 224 }], 225 "Tblt": [{ 226 "name": "endpoints", 227 "columns": [{ 228 "type": "STR", 229 "name": "scheme_name" 230 }, { 231 "type": "STR", 232 "name": "endpoint_nss" 233 }, { 234 "type": "UINT", 235 "name": "app_pid" 236 }, { 237 "type": "STR", 238 "name": "recv_rule" 239 }, { 240 "type": "STR", 241 "name": "rcv_script" 242 }], 243 "description": "Local endpoints, regardless of scheme name." 244 }, 245 { 246 "name": "inducts", 247 "columns": [{ 248 "type": "STR", 249 "name": "protocol_name" 250 }, { 251 "type": "STR", 252 "name": "duct_name" 253 }, { 254 "type": "STR", 255 "name": "cli_control" 256 }], 257 "description": "Inducts established locally for the indicated 258 CL protocol." 260 }, 261 { 262 "name": "outducts", 263 "columns": [{ 264 "type": "STR", 265 "name": "protocol_name" 266 }, { 267 "type": "STR", 268 "name": "duct_name" 269 }, { 270 "type": "UINT", 271 "name": "clo_pid" 272 }, { 273 "type": "STR", 274 "name": "clo_control" 275 }, { 276 "type": "UINT", 277 "name": "max_payload_length" 278 }], 279 "description": "If protocolName is specified, this table lists 280 all outducts established locally for the 281 indicated CL protocol. Otherwise, it lists all 282 locally established outducts, regardless of 283 their protocol." 284 }, 285 { 286 "name": "protocols", 287 "columns": [{ 288 "type": "STR", 289 "name": "name" 290 }, { 291 "type": "UINT", 292 "name": "payload_bpf" 293 }, { 294 "type": "UINT", 295 "name": "overhead_bpf" 296 }, { 297 "type": "UINT", 298 "name": "protocol class" 299 }], 300 "description": "Convergence layer protocols that can currently 301 be utilized at the local node." 302 }, 303 { 304 "name": "schemes", 305 "columns": [{ 306 "type": "STR", 307 "name": "scheme_name" 309 }, { 310 "type": "UINT", 311 "name": "fwd_pid" 312 }, { 313 "type": "STR", 314 "name": "fwd_cmd" 315 }, { 316 "type": "UINT", 317 "name": "admin_app_pid" 318 }, { 319 "type": "STR", 320 "name": "admin_app_cmd" 321 }], 322 "description": "Declared endpoint naming schemes." 323 }, 324 { 325 "name": "egress_plans", 326 "columns": [{ 327 "type": "STR", 328 "name": "neighbor_eid" 329 }, { 330 "type": "UINT", 331 "name": "clm_pid" 332 }, { 333 "type": "UINT", 334 "name": "nominal_rate" 335 }], 336 "description": "Egress plans." 337 } 338 ], 339 "Ctrl": [{ 340 "name": "endpoint_add", 341 "parmspec": [{ 342 "type": "STR", 343 "name": "endpoint_id" 344 }, { 345 "type": "UINT", 346 "name": "type" 347 }, { 348 "type": "STR", 349 "name": "rcv_script" 350 }], 351 "description": "Establish DTN endpoint named endpointId on the 352 local node. The remaining parameters indicate 353 what is to be done when bundles destined for 354 this endpoint arrive at a time when no 355 application has the endpoint open for bundle 356 reception. If type is 'x', then such bundles 357 are to be discarded silently and immediately. 358 If type is 'q', then such bundles are to be 359 enqueued for later delivery and, if recvScript 360 is provided, recvScript is to be executed." 361 }, 362 { 363 "name": "endpoint_change", 364 "parmspec": [{ 365 "type": "STR", 366 "name": "endpoint_id" 367 }, { 368 "type": "UINT", 369 "name": "type" 370 }, { 371 "type": "STR", 372 "name": "rcv_script" 373 }], 374 "description": "Change the action taken when bundles destined 375 for this endpoint arrive at a time when no 376 application has the endpoint open for bundle 377 reception." 378 }, 379 { 380 "name": "endpoint_del", 381 "parmspec": [{ 382 "type": "STR", 383 "name": "endpoint_id" 384 }], 385 "description": "Delete the endpoint identified by endpointId. 386 The control will fail if any bundles are 387 currently pending delivery to this endpoint." 388 }, 389 { 390 "name": "induct_add", 391 "parmspec": [{ 392 "type": "STR", 393 "name": "protocol_name" 394 }, { 395 "type": "STR", 396 "name": "duct_name" 397 }, { 398 "type": "STR", 399 "name": "cli_control" 400 }], 401 "description": "Establish a duct for reception of bundles via 402 the indicated CL protocol. The duct's data 403 acquisition structure is used and populated by 404 the induct task whose operation is initiated by 405 cliControl at the time the duct is started." 406 }, 407 { 408 "name": "induct_change", 409 "parmspec": [{ 410 "type": "STR", 411 "name": "protocol_name" 412 }, { 413 "type": "STR", 414 "name": "duct_name" 415 }, { 416 "type": "STR", 417 "name": "cli_control" 418 }], 419 "description": "Change the control used to initiate operation 420 of the induct task for the indicated duct." 421 }, 422 { 423 "name": "induct_del", 424 "parmspec": [{ 425 "type": "STR", 426 "name": "protocol_name" 427 }, { 428 "type": "STR", 429 "name": "duct_name" 430 }], 431 "description": "Delete the induct identified by protocolName and 432 ductName. The control will fail if any bundles 433 are currently pending acquisition via this 434 induct." 435 }, 436 { 437 "name": "induct_start", 438 "parmspec": [{ 439 "type": "STR", 440 "name": "protocol_name" 441 }, { 442 "type": "STR", 443 "name": "duct_name" 444 }], 445 "description": "Start the indicated induct task as defined for 446 the indicated CL protocol on the local node." 447 }, 448 { 449 "name": "induct_stop", 450 "parmspec": [{ 451 "type": "STR", 452 "name": "protocol_name" 454 }, { 455 "type": "STR", 456 "name": "duct_name" 457 }], 458 "description": "Stop the indicated induct task as defined for 459 the indicated CL protocol on the local node." 460 }, 461 { 462 "name": "manage_heap_max", 463 "parmspec": [{ 464 "type": "UINT", 465 "name": "max_database_heap_per_acquisition" 466 }], 467 "description": "Declare the maximum number of bytes of SDR heap 468 space that will be occupied by any single bundle 469 acquisition activity (nominally the acquisition 470 of a single bundle, but this is at the 471 discretion of the convergence-layer input task). 472 All data acquired in excess of this limit will 473 be written to a temporary file pending extraction 474 and dispatching of the acquired bundle or 475 bundles. The default is the minimum allowed 476 value (560 bytes), which is the approximate size 477 of a ZCO file reference object; this is the 478 minimum SDR heap space occupancy in the event 479 that all acquisition is into a file." 480 }, 481 { 482 "name": "outduct_add", 483 "parmspec": [{ 484 "type": "STR", 485 "name": "protocol_name" 486 }, { 487 "type": "STR", 488 "name": "duct_name" 489 }, { 490 "type": "STR", 491 "name": "clo_command" 492 }, { 493 "type": "UINT", 494 "name": "max_payload_length" 495 }], 496 "description": "Establish a duct for transmission of bundles via 497 the indicated CL protocol. the duct's data 498 transmission structure is serviced by the outduct 499 task whose operation is initiated by 500 CLOcommand at the time the duct is started. A 501 value of zero for maxPayloadLength indicates 502 that bundles of any size can be accommodated; 503 this is the default." 504 }, 505 { 506 "name": "outduct_change", 507 "parmspec": [{ 508 "type": "STR", 509 "name": "protocol_name" 510 }, { 511 "type": "STR", 512 "name": "duct_name" 513 }, { 514 "type": "STR", 515 "name": "clo_control" 516 }, { 517 "type": "UINT", 518 "name": "max_payload_length" 519 }], 520 "description": "Set new values for the indicated duct's payload 521 size limit and the control that is used to 522 initiate operation of the outduct task for this 523 duct." 524 }, 525 { 526 "name": "outduct_del", 527 "parmspec": [{ 528 "type": "STR", 529 "name": "protocol_name" 530 }, { 531 "type": "STR", 532 "name": "duct_name" 533 }], 534 "description": "Delete the outduct identified by protocolName 535 and ductName. The control will fail if any 536 bundles are currently pending transmission 537 via this outduct." 538 }, 539 { 540 "name": "outduct_start", 541 "parmspec": [{ 542 "type": "STR", 543 "name": "protocol_name" 544 }, { 545 "type": "STR", 546 "name": "duct_name" 547 }], 548 "description": "Start the indicated outduct task as defined for 549 the indicated CL protocol on the local node." 551 }, 552 { 553 "name": "egress_plan_block", 554 "parmspec": [{ 555 "type": "STR", 556 "name": "plan_name" 557 }], 558 "description": "Disable transmission of bundles queued for 559 transmission to the indicated node and 560 reforwards all non-critical bundles currently 561 queued for transmission to this node. This may 562 result in some or all of these bundles being 563 enqueued for transmission to the psuedo-node 564 limbo." 565 }, 566 { 567 "name": "egress_plan_unblock", 568 "parmspec": [{ 569 "type": "STR", 570 "name": "plan_name" 571 }], 572 "description": "Re-enable transmission of bundles to the 573 indicated node and reforwards all bundles in 574 limbo in the hope that the unblocking of this 575 egress plan will enable some of them to be 576 transmitted." 577 }, 578 { 579 "name": "outduct_stop", 580 "parmspec": [{ 581 "type": "STR", 582 "name": "protocol_name" 583 }, { 584 "type": "STR", 585 "name": "duct_name" 586 }], 587 "description": "Stop the indicated outduct task as defined for 588 the indicated CL protocol on the local node." 589 }, 590 { 591 "name": "protocol_add", 592 "parmspec": [{ 593 "type": "STR", 594 "name": "protocol_name" 595 }, { 596 "type": "UINT", 597 "name": "payload_bytes_per_frame" 598 }, { 599 "type": "UINT", 600 "name": "overhead_bytes_per_frame" 601 }, { 602 "type": "UINT", 603 "name": "nominal_data_rate" 604 }], 605 "description": "Establish access to the named convergence layer 606 protocol at the local node. The 607 payloadBytesPerFrame and overheadBytesPerFrame 608 arguments are used in calculating the estimated 609 transmission capacity consumption of each 610 bundle, to aid in route computation and 611 congesting forecasting. The optional 612 nominalDataRate argument overrides the hard 613 coded default continuous data rate for the 614 indicated protocol for purposes of rate control. 615 For all promiscuous prototocols-that is, 616 protocols whose outducts are not specifically 617 dedicated to transmission to a single identified 618 convergence-layer protocol endpoint- the 619 protocol's applicable nominal continuous data 620 rate is the data rate that is always used for 621 rate control over links served by that protocol; 622 data rates are not extracted from contact graph 623 information. This is because only the induct and 624 outduct throttles for non-promiscuous protocols 625 (LTP, TCP) can be dynamically adjusted in 626 response to changes in data rate between the 627 local node and its neighbors, as enacted per the 628 contact plan. Even for an outduct of a 629 non-promiscuous protocol the nominal data rate 630 may be the authority for rate control, in the 631 event that the contact plan lacks identified 632 contacts with the node to which the outduct is 633 mapped." 634 }, 635 { 636 "name": "protocol_del", 637 "parmspec": [{ 638 "type": "STR", 639 "name": "protocol_name" 640 }], 641 "description": "Delete the convergence layer protocol identified 642 by protocolName. The control will fail if any 643 ducts are still locally declared for this 644 protocol." 645 }, 646 { 647 "name": "protocol_start", 648 "parmspec": [{ 649 "type": "STR", 650 "name": "protocol_name" 651 }], 652 "description": "Start all induct and outduct tasks for inducts 653 and outducts that have been defined for the 654 indicated CL protocol on the local node." 655 }, 656 { 657 "name": "protocol_stop", 658 "parmspec": [{ 659 "type": "STR", 660 "name": "protocol_name" 661 }], 662 "description": "Stop all induct and outduct tasks for inducts 663 and outducts that have been defined for the 664 indicated CL protocol on the local node." 665 }, 666 { 667 "name": "scheme_add", 668 "parmspec": [{ 669 "type": "STR", 670 "name": "scheme_name" 671 }, { 672 "type": "STR", 673 "name": "forwarder_control" 674 }, { 675 "type": "STR", 676 "name": "admin_app_control" 677 }], 678 "description": "Declares an endpoint naming scheme for use in 679 endpoint IDs, which are structured as URIs: 680 schemeName:schemeSpecificPart. forwarderControl 681 will be executed when the scheme is started on 682 this node, to initiate operation of a forwarding 683 daemon for this scheme. adminAppControl will 684 also be executed when the scheme is started on 685 this node, to initiate operation of a daemon 686 that opens a custodian endpoint identified within 687 this scheme so that it can receive and process 688 custody signals and bundle status reports." 689 }, 690 { 691 "name": "scheme_change", 692 "parmspec": [{ 693 "type": "STR", 694 "name": "scheme_name" 696 }, { 697 "type": "STR", 698 "name": "forwarder_control" 699 }, { 700 "type": "STR", 701 "name": "admin_app_control" 702 }], 703 "description": "Set the indicated scheme's forwarderControl and 704 adminAppControl to the strings provided as 705 arguments." 706 }, 707 { 708 "name": "scheme_del", 709 "parmspec": [{ 710 "type": "STR", 711 "name": "scheme_name" 712 }], 713 "description": "Delete the scheme identified by schemeName. The 714 control will fail if any bundles identified in 715 this scheme are pending forwarding, 716 transmission, or delivery." 717 }, 718 { 719 "name": "scheme_start", 720 "parmspec": [{ 721 "type": "STR", 722 "name": "scheme_name" 723 }], 724 "description": "Start the forwarder and administrative endpoint 725 tasks for the indicated scheme task on the local 726 node." 727 }, 728 { 729 "name": "scheme_stop", 730 "parmspec": [{ 731 "type": "STR", 732 "name": "scheme_name" 733 }], 734 "description": "Stop the forwarder and administrative endpoint 735 tasks for the indicated scheme task on the 736 local node." 737 }, 738 { 739 "name": "watch", 740 "parmspec": [{ 741 "type": "UINT", 742 "name": "status" 743 }, { 744 "type": "STR", 745 "name": "activity_spec" 746 }], 747 "description": "Enable/Disable production of a continuous stream 748 of user selected Bundle Protocol activity 749 indication characters. A watch parameter of 1 750 selects all BP activity indication characters, 0 751 deselects allBP activity indication characters; 752 any other activitySpec such as acz~ selects all 753 activity indication characters in the string, 754 deselecting all others. BP will print each 755 selected activity indication character to stdout 756 every time a processing event of the associated 757 type occurs: a new bundle is queued for 758 forwarding, b bundle is queued for transmission, 759 c bundle is popped from its transmission queue, 760 m custody acceptance signal is received, w 761 custody of bundle is accepted, x custody of 762 bundle is refused, y bundle is accepted upon 763 arrival, z bundle is queued for delivery to an 764 application, ~ bundle is abandoned (discarded) 765 on attempt to forward it, ! bundle is destroyed 766 due to TTL expiration, & custody refusal 767 signal is recieved, # bundle is queued for 768 re-forwarding due to CL protocol failures, 769 j bundle is placed in 'limbo' for possible 770 future reforwarding, k bundle is removed from 771 'limbo' and queued for reforwarding, $ bundle's 772 custodial retransmission timeout interval 773 expired." 774 } 775 ] 776 } 778 5. IANA Considerations 780 At this time, this protocol has no fields registered by IANA. 782 6. References 784 6.1. Informative References 786 [I-D.birrane-dtn-ama] 787 Birrane, E., "Asynchronous Management Architecture", 788 draft-birrane-dtn-ama-07 (work in progress), June 2018. 790 6.2. Normative References 792 [I-D.birrane-dtn-adm] 793 Birrane, E., DiPietro, E., and D. Linko, "AMA Application 794 Data Model", draft-birrane-dtn-adm-02 (work in progress), 795 June 2018. 797 [I-D.birrane-dtn-amp] 798 Birrane, E., "Asynchronous Management Protocol", draft- 799 birrane-dtn-amp-04 (work in progress), June 2018. 801 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 802 Requirement Levels", BCP 14, RFC 2119, 803 DOI 10.17487/RFC2119, March 1997, 804 . 806 Authors' Addresses 808 Edward J. Birrane 809 Johns Hopkins Applied Physics Laboratory 811 Email: Edward.Birrane@jhuapl.edu 813 Evana DiPietro 814 Johns Hopkins Applied Physics Laboratory 816 Email: Evana.DiPietro@jhuapl.edu 818 David Linko 819 Johns Hopkins Applied Physics Laboratory 821 Email: David.Linko@jhuapl.edu