< draft-lemon-geneve-gbp-01.txt   draft-lemon-geneve-gbp-02.txt >
Internet Engineering Task Force J. Lemon, Ed. Internet Engineering Task Force J. Lemon, Ed.
Internet-Draft Broadcom Internet-Draft Broadcom
Intended status: Standards Track M. Smith Intended status: Standards Track M. Smith
Expires: September 3, 2018 Cisco Expires: September 12, 2019 Cisco
March 2, 2018 A. Isaac
Juniper
March 11, 2019
Geneve encapsulation for Group Based Policy Geneve encapsulation for Group Based Policy
draft-lemon-geneve-gbp-01 draft-lemon-geneve-gbp-02
Abstract Abstract
This document describes how a Group Policy Identifier is encapsulated This document describes how a Group Policy Identifier is encapsulated
in Geneve for the purposes of policy enforcement. in Geneve for the purposes of policy enforcement.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 3, 2018. This Internet-Draft will expire on September 12, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Conventions . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Requirement Language . . . . . . . . . . . . . . . . . . 2 1.2. Abbreviations used in this document . . . . . . . . . . . 2
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 2 2. Treatment By Intermediate Nodes . . . . . . . . . . . . . . . 2
3. Group Based Policy Encapsulation in Geneve . . . . . . . . . 2 3. Group Based Policy Encapsulation in Geneve . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . 4 6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
This document defines the group-based policy (GBP) encapsulation for This document defines the group-based policy (GBP) encapsulation for
Geneve [I-D.ietf-nvo3-geneve]. The GBP sub-header carries a 16-bit Geneve [I-D.ietf-nvo3-geneve]. The GBP sub-header carries a 16-bit
group policy ID that is semantically equivalent to the 16-bit group group policy ID that is semantically equivalent to the 16-bit group
policy ID defined in [I-D.smith-vxlan-group-policy]. policy ID defined in [I-D.smith-vxlan-group-policy].
2. Conventions Group-based policy provides a more scalable alternative to access
control lists (ACLs) by allowing separation of source marking and
destination enforcement. This allows a decrease in the amount of
information needed at each entry node, rather than a cross product of
every possible source and every possible destination. It also allows
assigning source marking based many different possibilities, not just
the source address. It also allows not having to know where the
packet will end up since whatever the destination is can enforce the
policy specific to the destination service.
2.1. Requirement Language 1.1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2.2. Abbreviations 1.2. Abbreviations used in this document
Abbreviations used in this document:
GBP: Group-Based Policy GBP: Group-Based Policy
Geneve: Generic Network Virtualization Encapsulation Geneve: Generic Network Virtualization Encapsulation
2. Treatment By Intermediate Nodes
Any receiving device may use the group policy information contained
in the Group-Based Policy (GBP) sub-header. If an intermediate
device applies policy based upon the GBP sub-header, then it must set
the Policy Applied Bit, described below.
If an intermediate device termintates the Geneve tunnel and
reencapsulates the data in a new tunnel with the ability to convey
the group policy information, it SHOULD propagate the group policy
information and the Policy Applied bit into the new tunnel, unless
there is an explicit policy not to do so.
3. Group Based Policy Encapsulation in Geneve 3. Group Based Policy Encapsulation in Geneve
For encapsulating group policy IDs into Geneve [I-D.ietf-nvo3-geneve] For encapsulating group policy IDs into Geneve [I-D.ietf-nvo3-geneve]
the group policy ID field is included in the Geneve header using the group policy ID field is included in the Geneve header using
tunnel options. The group policy ID field uses a tunnel option class tunnel options. The group policy ID field uses a tunnel option class
specific for GBP. In an administrative domain where GBP is used, specific for GBP. In an administrative domain where GBP is used,
insertion of the GBP tunnel option in Geneve is enabled at the Geneve insertion of the GBP tunnel option in Geneve is enabled at the Geneve
tunnel endpoints. The Geneve header is defined in tunnel endpoints. The Geneve header is defined in
[I-D.ietf-nvo3-geneve]. GBP semantics are described in [I-D.ietf-nvo3-geneve]. GBP semantics are described in
[I-D.smith-vxlan-group-policy]. [I-D.smith-vxlan-group-policy].
skipping to change at page 3, line 14 skipping to change at page 3, line 34
0 1 2 3 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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+
|Ver| Opt Len |O|C| Rsvd. | Protocol Type | | |Ver| Opt Len |O|C| Rsvd. | Protocol Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Hdr +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Hdr
| Virtual Network Identifier (VNI) | Reserved | | | Virtual Network Identifier (VNI) | Reserved | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+
| Option Class = GBP | Type |R|R|R| Length | | | Option Class = GBP | Type |R|R|R| Length | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ GBP +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ GBP
| GBP ID |A|D| Reserved | ID | GBP ID |A|D| Rsvd |Ver| Reserved | ID
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<-+
Figure 1: Group Based Policy as a Geneve Tunnel Option Figure 1: Group Based Policy as a Geneve Tunnel Option
The GBP header consists of 8 octets, as illustrated in Figure 1. The The GBP header consists of 8 octets, as illustrated in Figure 1. The
first 4 octets are the Geneve Tunnel Option header first 4 octets are the Geneve Tunnel Option header
[I-D.ietf-nvo3-geneve], whose format is as follows: [I-D.ietf-nvo3-geneve], whose format is as follows:
Option Class: 16-bit unsigned integer that determines the GBP option Option Class: 16-bit unsigned integer that determines the GBP option
class. The value is from the IANA registry setup for Geneve class. The value is from the IANA registry setup for Geneve
option classes as defined in [I-D.ietf-nvo3-geneve]. option classes as defined in [I-D.ietf-nvo3-geneve].
Type: 8-bit unsigned integer defining the GBP ID type. Two values Type: 8-bit unsigned integer defining the GBP ID type. Two values
are defined: are defined:
GBP_Source_ID: The Group Policy ID associated with the source of GBP_Source_ID: The Group Policy ID associated with the source of
the packet. the packet. The allocation of Group Policy ID values is
outside the scope of this document.
GBP_Destination_ID: The Group Policy ID associated with the end GBP_Destination_ID: The Group Policy ID associated with the end
destination of the packet. destination of the packet. The allocation of Group Policy ID
values is outside the scope of this document.
Note that if the packet carries a GBP_Destination_ID, it MUST also Note that if the packet carries a GBP_Destination_ID, it MUST also
carry a GBP_Source_ID. carry a GBP_Source_ID.
R (3 bits): Option control flags reserved for future use. MUST be R (3 bits): Option control flags reserved for future use. MUST be
zero on transmission and ignored on receipt. zero on transmission and ignored on receipt.
Length: 5-bit unsigned integer. Length of the GBP HDR in 4-octet Length: 5-bit unsigned integer. Length of the GBP HDR in 4-octet
units. units.
skipping to change at page 4, line 15 skipping to change at page 4, line 37
group policy MUST set the A bit to 1 after the policy has been group policy MUST set the A bit to 1 after the policy has been
applied. The A bit is set to 1 to indicate that the group policy applied. The A bit is set to 1 to indicate that the group policy
has already been applied to this packet. Policies that redirect has already been applied to this packet. Policies that redirect
the packet MUST NOT be applied by devices when the A bit is set. the packet MUST NOT be applied by devices when the A bit is set.
Policies that cause the packet to be dropped MAY be applied. Policies that cause the packet to be dropped MAY be applied.
Don't Learn bit (D bit): The D bit is set to 1 to indicate that the Don't Learn bit (D bit): The D bit is set to 1 to indicate that the
tunnel endpoint MUST NOT learn the source address of the tunnel endpoint MUST NOT learn the source address of the
encapsulated frame. encapsulated frame.
Reserved (14 bits): reserved for future use. MUST be zero on Rsvd (4 bits): reserved for future use. MUST be zero on
transmission and ignored on receipt.
Ver (2 bits): indicates the Version of the Group Policy sub-header.
The initial version is 0.
Reserved (8 bits): reserved for future use. MUST be zero on
transmission and ignored on receipt. transmission and ignored on receipt.
4. IANA Considerations 4. IANA Considerations
IANA is requested to allocate a Geneve "option class" number for GBP: IANA is requested to allocate a Geneve "option class" number for GBP:
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| Option Class | Description | Reference | | Option Class | Description | Reference |
+---------------+-------------+---------------+ +---------------+-------------+---------------+
| x | GBP_ID | This document | | x | GBP_ID | This document |
skipping to change at page 4, line 47 skipping to change at page 5, line 30
that this header can be inserted only by trusted entities, and can that this header can be inserted only by trusted entities, and can
not be altered before reaching the destination. This can be not be altered before reaching the destination. This can be
mitigated through physical security of the network and/or by mitigated through physical security of the network and/or by
encryption or validation of the entire packet, including the GBP. encryption or validation of the entire packet, including the GBP.
6. Normative References 6. Normative References
[I-D.ietf-nvo3-geneve] [I-D.ietf-nvo3-geneve]
Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic Gross, J., Ganga, I., and T. Sridhar, "Geneve: Generic
Network Virtualization Encapsulation", draft-ietf- Network Virtualization Encapsulation", draft-ietf-
nvo3-geneve-05 (work in progress), September 2017. nvo3-geneve-09 (work in progress), February 2019.
[I-D.smith-vxlan-group-policy] [I-D.smith-vxlan-group-policy]
Smith, M. and L. Kreeger, "VXLAN Group Policy Option", Smith, M. and L. Kreeger, "VXLAN Group Policy Option",
draft-smith-vxlan-group-policy-04 (work in progress), draft-smith-vxlan-group-policy-05 (work in progress),
October 2017. October 2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
Authors' Addresses Authors' Addresses
John Lemon (editor) John Lemon (editor)
Broadcom Limited Broadcom Inc.
270 Innovation Drive 270 Innovation Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: john.lemon@broadcom.com Email: john.lemon@broadcom.com
Michael Smith Michael Smith
Cisco Systems Cisco Systems
Email: michsmit@cisco.com Email: michsmit@cisco.com
Aldrin Isaac
Juniper Networks
1133 Innovation Way
Sunnyvale, CA 94089
USA
Email: aldrin.isaac@gmail.com
 End of changes. 19 change blocks. 
25 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/