FW: RFC 4024 on Voice Messaging Client Behaviour

This is a multi-part message in MIME format.

------_=_NextPart_001_01C588B0.220609B7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

FYI,=20

Another VPIM RFC has finally published.

That leaves three remaining in the RFC Editors Queue:

draft-ietf-vpim-ivm
draft-ietf-vpim-vpimdir
draft-ietf-vpim-routing

These should hopefully publish within the next month.

Cheers,
Glenn.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, July 13, 2005 5:58 PM
To: [email protected]
Cc: [email protected]
Subject: RFC 4024 on Voice Messaging Client Behaviour


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


        RFC 4024

        Title:      Voice Messaging Client Behaviour
        Author(s):  G. Parsons, J. Maruszak
        Status:     Informational
        Date:       July 2005
        Mailbox:    [email protected], [email protected]
        Pages:      9
        Characters: 18560
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ema-vpim-cb-02.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4024.txt


This document defines the expected behaviour of a client to various
aspects of a Voice Profile for Internet Mail (VPIM) message or any voice
and/or fax message.

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 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.


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.

------_=_NextPart_001_01C588B0.220609B7
Content-Type: application/octet-stream;
	name="ATT4699006.TXT"
Content-Description: ATT4699006.TXT
Content-Disposition: attachment;
	filename="ATT4699006.TXT"
Content-Transfer-Encoding: base64

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJSRkMtSU5GT0BSRkMtRURJVE9SLk9SRyINCg0KQ29udGVudC1UeXBl
OiB0ZXh0L3BsYWluDQpDb250ZW50LUlEOiA8MDUwNzEzMTQ1NjUxLlJGQ0BSRkMtRURJVE9SLk9S
Rz4NCg0KUkVUUklFVkU6IHJmYw0KRE9DLUlEOiByZmM0MDI0DQo=

------_=_NextPart_001_01C588B0.220609B7
Content-Type: application/octet-stream;
	name="rfc4024.URL"
Content-Description: rfc4024.URL
Content-Disposition: attachment;
	filename="rfc4024.URL"
Content-Transfer-Encoding: base64

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlzaS5lZHUvaW4tbm90ZXMvcmZjNDAy
NC50eHQNCg==

------_=_NextPart_001_01C588B0.220609B7
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
VPIM mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/vpim

------_=_NextPart_001_01C588B0.220609B7--