[rfc-dist] RFC 4484 on Trait-Based Authorization Requirements for the Session Initiation Protocol (SIP)
rfc-editor at rfc-editor.org
Thu Aug 31 15:50:32 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Trait-Based Authorization Requirements for the
Session Initiation Protocol (SIP)
Author: J. Peterson, J. Polk,
D. Sicker, H. Tschofenig
Date: August 2006
Mailbox: jon.peterson at neustar.biz,
jmpolk at cisco.com,
douglas.sicker at colorado.edu,
Hannes.Tschofenig at siemens.com
I-D Tag: draft-ietf-sipping-trait-authz-02.txt
This document lays out a set of requirements related to trait-based
authorization for the Session Initiation Protocol (SIP). While some
authentication mechanisms are described in the base SIP
specification, trait-based authorization provides information used to
make policy decisions based on the attributes of a participant in a
session. This approach provides a richer framework for
authorization, as well as allows greater privacy for users of an
identity system. This memo provides information for the Internet community.
This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.
INFORMATIONAL: 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
More information about the rfc-dist