Internet DRAFT - draft-dalela-vlans-and-dlep
draft-dalela-vlans-and-dlep
Mobile Ad Hoc Networks Working Group A. Dalela
Internet Draft A. Parashar
Intended status: Standards Track S.L. Ananth
Expires: September 2016 Cisco Systems
March 15, 2016
VLAN Extension to DLEP
draft-dalela-vlans-and-dlep-01.txt
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 15, 2016.
Copyright Notice
Copyright (c) 2016 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
Dalela Expires September 15, 2016 [Page 1]
Internet-Draft VLAN Extension to DLEP March 2016
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
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.
Abstract
This document introduces optional extension to the core DLEP
specification for VLAN encapsulation.
Table of Contents
1. Introduction...................................................2
2. Conventions used in this document..............................2
3. Terminology....................................................3
4. Overview.......................................................3
5. Operation......................................................4
5.1. Data Item Definitions.....................................4
6. USE Cases......................................................4
7. Security Considerations........................................5
8. IANA Considerations............................................5
8.1. Registrations.............................................5
9. References.....................................................5
9.1. Normative References......................................5
10. Acknowledgments...............................................6
1. Introduction
The Dynamic Link Exchange protocol [DLEP] runs between a router and
its attached modem devices, allowing the modem to communicate radio
link characteristics, and radio network convergence events as they
change. This draft describes an optional extension to DLEP protocol,
allowing for VLAN encapsulations to be implemented.
This draft doesn't attempt to suggest or make any modifications to
any other protocol or standard mentioned in the draft.
2. Conventions used in this document
In examples, "C:" and "S:" indicate lines sent by the client and
server respectively.
Dalela Expires September 15, 2016 [Page 2]
Internet-Draft VLAN Extension to DLEP March 2016
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 RFC 2119 [RFC2119].
In this document, these words will appear with that interpretation
only when in ALL CAPS. Lower case uses of these words are not to be
interpreted as carrying significance described in RFC 2119.
In this document, the characters ">>" preceding an indented line(s)
indicates a statement using the key words listed above. This
convention aids reviewers in quickly identifying or finding the
portions of this RFC covered by these keywords.
3. Terminology
Peer: A router and the modem with which it has established a DLEP
session are referred to as peers.
Neighbor: A router which is accessible via a peer's RF link.
VLAN-ID: This is 12-bit VLAN-ID field in [802.1Q] C-TAG or [802.1AD]
S-TAG or [802.1AH] B-TAG.
4. Overview
This protocol extension to DLEP provides a VLAN encapsulation
scheme. In this scheme, neighbor is characterized by the VLAN-ID. We
propose the following encapsulation tags to DLEP data traffic.
1. IEEE 802.1Q Tag
2. IEEE 802.1AD Tag
3. IEEE 802.1AH Tag
DLEP router and modem negotiate on the encapsulation and adds the
appropriate tag per the negotiation. DLEP router allocates VLAN-ID
corresponding to every neighbor.
For 802.1Q Tag encapsulation, neighbor's assigned VLAN-ID is set in
the [802.1Q] TAG's C-TAG VID.
For 802.1AD Tag encapsulation, neighbor's assigned VLAN-ID is set in
the [802.1AD] TAG's S-TAG VID.
For 802.1AH Tag encapsulation, neighbor's assigned VLAN-ID is set in
the [802.1AH] TAG's B-TAG VID.
Dalela Expires September 15, 2016 [Page 3]
Internet-Draft VLAN Extension to DLEP March 2016
This document describes the encapsulation only for the data traffic
between DLEP peers.
5. Operation
DLEP peers supporting this method of encapsulation MUST include a
DLEP 'Extensions Supported' data item, including the value TBD
representing this extension in the appropriate DLEP Session
Initialization and Session Initialization Response messages.
DLEP router allocates VLAN-ID corresponding to every neighbor. As
part of "DLEP Destination UP Response" message, the router will use
the "VLAN-ID Data Item" to assign VLAN-ID to the individual DLEP
neighbor. Refer section 5.1 for details.
Both modem and router tag the data traffic destined to or coming
from a neighbor with the VLAN-ID assigned to that neighbor.
5.1. Data Item Definitions
1. VLAN-ID
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 |
+----------------------------------------------------------------+
|Vlan-ID |
+----------------------------------------------------------------+
Figure 1 Assignment of VLAN to neighbors
Data Item Type: TBD
Length: 4
VLAN-ID: The "Vlan-ID" allocated to DLEP neighbor
The "VLAN-ID" data item is sent from a DLEP router to the peer as
part of "DLEP Destination Up Response" message.
6. USE Cases
1. 802.1Q Tag (VLAN Tag): When data traffic destined to a neighbor or
coming from a neighbor is not VLAN tagged, DLEP peers tag it with
802.1Q TAG, with VLAN-ID field set to the VLAN-ID assigned to that
neighbor.
Dalela Expires September 15, 2016 [Page 4]
Internet-Draft VLAN Extension to DLEP March 2016
2. 802.1AD Tag (VLAN-in-VLAN Tag): When data traffic destined to a
neighbor or coming from a neighbor is VLAN tagged (802.1Q tag),
DLEP peers tag it with 802.1AD TAG, with VLAN-ID field in S-TAG to
the VLAN-ID assigned to that neighbor.
3. 802.1AH Tag (VLAN-in-VLAN-in-VLAN Tag): When data traffic destined
to a neighbor or coming from a neighbor is VLAN-in-VLAN tagged
(802.1AD tag), DLEP peers tag it with 802.1AH TAG, with VLAN-ID
field in B-TAG to the VLAN-ID assigned to that neighbor.
7. Security Considerations
As an extension to the core DLEP protocol, the security
considerations of that protocol apply to this extension. This
extension adds no additional security mechanisms or features.
8. IANA Considerations
This section specifies requests to IANA.
8.1. Registrations
This specification defines new data items for DLEP. Assignments from
the DLEP data item registry is requested for:
1. VLAN-ID
9. References
9.1. Normative References
[DLEP] Ratliff, S., Berry, B., Jury, S., Satterwhite, D., Taylor,
R., "Dynamic Link Exchange Protocol (DLEP)",
https://tools.ietf.org/html/draft-ietf-manet-dlep-19
[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
[802.1Q] IEEE 802.1Q, "Virtual LANs",
http://www.ieee802.org/1/pages/802.1Q.html
[802.1AD] IEEE 802.1AD, "Provider Bridges",
http://www.ieee802.org/1/pages/802.1ad.html
[802.1AH] IEEE 802.1AH, "Provider Backbone Bridges",
http://www.ieee802.org/1/pages/802.1ah.html
Dalela Expires September 15, 2016 [Page 5]
Internet-Draft VLAN Extension to DLEP March 2016
10. Acknowledgments
This document was prepared using 2-Word-v2.0.template.dot.
Copyright (c) 2016 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, is permitted pursuant to, and subject to the license
terms contained in, the Simplified BSD License set forth in Section
4.c of the IETF Trust's Legal Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
Copyright (c) 2016 IETF Trust and the persons identified as authors
of the code. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
o Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
o Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the
distribution.
o Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Dalela Expires September 15, 2016 [Page 6]
Internet-Draft VLAN Extension to DLEP March 2016
Authors' Addresses
Ashish Dalela
Cisco Systems,
Cessna Business Park,
Bangalore 560103
India
Email: adalela@cisco.com
Arun Parashar
Cisco Systems,
Cessna Business Park,
Bangalore 560103
India
Email: arparash@cisco.com
S L Ananth
Cisco Systems,
Cessna Business Park,
Bangalore 560103
India
Email: alaxmina@cisco.com
Dalela Expires September 15, 2016 [Page 7]
