A new Request for Comments is now available in online RFC libraries.


        RFC 2750

        Title:      RSVP Extensions for Policy Control
        Author(s):  S. Herzog
        Status:     Standards Track
        Date:       January 2000
        Mailbox:    herzog@iphighway.com
        Pages:      13
        Characters: 26379
        Updates/Obsoletes/SeeAlso: None
        I-D Tag:    draft-ietf-rap-rsvp-ext-06.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2750.txt


This memo presents a set of extensions for supporting generic policy
based admission control in RSVP. It should be perceived as an
extension to the RSVP functional specifications [RSVP]
 
These extensions include the standard format of POLICY_DATA objects,
and a description of RSVP's handling of policy events.
 
This document does not advocate particular policy control mechanisms;
however, a Router/Server Policy Protocol description for these
extensions can be found in [RAP, COPS, COPS-RSVP].

This document is a product of the Resource Allocation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.