[Geopriv] RFC 5580 on Carrying Location Objects in RADIUS and Diameter

rfc-editor@rfc-editor.org Tue, 04 August 2009 22:49 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: geopriv@core3.amsl.com
Delivered-To: geopriv@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CA3F28C211; Tue, 4 Aug 2009 15:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.433
X-Spam-Level:
X-Spam-Status: No, score=-16.433 tagged_above=-999 required=5 tests=[AWL=0.566, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 ngC91wPMG2O1; Tue, 4 Aug 2009 15:49:34 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 5FD4B3A691A; Tue, 4 Aug 2009 15:48:35 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 8E5E22FA9B0; Tue, 4 Aug 2009 15:43:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090804224313.8E5E22FA9B0@bosco.isi.edu>
Date: Tue, 04 Aug 2009 15:43:13 -0700
Cc: geopriv@ietf.org, rfc-editor@rfc-editor.org
Subject: [Geopriv] RFC 5580 on Carrying Location Objects in RADIUS and Diameter
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 22:49:35 -0000

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

        
        RFC 5580

        Title:      Carrying Location Objects in RADIUS 
                    and Diameter 
        Author:     H. Tschofenig, Ed.,
                    F. Adrangi, M. Jones,
                    A. Lior, B. Aboba
        Status:     Standards Track
        Date:       August 2009
        Mailbox:    Hannes.Tschofenig@gmx.net, 
                    farid.adrangi@intel.com, 
                    mark.jones@bridgewatersystems.com,
                    avi@bridgewatersystems.com, 
                    bernarda@microsoft.com
        Pages:      53
        Characters: 119753
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-geopriv-radius-lo-24.txt

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

This document describes procedures for conveying access-network
ownership and location information based on civic and geospatial
location formats in Remote Authentication Dial-In User Service
(RADIUS) and Diameter.

The distribution of location information is a privacy-sensitive task.
Dealing with mechanisms to preserve the user's privacy is important
and is addressed in this document.  [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
USC/Information Sciences Institute