RFC 6796 on A User Agent Profile Data Set for Media Policy

rfc-editor@rfc-editor.org Thu, 06 December 2012 22:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E0221E8039 for <ietf-announce@ietfa.amsl.com>; Thu, 6 Dec 2012 14:35:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.7
X-Spam-Level:
X-Spam-Status: No, score=-101.7 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8MCfYPUzsPN for <ietf-announce@ietfa.amsl.com>; Thu, 6 Dec 2012 14:35:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id AB91D21E804A for <ietf-announce@ietf.org>; Thu, 6 Dec 2012 14:35:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CE08972F4F6; Thu, 6 Dec 2012 14:27:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6796 on A User Agent Profile Data Set for Media Policy
From: rfc-editor@rfc-editor.org
Message-Id: <20121206222712.CE08972F4F6@rfc-editor.org>
Date: Thu, 06 Dec 2012 14:27:12 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 06 Dec 2012 22:35:33 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6796

        Title:      A User Agent Profile Data 
                    Set for Media Policy 
        Author:     V. Hilt, G. Camarillo,
                    J. Rosenberg, D. Worley
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2012
        Mailbox:    volker.hilt@bell-labs.com, 
                    Gonzalo.Camarillo@ericsson.com, 
                    jdrosen@jdrosen.net, worley@ariadne.com
        Pages:      43
        Characters: 88634
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-camarillo-rai-media-policy-dataset-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6796.txt

This specification defines an XML document format to describe the
media properties of Session Initiation Protocol (SIP) sessions.
Examples for media properties are the codecs or media types used in
the session.  This document also defines an XML document format to
describe policies that limit the media properties of SIP sessions.
[STANDARDS-TRACK]


This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-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