[rfc-dist] RFC 4230 on RSVP Security Properties
rfc-editor at rfc-editor.org
Wed Dec 21 11:15:40 PST 2005
A new Request for Comments is now available in online RFC libraries.
Title: RSVP Security Properties
Author(s): H. Tschofenig, R. Graveman
Date: December 2005
Mailbox: Hannes.Tschofenig at siemens.com, rfg at acm.org
I-D Tag: draft-ietf-nsis-rsvp-sec-properties-06.txt
This document summarizes the security properties of RSVP. The goal
of this analysis is to benefit from previous work done on RSVP and to
capture knowledge about past activities.
This document is a product of the Next Steps in Signaling Working
Group of the IETF.
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. 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 at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at 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.
More information about the rfc-dist