[Pce] I-D Action: draft-ietf-pce-wson-rwa-ext-09.txt

2018-11-04 Thread internet-drafts


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

Title   : PCEP Extension for WSON Routing and Wavelength 
Assignment
Authors : Young Lee
  Ramon Casellas
Filename: draft-ietf-pce-wson-rwa-ext-09.txt
Pages   : 25
Date: 2018-11-04

Abstract:
   This document provides the Path Computation Element communication
   Protocol (PCEP) extensions for the support of Routing and Wavelength
   Assignment (RWA) in Wavelength Switched Optical Networks (WSON).
   Lightpath provisioning in WSONs requires a routing and wavelength
   assignment (RWA) process.  From a path computation perspective,
   wavelength assignment is the process of determining which wavelength
   can be used on each hop of a path and forms an additional routing
   constraint to optical light path computation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-wson-rwa-ext/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-wson-rwa-ext-09
https://datatracker.ietf.org/doc/html/draft-ietf-pce-wson-rwa-ext-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-wson-rwa-ext-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


[Pce] I-D Action: draft-ietf-pce-pcep-extension-for-pce-controller-00.txt

2018-11-04 Thread internet-drafts


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

Title   : PCEP Procedures and Protocol Extensions for Using PCE 
as a Central Controller (PCECC) of LSPs
Authors : Quintin Zhao
  Zhenbin Li
  Dhruv Dhody
  Satish Karunanithi
  Adrian Farrel
  Chao Zhou
Filename: 
draft-ietf-pce-pcep-extension-for-pce-controller-00.txt
Pages   : 30
Date: 2018-11-04

Abstract:
   The Path Computation Element (PCE) is a core component of Software-
   Defined Networking (SDN) systems.  It can compute optimal paths for
   traffic across a network and can also update the paths to reflect
   changes in the network or traffic demands.

   PCE was developed to derive paths for MPLS Label Switched Paths
   (LSPs), which are supplied to the head end of the LSP using the Path
   Computation Element Communication Protocol (PCEP).  But SDN has a
   broader applicability than signaled (G)MPLS traffic-engineered (TE)
   networks, and the PCE may be used to determine paths in a range of
   use cases.  PCEP has been proposed as a control protocol for use in
   these environments to allow the PCE to be fully enabled as a central
   controller.

   A PCE-based central controller (PCECC) can simplify the processing of
   a distributed control plane by blending it with elements of SDN and
   without necessarily completely replacing it.  Thus, the LSP can be
   calculated/setup/initiated and the label forwarding entries can also
   be downloaded through a centralized PCE server to each network
   devices along the path while leveraging the existing PCE technologies
   as much as possible.

   This document specifies the procedures and PCEP protocol extensions
   for using the PCE as the central controller.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controller-00
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-extension-for-pce-controller-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


[Pce] I-D Action: draft-ietf-pce-hierarchy-extensions-06.txt

2018-11-04 Thread internet-drafts


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

Title   : Extensions to Path Computation Element Communication 
Protocol (PCEP) for Hierarchical Path Computation Elements (PCE)
Authors : Fatai Zhang
  Quintin Zhao
  Oscar Gonzalez de Dios
  R. Casellas
  Daniel King
Filename: draft-ietf-pce-hierarchy-extensions-06.txt
Pages   : 30
Date: 2018-11-04

Abstract:
   The Hierarchical Path Computation Element (H-PCE) architecture is
   defined in RFC 6805.  It provides a mechanism to derive an optimum
   end-to-end path in a multi-domain environment by using a hierarchical
   relationship between domains to select the optimum sequence of
   domains and optimum paths across those domains.

   This document defines extensions to the Path Computation Element
   Protocol (PCEP) to support Hierarchical PCE procedures.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-hierarchy-extensions-06
https://datatracker.ietf.org/doc/html/draft-ietf-pce-hierarchy-extensions-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-hierarchy-extensions-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


Re: [Pce] New Version Notification for draft-ietf-pce-hierarchy-extensions-06.txt

2018-11-04 Thread daniel
Greetings PCE'rs,

Please find a new version of draft-ietf-pce-hierarchy-extensions (version 06). 
Thanks to Adrian Farrel for his recent and thorough review, it helped the 
authors polish the I-D. 

Revisions to the new version of the I-D include:

- Updated Abstract
- Updated Introduction
- Updated Security text
- Added RFC7399 (Unanswered questions of the PCE) text and reference to 
Introduction Scope
- Consistency of "Objective Functions" text
- Revised H-PCE-CAPABILITY TLV format and behavior
- Cleaned up Section 3.3.1 OF Codes 
- Consistency of text and readability updates
- Added IANA allocation policy to IANA Section
- Implementation Status moved to an Appendix with statement that this will be 
removed before publication

