Graceful Shutdown in MPLS Traffic Engineering Networks draftaliccampmplsgracefulshutdown02'txt

1
Graceful Shutdown in MPLS Traffic Engineering
Networks draft-ali-ccamp-mpls-graceful-shutdown-
02.txt
Zafar Ali (zali_at_cisco.com) Jean Philippe Vasseur
(jpv_at_cisco.com) Anca Zamfir (ancaz_at_cisco.com)
2
IETF May Fall in Love with Canada!

• Canada has places that are colder than Minnesota,
  i.e., Ideal Venue for Winter -)
• IETF in Canada can still be counted as outside-US
  conference event, Eh -)

• Joke aside, Welcome to Canada (Bienvenue).
• I could like to thank IETF for having this
  conference in Canada Its good to travel without
  Passport, for a change -) .

3
History of the Draft

• It was first presented at IETF 60 in August 2004.
  
• There is a general agreement on the requirements.
  
• We need to close on the Signaling Solution
  (discussion focus for today).

4
Desired Attributes of the Signaling Solution

• As the Ingress LSR is expected to perform
  make-before-break for the LSP (using the resource
  that is being shutdown), we should be able to
  specify the TE resource (link/ node) under
  graceful shutdown.
• Conveying signaling message to the Ingress LSR
  suffices. I.e., we should be able to make use of
  the Notify Message.
• As use of the Notify Message is optional, we
  should also be able to make use of PathErr
  message.

5
Comparing on-the-table Signaling Solutions
6
Proposed Solution

• We propose to overload TE link maintenance
  required sub-code of the Notify Error Code (24)
  of the ERROR_SPEC.
• The ERROR_SPEC with code 24/ sub-code TBD can
  then be carried in either PathErr or Notify
  message to signal GS condition.
• The Ingress LSR is expected to perform
  make-before-break for the LSP (using resources
  that are being shutdown).
• The IGP based solution is also based on an
  existing framework.

Proposed changes are minor and straight forward
and are based on an existing framework.
7
Next Steps

• There is a general agreement on the requirements.
• The Work in within the Scope of CCAMP.
• We have addressed all existing comments on this
  draft (except some off-line comments from Dimitri
  on Version 2).
• We would like to request WG to accept this ID as
  a WG document.