Discussion list for Path Computation Element (PCE) - based architecture for computation of paths in MPLS and GMPLS

internet-drafts | 5 Jul 2012 15:12

I-D Action: draft-ietf-pce-pcep-domain-sequence-01.txt


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

	Title           : Standard Representation Of Domain Sequence
	Author(s)       : Dhruv Dhody
                          Udayasree Palle
                          Ramon Casellas
	Filename        : draft-ietf-pce-pcep-domain-sequence-01.txt
	Pages           : 31
	Date            : 2012-07-05

Abstract:
   The ability to compute shortest constrained Traffic Engineering Label
   Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and
   Generalized MPLS (GMPLS) networks across multiple domains has been
   identified as a key requirement for P2P and P2MP scenarios.  In this
   context, a domain is a collection of network elements within a common
   sphere of address management or path computational responsibility
   such as an IGP area or an Autonomous Systems.  This document
   specifies a standard representation and encoding of a domain
   sequence, which is defined as an ordered sequence of domains
   traversed to reach the destination domain.  This document also
   defines new sub-objects to be used to encode domain identifiers.

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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-pce-pcep-domain-sequence-01

(Continue reading)

headers

Dhruv Dhody | 7 Jul 2012 07:26

Re: I-D Action: draft-ietf-pce-pcep-domain-sequence-01.txt

Dear WG,

We have updated the domain-sequence draft 
'draft-ietf-pce-pcep-domain-sequence-01'

The main changes are - 
(1) Documenting two mechanism for encoding of the domain-sequence
sub-objects 
    in IRO
      - a New IRO Type: With new processing rules like order, Loose/Strict, 
        unknown sub-objects etc
      - Use of IRO Type 1(RFC 5440): New sub-objects encoding in the IRO,
with 
        no inherent order and existing processing rules. 

(2) Section on use of the sub-objects in XRO, ERO, EXRS. 

(3) Manageability, Security and IANA considerations

(4) Comments and suggestions from Adrian's Mails 
    [http://www.ietf.org/mail-archive/web/pce/current/msg02782.html]	
      - Added both options for IRO in the draft
      - Clarified the encoding of sub-objects and the difference with TLVs 
      - Loose handling for the new IRO type
      - Mode of operations
      - Unknown sub-object handling v/s constraints not met
      - Relationship with PCE Sequence 

*******
Poll:

(Continue reading)