From owner-um@snowshore.com Mon Feb 25 18:16:25 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1PNGPT05662 for um-outgoing; Mon, 25 Feb 2002 18:16:25 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from esanborn (keeper.snowshore.com [216.57.133.4]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1PNGPB05658 for ; Mon, 25 Feb 2002 18:16:25 -0500 (EST) Message-Id: <200202252316.g1PNGPB05658@flyingfox.snowshore.com> From: Ed Sanborn To: um@snowshore.com Subject: Test message #1 Date: Mon, 25 Feb 2002 18:16:11 -0500 X-Mailer: CorporateTime Outlook Connector 3.1.2 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by flyingfox.snowshore.com id g1PNGPB05659 Sender: owner-um@snowshore.com Precedence: bulk Just a test... Ed Sanborn (978) 367-8478 Principal Network Administrator SnowShore Networks 285 Billerica Rd. Chelmsford, MA. 01824 From owner-um@snowshore.com Tue Feb 26 11:34:04 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1QGY4G20088 for um-outgoing; Tue, 26 Feb 2002 11:34:04 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1QGY2B20084 for ; Tue, 26 Feb 2002 11:34:03 -0500 (EST) Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56]) by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1QGXtq07740; Tue, 26 Feb 2002 11:33:55 -0500 (EST) Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1QGXru27143; Tue, 26 Feb 2002 11:33:53 -0500 (EST) Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id ; Tue, 26 Feb 2002 11:33:53 -0500 Message-ID: From: "Glenn Parsons" To: ietf-fax@imc.org Cc: IETF VPIM List , um@snowshore.com Subject: ID-ACTIONs on UM Date: Tue, 26 Feb 2002 11:33:50 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C1BEE3.5F4007D0" Sender: owner-um@snowshore.com Precedence: bulk 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_000_01C1BEE3.5F4007D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1BEE3.5F4007D0" ------_=_NextPart_001_01C1BEE3.5F4007D0 Content-Type: text/plain; charset="iso-8859-1" Folks, These drafts discuss some general unified messaging (UM) client issues that I think would be worth discussing at both the FAX and VPIM WGs. After some discussion, I suggest we need to decide between the following: a) create a new BOF/WG to work on UM b) recharter VPIM and/or FAX to work on this c) close and combine VPIM and FAX into a new UM WG to work on this and remaining VPIM/FAX topics Cheers, Glenn Parsons VPIM WG Chair <<[VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt>> <<[VPIM] I-D ACTION:draft-burger-um-reqts-00.txt>> ------_=_NextPart_001_01C1BEE3.5F4007D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ID-ACTIONs on UM

Folks,

These drafts discuss some general = unified messaging (UM) client issues that I think would be worth = discussing at both the FAX and VPIM WGs.

After some discussion, I suggest we = need to decide between the following:
a) create a new BOF/WG to work on = UM
b) recharter VPIM and/or FAX to work = on this
c) close and combine VPIM and FAX = into a new UM WG to work on this and remaining VPIM/FAX topics

Cheers,
Glenn Parsons
VPIM WG Chair

  <<[VPIM] I-D = ACTION:draft-vaudreuil-um-issues-00.txt>> <<[VPIM] I-D = ACTION:draft-burger-um-reqts-00.txt>>

