1. 71st IETF Philadelphia, March 2008 ERO Extensions for Path Key draft-bradford-ccamp-path-key-ero-01.txt Richard Bradford : rbradfor@cisco.com JP Vasseur : jvasseur@cisco.com Adrian Farrel : adrian@olddog.co.uk

2. 71st IETF Philadelphia, March 2008 Background in PCE Working Group Cooperating PCEs may be used to compute inter- domain paths –Each PCE is responsible for the computation in a single domain –Each PCE contributes a segment of the whole LSP route –By concatenating the segments, the ingress LSR can be provided with the full path of the end-to-end LSP PCE Path Segment Full path = Path Segment + Path Segment

3. 71st IETF Philadelphia, March 2008 Topology Confidentiality in PCE WG Problem is that operators of separate domains dont want to share information about the path in their domain –In RSVP-TE they would filter the RRO at the domain boundary Solution in PCE WG is to designate the path segment as a Confidential Path Segment –Replace it in the PCE messages with a Path Key –Key is decoded on entry into downstream domain PCE Path Key Full path = Path Segment + Path Key Decode Path Key

4. 71st IETF Philadelphia, March 2008 Issue for RSVP-TE We need to convey the Path Key as part of the Explicit Route –This draft simply defines a new ERO subobject –Subobject can also be used in RRO –Content of subobject is defined by PCE WG –Format of subobject is defined in this draft –Processing rules are simple

5. 71st IETF Philadelphia, March 2008 Plans People in PCE WG have implementation plans This extension is needed to support them Do it in CCAMP or PCE? –I prefer that we do all protocol extensions in CCAMP Make it a CCAMP WG draft? –Authors believe it is ready