idnits 2.17.00 (12 Aug 2021) /tmp/idnits21938/draft-dlep-containers-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 19, 2017) is 1760 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) == Unused Reference: 'RFC5226' is defined on line 142, but no explicit reference was found in the text == Outdated reference: draft-ietf-manet-dlep has been published as RFC 8175 -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Taylor 3 Internet-Draft Airbus Defence & Space 4 Intended status: Standards Track July 19, 2017 5 Expires: January 20, 2018 7 Container Data Items for DLEP 8 draft-dlep-containers-00 10 Abstract 12 Several DLEP extensions are being suggested that require the ability 13 to group a set of DLEP Data Items into a logical set or bag. This 14 document species a generic method of defining such a bag of Data 15 Items, in what this document defines as a Data Item Container. This 16 document also describes what an extension using Data Item Containers 17 must specify in the extension specification. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 20, 2018. 36 Copyright Notice 38 Copyright (c) 2017 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Conventions and Terminology . . . . . . . . . . . . . . . 2 55 2. Container Data Item . . . . . . . . . . . . . . . . . . . . . 2 56 2.1. Specification of Conatiner Data Items . . . . . . . . . . 3 57 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 58 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 59 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 61 5.2. Informative References . . . . . . . . . . . . . . . . . 4 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 64 1. Introduction 66 A DLEP Data Item Container defined by this document is a generic 67 wrapper or container of DLEP Data Items, where the presence of the 68 container around the Data Items implies a logical association between 69 the Data Items in the Container. 71 This document does not define a new DLEP extension, but does instead 72 define a set of guidelines for DLEP extension authors. 74 1.1. Conventions and Terminology 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in BCP 14, RFC 2119 79 [RFC2119]. 81 2. Container Data Item 83 The Container Data Item allows a DLEP extension to parenthesize a set 84 of DLEP Data Items, implying a logical assocaition between the Data 85 Items in the container. 87 The Container Data Item contains the following fields: 89 0 1 2 3 90 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 91 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 92 | Data Item Type | Length | 93 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 94 : DLEP Data Items (zero or more) : 95 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 96 Data Item Type: Defined by the extension. Allocated from IANA "DLEP 97 Data Item Values" registry. 99 Length: Sum of Lengths of contained DLEP Data Items, including 100 header lengths, i.e. the total length of the Container Data Item 102 DLEP Data Items: 0 or more DLEP Data Items, as defined in 103 [I-D.ietf-manet-dlep]. 105 2.1. Specification of Conatiner Data Items 107 When the use of a Container Data Item is defined in a DLEP extension 108 specification, the specification MUST define which DLEP Data Items 109 are valid within the Conatiner, and also the multiplicity of Data 110 Items in the Container. 112 Unless otherwise allowed by an individual DLEP extension 113 specification, any Data Item not defined as allowed in the Container 114 MUST NOT appear, and an implementation receiving such a Data Item 115 MUST teminate the DLEP session, using the DLEP Status Code 'Invalid 116 Data'. 118 3. Security Considerations 120 I'm not sure there are any. 122 4. IANA Considerations 124 None. 126 5. References 128 5.1. Normative References 130 [I-D.ietf-manet-dlep] 131 Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B. 132 Berry, "Dynamic Link Exchange Protocol (DLEP)", draft- 133 ietf-manet-dlep-26 (work in progress), December 2016. 135 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 136 Requirement Levels", BCP 14, RFC 2119, 137 DOI 10.17487/RFC2119, March 1997, 138 . 140 5.2. Informative References 142 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 143 IANA Considerations Section in RFCs", RFC 5226, 144 DOI 10.17487/RFC5226, May 2008, 145 . 147 Author's Address 149 Rick Taylor 150 Airbus Defence & Space 151 Quadrant House 152 Celtic Springs 153 Coedkernew 154 Newport NP10 8FZ 155 UK 157 Email: rick@tropicalstormsoftware.com