RFC 2872 on Application Identifiers for RSVP
RFC Editor <rfc-ed@ISI.EDU> Thu, 06 July 2000 00:57 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20023; Wed, 5 Jul 2000 20:57:33 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA00578 for ietf-123-outbound.10@ietf.org; Wed, 5 Jul 2000 20:55:03 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA00225 for <all-ietf@loki.ietf.org>; Wed, 5 Jul 2000 20:13:21 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19065 for <all-ietf@ietf.org>; Wed, 5 Jul 2000 20:13:19 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA22869; Wed, 5 Jul 2000 17:13:20 -0700 (PDT)
Message-Id: <200007060013.RAA22869@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2872 on Application Identifiers for RSVP
Cc: rfc-ed@ISI.EDU, rap@iphighway.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 05 Jul 2000 17:13:19 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2872 Title: Application and Sub Application Identity Policy Element for Use with RSVP Author(s): Y. Bernet, R. Pabbati Status: Standards Track Date: June 2000 Mailbox: yoramb@microsoft.com, rameshpa@microsoft.com Pages: 6 Characters: 10933 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rap-rsvp-appid-01.txt URL: ftp://ftp.isi.edu/in-notes/rfc2872.txt RSVP [RFC 2205] signaling messages typically include policy data objects, which in turn contain policy elements. Policy elements may describe user and/or application information, which may be used by RSVP aware network elements to apply appropriate policy decisions to a traffic flow. This memo details the usage of policy elements that provide application information. 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 2872 on Application Identifiers for RSVP RFC Editor