Internet DRAFT - draft-dlep-containers
draft-dlep-containers
Network Working Group R. Taylor
Internet-Draft Airbus Defence & Space
Intended status: Standards Track July 19, 2017
Expires: January 20, 2018
Container Data Items for DLEP
draft-dlep-containers-00
Abstract
Several 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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 20, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Taylor Expires January 20, 2018 [Page 1]
Internet-Draft Container Data Items for DLEP July 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions and Terminology . . . . . . . . . . . . . . . 2
2. Container Data Item . . . . . . . . . . . . . . . . . . . . . 2
2.1. Specification of Conatiner Data Items . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Normative References . . . . . . . . . . . . . . . . . . 3
5.2. Informative References . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
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.
1.1. Conventions and Terminology
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
[RFC2119].
2. Container Data Item
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:
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data Item Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: DLEP Data Items (zero or more) :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Taylor Expires January 20, 2018 [Page 2]
Internet-Draft Container Data Items for DLEP July 2017
Data Item Type: Defined by the extension. Allocated from IANA "DLEP
Data Item Values" registry.
Length: Sum of Lengths of contained DLEP Data Items, including
header lengths, i.e. the total length of the Container Data Item
DLEP Data Items: 0 or more DLEP Data Items, as defined in
[I-D.ietf-manet-dlep].
2.1. Specification of Conatiner Data Items
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'.
3. Security Considerations
I'm not sure there are any.
4. IANA Considerations
None.
5. References
5.1. Normative References
[I-D.ietf-manet-dlep]
Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
Berry, "Dynamic Link Exchange Protocol (DLEP)", draft-
ietf-manet-dlep-26 (work in progress), December 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
Taylor Expires January 20, 2018 [Page 3]
Internet-Draft Container Data Items for DLEP July 2017
5.2. Informative References
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
Author's Address
Rick Taylor
Airbus Defence & Space
Quadrant House
Celtic Springs
Coedkernew
Newport NP10 8FZ
UK
Email: rick@tropicalstormsoftware.com
Taylor Expires January 20, 2018 [Page 4]
