idnits 2.17.1 draft-ietf-rap-rsvp-newidentity-02.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 3182 5 Title: Identity Representation for RSVP 6 Author(s): S. Yadav, R. Yavatkar, R. Pabbati, 7 P. Ford, T. Moore, S. Herzog, R. Hess 8 Status: Standards Track 9 Date: October 2001 10 Mailbox: rodney.hess@intel.com, Satyendra.Yadav@intel.com, 11 rameshpa@microsoft.com, peterf@microsoft.com, 12 timmoore@microsoft.com, 13 herzog@policyconsulting.com 14 Pages: 18 15 Characters: 36544 16 Obsoletes: 2752 18 I-D Tag: draft-ietf-rap-rsvp-newidentity-02.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3182.txt 22 This document describes the representation of identity information in 23 POLICY_DATA object for supporting policy based admission control in 24 the Resource ReSerVation Protocol (RSVP). The goal of identity 25 representation is to allow a process on a system to securely identify 26 the owner and the application of the communicating process (e.g., user 27 id) and convey this information in RSVP messages (PATH or RESV) in a 28 secure manner. We describe the encoding of identities as RSVP policy 29 element. We describe the processing rules to generate identity policy 30 elements for multicast merged flows. Subsequently, we describe 31 representations of user identities for Kerberos and Public Key based 32 user authentication mechanisms. In summary, we describe the use of 33 this identity information in an operational setting. 35 This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment 36 error and a field size definition error in ErrorValue in RFC 2752. 38 This document is a product of the Resource Allocation Protocol Working 39 Group of the IETF. 41 This is now a Proposed Standard Protocol. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.