draft-ietf-pce-stateful-sync-optimizations-07.txt   draft-ietf-pce-stateful-sync-optimizations-08.txt 
PCE Working Group E. Crabbe PCE Working Group E. Crabbe
Internet-Draft Oracle Internet-Draft Oracle
Intended status: Standards Track I. Minei Intended status: Standards Track I. Minei
Expires: June 11, 2017 Google, Inc. Expires: July 27, 2017 Google, Inc.
J. Medved J. Medved
Cisco Systems, Inc. Cisco Systems, Inc.
R. Varga R. Varga
Pantheon Technologies SRO Pantheon Technologies SRO
X. Zhang X. Zhang
D. Dhody D. Dhody
Huawei Technologies Huawei Technologies
December 8, 2016 January 23, 2017
Optimizations of Label Switched Path State Synchronization Procedures Optimizations of Label Switched Path State Synchronization Procedures
for a Stateful PCE for a Stateful PCE
draft-ietf-pce-stateful-sync-optimizations-07 draft-ietf-pce-stateful-sync-optimizations-08
Abstract Abstract
A stateful Path Computation Element (PCE) has access to not only the A stateful Path Computation Element (PCE) has access to not only the
information disseminated by the network's Interior Gateway Protocol information disseminated by the network's Interior Gateway Protocol
(IGP), but also the set of active paths and their reserved resources (IGP), but also the set of active paths and their reserved resources
for its computation. The additional Label Switched Path (LSP) state for its computation. The additional Label Switched Path (LSP) state
information allows the PCE to compute constrained paths while information allows the PCE to compute constrained paths while
considering individual LSPs and their interactions. This requires a considering individual LSPs and their interactions. This requires a
reliable state synchronization mechanism between the PCE and the reliable state synchronization mechanism between the PCE and the
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 June 11, 2017. This Internet-Draft will expire on July 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
skipping to change at page 16, line 8 skipping to change at page 16, line 8
In order to allow a stateful PCE to control the LSP-DB In order to allow a stateful PCE to control the LSP-DB
synchronization after establishing a PCEP session, both PCEP speakers synchronization after establishing a PCEP session, both PCEP speakers
MUST set F bit to 1 in the OPEN message. If the TRIGGERED-INITIAL- MUST set F bit to 1 in the OPEN message. If the TRIGGERED-INITIAL-
SYNC capability is not advertised by a PCE and the PCC receives a SYNC capability is not advertised by a PCE and the PCC receives a
PCUpd with the SYNC flag set to 1, it MUST send a PCErr with the SRP- PCUpd with the SYNC flag set to 1, it MUST send a PCErr with the SRP-
ID-number of the PCUpd, Error-Type 20 and Error-Value TBD (suggested ID-number of the PCUpd, Error-Type 20 and Error-Value TBD (suggested
value - 4) 'Attempt to trigger synchronization when the TRIGGERED- value - 4) 'Attempt to trigger synchronization when the TRIGGERED-
SYNC capability has not been advertised' (see Section 8.1). If the SYNC capability has not been advertised' (see Section 8.1). If the
LSP-DB Version is mis-matched, it can send a PCUpd message with PLSP- LSP-DB Version is mis-matched, it can send a PCUpd message with PLSP-
ID = 0 and SYNC = 1 in order to trigger the LSP-DB synchronization ID = 0 and SYNC = 1 in order to trigger the LSP-DB synchronization
process. In this way, the PCE can control the sequence of LSP process. The PCUpd message MUST include an empty ERO as its intended
synchronization among all the PCCs that are re-establishing PCEP path and SHOULD NOT include the optional objects for its attributes.
sessions with it. When the capability of PCE control is enabled, In this way, the PCE can control the sequence of LSP synchronization
only after a PCC receives this message, it will start sending among all the PCCs that are re-establishing PCEP sessions with it.
information to the PCE. The PCC SHOULD NOT send PCRpt messages to When the capability of PCE control is enabled, only after a PCC
the stateful PCE before it triggers the State Synchronization. This receives this message, it will start sending information to the PCE.
PCE-triggering capability can be applied to both full and incremental The PCC SHOULD NOT send PCRpt messages to the stateful PCE before it
state synchronization. If applied to the later, the PCCs only send triggers the State Synchronization. This PCE-triggering capability
information that PCE does not possess, which is inferred from the can be applied to both full and incremental state synchronization.
LSP-DB version information exchanged in the OPEN message (see If applied to the later, the PCCs only send information that PCE does
Section 4.2 for detailed procedure). not possess, which is inferred from the LSP-DB version information
exchanged in the OPEN message (see Section 4.2 for detailed
procedure).
Once the initial state synchronization is triggered by the PCE, the Once the initial state synchronization is triggered by the PCE, the
procedures and error checks remain unchanged from the full state procedures and error checks remain unchanged from the full state
synchronization ([I-D.ietf-pce-stateful-pce]). synchronization ([I-D.ietf-pce-stateful-pce]).
6. PCE-triggered Re-synchronization 6. PCE-triggered Re-synchronization
6.1. Motivation 6.1. Motivation
The accuracy of the computations performed by the PCE is tied to the The accuracy of the computations performed by the PCE is tied to the
skipping to change at page 17, line 9 skipping to change at page 17, line 11
SHOULD NOT include any parameter updates for the LSP, and the PCC SHOULD NOT include any parameter updates for the LSP, and the PCC
SHOULD ignore such updates if the SYNC flag is set. The PCC MUST SHOULD ignore such updates if the SYNC flag is set. The PCC MUST
respond with a PCRpt message with the LSP state, SYNC Flag set to 0 respond with a PCRpt message with the LSP state, SYNC Flag set to 0
and MUST include the SRP-ID-number of the PCUpd message that and MUST include the SRP-ID-number of the PCUpd message that
triggered the resynchronization. triggered the resynchronization.
The PCE can also trigger re-synchronization of the entire LSP The PCE can also trigger re-synchronization of the entire LSP
database. The PCE MUST first mark all LSPs in the LSP database that database. The PCE MUST first mark all LSPs in the LSP database that
were previously reported by the PCC as stale and then send a PCUpd were previously reported by the PCC as stale and then send a PCUpd
with an LSP object containing a PLSP-ID of 0 and with the SYNC flag with an LSP object containing a PLSP-ID of 0 and with the SYNC flag
set to 1. This PCUpd message is the trigger for the PCC to enter the set to 1. The PCUpd message MUST include an empty ERO as its
synchronization phase as described in [I-D.ietf-pce-stateful-pce] and intended path and SHOULD NOT include the optional objects for its
start sending PCRpt messages. After the receipt of the end-of- attributes. This PCUpd message is the trigger for the PCC to enter
the synchronization phase as described in [I-D.ietf-pce-stateful-pce]
and start sending PCRpt messages. After the receipt of the end-of-
synchronization marker, the PCE will purge LSPs which were not synchronization marker, the PCE will purge LSPs which were not
refreshed. The SRP-ID-number of the PCUpd that triggered the re- refreshed. The SRP-ID-number of the PCUpd that triggered the re-
synchronization SHOULD be included in each of the PCRpt messages. synchronization SHOULD be included in each of the PCRpt messages.
If the TRIGGERED-RESYNC capability is not advertised by a PCE and the If the TRIGGERED-RESYNC capability is not advertised by a PCE and the
PCC receives a PCUpd with the SYNC flag set to 1, it MUST send a PCC receives a PCUpd with the SYNC flag set to 1, it MUST send a
PCErr with the SRP-ID-number of the PCUpd, Error-Type 20 and Error- PCErr with the SRP-ID-number of the PCUpd, Error-Type 20 and Error-
Value TBD (suggested value - 4) 'Attempt to trigger synchronization Value TBD (suggested value - 4) 'Attempt to trigger synchronization
when the TRIGGERED-SYNC capability has not been advertised' (see when the TRIGGERED-SYNC capability has not been advertised' (see
Section 8.1). Section 8.1).
 End of changes. 7 change blocks. 
19 lines changed or deleted 23 lines changed or added

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