[rfc-dist] RFC 4119 on A Presence-based GEOPRIV Location Object Format

[rfc-editor@rfc-editor.org]

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

        RFC 4119

        Title:      A Presence-based GEOPRIV Location Object Format
        Author(s):  J. Peterson
        Status:     Standards Track
        Date:       December 2005
        Mailbox:    jon.peterson at neustar.biz
        Pages:      24
        Characters: 53522
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-geopriv-pidf-lo-03.txt


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


This document describes an object format for carrying geographical
information on the Internet.  This location object extends the
Presence Information Data Format (PIDF), which was designed for
communicating privacy-sensitive presence information and which has
similar properties.  [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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to \"rfc-info at RFC-EDITOR.ORG\" with the message body 

\"help: ways_to_get_rfcs\".  For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 
Type: 
Size: 0 bytes
Desc: not available
Url : http://mailman.rfc-editor.org/pipermail/rfc-dist/attachments/20051213/ef94438b/attachment.ksh