RE: draft-nerenberg-imap-binary-00.txt
"Glenn Parsons" <[email protected]> Wed, 22 Nov 2000 16:38:12 -0500
| Newsgroups | gmane.ietf.imap-voice |
|---|---|
| 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. ------_=_NextPart_001_01C054CC.83B8ECD0 Content-Type: text/plain > > > I hadn't realized that you and Steve had been discussing this, > otherwise > > > I would have held off with BINARY for a bit. > > > That's why I was a bit surprised to see your document! :-) > > So was Steve :-) I apologise for starting all this confusion. > So is Steve still planning to do a draft on this :-) > > I like the XFETCH architecture, > > however I'm not convinced (yet) that a server should have to implement > > external channel support just to get BINARY. At this point I think the > > two are really distinct issues, and should be separate extensions. > > OK with me. > The other VPIM requirements from the expired draft-ema-vpim-imap-01.txt (but still on www.vpim.org) are: This document is an overview of proposals for various extensions to IMAP to meet the requirements of voice mail systems. The topics included are - Binary Attachment transfer - External Reference - Alternate Codec Request - Streaming audio attachments - Message length Indicator - Body part read indicator Steve indicated to me last week that he would combine the first two into one proposal. Do we expect two proposals now? Thanks, Glenn. ------_=_NextPart_001_01C054CC.83B8ECD0 Content-Type: text/html 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=3Dus-ascii"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2652.35"> <TITLE>RE: draft-nerenberg-imap-binary-00.txt</TITLE> </HEAD> <BODY> <BR> <UL> <P><FONT SIZE=3D2 FACE=3D"Monaco">> > I hadn't realized that you = and Steve had been discussing this, otherwise</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">> > I would have held off with = BINARY for a bit.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">> That's why I was a bit surprised = to see your document! :-)</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">So was Steve :-) I apologise = for starting all this confusion.</FONT> </P> </UL> <P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">So is Steve still planning to = do a draft on this :-)</FONT> </P> <UL> <P><FONT SIZE=3D2 FACE=3D"Monaco">> I like the XFETCH = architecture,</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">> however I'm not convinced (yet) = that a server should have to implement</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">> external channel support just = to get BINARY. At this point I think the</FONT> <BR><FONT SIZE=3D2 FACE=3D"Monaco">> two are really distinct issues, = and should be separate extensions.</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Monaco">OK with me.</FONT> </P> </UL> <P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">The other VPIM requirements = from the expired draft-ema-vpim-imap-01.txt (but still on www.vpim.org) = are:</FONT> </P> <UL> <P><FONT FACE=3D"Arial"> This document is an overview = of proposals for various extensions to =0D IMAP = to meet the requirements of voice mail systems. The topics = =0D included are =0D - = Binary Attachment transfer=0D - External = Reference =0D - Alternate Codec = Request=0D - Streaming audio = attachments=0D - Message length = Indicator=0D - Body part read = indicator</FONT></P> </UL> <P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Steve indicated to me last = week that he would combine the first two into one proposal. Do we = expect two proposals now?</FONT> </P> <P><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Thanks,</FONT> <BR><FONT COLOR=3D"#0000FF" FACE=3D"Arial">Glenn.</FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C054CC.83B8ECD0--