------_=_NextPart_001_01C1BEE3.5F4007D0-- ------_=_NextPart_000_01C1BEE3.5F4007D0 Content-Type: message/rfc822 Message-ID: <200202221120.GAA27151@ietf.org> From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org To: Cc: ietf-imapext@imc.org, vpim@lists.neystadt.org Subject: [VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt Date: Fri, 22 Feb 2002 06:20:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C1BEE3.5F4007D0" ------_=_NextPart_002_01C1BEE3.5F4007D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_003_01C1BEE3.5F4007D0" ------_=_NextPart_003_01C1BEE3.5F4007D0 Content-Type: text/plain A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Messaging profile for telephone-based Messaging clients Author(s) : G. Vaudreuil Filename : draft-vaudreuil-um-issues-00.txt Pages : 12 Date : 21-Feb-02 This document discussed issues and requirements for a profile of the IMAP 4, message submission, and notification protocols for use by telephone user interfaces delivering the traditional voice mail user experience. Experience with IMAP 4 and voice mail systems has shown quite a few limitations that may be addressed by protocol extensions and standardized conventions between clients and servers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-vaudreuil-um-issues-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-vaudreuil-um-issues-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-vaudreuil-um-issues-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_003_01C1BEE3.5F4007D0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable [VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt

A New Internet-Draft is available from the on-line = Internet-Drafts directories.


        Title           : = Messaging profile for telephone-based Messaging
          &nb= sp;           &nb= sp;   clients
        Author(s)       : G. = Vaudreuil
        Filename        : = draft-vaudreuil-um-issues-00.txt
        Pages           : = 12
        Date    =         : 21-Feb-02
       =20
This document discussed issues and requirements for = a profile of the
IMAP 4, message submission, and notification = protocols for use by
telephone user interfaces delivering the traditional = voice mail user
experience.  Experience with IMAP 4 and voice = mail systems has shown
quite a few limitations that may be addressed by = protocol extensions and
standardized conventions between clients and = servers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vaudreuil-um= -issues-00.txt

To remove yourself from the IETF Announcement list, = send a message to
ietf-announce-request with the word unsubscribe in = the body of the message.

Internet-Drafts are also available by anonymous FTP. = Login with the username
"anonymous" and a password of your e-mail = address. After logging in,
type "cd internet-drafts" and then
        "get = draft-vaudreuil-um-issues-00.txt".

A list of Internet-Drafts directories can be found = in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by = e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-vaudreuil-um-issues-00.txt".
       =20
NOTE:   The mail server at ietf.org can = return the document in
        MIME-encoded form by using the "mpack" = utility.  To use this
        feature, = insert the command "ENCODING mime" before the = "FILE"
        command.  To decode the response(s), you will need = "munpack" or
        a = MIME-compliant mail reader.  Different MIME-compliant mail = readers
        exhibit = different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have = been split
        up into = multiple messages), so check your local documentation on
        how to = manipulate these messages.
        =        =20
        =        =20
Below is the data which will enable a MIME compliant = mail reader
implementation to automatically retrieve the ASCII = version of the
Internet-Draft.

  ------_=_NextPart_003_01C1BEE3.5F4007D0-- ------_=_NextPart_002_01C1BEE3.5F4007D0 Content-Type: message/rfc822 To: Subject: Date: Mon, 25 Feb 2002 06:19:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_004_01C1BEE3.5F4007D0" ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_005_01C1BEE3.5F4007D0" ------_=_NextPart_005_01C1BEE3.5F4007D0 Content-Type: text/plain ------_=_NextPart_005_01C1BEE3.5F4007D0 Content-Type: text/html

  ------_=_NextPart_005_01C1BEE3.5F4007D0-- ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: application/octet-stream; name="ATT49682" Content-Disposition: attachment; filename="ATT49682" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020221155809.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-vaudreuil-um-issues-00.txt ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: message/external-body; site="internet-drafts"; dir="draft-vaudreuil-um-issues-00"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_004_01C1BEE3.5F4007D0-- ------_=_NextPart_002_01C1BEE3.5F4007D0-- ------_=_NextPart_000_01C1BEE3.5F4007D0 Content-Type: message/rfc822 Message-ID: <200202221120.GAA27119@ietf.org> From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org To: Cc: vpim@lists.neystadt.org, ietf-imapext@imc.org Subject: [VPIM] I-D ACTION:draft-burger-um-reqts-00.txt Date: Fri, 22 Feb 2002 06:20:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C1BEE3.5F4007D0" ------_=_NextPart_002_01C1BEE3.5F4007D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_003_01C1BEE3.5F4007D0" ------_=_NextPart_003_01C1BEE3.5F4007D0 Content-Type: text/plain A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Internet Unified Messaging Requirements Author(s) : E. Burger Filename : draft-burger-um-reqts-00.txt Pages : 6 Date : 21-Feb-02 Internet Unified Messaging brings together the body of work done in VPIM, FPIM, IMAPEXT, and other IETF work groups. The goal is to provide a single infrastructure, mailbox, and set of interfaces for a user to get, respond to, and manipulate all of their messages, no matter what the media or source. This document describes the requirements for providing such a service. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-burger-um-reqts-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-burger-um-reqts-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-burger-um-reqts-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_003_01C1BEE3.5F4007D0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable [VPIM] I-D ACTION:draft-burger-um-reqts-00.txt

A New Internet-Draft is available from the on-line = Internet-Drafts directories.


        Title           : = Internet Unified Messaging Requirements
        Author(s)       : E. = Burger
        Filename        : = draft-burger-um-reqts-00.txt
        Pages           : = 6
        Date    =         : 21-Feb-02
       =20
Internet Unified Messaging brings together the body = of work done in
VPIM, FPIM, IMAPEXT, and other IETF work = groups.  The goal is to
provide a single infrastructure, mailbox, and set of = interfaces for
a user to get, respond to, and manipulate all of = their messages, no
matter what the media or source.  This document = describes the
requirements for providing such a service.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-burger-um-re= qts-00.txt

To remove yourself from the IETF Announcement list, = send a message to
ietf-announce-request with the word unsubscribe in = the body of the message.

Internet-Drafts are also available by anonymous FTP. = Login with the username
"anonymous" and a password of your e-mail = address. After logging in,
type "cd internet-drafts" and then
        "get = draft-burger-um-reqts-00.txt".

A list of Internet-Drafts directories can be found = in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by = e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-burger-um-reqts-00.txt".
       =20
NOTE:   The mail server at ietf.org can = return the document in
        MIME-encoded form by using the "mpack" = utility.  To use this
        feature, = insert the command "ENCODING mime" before the = "FILE"
        command.  To decode the response(s), you will need = "munpack" or
        a = MIME-compliant mail reader.  Different MIME-compliant mail = readers
        exhibit = different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have = been split
        up into = multiple messages), so check your local documentation on
        how to = manipulate these messages.
        =        =20
        =        =20