There is one material change to protocol solution in the I-D. It is proposed 
that the H-PCE-CAPABILITY TLV should now use one flag (P-bit), instead of two. 
If set, will signal that the child PCE wishes to use the peer PCE as a parent 
PCE:

https://tools.ietf.org/html/draft-ietf-pce-hierarchy-extensions-06#page-8

The authors will follow-up with Adrian, via the PCE list, and respond to his 
specific comments in a separate email. 

BR, Dan. 

-Original Message-
From: internet-dra...@ietf.org  
Sent: 05 November 2018 11:29
To: Oscar de Dios ; Daniel King ; Fatai 
Zhang ; Oscar Gonzalez de Dios ; Quintin 
Zhao ; pce-cha...@ietf.org
Subject: New Version Notification for draft-ietf-pce-hierarchy-extensions-06.txt


A new version of I-D, draft-ietf-pce-hierarchy-extensions-06.txt
has been successfully submitted by Daniel King and posted to the IETF 
repository.

Name:   draft-ietf-pce-hierarchy-extensions
Revision:   06
Title:  Extensions to Path Computation Element Communication Protocol 
(PCEP) for Hierarchical Path Computation Elements (PCE)
Document date:  2018-11-05
Group:  pce
Pages:  30
URL:
https://www.ietf.org/internet-drafts/draft-ietf-pce-hierarchy-extensions-06.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-pce-hierarchy-extensions/
Htmlized:   
https://tools.ietf.org/html/draft-ietf-pce-hierarchy-extensions-06
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-ietf-pce-hierarchy-extensions
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-hierarchy-extensions-06

Abstract:
   The Hierarchical Path Computation Element (H-PCE) architecture is
   defined in RFC 6805.  It provides a mechanism to derive an optimum
   end-to-end path in a multi-domain environment by using a hierarchical
   relationship between domains to select the optimum sequence of
   domains and optimum paths across those domains.

   This document defines extensions to the Path Computation Element
   Protocol (PCEP) to support Hierarchical PCE procedures.


___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


[Pce] FW: VN Association @ PCE

2018-11-04 Thread Leeyoung
Hi Jon,

The following is the text agreed upon between Igor and Dhruv and myself. 
--- we will update the draft with this added text in the revision.

NEW: VN association can be generally applicable to bundle TE tunnel sets where 
a VN member within a VN corresponds to a TE tunnel

Thanks.
Young

-Original Message-
From: Leeyoung 
Sent: Monday, November 5, 2018 1:07 AM
To: 'Dhruv Dhody' ; Igor Bryskin 
Subject: RE: VN Association @ PCE

Hi Dhruv,

Igor agreed with the proposal. 

Young

-Original Message-
From: Leeyoung 
Sent: Sunday, November 4, 2018 11:06 PM
To: 'Dhruv Dhody' ; Igor Bryskin 
Subject: RE: VN Association @ PCE

Igor,

On your comment on PCE VN association: 
> Igor: This is a good idea but could it be done in a generic way rather at a
>   "VN association" specifically. Just like a group of LSPs in a mesh.

Our resolution is to add text: "VN association can be generally applicable to 
bundle TE tunnel sets where a VN member within a VN corresponds to a TE tunnel."

What do you think? 

Thanks.
Young

-Original Message-
From: Dhruv Dhody [mailto:dhruv.i...@gmail.com] 
Sent: Sunday, November 4, 2018 10:35 PM
To: Leeyoung 
Subject: Re: VN Association @ PCE

Lets talk this over! We need to get Igor on board as well.
On Mon, Nov 5, 2018 at 11:25 AM Leeyoung  wrote:
>
> Hi Dhruv,
>
> I think we can say that VN association includes tunnel sets. When defining 
> VN, we can say we can bundle TE tunnels.
>
> What do you think? We may add text: "VN association can be generally 
> applicable to bundle TE tunnel sets."
>
> Young
>
> -Original Message-
> From: Dhruv Dhody [mailto:dhruv.i...@gmail.com]
> Sent: Sunday, November 4, 2018 8:58 PM
> To: Leeyoung 
> Subject: VN Association @ PCE
>
> Hi Young,
>
> We will be asked if we have resolved the Igor comments on the mic from IETF 
> 102.
>
> https://datatracker.ietf.org/doc/minutes-102-pce/
>
> 4. Previously Discussed Topics
> 4.1. ACTN VN Association (Daniele Ceccarelli, 10 min) [90/90]
> draft-leedhody-pce-vn-association-05
>
> Igor: This is a good idea but could it be done in a generic way rather at a
>   "VN association" specifically. Just like a group of LSPs in a mesh.
> Daniele Ceccarelli: Association is anyway generic, This is a new association
> type, you could define another!
> Igor: Think of a TE tunnel set.
> Daniele: You can define another association.
> Young: What Igor is asking is can it cover more than VN, with a generic TE
>tunnel set included.
>
> Thanks!
> Dhruv
___
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce