[Stox] Barry Leiba's comments on draft-ietf-stox-groupchat

Peter Saint-Andre - &yet <peter@andyet.net> Thu, 05 March 2015 17:36 UTC

Return-Path: <peter@andyet.net>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC8C1A1BA7 for <stox@ietfa.amsl.com>; Thu, 5 Mar 2015 09:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWM3Y7mI4JaF for <stox@ietfa.amsl.com>; Thu, 5 Mar 2015 09:36:01 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 020A01A0146 for <stox@ietf.org>; Thu, 5 Mar 2015 09:36:01 -0800 (PST)
Received: by iecvy18 with SMTP id vy18so14407618iec.9 for <stox@ietf.org>; Thu, 05 Mar 2015 09:36:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=e26SEBiGMvzZGpTEVxDGyo/OAlIuLwcZv2u+hvdVGms=; b=kBJyrzivJ0oRaZsMiWIA5K8WrVtZyEDmQLslRTBcfMLj7Y7W7hyhwQwb6GZ7A2B4u0 0YQd89cX7RaEWtLFrt8sS9nMxNaf6r/ruy0KFgJeD47E7mqS3JSHQcrbhV5DIH+lavtk LlFfQfHCtTKCPQacpQZSn3z089uZucHCSZjbFjHUhabpJxzyr86QFCYw7zw5goVL/ufZ OgeWEkmMEdW1fDc40l8rnj44U1ihlLphbIV8DPD3c7j71tdgs6LbPCZBMkJwZ/W2Ciee 8eWnOaICaHVT4HNns3k3KBt1byekCic9FQY1vVAfbTQ79irpKYHz2KgNYE86NpXxSOWA dHZQ==
X-Gm-Message-State: ALoCoQk0i4aVsFcNQtC/dmDwoHvInPGmgG8QUWIzklyWfsY231xdubqwq14rTS88om73JFYgzClE
X-Received: by 10.42.37.144 with SMTP id y16mr4915210icd.51.1425576960454; Thu, 05 Mar 2015 09:36:00 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id y142sm5364401iod.25.2015.03.05.09.35.59 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Mar 2015 09:35:59 -0800 (PST)
Message-ID: <54F893FF.1060901@andyet.net>
Date: Thu, 05 Mar 2015 10:35:59 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>, "stox@ietf.org" <stox@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/stox/vKb7E-hojvA2SUPIUssUJUOzAOc>
Subject: [Stox] Barry Leiba's comments on draft-ietf-stox-groupchat
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2015 17:36:02 -0000

My apologies for missing the IESG feedback on draft-ietf-stox-groupchat 
(it seems that email notifications were not set up for that I-D as they 
were for the others).

For WG participants, you can find the comments here:

https://datatracker.ietf.org/doc/draft-ietf-stox-groupchat/ballot/

Barry Leiba wrote:

    -- Section 5.5.2 --

       The XMPP message type ought to
       be "chat" (and is not allowed to be "groupchat").

    I think this is fine, but because of your careful and measured use
    of 2119 throughout the document set, I wonder how this is meant to
    be different from 'and MUST NOT be "groupchat"'?

Those guidelines come from XEP-0045, so repeating the normative keywords 
from there seems ill-advised.

    -- Section 5.8 --

    I suggest:

    OLD
       |    <status>Time to go!</status>

    NEW
       |    <status>O, look! methinks I see my cousin's ghost</status>

Sure. You're really getting into the Shakespearean spirit, eh?

    -- Section 10 --

    My comment in stox-chat applies here, as well, though I note that
    in this case you do not already have a reference to stox-im to work
    with.

Right - there's no established method for encryption of multi-party 
messaging (that problem is even harder than one-to-one messaging).

Peter

-- 
Peter Saint-Andre
https://andyet.com/