Below is the data which will enable a MIME compliant = mail reader
implementation to automatically retrieve the ASCII = version of the
Internet-Draft.

  ------_=_NextPart_003_01C1BEE3.5F4007D0-- ------_=_NextPart_002_01C1BEE3.5F4007D0 Content-Type: message/rfc822 To: Subject: Date: Mon, 25 Feb 2002 06:19:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_004_01C1BEE3.5F4007D0" ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_005_01C1BEE3.5F4007D0" ------_=_NextPart_005_01C1BEE3.5F4007D0 Content-Type: text/plain ------_=_NextPart_005_01C1BEE3.5F4007D0 Content-Type: text/html

  ------_=_NextPart_005_01C1BEE3.5F4007D0-- ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: application/octet-stream; name="ATT88278" Content-Disposition: attachment; filename="ATT88278" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20020221154736.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-burger-um-reqts-00.txt ------_=_NextPart_004_01C1BEE3.5F4007D0 Content-Type: message/external-body; site="internet-drafts"; dir="draft-burger-um-reqts-00"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_004_01C1BEE3.5F4007D0-- ------_=_NextPart_002_01C1BEE3.5F4007D0-- ------_=_NextPart_000_01C1BEE3.5F4007D0-- From owner-um@snowshore.com Wed Feb 27 03:04:42 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1R84gD15647 for um-outgoing; Wed, 27 Feb 2002 03:04:42 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1R84fB15639 for ; Wed, 27 Feb 2002 03:04:41 -0500 (EST) Received: from eburger (ANice-102-2-1-235.abo.wanadoo.fr [193.252.60.235]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id AAA02349; Wed, 27 Feb 2002 00:04:37 -0800 (PST) Reply-To: From: "Eric Burger" To: "Jonathan Rosenberg" Cc: "Robert Sparks" , "IETF UM" Subject: IM and UM Date: Wed, 27 Feb 2002 03:04:25 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <3C7C58E3.67633445@dynamicsoft.com> Sender: owner-um@snowshore.com Precedence: bulk Honestly, IM wasn't on the radar screen. There has been a lot of thought on the notification side, like Rohan's work on SIP-mwi and Noam's work on SNAP. Are you're thinking of a short message store in the case of a person sending an off-line IM? If so, no, we haven't thought about it and yes, we really should. -----Original Message----- From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] Sent: Tuesday, February 26, 2002 10:56 PM To: Eric Burger; Robert Sparks Subject: [Fwd: I-D ACTION:draft-burger-um-reqts-00.txt] Eric, This is very timely. We need a solution for fetching and management of IM as well. Having a unified solution for it all would be excellent. I hope IM requirements can be considered too. Where is this being discussed? Is there a bof or something? Are there protocol proposals? [snip] From owner-um@snowshore.com Wed Feb 27 03:14:51 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1R8Eoe19619 for um-outgoing; Wed, 27 Feb 2002 03:14:50 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1R8EmB19603 for ; Wed, 27 Feb 2002 03:14:48 -0500 (EST) Received: from eburger (ANice-102-2-1-235.abo.wanadoo.fr [193.252.60.235]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id AAA02749; Wed, 27 Feb 2002 00:14:44 -0800 (PST) Reply-To: From: "Eric Burger" To: "Jonathan Rosenberg" Cc: "Robert Sparks" , "IETF UM" Subject: Goals & Infrastructure Date: Wed, 27 Feb 2002 03:14:32 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <3C7C58E3.67633445@dynamicsoft.com> Sender: owner-um@snowshore.com Precedence: bulk It's not so much that clients and servers should not change, it's more that the UM framework must be backwards compatible with RFC [2]822 and all of the existing infrastructure. The approach is the same one I promoted for IVM: UM-aware clients and servers understand UM semantics. Non-UM-aware clients and servers can participate in a UM interaction, but they may either lose the UM semantics or not understand the UM semantics. Part of the work for UM is to characterize the scenarios. -----Original Message----- From: Jonathan Rosenberg [mailto:jdrosen@dynamicsoft.com] Sent: Tuesday, February 26, 2002 10:56 PM To: Eric Burger; Robert Sparks Subject: [Fwd: I-D ACTION:draft-burger-um-reqts-00.txt] [snip] Also, the requirements confused me a little; it seemed to say that clients and servers should not change. OK, if nothing changes, what are you doing differently? [snip] From owner-um@snowshore.com Wed Feb 27 18:23:31 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1RNNVt21552 for um-outgoing; Wed, 27 Feb 2002 18:23:31 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from mail3.notes.ricoh.co.jp (mail3.notes.ricoh.co.jp [202.211.49.20]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1RNNSB21548 for ; Wed, 27 Feb 2002 18:23:29 -0500 (EST) Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@azteca [133.139.250.74]) by mail3.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA21622; Thu, 28 Feb 2002 08:22:15 +0900 (JST) Received: from lily.toda.ricoh.co.jp (lily.toda.ricoh.co.jp [133.139.60.72]) by azteca.isd.ricoh.co.jp (Mirapoint) with ESMTP id ACH31976; Thu, 28 Feb 2002 08:22:14 +0900 (JST) Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by lily.toda.ricoh.co.jp (8.9.1/3.7Wlily sendmail.cf v8) with ESMTP id IAA03843; Thu, 28 Feb 2002 08:19:36 +0900 (JST) To: gparsons@nortelnetworks.com Cc: ietf-fax@imc.org, vpim@lists.neystadt.org, um@snowshore.com Subject: Re: ID-ACTIONs on UM In-Reply-To: References: X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20020228082413K.tamura@toda.ricoh.co.jp> Date: Thu, 28 Feb 2002 08:24:13 +0900 (JST) From: Hiroshi Tamura X-Dispatcher: imput version 20000228(IM140) Lines: 29 Sender: owner-um@snowshore.com Precedence: bulk Glenn, Thanks for your suggestion. > These drafts discuss some general unified messaging (UM) client issues that > I think would be worth discussing at both the FAX and VPIM WGs. Yes. > After some discussion, I suggest we need to decide between the following: > a) create a new BOF/WG to work on UM > b) recharter VPIM and/or FAX to work on this > c) close and combine VPIM and FAX into a new UM WG to work on this and > remaining VPIM/FAX topics One idea, I think. Anyway, the time for this topic is necessary at FAX WG meeting. I think we can arrange 10-20 minutes. > <<[VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt>> <<[VPIM] I-D > ACTION:draft-burger-um-reqts-00.txt>> Regards, -- Hiroshi Tamura, Co-chair of IETF-FAX WG E-mail: tamura@toda.ricoh.co.jp - This list is maintained by Snowshore Networks - http://www.snowshore.com All comments on this list are the comments of the message originators and Snowshore is not to be held responsible for any actions or comments found on this list. The archives for this list can be found at http://flyingfox.snowshore.com/um_archive/maillist.html From owner-um@snowshore.com Thu Feb 28 15:58:48 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1SKwm109726 for um-outgoing; Thu, 28 Feb 2002 15:58:48 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1SKwlB09722 for ; Thu, 28 Feb 2002 15:58:47 -0500 (EST) Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15]) by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id g1SKwfh18316; Thu, 28 Feb 2002 12:58:41 -0800 (PST) Received: from DWINGW2K (dhcp-128-107-139-147.cisco.com [128.107.139.147]) by mira-sjcm-3.cisco.com (Mirapoint) with SMTP id ADV74617; Thu, 28 Feb 2002 12:48:24 -0800 (PST) From: "Dan Wing" To: "Glenn Parsons" , Cc: "IETF VPIM List" , Subject: RE: ID-ACTIONs on UM Date: Thu, 28 Feb 2002 12:58:40 -0800 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0553_01C1C057.A4F657A0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-um@snowshore.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0553_01C1C057.A4F657A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit ID-ACTIONs on UMI have long thought (c) would be best. I think the application area directors would also prefer (c), as it reduces the number of working groups. -d -----Original Message----- From: owner-ietf-fax@mail.imc.org [mailto:owner-ietf-fax@mail.imc.org]On Behalf Of Glenn Parsons Sent: Tuesday, February 26, 2002 8:34 AM To: ietf-fax@imc.org Cc: IETF VPIM List; um@snowshore.com Subject: ID-ACTIONs on UM Folks, These drafts discuss some general unified messaging (UM) client issues that I think would be worth discussing at both the FAX and VPIM WGs. After some discussion, I suggest we need to decide between the following: a) create a new BOF/WG to work on UM b) recharter VPIM and/or FAX to work on this c) close and combine VPIM and FAX into a new UM WG to work on this and remaining VPIM/FAX topics Cheers, Glenn Parsons VPIM WG Chair <<[VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt>> <<[VPIM] I-D ACTION:draft-burger-um-reqts-00.txt>> ------=_NextPart_000_0553_01C1C057.A4F657A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ID-ACTIONs on UM

I = have long=20 thought (c) would be best.  I think the application area directors = would=20 also prefer (c), as it reduces the number of working = groups.
 
-d
-----Original Message-----
From: = owner-ietf-fax@mail.imc.org=20 [mailto:owner-ietf-fax@mail.imc.org]On Behalf Of Glenn=20 Parsons
Sent: Tuesday, February 26, 2002 8:34 = AM
To:=20 ietf-fax@imc.org
Cc: IETF VPIM List;=20 um@snowshore.com
Subject: ID-ACTIONs on = UM

Folks,

These drafts discuss some general = unified=20 messaging (UM) client issues that I think would be worth discussing at = both=20 the FAX and VPIM WGs.

After some discussion, I suggest we = need to decide=20 between the following:
a) = create a new=20 BOF/WG to work on UM
b) = recharter VPIM=20 and/or FAX to work on this
c) = close and=20 combine VPIM and FAX into a new UM WG to work on this and remaining = VPIM/FAX=20 topics

