RE: Last call on draft-gahrns-imap-referrals-01
"Mike Gahrns (Exchange)" <mikega@exchange.microsoft.com> Tue, 25 March 1997 19:27 UTC
Received: from cnri by ietf.org id ab10410; 25 Mar 97 14:27 EST
Received: from ietf.org by CNRI.Reston.VA.US id aa18102; 25 Mar 97 14:27 EST
Received: from ietf.org by ietf.org id aa10403; 25 Mar 97 14:27 EST
Received: from doggate.microsoft.com by ietf.org id aa10399; 25 Mar 97 14:27 EST
Received: by DOGGATE with Internet Mail Service (5.0.1457.3) id <HM5K49W9>; Tue, 25 Mar 1997 11:24:18 -0800
Message-ID: <0A684133865BCF118F0E08002BE7ADACE1AF76@DABONE>
Sender: iesg-request@ietf.org
From: "Mike Gahrns (Exchange)" <mikega@exchange.microsoft.com>
To: "'Harald Alvestrand (IETF Area Director)'" <Harald.T.Alvestrand@uninett.no>
Cc: 'IESG' <iesg@ietf.org>, "'Keith Moore (IETF Area Director)'" <moore+iesg@cs.utk.edu>
Subject: RE: Last call on draft-gahrns-imap-referrals-01
Date: Tue, 25 Mar 1997 11:24:12 -0800
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain
Hi Harald, I agree with your concern regarding avoiding areas that would need to deal with synchronization between multiple servers, and will definitely avoid that. However, I am was thinking about a less ambitious approach. As in the SELECT of a mailbox case, the referral would be just a hint to the client that it needs to make a connection to another server to access that mailbox. For APPEND I envisioned something like: e.g. C: A001 APPEND mailboxfoo data... S: A001 NO [REFERRAL IMAP://Server2/mailboxfoo] Remote mailbox The client would then need to do a connection to the server2 to append the data. This saves the client from needing to select the folder first before doing the append. COPY would be more difficult for the client. Essentially a tagged NO with a referral would be a hint to the client that it needs to make a connection to another server, and APPEND the data itself, rather than relying on the server to do it. These suggestions have come about as our client team is getting some implementation experience under their belts with this draft. I would like to try to incorporate their ideas/experience if possible. What would your thoughts be, if a subsequent draft, took the less ambitious approach outlined above? P.S. I will be travelling the rest of this week, and may be quite unresponsive on e-mail. Apologies for any delay in getting back to you. thx, -mikega > ---------- > From: > Harald.T.Alvestrand@uninett.no[SMTP:Harald.T.Alvestrand@uninett.no] > Sent: Tuesday, March 25, 1997 2:26 AM > To: Mike Gahrns (Exchange) > Cc: 'IESG'; 'Keith Moore (IETF Area Director)' > Subject: Re: Last call on draft-gahrns-imap-referrals-01 > > Mike, > it seems to me that adding COPY and APPEND to the redirects leads > you into the area where you have to synchronize between multiple > IMAP servers (espec. COPY). > I'm not sure this is a good idea on the first try; would it be better > to issue this Proposed Standard now, and add extensions later? > > Harald A > >
- Last call on draft-gahrns-imap-referrals-01 Mike Gahrns (Exchange)
- Re: Last call on draft-gahrns-imap-referrals-01 Harald.T.Alvestrand
- RE: Last call on draft-gahrns-imap-referrals-01 Mike Gahrns (Exchange)
- Re: Last call on draft-gahrns-imap-referrals-01 Harald.T.Alvestrand
- RE: Last call on draft-gahrns-imap-referrals-01 Mike Gahrns (Exchange)