Upload
joy-lester
View
213
Download
1
Embed Size (px)
Citation preview
1
Ping and Traceroute for GMPLS LSPs in Non-Packet Switched Networks
draft-ali-ccamp-gmpls-lsp-ping-traceroute-01.txt
Zafar Ali, Roberto Cassata (Cisco Systems) Marco Anisetti, Valerio Bellandi, Ernesto Damiani,
Francesco Diana, Umberto Raimondi (University of Milan) T. Otani (KDDI R&D Laboratories)
22271th IETF, CCAMP WG, 71th IETF, CCAMP WG, Philadelphia March 2008Philadelphia March 2008
Outline
• Requirements Addressed
• Scope of the Draft
• GMPLS OAM Solutions (Changes from Previous Version).
• Next Steps
33371th IETF, CCAMP WG, 71th IETF, CCAMP WG, Philadelphia March 2008Philadelphia March 2008
Requirements Addressed
• In pure light path even if every node along the path is connected, the reachability of the end node with an acceptable signal quality is not guaranteed.
• For Operational and Management purposes, SP needs to be aware of all physical evidence (consisting of optical measurements such as signal power, OSNR, Optical Channel Monitor, etc.) that have effect on the light-path, before using the LSP for traffic.
• The proposed technique is suitable for optical networks that suffer of physical dysfunction due the non-ideal optical transmission medium and/or to critical situations.
• Tracerouting with Measurements (Evidence) Collection.
• GMPLS LSP Ping.
444
Scope of the Draft
• “Use of OAM functionality provided by the data planes is RECOMMENDED and procedures described in this draft are only assumed to be applied when OAM mechanisms are not supported by the data plane or are deficient.”
• “The draft relies on control plan mechanism to provide required OAM functions. Specifically the proposed solutions are based on Link Management Protocol (LMP) [RFC4204] and RSVP-TE [RFC3209], [RFC3473] and do not require any extension to the data plan.”
• The draft addresses some GMPLS OAM requirements stated in the draft-ietf-ccamp-gmpls-oam-requirements-00.txt
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
555
Optical Path Quality Evaluation
• The quality of an optical path is done by collecting the physical evidences along an LSP and evaluating them (e.g. for faulty point detection).
• In this draft we extend the LSP_ATTRIBUTES to perform the evidence collection hop by hop.
• In evidences collection process certain evidences require a mutually exclusive access.
Therefore the entire LSP needs to be locked until the evidence collection process is performed.
If other evidence collection process tries to retrieve evidences on the same node-resource already under Administrative Evidences Locking status, it must be aborted.
• The draft uses RSVP Admin status object to define LSP Administrative Evidences Locking status and to make sure that all nodes are ready to collect the blocking evidence.
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
666
Extensions: Administrative Status Object extension
• We propose and extension to Administrative status object by adding two bits for locking purpose
• Blocking node (B): 1 bit. When set, indicates that locking procedure is ongoing.
• Confirm blocking (C): 1 bit. When set, indicates that an the locking procedure is successfully ongoing.
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
777
Tracerouting with non-blocking evidence collection
PXC1 PXC2None-PSC Node1
Path Message Path Message Path Message
Resv Message Resv Message Resv MessageResv Message
Evidence Collection Request TLV
Evidences Recording TLV
Free
Evidence Reading
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
888
Tracerouting with blocking evidence collection and all nodes ready for evidence collection
PXC1 PXC2None-PSC Node1
B=1C=1R=1
B=1C=1R=1
B=1C=1R=1
B=1C=1R=0
B=1C=1R=0
B=1C=1R=0
Free
Locked
Lock Required
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
999
PXC1 PXC2None-PSC Node1
B=1C=1R=1
B=1C=0R=1
B=1C=1R=1
B=1C=0R=0
B=1C=0R=0
B=1C=0R=0
Free
Locked
Lock Required
Tracerouting with blocking evidence collection with some node(s) blocked for evidence collection
71th IETF, CCAMP WG, 71th IETF, CCAMP WG, PhiladelphiaPhiladelphia, Dec. 2008, Dec. 2008
11111171th IETF, CCAMP WG, 71th IETF, CCAMP WG, Philadelphia March 2008Philadelphia March 2008
Next Steps
• This work is within CCAMP Charter.
• The draft addresses some GMPLS OAM requirements stated in the draft-ietf-ccamp-gmpls-oam-requirements-00.txt.
• At this point we are looking for more feedback and next steps for this work.
121212
Thank You.