Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement
draft-ietf-ccamp-rsvp-node-id-based-hello-03

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    ccamp mailing list <ccamp@ops.ietf.org>, 
    ccamp chair <ccamp-chairs@tools.ietf.org>
Subject: Protocol Action: 'Node ID based RSVP Hello: A 
         Clarification Statement' to Proposed Standard 

The IESG has approved the following document:

- 'Node ID based RSVP Hello: A Clarification Statement '
   <draft-ietf-ccamp-rsvp-node-id-based-hello-04.txt> as a Proposed Standard

This document is the product of the Common Control and Measurement Plane 
Working Group. 

The IESG contact persons are Alex Zinin and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-node-id-based-hello-04.txt

Ballot Text

Technical Summary
 
   Use of Node-ID based RSVP Hello messages is implied in a number of
   cases, e.g., when data and control plan are separated, when TE links
   are unnumbered. Furthermore, when link level failure detection is
   performed by some means other than exchanging RSVP Hello messages,
   use of Node-ID based Hello session is optimal for detecting signaling
   adjacency failure for Resource reSerVation Protocol-Traffic
   Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear
   and this document formalizes use of Node-ID based RSVP Hello session
   as a best current practice (BCP) in some scenarios. The procedure
   described in this document applies to both Multi-Protocol Label
   Switching (MPLS) and Generalized MPLS (GMPLS) capable nodes.

 
Working Group Summary
 
 The WG had consensus on progressing this document.
 
Protocol Quality
 
 The document has been reviewed for the IESG by Alex Zinin.

Note to RFC Editor
 
 Abstract
Delete "as a best current practice (BCP)" as follows...
OLD
   Use of Node-ID based RSVP Hello messages is implied in a number of
   cases, e.g., when data and control plan are separated, when TE links
   are unnumbered. Furthermore, when link level failure detection is
   performed by some means other than exchanging RSVP Hello messages,
   use of Node-ID based Hello session is optimal for detecting signaling
   adjacency failure for Resource reSerVation Protocol-Traffic
   Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear
   and this document formalizes use of Node-ID based RSVP Hello session
   as a best current practice (BCP) in some scenarios. The procedure
   described in this document applies to both Multi-Protocol Label
   Switching (MPLS) and Generalized MPLS (GMPLS) capable nodes.
NEW
   Use of Node-ID based RSVP Hello messages is implied in a number of
   cases, e.g., when data and control plan are separated, when TE links
   are unnumbered. Furthermore, when link level failure detection is
   performed by some means other than exchanging RSVP Hello messages,
   use of Node-ID based Hello session is optimal for detecting signaling
   adjacency failure for Resource reSerVation Protocol-Traffic
   Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear
   and this document formalizes use of Node-ID based RSVP Hello session
   in some scenarios. The procedure described in this document applies to
   both Multi-Protocol Label Switching (MPLS) and Generalized MPLS
   (GMPLS) capable nodes.

RFC Editor Note