Zafar Ali, Danny Prairie and Reshad Rahman

1. Administrative Control of RSVP Hello and Graceful Restart Proceduredraft-ali-ccamp-rsvp-hello-gr-admin-00.txt Zafar Ali, Danny Prairie andReshad Rahman zali@cisco.com, dprairie@cisco.com, rrahman@cisco.com

2. Requirement • RSVP Hellos are not mandatory and are only required to run when needed. • There are applications that run RSVP Hellos with intervals on the order of milliseconds. • Requirement is to reduce the number of RSVP messages to a minimal required count • Ability to administratively shutdown RSVP Hellos and Graceful Restart (GR) procedure without impacting the traffic is a desirable network operation.

3. Enable RSVP GR/ Hello Hello Message Exchange Problem Statement ... Disable RSVP GR/ Hello • RSVP Hellos do NOT stop! • This behavior is unlike other protocols. • Presently, the specifications do not provide a procedure to signal the intent to administratively shutdown or remove RSVP Hello sessions. • The only way to get around this limitation is to continue to run Hellos even after applications have no use of them, which is undesirable. The administrative shutdown of RSVP Hello or GR sessions may cause traffic disruption for LSPs that depend on the health of the Hello session.

4. Disable RSVP GR/ Hello Hello Message with Restart Cap Object Hello Message without Restart Cap Object Proposed Solution Signaling Graceful Removal of RSVP GR Session ... Signaling Graceful Removal of RSVP Hello Session • The Admin_Status Object is overloaded and its use in the context of RSVP Hello is specified. • We are open to other suggestions. • Procedure is optional and backward compatible.

5. Next Steps • Given that, • There seems to be an agreement in using removal of RSVP Restart Cap Object for disabling GR procedure. • We are open to comments for alternative ways to signal removal of RSVP Hello session. • The procedures are optional and backward compatible. • We would like the WG to adopt this ID as a WG document.