Re: [apps-discuss] APPSDIR review of draft-ietf-simple-chat-13

Ben Campbell <ben@nostrum.com> Tue, 07 February 2012 20:11 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC05121F855F; Tue, 7 Feb 2012 12:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8iy1UsJ8xf7f; Tue, 7 Feb 2012 12:11:12 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 272F221F84F2; Tue, 7 Feb 2012 12:11:11 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q17KB7Ze001803 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 7 Feb 2012 14:11:07 -0600 (CST) (envelope-from ben@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="iso-8859-1"
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <4F313153.8050806@ericsson.com>
Date: Tue, 07 Feb 2012 14:11:09 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B570C27E-ABB6-4357-8CA8-7C893BC54BCA@nostrum.com>
References: <4F2FA266.8040406@telecomitalia.it> <4F313153.8050806@ericsson.com>
To: "Miguel A. Garcia" <Miguel.A.Garcia@ericsson.com>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>, IESG <iesg@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-simple-chat-13
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2012 20:11:19 -0000

On Feb 7, 2012, at 8:12 AM, Miguel A. Garcia wrote:

>> In Section 7.1:
>> 
>>     The reservation of a nickname can fail, e.g. if the NICKNAME request
>>     contains a malformed or non-existent Use-Nickname header field, or
>>     if the same nickname has already been reserved by another
>>     participant (i.e., by another URI) in the chat room.  The
>>     validation can also fail where the sender of the message is not
>>     entitled to reserve the nickname.  In any of these cases the MSRP
>>     switch MUST answer the NICKNAME request with a 423 response.  The
>>     semantics of the 423 response are: "Nickname usage failed; the
>>     nickname is not allocated to this user".
>> 
>> It would be better to use different response codes for different error
>> conditions.
> 
> I also sympathize your proposal. We had this for avoiding creating very detailed error conditions. But I wouldn't mind to differentiate both error cases. Perhaps we should take this to the WG for comments.

I agree that if we think we need to allocate additional error codes, we should run that by the work group. Miguel, can you send a note to the SIMPLE list on that?

Thanks!

Ben.