Container Data Items for DLEPAirbus Defence & SpaceQuadrant HouseCeltic SpringsCoedkernewNewportNP10 8FZUKrick@tropicalstormsoftware.comSeveral DLEP extensions are being suggested that require the ability to group a set of DLEP Data Items into a logical set or bag. This document species a generic method of defining such a bag of Data Items, in what this document defines as a Data Item Container. This document also describes what an extension using Data Item Containers must specify in the extension specification. A DLEP Data Item Container defined by this document is a generic wrapper or container of DLEP Data Items, where the presence of the container around the Data Items implies a logical association between the Data Items in the Container. This document does not define a new DLEP extension, but does instead define a set of guidelines for DLEP extension authors. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 . The Container Data Item allows a DLEP extension to parenthesize a set of DLEP Data Items, implying a logical assocaition between the Data Items in the container. The Container Data Item contains the following fields: Defined by the extension. Allocated from IANA "DLEP Data Item Values" registry. Sum of Lengths of contained DLEP Data Items, including header lengths, i.e. the total length of the Container Data Item 0 or more DLEP Data Items, as defined in . When the use of a Container Data Item is defined in a DLEP extension specification, the specification MUST define which DLEP Data Items are valid within the Conatiner, and also the multiplicity of Data Items in the Container. Unless otherwise allowed by an individual DLEP extension specification, any Data Item not defined as allowed in the Container MUST NOT appear, and an implementation receiving such a Data Item MUST teminate the DLEP session, using the DLEP Status Code 'Invalid Data'. I'm not sure there are any. None. Key words for use in RFCs to Indicate Requirement LevelsIn many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.Dynamic Link Exchange Protocol (DLEP)When routing devices rely on modems to effect communications over wireless links, they need timely and accurate knowledge of the characteristics of the link (speed, state, etc.) in order to make routing decisions. In mobile or other environments where these characteristics change frequently, manual configurations or the inference of state through routing or transport protocols does not allow the router to make the best decisions. A bidirectional, event- driven communication channel between the router and the modem is necessary.Guidelines for Writing an IANA Considerations Section in RFCsMany protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.