Subject: RE: [Geopriv] Correction: RFC 4119 on A Presence-based GEOPRIV LocationObject Format

From: "Winterbottom, James" <[email-masked]>
Date: Fri, 16 Dec 2005 19:41:19 -0600

At last!!!

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]] On
Behalf
> Of [email-masked]
> Sent: Saturday, 17 December 2005 12:16 PM
> To: [email-masked]
> Cc: [email-masked]; [email-masked]
> Subject: [Geopriv] Correction: RFC 4119 on A Presence-based GEOPRIV
> LocationObject Format
> 
> 
> 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:    [email-masked]
>         Pages:      24
>         Characters: 53522
>         Updates/Obsoletes/SeeAlso:    None
> 
>         I-D Tag:    draft-ietf-geopriv-pidf-lo-03.txt
> 
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4119.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.
> 
> This document is a product of the Geographic Location/Privacy Working
> Group of the IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> 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 [email-masked].  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to [email-masked].
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to [email-masked] with the message body
> help: ways_to_get_rfcs.  For example:
> 
>         To: [email-masked]
>         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 [email-masked].
Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> Submissions for Requests for Comments should be sent to
> [email-masked].  Please consult RFC 2223, Instructions to
RFC
> Authors, for further information.
> 
> 
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
> 
> ...
> 
> Below is the data which will enable a MIME compliant Mail Reader
> implementation to automatically retrieve the ASCII version
> of the RFCs.
------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]

_______________________________________________
Geopriv mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/geopriv