Re: [Anima-signaling] Two definite proposals for GRASP protocol change

Carsten Bormann <cabo@tzi.org> Sun, 10 January 2016 19:57 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: anima-signaling@ietfa.amsl.com
Delivered-To: anima-signaling@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876031ACEFE for <anima-signaling@ietfa.amsl.com>; Sun, 10 Jan 2016 11:57:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 m-4U7RwfEDnM for <anima-signaling@ietfa.amsl.com>; Sun, 10 Jan 2016 11:57:34 -0800 (PST)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 984641ACEFD for <anima-signaling@ietf.org>; Sun, 10 Jan 2016 11:57:34 -0800 (PST)
Received: from mfilter33-d.gandi.net (mfilter33-d.gandi.net [217.70.178.164]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id F3AA441C080; Sun, 10 Jan 2016 20:57:32 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter33-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter33-d.gandi.net (mfilter33-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id ZJM8nIRrhrms; Sun, 10 Jan 2016 20:57:31 +0100 (CET)
X-Originating-IP: 93.199.254.229
Received: from nar.local (p5DC7FEE5.dip0.t-ipconnect.de [93.199.254.229]) (Authenticated sender: cabo@cabo.im) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id E237941C087; Sun, 10 Jan 2016 20:57:30 +0100 (CET)
Message-ID: <5692B7AF.4010802@tzi.org>
Date: Sun, 10 Jan 2016 20:57:35 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <5668F8CA.2010205@gmail.com> <56698A77.5090003@tzi.org> <5669911D.30306@tzi.org> <5669DC59.2090505@gmail.com> <56925EBC.6010207@tzi.org> <5692A875.203@gmail.com>
In-Reply-To: <5692A875.203@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima-signaling/_6S093dFsQf1eqwDqhuaDXdkV_I>
Cc: Anima signaling DT <anima-signaling@ietf.org>
Subject: Re: [Anima-signaling] Two definite proposals for GRASP protocol change
X-BeenThere: anima-signaling@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Mailing list for the signaling design team of the ANIMA WG <anima-signaling.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-signaling/>
List-Post: <mailto:anima-signaling@ietf.org>
List-Help: <mailto:anima-signaling-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Jan 2016 19:57:36 -0000

> You are correct. That general pattern is not in the definitive CDDL
> in Section 6 "CDDL Specification of GRASP". I was just looking for a
> way to express the general form of the messages. Would it be better to
> just say it in words at this point, without using pseudo-CDDL?

The (not so pseudo) CDDL is fine.
Actually, the CDDL authors added the ".within" annotation to be able to
combine a statement giving a coarse overall structure formally with the
detailed specification.  (Something that would really solve a number of
problems with the way ABNF is used, by the way.)

>> Editorially, I'm not sure I have said that, but I'm not a big fan of the
>> non-parsable ("fragmentary") pieces of CDDL in the CDDL fragments.
>> They make it a bit harder to extract all the fragments and check
>> automatically whether they are consistent with the overall structure in
>> section 6.  (They also make we want to quibble over the exact
>> fragmentary syntax to be used.)  Instead of
>>
>>      initiator /=   ; defined below
>>      objective /=   ; defined below
>>
>> how about:
>>      ; initiator and objective are defined below
>>
>> (But then, saying four times that initiator and six times that objective
>> is defined below doesn't make a lot of sense either.)
>>
>> All this is more in the sense of food for thought than in the sense of
>> "Houston, we have a problem".
> 
> I certainly don't have a closed mind on that. However, it would be a bit
> annoying for the reader to be told many times "Please refer to section 6
> for the detailed format." Maybe we should see what the WG thinks.

I don't have a problem with fragments in the text -- in fact, the COSE
group just had extensive deliberations about using those and arrived at
a very good consensus for having the in-line fragments.  I just want to
make sure they do parse, so they can be checked automatically against
the collected specification.  (I'm also not a big fan of restating the
obvious, when that really is likely to be obvious to the reader at this
point.)

>> I had to add three lines of code to the relay function to do this.
>> So I now propose to remove the 'initiator' field from the messages where
>> I added it (and add the necessary clarifications about using the source
>> IP address). That will be a straightforward change to the -02D draft
>> that I sent yesterday, so co-authors, please let me know what you think
>> ASAP.

Great!

Grüße, Carsten