RFC 6050 on A Session Initiation Protocol (SIP) Extension for the Identification of Services
rfc-editor@rfc-editor.org Mon, 22 November 2010 18:25 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09B9D28C14C for <ietf-announce@core3.amsl.com>; Mon, 22 Nov 2010 10:25:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.362
X-Spam-Level:
X-Spam-Status: No, score=-102.362 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvleD4UGlxgi for <ietf-announce@core3.amsl.com>; Mon, 22 Nov 2010 10:25:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 231A728C140 for <ietf-announce@ietf.org>; Mon, 22 Nov 2010 10:25:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 70994E06F1; Mon, 22 Nov 2010 10:26:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6050 on A Session Initiation Protocol (SIP) Extension for the Identification of Services
From: rfc-editor@rfc-editor.org
Message-Id: <20101122182631.70994E06F1@rfc-editor.org>
Date: Mon, 22 Nov 2010 10:26:31 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 18:25:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6050
Title: A Session Initiation Protocol (SIP)
Extension for the Identification of Services
Author: K. Drage
Status: Informational
Stream: IETF
Date: November 2010
Mailbox: drage@alcatel-lucent.com
Pages: 19
Characters: 41021
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-drage-sipping-service-identification-05.txt
URL: http://www.rfc-editor.org/rfc/rfc6050.txt
This document describes private extensions to the Session Initiation
Protocol (SIP) that enable a network of trusted SIP servers to assert
the service of authenticated users. The use of these extensions is
only applicable inside an administrative domain with previously
agreed-upon policies for generation, transport, and usage of such
information. This document does NOT offer a general service
identification model suitable for use between different trust domains
or for use in the Internet at large.
The document also defines a URN to identify both services and User
Agent (UA) applications. This URN can be used within the SIP header
fields defined in this document to identify services, and also within
the framework defined for caller preferences and callee capabilities
to identify usage of both services and applications between end UAs.
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC