MPLS-TP OAM Framework draft-ietf-mpls-tp-oam-framework-07 editors: Dave Allan, Italo Busi, Ben Niven-Jenkins

1
MPLS-TP OAM Frameworkdraft-ietf-mpls-tp-oam-fram
ework-07editorsDave Allan, Italo Busi,Ben
Niven-Jenkins
2
Changes Since Anaheim

• Weve revd the document twice
• Processed the comments of two last calls
• Including liaisons from SG15
• Tightened Up the document significantly
• Terminology Changes
• PST ? SPME
• Terminology Clarifications
• Too many to mention
• Concept clarifications
• Up down MEP, per node/per interface MIPs
• Some implications of instantiating SPMEs
• Noting actual procedures are out of scope

3
Changes Since Anaheim-2

• Some changes of note
• Uniform model of TTL copying allowed for SPMEs
• Implication being TTL will address SPME MIPs,
  which can then only use of an out of band
  return path
• Operation of LKI and LKR significantly clarified

4
Fault Reporting
S-PE
S-PE
P
P
A
D
B
C
PW MEG
MIP
MIP
LSP MEG
MEP
MEP
MIP
MIP
Server MEG
MEP
MEP
5
Lock Reporting
S-PE
S-PE
P
P
A
D
B
C
PW MEG
MIP
MIP
LSP MEG
MEP
MEP
MIP
MIP
Server MEG
MEP
MEP
6
Open Issues

• Practical limits of detecting unexpected OAM
  encapsulation, a.k.a. mis-connectivity defect
• How far into heuristics do we want to mandate?
• Short pipe and uniform models for SPMEs
• Decoupling the configuration of TTL and TC
  copying is not actually mandated anywhere
• Description of SPME MEGs
• Can be any two points before SPME is setup
• Providing SPME does not overlap other SPMEs
• These two points become "adjacent" at the LSP
  sub-layer after the SPME is setup

7
Next Steps

• The document is quite close to a last last call
• Third time lucky?
• Well look to resolve the last few outstanding
  issues and request a last call before Beijing