RFC 3520 on Session Authorization Policy Element
rfc-editor@rfc-editor.org Mon, 14 April 2003 22:34 UTC
Received: from ran.ietf.org (ran.ietf.org [10.27.6.60]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25482; Mon, 14 Apr 2003 18:34:19 -0400 (EDT)
Received: from majordomo by ran.ietf.org with local (Exim 4.10) id 195CoR-0007Ki-00 for ietf-announce-list@ran.ietf.org; Mon, 14 Apr 2003 18:52:31 -0400
Received: from odin.ietf.org ([10.27.2.28] helo=ietf.org) by ran.ietf.org with esmtp (Exim 4.10) id 195CmV-0006Ys-00 for all-ietf@ran.ietf.org; Mon, 14 Apr 2003 18:50:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25263 for <all-ietf@ietf.org>; Mon, 14 Apr 2003 18:30:39 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 195CVj-0005ll-00 for all-ietf@ietf.org; Mon, 14 Apr 2003 18:33:11 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 195CVi-0005li-00 for all-ietf@ietf.org; Mon, 14 Apr 2003 18:33:10 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h3EMXG011857; Mon, 14 Apr 2003 15:33:16 -0700 (PDT)
Message-Id: <200304142233.h3EMXG011857@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3520 on Session Authorization Policy Element
Cc: rfc-editor@rfc-editor.org, rap@ops.ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 14 Apr 2003 15:33:16 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3520 Title: Session Authorization Policy Element Author(s): L-N. Hamer, B. Gage, B. Kosinski, H. Shieh Status: Standards Track Date: April 2003 Mailbox: nhamer@nortelnetworks.com, brettk@invidi.com, gageb@nortelnetworks.com, hugh.shieh@attws.com Pages: 30 Characters: 63445 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rap-rsvp-authsession-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3520.txt This document describes the representation of a session authorization policy element for supporting policy-based per-session authorization and admission control. The goal of session authorization is to allow the exchange of information between network elements in order to authorize the use of resources for a service and to co-ordinate actions between the signaling and transport planes. This document describes how a process on a system authorizes the reservation of resources by a host and then provides that host with a session authorization policy element which can be inserted into a resource reservation protocol (e.g., the Resource ReSerVation Protocol (RSVP) PATH message) to facilitate proper and secure reservation of those resources within the network. We describe the encoding of session authorization information as a policy element conforming to the format of a Policy Data object (RFC 2750) and provide details relating to operations, processing rules and error scenarios. 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.