RFC 5687 on GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements

rfc-editor@rfc-editor.org Wed, 10 March 2010 19:17 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 214313A6926; Wed, 10 Mar 2010 11:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level:
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 NaDCjSU3qPoV; Wed, 10 Mar 2010 11:17:34 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 8F47B3A695F; Wed, 10 Mar 2010 11:17:26 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C8558E0724; Wed, 10 Mar 2010 11:17:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5687 on GEOPRIV Layer 7 Location Configuration Protocol: Problem Statement and Requirements
From: rfc-editor@rfc-editor.org
Message-Id: <20100310191731.C8558E0724@rfc-editor.org>
Date: Wed, 10 Mar 2010 11:17:31 -0800 (PST)
Cc: geopriv@ietf.org, 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: Wed, 10 Mar 2010 19:17:36 -0000

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

        
        RFC 5687

        Title:      GEOPRIV Layer 7 Location Configuration 
                    Protocol: Problem Statement and Requirements 
        Author:     H. Tschofenig, H. Schulzrinne
        Status:     Informational
        Date:       March 2010
        Mailbox:    Hannes.Tschofenig@gmx.net, 
                    hgs+ecrit@cs.columbia.edu
        Pages:      21
        Characters: 40880
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geopriv-l7-lcp-ps-10.txt

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

This document provides a problem statement, lists requirements, and
captures design aspects for a GEOPRIV Layer 7 (L7) Location
Configuration Protocol (LCP).  This protocol aims to allow an end
host to obtain location information, by value or by reference, from a
Location Information Server (LIS) that is located in the access
network.  The obtained location information can then be used for a
variety of different protocols and purposes.  For example, it can be
used as input to the Location-to-Service Translation (LoST) Protocol
or to convey location within the Session Initiation Protocol (SIP) to
other entities.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

This document is a product of the Geographic Location/Privacy 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