idnits 2.17.1 draft-loiseau-dtn-cla-eid-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. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 21, 2018) is 1976 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-31) exists of draft-ietf-dtn-bpbis-11 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Delay Tolerant Network L. Loiseau 3 Internet-Draft RightMesh 4 Intended status: Standards Track November 21, 2018 5 Expires: May 25, 2019 7 Using CLA-Specific Endpoint IDs to identify Channel Endpoint 8 draft-loiseau-dtn-cla-eid-00 10 Abstract 12 This document describes a specific EID scheme namely "cla" that meets 13 the requirement for endpoint identification as defined in the Bundle 14 Protocol and that also uniquely identifies a Convergence Layer 15 Adapter "channel" and is, in essence, an interface identifier (IID). 16 Such IID is comprised of two parts: a "cla-identifier" part that 17 identifies a specific convergence layer adapter, and a "cla- 18 parameters" part that is a cla-specific list of parameter describing 19 a single channel managed by this convergence layer adapter. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on May 25, 2019. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Convention used in this document . . . . . . . . . . . . . . 2 57 3. IID: Scheme Syntax and Rules . . . . . . . . . . . . . . . . 3 58 4. CLA Additional Services . . . . . . . . . . . . . . . . . . . 3 59 4.1. IID as an Egress Identifier . . . . . . . . . . . . . . . 3 60 4.2. IID as an Ingress Identifier . . . . . . . . . . . . . . 3 61 5. IIDs Examples . . . . . . . . . . . . . . . . . . . . . . . . 4 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 This document describes a specific EID scheme namely "cla" that meets 70 the requirement for endpoint identification as defined in the Bundle 71 Protocol[I-D.ietf-dtn-bpbis] and that is managed by convergence layer 72 adapters (CLA). Such EID of the scheme "cla" is called an Interface 73 Identifier (IID) and within the context of the bundle protocol 74 operation is used to identify channel endpoints. A Bundle Protocol 75 Interface represents the abstraction of an underlying transport 76 channel, managed by a CLA, and that provides the set of services 77 described in section 7.2 of [I-D.ietf-dtn-bpbis]. A convergence 78 layer adapter that conforms to this specification SHALL provide the 79 two additional services: 81 1. egress: MUST provide an IID for every channel that is open and 82 for which an interface is available for sending bundles. 84 2. ingress: If applicable, MAY provide an IID identifying the local 85 Bundle Node for every channel that is open. 87 2. Convention used in this document 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in [RFC2119]. 93 3. IID: Scheme Syntax and Rules 95 The general syntax of an IID is: 97 cla:: 99 CLA-NAME is the name of the convergence layer adapter that can parse 100 or generate this IID. 102 CLA-SPECIFIC-PART is the convergence layer specific part that 103 identifies a specific cla channel. This part must be unambiguous and 104 can be automatically guessed by any peer implementing this CLA and 105 that knows the parameter for this channel. 107 4. CLA Additional Services 109 4.1. IID as an Egress Identifier 111 Convergence layer adapters provide a service interface used to send 112 and receive Bundle with other Bundle Nodes. In this context, an IID 113 identifies an interface in a way that is unambiguous meaning that two 114 different interfaces should never have the same IID. IIDs being 115 transport-layer interface identifier MUST exactly map to an 116 underlying transport channel. Such IID is, in effect, used to 117 identify the egress part of an interface. 119 Every Bundle that is schedule for forwarding and whose destination 120 EID matches an egress-IID must be directly forwarded to the 121 underlying matching transport channel. 123 4.2. IID as an Ingress Identifier 125 When applicable, a bundle node may be addressable in a way that is 126 specific to a convergence layer adapter. For instance with 127 stcp[I-D.burleigh-dtn-stcp] each bundle node can be uniquely 128 identified with its pair {ip address, tcp port} and other bundle 129 nodes may use an IID to address bundles to it. In some other case, 130 it may not be possible to create such an identifier, for instance 131 with a USB cla (where the transport channel is a folder in a USB 132 drive), it wouldn't really make much sense to have a cla-specific 133 address that would be automatically derivable by other bundle node. 134 Such IID is, in effect, used to identify the ingress part of an 135 interface. 137 If it is applicable to derive such ingress-IID to address the local 138 bundle node instance, each bundle that is received and whose 139 destination field is this IID should be processed for local delivery. 141 5. IIDs Examples 143 This appendix provides some examples for IIDs. 145 cla:stcp:10.1.123.1:4556 147 Figure 1: STCP-specific EID identifying an Interface to another 148 Bundle Node with its IP address and TCP port 150 cla:usb:1d6b:0002:folder1 152 Figure 2: USB-specific EID identifying an Interface over a mounted 153 usb device described as its bus address and folder 155 cla:mailcl:xxxx@ietf.org:[dtn] 157 Figure 3: MAILCL-specific EID that identifies a channel over SMTP 158 protocol described as a mail address and subject filter 160 6. References 162 6.1. Normative References 164 [I-D.ietf-dtn-bpbis] 165 Fall, K. and E. Birrane, "Bundle Protocol Version 7", 166 draft-ietf-dtn-bpbis-11 (work in progress), May 2018. 168 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 169 Requirement Levels", BCP 14, RFC 2119, 170 DOI 10.17487/RFC2119, March 1997, . 173 6.2. Informative References 175 [I-D.burleigh-dtn-stcp] 176 Burleigh, S., "Simple TCP Convergence-Layer Protocol", 177 draft-burleigh-dtn-stcp-00 (work in progress), September 178 2018. 180 Author's Address 182 Lucien Loiseau 183 RightMesh 185 Email: loiseau.lucien@gmail.com