ERO Extensions for Path Key draft-bradford-ccamp-path-key-ero-01.txt

1
ERO Extensions for Path Keydraft-bradford-ccamp-
path-key-ero-01.txt

• Richard Bradford rbradfor_at_cisco.com
• JP Vasseur jvasseur_at_cisco.com
• Adrian Farrel adrian_at_olddog.co.uk

2
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

Path Segment
PCE
PCE
Full path Path Segment Path Segment
3
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

Path Key
PCE
PCE
Full path Path Segment Path Key
Decode Path Key
4
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
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