[Gen-art] Gen-ART review of draft-ietf-simple-chat-13

Christer Holmberg <christer.holmberg@ericsson.com> Sat, 11 February 2012 10:13 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BE221F854B for <gen-art@ietfa.amsl.com>; Sat, 11 Feb 2012 02:13:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.184
X-Spam-Level:
X-Spam-Status: No, score=-9.184 tagged_above=-999 required=5 tests=[AWL=1.415, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 ejJnsVSxrR3W for <gen-art@ietfa.amsl.com>; Sat, 11 Feb 2012 02:13:49 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 2F12A21F8542 for <gen-art@ietf.org>; Sat, 11 Feb 2012 02:13:49 -0800 (PST)
X-AuditID: c1b4fb39-b7bf2ae0000069a1-af-4f363f5bfdec
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 28.64.27041.B5F363F4; Sat, 11 Feb 2012 11:13:48 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.175]) by esessmw0247.eemea.ericsson.se ([153.88.115.93]) with mapi; Sat, 11 Feb 2012 11:13:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "draft-ietf-simple-chat.all@tools.ietf.org" <draft-ietf-simple-chat.all@tools.ietf.org>
Date: Sat, 11 Feb 2012 11:13:47 +0100
Thread-Topic: Gen-ART review of draft-ietf-simple-chat-13
Thread-Index: AQHM6KXXwYnbX7WMyEKD7vOb2ZWL0A==
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D31BA1E@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: [Gen-art] Gen-ART review of draft-ietf-simple-chat-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2012 10:13:50 -0000

I am the assigned Gen-ART reviewer for this draft. For background on 
Gen-ART, please see the FAQ at 
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments 
you may receive.

Document:                  draft-ietf-simple-chat-13
Reviewer:                   Christer Holmberg
Review Date:              12-02.11
IETF LC End Date:     12-02-06
IESG Telechat date: (if known)

Summary:          Ready, but some additional text may be needed based on the minor issues.

Major issues:     None

Minor issues:

- The second paragraph of section 7.1 says that a NICKNAME request MUST contain a Use-Nickname header, but in the sixth paragraph the inclusion is a SHOULD.

- It is not clearly indicated whether the Use-Nickname header is allowed for other methods than NICKNAME.

- Section 8 does not specify whether there are SDP offer/answer considerations/restrictions associated with the new attribute. For example: 
-- Must the attribute tokens in an answer be a subset of the tokens in an offer?
-- Can an SDP answer contain an attribute if the offer didn't?
-- If a user sends a new SDP offer within a session, can the token values be modified? What does it mean if the attribute is not present in a new SDP offer?


Nits/editorial comments:

- Sometimes the document talks about "multi-party chat", "multi-party conference", "conference", and "chat room". Would it be possible to use more consistant terminology?

- Requirements
-- REQ-4: Isn't this requirement already covered by REQ-3?
-- REQ-6: Change "progress" to "duration" or "length".

- There is no definition/reference for "roster".


Regards,

Christer