[Ecrit] RFC 6444 on Location Hiding: Problem Statement and Requirements
rfc-editor@rfc-editor.org Wed, 04 January 2012 22:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3D8711E80B6; Wed, 4 Jan 2012 14:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.346
X-Spam-Level:
X-Spam-Status: No, score=-102.346 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, 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 D9FHiA4J8DPt; Wed, 4 Jan 2012 14:56:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 6851E11E80C5; Wed, 4 Jan 2012 14:56:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E123972E004; Wed, 4 Jan 2012 14:54:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120104225423.E123972E004@rfc-editor.org>
Date: Wed, 04 Jan 2012 14:54:23 -0800
Cc: ecrit@ietf.org, rfc-editor@rfc-editor.org
Subject: [Ecrit] RFC 6444 on Location Hiding: Problem Statement and Requirements
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2012 22:56:39 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6444 Title: Location Hiding: Problem Statement and Requirements Author: H. Schulzrinne, L. Liess, H. Tschofenig, B. Stark, A. Kuett Status: Informational Stream: IETF Date: January 2012 Mailbox: hgs+ecrit@cs.columbia.edu, L.Liess@telekom.de, Hannes.Tschofenig@gmx.net, barbara.stark@att.com, andres.kytt@skype.net Pages: 9 Characters: 18495 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ecrit-location-hiding-req-04.txt URL: http://www.rfc-editor.org/rfc/rfc6444.txt The emergency services architecture developed in the IETF Emergency Context Resolution with Internet Technology (ECRIT) working group describes an architecture where location information is provided by access networks to endpoints or Voice over IP (VoIP) service providers in order to determine the correct dial string and information to route the call to a Public Safety Answering Point (PSAP). To determine the PSAP Uniform Resource Identifier (URI), the usage of the Location-to-Service Translation (LoST) protocol is envisioned. This document provides a problem statement and lists requirements for situations where the Internet Access Provider (IAP) and/or the Internet Service Provider (ISP) are only willing to disclose limited or no location information. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Emergency Context Resolution with Internet Technologies 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-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