idnits 2.17.1 draft-ietf-rap-rsvp-authsession-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3520 5 Title: Session Authorization Policy Element 6 Author(s): L-N. Hamer, B. Gage, B. Kosinski, H. Shieh 7 Status: Standards Track 8 Date: April 2003 9 Mailbox: nhamer@nortelnetworks.com, 10 brettk@invidi.com, gageb@nortelnetworks.com, 11 hugh.shieh@attws.com 12 Pages: 30 13 Characters: 63445 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-rap-rsvp-authsession-05.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3520.txt 20 This document describes the representation of a session 21 authorization policy element for supporting policy-based per-session 22 authorization and admission control. The goal of session 23 authorization is to allow the exchange of information between 24 network elements in order to authorize the use of resources for a 25 service and to co-ordinate actions between the signaling and 26 transport planes. This document describes how a process on a system 27 authorizes the reservation of resources by a host and then provides 28 that host with a session authorization policy element which can be 29 inserted into a resource reservation protocol (e.g., the Resource 30 ReSerVation Protocol (RSVP) PATH message) to facilitate proper and 31 secure reservation of those resources within the network. We describe 32 the encoding of session authorization information as a policy element 33 conforming to the format of a Policy Data object (RFC 2750) and 34 provide details relating to operations, processing rules and error 35 scenarios. 37 This document is a product of the Resource Allocation Protocol Working 38 Group of the IETF. 40 This is now a Proposed Standard Protocol. 42 This document specifies an Internet standards track protocol for 43 the Internet community, and requests discussion and suggestions 44 for improvements. Please refer to the current edition of the 45 "Internet Official Protocol Standards" (STD 1) for the 46 standardization state and status of this protocol. Distribution 47 of this memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.