Cheers,
Glenn=20 Parsons
VPIM WG Chair =

 =20 <<[VPIM] I-D ACTION:draft-vaudreuil-um-issues-00.txt>>=20 <<[VPIM] I-D=20 ACTION:draft-burger-um-reqts-00.txt>>=20

------=_NextPart_000_0553_01C1C057.A4F657A0-- - This list is maintained by Snowshore Networks - http://www.snowshore.com All comments on this list are the comments of the message originators and Snowshore is not to be held responsible for any actions or comments found on this list. The archives for this list can be found at http://flyingfox.snowshore.com/um_archive/maillist.html From owner-um@snowshore.com Thu Feb 28 18:53:16 2002 Received: (from majordomo@localhost) by flyingfox.snowshore.com (8.11.2/8.11.2) id g1SNrG412942 for um-outgoing; Thu, 28 Feb 2002 18:53:16 -0500 (EST) X-Authentication-Warning: flyingfox.snowshore.com: majordomo set sender to owner-um@mail.snowshore.com using -f Received: from duck.mail.pas.earthlink.net (duck.mail.pas.earthlink.net [207.217.121.117]) by flyingfox.snowshore.com (8.11.2/8.11.2) with ESMTP id g1SNrEB12935 for ; Thu, 28 Feb 2002 18:53:14 -0500 (EST) Received: from eburger (ANice-102-2-1-235.abo.wanadoo.fr [193.252.60.235]) by duck.mail.pas.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA19230; Thu, 28 Feb 2002 15:53:11 -0800 (PST) Reply-To: From: "Eric Burger" To: , "IETF UM" , Subject: FW: [VPIM] I-D ACTION:draft-burger-imap-chanuse-00.txt Date: Thu, 28 Feb 2002 18:52:58 -0500 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0091_01C1C089.23B60AF0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-um@snowshore.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0091_01C1C089.23B60AF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit This draft may be of interest to your groups. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IMAP CHANNEL Use Cases Author(s) : E. Burger Filename : draft-burger-imap-chanuse-00.txt Pages : 7 Date : 27-Feb-02 This document describes different use cases for using the IMAP CHANNEL facility. Discussion of this and related drafts are on the IMAP Voice list. To subscribe, send the message 'subscribe' to ietf-imap-voice-request@imc.org . A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-burger-imap-chanuse-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-burger-imap-chanuse-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-burger-imap-chanuse-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------=_NextPart_000_0091_01C1C089.23B60AF0 Content-Type: Message/External-body; name="ATT00004.dat" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="ATT00004.dat" Content-Type: text/plain Content-ID: <20020227125026.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-burger-imap-chanuse-00.txt ------=_NextPart_000_0091_01C1C089.23B60AF0 Content-Type: Message/External-body; name="draft-burger-imap-chanuse-00.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="draft-burger-imap-chanuse-00.txt" Content-Type: text/plain Content-ID: <20020227125026.I-D@ietf.org> ------=_NextPart_000_0091_01C1C089.23B60AF0-- - This list is maintained by Snowshore Networks - http://www.snowshore.com All comments on this list are the comments of the message originators and Snowshore is not to be held responsible for any actions or comments found on this list. The archives for this list can be found at http://flyingfox.snowshore.com/um_archive/maillist.html