Exclude Routes - Extension to Resource ReserVation Protocol-Traffic Engineering (RSVP-TE)
draft-ietf-ccamp-rsvp-te-exclude-route-06

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: 'Exclude Routes - Extension to 
         RSVP-TE' to Proposed Standard 

The IESG has approved the following document:

- 'Exclude Routes - Extension to RSVP-TE '
   <draft-ietf-ccamp-rsvp-te-exclude-route-07.txt> as a Proposed Standard

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

The IESG contact persons are Ross Callon and David Ward.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-exclude-route-07.txt

Ballot Text

Technical Summary
 
  In some networks where precise explicit paths are not computed at the
  head end it may be useful to specify and signal abstract nodes and
  resources that are to be explicitly excluded from routes. These
  exclusions may apply to the whole path, or to parts of a path between
  two abstract nodes specified in an explicit path. How Shared Risk
  Link Groups (SLRGs) can be excluded is also specified in this
  document.

  This document specifies ways to communicate route exclusions during
  path setup using RSVP-TE.
 
Working Group Summary
 
  no reports of any dissent
 
Protocol Quality
 
  Ross Callon has reviewed this for the IESG, and Eric Gray has
  provided Gen-ART review comments. The document has been updated
  in response to Eric's and Ross' comments. I know of at least one
  implementation with some deployment, and I suspect that there is
  more than one implementation.

RFC Editor Note