John C Klensin | 17 Jul 2012 16:17

Comprehensive WG LC review of draft-ietf-eai-5738bis-06 (IMAP)

Hi.  Review attached as promised.

The funky numbering is due to this having been mostly complete
on -04.  There might still be some residual issues from it.

Martin raised the question of whether the titles of these
documents are really what we want.  This is just about the last
chance if anyone has strong feelings and specific suggestions.

    best,
     john
draft-ietf-eai-5738bis-06

(1) Introduction, paragraph 1

Nit: Extra space after "[RFC6532]" and before "." in the first
sentence. 

I believe that the Introduction would be improved by starting
it with a paragraph very similar to the first paragraph of the
introduction to draft-ietf-eai-rfc5721bis (ideally as
modified in response to this set of comments).

(1a) Introduction, paragraph 3

I believe this is sufficient, but someone is almost certain to
want a complete discussion about differences from 5738.  We
should prepare for a small snit about refusing.  I note that
(Continue reading)

Martin J. Dürst | 18 Jul 2012 06:50
Picon
Gravatar

Re: Comprehensive WG LC review of draft-ietf-eai-5738bis-06 (IMAP)

Very small nit:

On 2012/07/17 23:17, John C Klensin wrote:
> Hi.  Review attached as promised.

 > (10) Section 7, last paragraph  (editorial nit)
 >
 > Old:
 > 	impossible, at least at the time,
 > New:
 > 	impossible, at least at the present time,

I suggest "impossible, at least at the time of writing[/publication] of 
this specification".

Otherwise, the spec reads strange in a few years.

Regards,   Martin.
John C Klensin | 18 Jul 2012 11:41

Re: Comprehensive WG LC review of draft-ietf-eai-5738bis-06 (IMAP)

Definitely better.
thanks,
   john

--On Wednesday, July 18, 2012 13:50 +0900 "\"Martin J. Dürst\""
<duerst <at> it.aoyama.ac.jp> wrote:

> Very small nit:
> 
> On 2012/07/17 23:17, John C Klensin wrote:
>> Hi.  Review attached as promised.
> 
>  > (10) Section 7, last paragraph  (editorial nit)
>  >
>  > Old:
>  > 	impossible, at least at the time,
>  > New:
>  > 	impossible, at least at the present time,
> 
> I suggest "impossible, at least at the time of
> writing[/publication] of this specification".
> 
> Otherwise, the spec reads strange in a few years.
> 
> Regards,   Martin.

_______________________________________________
IMA mailing list
IMA <at> ietf.org
https://www.ietf.org/mailman/listinfo/ima
(Continue reading)


Gmane