BCP 160, RFC 6280 on An Architecture for Location and Location Privacy in Internet Applications
rfc-editor@rfc-editor.org Sat, 23 July 2011 20:57 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 6B66F21F8C06; Sat, 23 Jul 2011 13:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level:
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, 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 AF6uHVSESEVS; Sat, 23 Jul 2011 13:57:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfa.amsl.com (Postfix) with ESMTP id BF3B421F8C02; Sat, 23 Jul 2011 13:57:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 294A298C4F4; Sat, 23 Jul 2011 13:57:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 160, RFC 6280 on An Architecture for Location and Location Privacy in Internet Applications
From: rfc-editor@rfc-editor.org
Message-Id: <20110723205737.294A298C4F4@rfc-editor.org>
Date: Sat, 23 Jul 2011 13:57:37 -0700
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: Sat, 23 Jul 2011 20:57:38 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 160
RFC 6280
Title: An Architecture for Location and
Location Privacy in Internet Applications
Author: R. Barnes, M. Lepinski,
A. Cooper, J. Morris,
H. Tschofenig, H. Schulzrinne
Status: Best Current Practice
Stream: IETF
Date: July 2011
Mailbox: rbarnes@bbn.com,
mlepinski@bbn.com,
acooper@cdt.org, jmorris@cdt.org,
Hannes.Tschofenig@gmx.net, hgs@cs.columbia.edu
Pages: 41
Characters: 99801
Updates: RFC3693, RFC3694
See Also: BCP0160
I-D Tag: draft-ietf-geopriv-arch-03.txt
URL: http://www.rfc-editor.org/rfc/rfc6280.txt
Location-based services (such as navigation applications, emergency
services, and management of equipment in the field) need geographic
location information about Internet hosts, their users, and other
related entities. These applications need to securely gather and
transfer location information for location services, and at the same
time protect the privacy of the individuals involved. This document
describes an architecture for privacy-preserving location-based
services in the Internet, focusing on authorization, security, and
privacy requirements for the data formats and protocols used by these
services. This memo documents an Internet Best Current Practice.
This document is a product of the Geographic Location/Privacy Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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