< draft-ietf-pce-association-policy-03.txt   draft-ietf-pce-association-policy-04.txt >
PCE Working Group D. Dhody, Ed. PCE Working Group D. Dhody, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track S. Sivabalan Intended status: Standards Track S. Sivabalan
Expires: December 21, 2018 Cisco Systems, Inc. Expires: June 21, 2019 Cisco Systems, Inc.
S. Litkowski S. Litkowski
Orange Orange
J. Tantsura J. Tantsura
Individual Apstra, Inc.
J. Hardwick J. Hardwick
Metaswitch Networks Metaswitch Networks
June 19, 2018 December 18, 2018
Path Computation Element communication Protocol extension for Path Computation Element communication Protocol extension for
associating Policies and LSPs associating Policies and LSPs
draft-ietf-pce-association-policy-03 draft-ietf-pce-association-policy-04
Abstract Abstract
This document introduces a simple mechanism to associate policies to This document introduces a simple mechanism to associate policies to
a group of Label Switched Paths (LSPs) via an extension to the Path a group of Label Switched Paths (LSPs) via an extension to the Path
Computation Element (PCE) Communication Protocol (PCEP). Computation Element (PCE) Communication Protocol (PCEP).
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
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 December 21, 2018. This Internet-Draft will expire on June 21, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 6, line 22 skipping to change at page 6, line 22
4. Overview 4. Overview
As per [I-D.ietf-pce-association-group], LSPs are associated with As per [I-D.ietf-pce-association-group], LSPs are associated with
other LSPs with which they interact by adding them to a common other LSPs with which they interact by adding them to a common
association group. Grouping can also be used to define association association group. Grouping can also be used to define association
between LSPs and policies associated to them. One new Association between LSPs and policies associated to them. One new Association
Type is defined in this document, based on the generic Association Type is defined in this document, based on the generic Association
object - object -
o Association type = TBD1 ("Policy Association Type") for Policy o Association type = TBD1 ("Policy Association Type") for Policy
Association Group (PAG) Association Group (PAG).
[I-D.ietf-pce-association-group] specify the mechanism for the [I-D.ietf-pce-association-group] specify the mechanism for the
capability advertisement of the association types supported by a PCEP capability advertisement of the association types supported by a PCEP
speaker by defining a ASSOC-Type-List TLV to be carried within an speaker by defining a ASSOC-Type-List TLV to be carried within an
OPEN object. This capability exchange for the association type OPEN object. This capability exchange for the association type
described in this document (i.e. Policy Association Type) MUST be described in this document (i.e. Policy Association Type) MUST be
done before using the policy association. Thus the PCEP speaker MUST done before using the policy association. Thus the PCEP speaker MUST
include the Policy Association Type (TBD1) in the ASSOC-Type-List TLV include the Policy Association Type (TBD1) in the ASSOC-Type-List TLV
before using the PAG in the PCEP messages. before using the PAG in the PCEP messages.
skipping to change at page 7, line 42 skipping to change at page 7, line 42
o VENDOR-INFORMATION-TLV: Used to communicate arbitrary vendor o VENDOR-INFORMATION-TLV: Used to communicate arbitrary vendor
specific behavioral information, described in [RFC7470]. specific behavioral information, described in [RFC7470].
5.1. Policy Parameters TLV 5.1. Policy Parameters TLV
The POLICY-PARAMETERS-TLV is an optional TLV that can be carried in The POLICY-PARAMETERS-TLV is an optional TLV that can be carried in
ASSOCIATION object (with "Policy Association Type") to carry opaque ASSOCIATION object (with "Policy Association Type") to carry opaque
information needed to apply the policy at the PCEP peer. In some information needed to apply the policy at the PCEP peer. In some
cases to apply a PCE policy successfully, it is required to also cases to apply a PCE policy successfully, it is required to also
associate some policy parameters that needs to be evaluated to associate some policy parameters that needs to be evaluated, to
successfully apply the said policy. This TLV is used to carry those successfully apply the said policy. This TLV is used to carry those
policy parameters. The TLV could include one or more policy related policy parameters. The TLV could include one or more policy related
parameter. The encoding format and the order MUST be known to the parameter. The encoding format and the order MUST be known to the
PCEP peers, this could be done during configuration of policy (and PCEP peers, this could be done during configuration of policy (and
its association parameters) for the PAG. The TLV format is as per its association parameters) for the PAG. The TLV format is as per
the format of the PCEP TLVs, as defined in [RFC5440], and shown in the format of the PCEP TLVs, as defined in [RFC5440], and shown in
Figure 2. Only one POLICY-PARAMETERS-TLV can be carried and only the Figure 2. Only one POLICY-PARAMETERS-TLV can be carried and only the
first occurrence is processed and any others MUST be ignored. first occurrence is processed and any others MUST be ignored.
0 1 2 3 0 1 2 3
skipping to change at page 11, line 44 skipping to change at page 11, line 44
[RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path [RFC8281] Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "Path
Computation Element Communication Protocol (PCEP) Computation Element Communication Protocol (PCEP)
Extensions for PCE-Initiated LSP Setup in a Stateful PCE Extensions for PCE-Initiated LSP Setup in a Stateful PCE
Model", RFC 8281, DOI 10.17487/RFC8281, December 2017, Model", RFC 8281, DOI 10.17487/RFC8281, December 2017,
<https://www.rfc-editor.org/info/rfc8281>. <https://www.rfc-editor.org/info/rfc8281>.
[I-D.ietf-pce-segment-routing] [I-D.ietf-pce-segment-routing]
Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W., Sivabalan, S., Filsfils, C., Tantsura, J., Henderickx, W.,
and J. Hardwick, "PCEP Extensions for Segment Routing", and J. Hardwick, "PCEP Extensions for Segment Routing",
draft-ietf-pce-segment-routing-11 (work in progress), draft-ietf-pce-segment-routing-14 (work in progress),
November 2017. October 2018.
[I-D.ietf-pce-pcep-yang] [I-D.ietf-pce-pcep-yang]
Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A Dhody, D., Hardwick, J., Beeram, V., and J. Tantsura, "A
YANG Data Model for Path Computation Element YANG Data Model for Path Computation Element
Communications Protocol (PCEP)", draft-ietf-pce-pcep- Communications Protocol (PCEP)", draft-ietf-pce-pcep-
yang-07 (work in progress), March 2018. yang-09 (work in progress), October 2018.
Appendix A. Contributor Addresses Appendix A. Contributor Addresses
Qin Wu Qin Wu
Huawei Technologies Huawei Technologies
101 Software Avenue, Yuhua District 101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012 Nanjing, Jiangsu 210012
China China
EMail: sunseawq@huawei.com EMail: sunseawq@huawei.com
skipping to change at page 13, line 18 skipping to change at page 13, line 18
Canada Canada
EMail: msiva@cisco.com EMail: msiva@cisco.com
Stephane Litkowski Stephane Litkowski
Orange Orange
EMail: stephane.litkowski@orange.com EMail: stephane.litkowski@orange.com
Jeff Tantsura Jeff Tantsura
Individual Apstra, Inc.
EMail: jefftant.ietf@gmail.com EMail: jefftant.ietf@gmail.com
Jonathan Hardwick Jonathan Hardwick
Metaswitch Networks Metaswitch Networks
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
UK UK
EMail: Jonathan.Hardwick@metaswitch.com EMail: Jonathan.Hardwick@metaswitch.com
 End of changes. 10 change blocks. 
11 lines changed or deleted 11 lines changed or added

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