VPIM has finished

"Glenn Parsons" <[email protected]> Sun, 6 Nov 2005 20:34:53 -0500
Newsgroups gmane.ietf.vpim
Message-ID <085091CB2CA14E4B8B163FFC37C84E9D06FB73CB@zcarhxm0.corp.nortel.com>
This is a multi-part message in MIME format.

--===============0985679667==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5E33B.7392E6AC"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5E33B.7392E6AC
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Folks,

FYI, in case you did not notice, after many years the final VPIM RFCs =
have made it through the RFC Editor's Queue.

RFC4237 <ftp://ftp.rfc-editor.org/in-notes/rfc4237.txt>        Voice =
Messaging Directory Service =20
RFC4238 <ftp://ftp.rfc-editor.org/in-notes/rfc4238.txt>        Voice =
Message Routing Service =20
RFC4239 <ftp://ftp.rfc-editor.org/in-notes/rfc4239.txt>        Internet =
Voice Messaging (IVM)  =20

In my mind, even though the WG was closed some time ago, the work of the =
VPIM WG is now complete.

And to celebrate, Nortel is hosting IETF 64 in Vancouver :-)

The mailing list remains open to discuss any issues with the published =
RFCs.

Cheers,
Glenn.

------_=_NextPart_001_01C5E33B.7392E6AC
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 =
6.5.7233.28">
<TITLE>VPIM has finished</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Folks,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">FYI, in case you did not notice, after =
many years the final VPIM RFCs have made it through the RFC Editor's =
Queue.</FONT>
</P>

<P><A HREF=3D"ftp://ftp.rfc-editor.org/in-notes/rfc4237.txt"><U><B><FONT =
COLOR=3D"#0000FF" FACE=3D"Arial">RFC4237</FONT></B></U></A><FONT =
FACE=3D"Arial"> =A0=A0=A0=A0=A0<B> Voice Messaging Directory Service =
=A0</B><BR>
</FONT><A =
HREF=3D"ftp://ftp.rfc-editor.org/in-notes/rfc4238.txt"><U></U><U><B><FONT=
 COLOR=3D"#0000FF" FACE=3D"Arial">RFC4238</FONT></B></U></A><FONT =
FACE=3D"Arial"> =A0=A0=A0=A0=A0</FONT><B><FONT FACE=3D"Arial"> Voice =
Message Routing Service =A0</FONT></B><BR>
<A =
HREF=3D"ftp://ftp.rfc-editor.org/in-notes/rfc4239.txt"><U></U><U><B><FONT=
 COLOR=3D"#0000FF" FACE=3D"Arial">RFC4239</FONT></B></U></A><FONT =
FACE=3D"Arial"> =A0=A0=A0=A0=A0</FONT><B><FONT FACE=3D"Arial"> Internet =
Voice Messaging (IVM) =A0</FONT></B><FONT FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In my mind, even though the WG was =
closed some time ago, the work of the VPIM WG is now complete.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">And to celebrate, Nortel is hosting =
IETF 64 in Vancouver :-)</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The mailing list remains open to =
discuss any issues with the published RFCs.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Cheers,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Glenn.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C5E33B.7392E6AC--


--===============0985679667==
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

--===============0985679667==--