RFC 6447 on Filtering Location Notifications in the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Fri, 27 January 2012 17:28 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 0431621F85C9; Fri, 27 Jan 2012 09:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.147
X-Spam-Level:
X-Spam-Status: No, score=-102.147 tagged_above=-999 required=5 tests=[AWL=-0.147, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUE2x2dZ0k+O; Fri, 27 Jan 2012 09:28:42 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5E821F85AF; Fri, 27 Jan 2012 09:28:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 752A6B1E004; Fri, 27 Jan 2012 09:25:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6447 on Filtering Location Notifications in the Session Initiation Protocol (SIP)
From: rfc-editor@rfc-editor.org
Message-Id: <20120127172503.752A6B1E004@rfc-editor.org>
Date: Fri, 27 Jan 2012 09:25:03 -0800
Cc: geopriv@ietf.org, 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: Fri, 27 Jan 2012 17:28:43 -0000

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

        
        RFC 6447

        Title:      Filtering Location Notifications in the 
                    Session Initiation Protocol (SIP) 
        Author:     R. Mahy, B. Rosen, H. Tschofenig
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2012
        Mailbox:    rohan@ekabal.com, 
                    br@brianrosen.net, 
                    Hannes.Tschofenig@gmx.net
        Pages:      19
        Characters: 36577
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geopriv-loc-filters-11.txt

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

This document describes filters that limit asynchronous location
notifications to compelling events.  These filters are designed as an
extension to RFC 4661, an XML-based format for event notification
filtering, and based on RFC 3856, the SIP presence event package.
The resulting location information is conveyed in existing location
formats wrapped in the Presence Information Data Format Location
Object (PIDF-LO).  [STANDARDS-TRACK]

This document is a product of the Geographic Location/Privacy Working Group of the IETF.

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