--On Wednesday, 29 January, 2003 20:20 -0500 Thomas Narten
<[EMAIL PROTECTED]> wrote:
...
As one of the authors of RFC 2434 "Guidelines for Writing an
IANA Considerations Section in RFCs", I have long regretted
defining the term "IETF Consensus" as it is in that document.
2434 says:
IET
"Spencer Dawkins" <[EMAIL PROTECTED]> wrote:
> David, you're a genius!
Thanks. Can I use you for a reference? B-) (See signature.)
> Glenn Parson told me he was VERY proud of the LEMONADE acronymn,
Yes, and now that I've gone and looked up what it is and all that (hey, I was
away from IETF
RJ Atkinson <[EMAIL PROTECTED]> writes:
> On Thursday, Jan 23, 2003, at 17:54 America/Montreal, Bob Braden wrote:
> > I interpret "IETF consensus" as meaning that at least a Last
> > Call was conducted. To use any other interpretation seems to me to
> > be dishonest. I guess I am agreeing with K
--On Wednesday, 29 January, 2003 13:06 -0800
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
I agree. And unfortunately, I think this is due to a serious
problem about which I'm quite distressed:
The proposed charter contained in the announcement is *not*
the proposed charter worked out on th
"Spencer Dawkins" <[EMAIL PROTECTED]> writes:
> what's an obvious name for a working group PRUNING IMAP4?
>
> "minIMAP4rev1"? "IMAP4rev1minus"?...
MAPLET -- Message Access Protocol Limited to Efficient Tasks?
--
David J. Aronson, Software Engineer for hire in Washington DC area.
See http://dja
> I agree. And unfortunately, I think this is due to a serious problem
> about which I'm quite distressed:
> The proposed charter contained in the announcement is *not* the
> proposed charter worked out on the LEMONADE BOF mailing list. Not
> even close. The one on the list went through several re
Hi, Pete,
I've been looking at the BOF announcements for LEMONADE previously,
and this wasn't the impression I had, at all. Thank you for clarifying.
The clarification makes it more obvious this may be the right thing to do.
But...
If this proposed working group is, indeed, trimming down IMAP4 (
John and I are in a great deal more agreement that I first suspected.
On 1/29/03 at 3:06 PM -0500, John C Klensin wrote:
But, Pete, for reasons you presumably understand, "profiles" (note
plural) gives me as much anxiety as "lets add lots more excrement to
this protocol".
Yes, if the result o
--On Wednesday, 29 January, 2003 13:28 -0600 Pete Resnick
<[EMAIL PROTECTED]> wrote:
On 1/29/03 at 1:40 PM -0500, John C Klensin wrote:
Now we have a WG proposal which seems to have a major theme
of adding more capabilities and options to IMAP
Before everyone ends up latching onto this: You
On 1/29/03 at 1:40 PM -0500, John C Klensin wrote:
Now we have a WG proposal which seems to have a major theme of
adding more capabilities and options to IMAP
Before everyone ends up latching onto this: You quite conveniently
ignore something very important in the first statement of purpose in
On 1/29/03 at 6:13 PM +0700, Robert Elz wrote:
A new IETF working group has been proposed in the Applications Area.
[...]
Enhancements to Internet email to support diverse service
environments (lemonade)
[...]
2. Enhance the existing IMAP4 message retrieval protocol to
satisfy the requireme
--On Tuesday, 28 January, 2003 18:12 -0500 Jacqueline Hargest
<[EMAIL PROTECTED]> wrote:
A new IETF working group has been proposed in the Applications
Area. The IESG has not made any determination as yet.
The following description was submitted, and is provided for
informational purposes only.
and I forgot
the archives are at
http://eikenes.alvestrand.no/pipermail/problem-statement/
--On 24. januar 2003 20:30 +0100 Harald Tveit Alvestrand
<[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] - use the "-request" convention to
subscribe.
This list was set up in conjunction with the IESG pl
Date:Tue, 28 Jan 2003 18:12:05 -0500
From:Jacqueline Hargest <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| A new IETF working group has been proposed in the Applications Area.
[...]
| Enhancements to Internet email to support diverse service environments
14 matches
Mail list logo
