[lemonade] Comments on draft-ietf-lemonade-catenate-05.txt

Randall Gellens <randy@qualcomm.com> Wed, 27 July 2005 01:57 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxbAc-0006kR-4K; Tue, 26 Jul 2005 21:57:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxbAa-0006kE-Ja; Tue, 26 Jul 2005 21:57:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11643; Tue, 26 Jul 2005 21:57:14 -0400 (EDT)
Received: from warlock.qualcomm.com ([129.46.50.49]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dxbfj-0001Sz-0c; Tue, 26 Jul 2005 22:29:29 -0400
Received: from [192.168.1.13] (vpn-10-50-0-131.qualcomm.com [10.50.0.131]) by warlock.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id j6R1utoZ002743; Tue, 26 Jul 2005 18:56:56 -0700 (PDT)
Mime-Version: 1.0
Message-Id: <p07000c1dbf0c94eddef2@[192.168.1.13]>
X-Mailer: Eudora for Mac OS X v7.0a
X-message-flag: Using Outlook? Upgrade to Eudora: <http://www.eudora.com>
Date: Tue, 26 Jul 2005 18:51:39 -0700
To: iesg@ietf.org, presnick@qualcomm.com
From: Randall Gellens <randy@qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Lemonade <lemonade@ietf.org>
Subject: [lemonade] Comments on draft-ietf-lemonade-catenate-05.txt
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

In Section 4 (Response Codes), do we really mean "may return a 
response code"?  I think "SHOULD return a response code" would be 
better, but in any case it is not clear if "may" is intended to be 
normative.

In Section 4.1 (BADURL Response), it is not clear if "invalid" means 
syntactically or semantically regarding UIDs and body parts.  That 
is, is this response code to be used if the syntax is bad or if the 
referenced item does not exist?

in Section 4.2 (TOOBIG Response), "The server may also wish to 
return" perhaps would be more clear written normatively, as "The 
server MAY return".

Also, in the super nit-pick category, line 190 has "e.g." which 
should be "e.g.," (it needs a comma).
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly-selected tag: ---------------
To die for an idea is unquestionably noble. But how much nobler it
would be if men died for ideas that were true!
    --H.L. Mencken

_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade