Fwd: RFC 4770 on vCard Extensions for Instant Messaging (IM)

>Date: Wed, 10 Jan 2007 14:07:34 -0800
>To: [email protected], [email protected]
>From: [email protected]
>X-Spam-Score: -14.8 (--------------)
>X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
>Cc: [email protected]
>Subject: RFC 4770 on vCard Extensions for Instant Messaging (IM)
>X-BeenThere: [email protected]
>X-Mailman-Version: 2.1.5
>List-Id: ietf-announce.ietf.org
>List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
>	<mailto:[email protected]?subject=unsubscribe>
>List-Post: <mailto:[email protected]>
>List-Help: <mailto:[email protected]?subject=help>
>List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>,
>	<mailto:[email protected]?subject=subscribe>
>
>
>A new Request for Comments is now available in online RFC libraries.
>
>        
>         RFC 4770
>
>         Title:      vCard Extensions for Instant Messaging
>                     (IM)
>         Author:     C. Jennings, J. Reschke, Ed.
>         Status:     Standards Track
>         Date:       January 2007
>         Mailbox:    [email protected],
>                     [email protected]
>         Pages:      7
>         Characters: 11077
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-jennings-impp-vcard-08.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc4770.txt
>
>This document describes an extension to vCard to support Instant
>Messaging (IM) and Presence Protocol (PP) applications.  IM and PP
>are becoming increasingly common ways of communicating, and users
>want to save this contact information in their address books.  It
>allows a URI that is associated with IM or PP to be specified inside
>a vCard.  [STANDARDS TRACK]
>
>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 [email protected].  Requests to be
>added to or deleted from the RFC-DIST distribution list should
>be sent to [email protected].
>
>Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>an EMAIL message to [email protected] with the message body
>
>help: ways_to_get_rfcs. For example:
>
>         To: [email protected]
>         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 protected].  Unless
>specifically noted otherwise on the RFC itself, all RFCs are for
>unlimited distribution.
>
>Submissions for Requests for Comments should be sent to
>[email protected].  Please consult RFC 2223, Instructions to RFC
>Authors, for further information.
>
>
>The RFC Editor Team
>USC/Information Sciences Institute
>
>...
>
>
>
>_______________________________________________
>IETF-Announce mailing list
>[email protected]
>https://www1.ietf.org/mailman/listinfo/ietf-announce