VPIM v2 now published as Draft Standard
"Glenn Parsons" <[email protected]> Fri, 9 Jul 2004 13:47:38 -0400
| Newsgroups | gmane.ietf.vpim |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1114981652== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C465DC.D36A0AEC" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C465DC.D36A0AEC Content-Type: text/plain; charset="ISO-8859-1" Folks, In case you missed it, VPIM v2 has finally been published as a draft standard. You may recall that we finished work on this revision several years ago. It has taken a while to bring the various VPIM references to the same level of maturity. Draft standard is the second of three levels of maturity for IETF standards and is an indication of the increasing number of VPIM implementations and deployment. RFC 3801, 3802, 3803 are the new RFCs. Note that the changes from the RFC 2421-2424 are mostly editorial (the details are noted in the RFCs). FYI, we are working to move the remaining I-Ds on IVM and VPIM directory through the publication process in the coming months. Cheers, Glenn Parsons Chair, VPIM WG Begin forwarded message: > From: <[email protected]> > Date: Thu Jun 24, 2004 5:22:23 PM Canada/Eastern > Cc: <[email protected]>, <[email protected]> > Subject: RFC 3801 on Voice Profile for Internet Mail - version 2 (VPIMv2) > > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 3801 > > Title: Voice Profile for Internet Mail - version 2 > (VPIMv2) > Author(s): G. Vaudreuil, G. Parsons > Status: Standards Track > Date: June 2004 > Mailbox: [email protected], [email protected] > Pages: 55 > Characters: 118122 > Obsoletes: 2421 > > I-D Tag: draft-ietf-vpim-vpimv2r2-05.txt > > URL: ftp://ftp.rfc-editor.org/in-notes/rfc3801.txt > > > This document specifies a restricted profile of the Internet > multimedia messaging protocols for use between voice processing server > platforms. The profile is referred to as the Voice Profile for > Internet Mail (VPIM) in this document. These platforms have > historically been special-purpose computers and often do not have the > same facilities normally associated with a traditional Internet > Email-capable computer. As a result, VPIM also specifies additional > functionality, as it is needed. This profile is intended to specify > the minimum common set of features to allow interworking between > conforming systems. > > This document obsoletes RFC 2421 and describes version 2 of the > profile with greater precision. No protocol changes were made in this > revision. A list of changes from RFC 2421 are noted in Appendix F. > Appendix A summarizes the protocol profiles of this version of VPIM. > > This document is a product of the Voice Profile for Internet Mail > Working Group of the IETF. > > This is now a Draft 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 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.echo > 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 > > ... > > ------_=_NextPart_001_01C465DC.D36A0AEC Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3DISO-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2656.31"> <TITLE>VPIM v2 now published as Draft Standard</TITLE> </HEAD> <BODY> <P><FONT FACE=3D"Arial">Folks, </FONT> </P> <P><FONT FACE=3D"Arial">In case you missed it, VPIM v2 has finally been = published as a draft standard. You may recall that we = finished work on this revision several years ago. It has taken a = while to bring the various VPIM references to the same level of = maturity.</FONT></P> <P><FONT FACE=3D"Arial">Draft standard is the second of three levels of = maturity for IETF standards and is an indication of the increasing = number of VPIM implementations and deployment.</FONT></P> <P><B><FONT FACE=3D"Arial">RFC 3801, 3802, 3803</FONT></B> <FONT = FACE=3D"Arial">are the new RFCs. </FONT> </P> <P><FONT FACE=3D"Arial">Note that the changes from the RFC 2421-2424 = are mostly editorial (the details are noted in the RFCs).</FONT> </P> <P><FONT FACE=3D"Arial">FYI, we are working to move the remaining I-Ds = on IVM and VPIM directory through the publication process in the coming = months.</FONT></P> <P><FONT FACE=3D"Arial">Cheers, </FONT> <BR><FONT FACE=3D"Arial">Glenn Parsons</FONT> <BR><FONT FACE=3D"Arial">Chair, VPIM WG </FONT> </P> <BR> <P><FONT FACE=3D"Arial">Begin forwarded message: </FONT> </P> <BR> <UL> <P><B><FONT FACE=3D"Arial">From:</FONT></B> <FONT = FACE=3D"Arial"><[email protected]> </FONT> <BR><B><FONT FACE=3D"Arial">Date:</FONT></B> <FONT FACE=3D"Arial">Thu = Jun 24, 2004 5:22:23 PM Canada/Eastern </FONT> <BR><B><FONT FACE=3D"Arial">Cc:</FONT></B> <FONT = FACE=3D"Arial"><[email protected]>, = <[email protected]> </FONT> <BR><B><FONT FACE=3D"Arial">Subject:</FONT></B> <FONT = FACE=3D"Arial">RFC 3801 on Voice Profile for Internet Mail - version 2 = (VPIMv2) </FONT> </P> <BR> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">A new Request for Comments is now = available in online RFC libraries.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 RFC = 3801</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = Title:=A0=A0=A0=A0=A0 Voice Profile for Internet Mail - version 2 = </FONT> <BR><FONT SIZE=3D2 = FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= (VPIMv2) </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 Author(s):=A0 = G. Vaudreuil, G. Parsons </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = Status:=A0=A0=A0=A0 Standards Track </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = Date:=A0=A0=A0=A0=A0=A0 June 2004 </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = Mailbox:=A0=A0=A0 [email protected], [email protected] </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = Pages:=A0=A0=A0=A0=A0 55 </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 Characters: = 118122 </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 Obsoletes:=A0 = 2421</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 I-D = Tag:=A0=A0=A0 draft-ietf-vpim-vpimv2r2-05.txt</FONT><FONT = FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 = URL:=A0=A0=A0=A0=A0=A0=A0</FONT><U> <FONT COLOR=3D"#0000FF" SIZE=3D2 = FACE=3D"Arial"><A = HREF=3D"ftp://ftp.rfc-editor.org/in-notes/rfc3801.txt" = TARGET=3D"_blank">ftp://ftp.rfc-editor.org/in-notes/rfc3801.txt</A></FON= T></U><FONT FACE=3D"Arial"> </FONT> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">This document specifies a restricted = profile of the Internet </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">multimedia messaging protocols for = use between voice processing server </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">platforms.=A0 The profile is referred = to as the Voice Profile for </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Internet Mail (VPIM) in this = document.=A0 These platforms have </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">historically been special-purpose = computers and often do not have the </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">same facilities normally associated = with a traditional Internet </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Email-capable computer.=A0 As a = result, VPIM also specifies additional </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">functionality, as it is needed.=A0 = This profile is intended to specify </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">the minimum common set of features to = allow interworking between </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">conforming systems.</FONT><FONT = FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">This document obsoletes RFC 2421 and = describes version 2 of the </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">profile with greater precision.=A0 No = protocol changes were made in this </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">revision.=A0 A list of changes from = RFC 2421 are noted in Appendix F. </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Appendix A summarizes the protocol = profiles of this version of VPIM.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">This document is a product of the = Voice Profile for Internet Mail </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Working Group of the = IETF.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">This is now a Draft Standard = Protocol.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">This document specifies an Internet = standards track protocol for </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">the Internet community, and requests = discussion and suggestions </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">for improvements.=A0 Please refer to = the current edition of the </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">"Internet Official Protocol = Standards" (STD 1) for the </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">standardization state and status of = this protocol.=A0 Distribution </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">of this memo is = unlimited.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">This announcement is sent to the IETF = list and the RFC-DIST list. </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Requests to be added to or deleted = from the IETF distribution list </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">should be sent to = [email protected].=A0 Requests to be </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">added to or deleted from the RFC-DIST = distribution list should </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">be sent to = [email protected].</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Details on obtaining RFCs via FTP or = EMAIL may be obtained by sending </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">an EMAIL message to = [email protected] with the message body </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">help: ways_to_get_rfcs.=A0 For = example:</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 To: = [email protected] </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 Subject: = getting rfcs</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">=A0=A0=A0=A0=A0=A0=A0 help: = ways_to_get_rfcs</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Requests for special distribution = should be addressed to either the </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">author of the RFC in question, or to = [email protected].=A0 Unless </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">specifically noted otherwise on the = RFC itself, all RFCs are for </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">unlimited distribution.echo </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Submissions for Requests for Comments = should be sent to </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">[email protected].=A0 Please = consult RFC 2223, Instructions to RFC </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Authors, for further = information.</FONT><FONT FACE=3D"Arial"> </FONT> </P> <BR> <P><FONT SIZE=3D2 FACE=3D"Arial">Joyce K. Reynolds and Sandy Ginoza = </FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">USC/Information Sciences = Institute</FONT><FONT FACE=3D"Arial"> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">...</FONT><FONT FACE=3D"Arial"> = </FONT> </P> <BR> </UL> </BODY> </HTML> ------_=_NextPart_001_01C465DC.D36A0AEC-- --===============1114981652== 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 --===============1114981652==--