Re: [MMUSIC] Changes for draft-ietf-mmusic-trickle-ice-sip-14 - ABNF

Thomas Stach <thomass.stach@gmail.com> Wed, 09 May 2018 18:13 UTC

Return-Path: <thomass.stach@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3056E12D940; Wed, 9 May 2018 11:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rcZIGRAPICIA; Wed, 9 May 2018 11:13:31 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 B2F2F126FB3; Wed, 9 May 2018 11:13:30 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id a67-v6so6570wmf.3; Wed, 09 May 2018 11:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=cozU7hpDLxh795EngTMEGYBwJu7UO7SM4W2uDMxdKvc=; b=ZD5ajYjuj/wgorgEU2FJb+2UVCS69zXP1UIpfNUEgEKVDJGfZ48kzcO6WvitCU3v2k 3F31UFUuRJObC4frIwAI9SPc/EsCoQ1HcBu10c5pHJWYRZ9KxWuG/u81D4dHd9SyEdn4 LfXHJu32CVkMpAzhx1X85y3AlBYz6P+ro1xFv73zxmC+rX4l8U+TFlmtW8Ck1+b3Q5V4 VIHjfD67KY4zvW8g40RAUYu8Ks4vk7Up5vMFx2ydaiou1SThKAKJU0yuHPgvKktGwmpD EBZvrSdzYZhtTbLT4lFUyUzndOMQiOUnRCgMinyG5yGiy9jGby60jr7zggINNReAMm6z l6ew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=cozU7hpDLxh795EngTMEGYBwJu7UO7SM4W2uDMxdKvc=; b=G4pkiJwOM2y1Jr597/j47T3Sc36Vxnwhvewe4l87U6W2h3S93eArYd2UUapVAGulm5 64y5DFALoa7Zi3HlfsPzOQ5+QOlKgGTmelOnqs5YQkjbfnVGFyqgWqM8gy4rc9VNVpAo WmnMKnJTGFPOXc8L7LwfIG/qsIynBtRznmIET2Mes0LWoAm4MQwegjc9Dr1k7/7iBxLG 5StNFqWq1A0LfeBGdfGOQLxlKHngUpztKWZmw5HaEgyUPdBefIPDYLlqsUtfNApi2d83 8eo/3krAk7w84BGVa1to9/ESrnntEF52XgTY8HSBsv+VkgJhhFbfexzPeDnlY2fGwWZm U7bg==
X-Gm-Message-State: ALQs6tCyNQiXBpqSjpYAKmmvULuW+SO4KVhV8fXQBJw3UjLNwnf0lz5a p3rH7F8Xi1cOKUWc6J8U9P1XwAvdlDo=
X-Google-Smtp-Source: AB8JxZr0ou3O2Ewm5oc5MXDwWCvYV4DZwJYo9Duw7QLoyEdVDMM3MsXVlGndRIYis+xZYMD3lHo1lA==
X-Received: by 2002:a50:b6ba:: with SMTP id d55-v6mr60962699ede.250.1525889608873; Wed, 09 May 2018 11:13:28 -0700 (PDT)
Received: from [192.168.2.112] ([213.90.79.148]) by smtp.googlemail.com with ESMTPSA id d8-v6sm8228354edk.50.2018.05.09.11.13.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 May 2018 11:13:27 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, MMUSIC <mmusic@ietf.org>, "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
References: <d39c9615-ad46-a840-fd02-9a3eac4b53a9@gmail.com> <D7161134.2F512%christer.holmberg@ericsson.com> <919f4302-29b2-3f48-ffef-aab290bb6e96@gmail.com> <7594FB04B1934943A5C02806D1A2204B72EB88D8@ESESSMB109.ericsson.se>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <2950acc1-ab24-ebb4-cc50-1c64193fbe0d@gmail.com>
Date: Wed, 09 May 2018 20:13:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EB88D8@ESESSMB109.ericsson.se>
Content-Type: multipart/alternative; boundary="------------BAA2E6C176E5E28FE6533A33"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QL4uCGFSsi5Dw_juQ0xNO40o9aI>
Subject: Re: [MMUSIC] Changes for draft-ietf-mmusic-trickle-ice-sip-14 - ABNF
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 18:13:33 -0000

Christer,


On 2018-05-07 21:41, Christer Holmberg wrote:
> Hi Thomas,
>
> I hope Paul can jump in on this one too, since it’s ABNF related :)
>
>>> However, I think there are some issue with the ABNF (not related to Adam¹s
>>> issue).
>>>
>>> For example, the syntax says:
>>>
>>>    ice-pwd-attribute      = %s"a" "=" ice-pwd-att
>>>
>>> Then the draft says:
>>>
>>>    with ice-pwd-attribute from [I-D.ietf-mmusic-ice-sip-sdp],
>> which says
>>
>> ice-pwd-att           = "ice-pwd:" password
>> i.e. doesn't introduce a second a=
> First, I think the structure in draft-ice-sip-sdp is wrong. It shall be something like:
>
>        Attribute Name: ice-pwd
>
>        Attribute Value: ice-pwd-att
>
>        Usage Level: media
>
>        Charset Dependent: No
>
>        Mux Category: TBD
>
>      The Augmented BNF syntax [RFC5234] for the attribute is:
>
>        ice-pwd-att = password
>        password = blah blah...
>
> Now, whether we should use that syntax also in trickle-ice I don't know. I would like to hear Paul's opinion.
You are mixing up the ABNF syntax and the IANA registration template.

The ABNF syntax in section 5.4 of draft-ietf-mmusic-ice-sip-sdp-16 and 
also section 15.4 of RFC 5245
both define the ABNF grammar as

   ice-pwd-att           = "ice-pwd" ":" password

I don't think it is a good idea to re-define the ice-pwd-att token as
  ice-pwd-att = password
  
If you want to add text to the IANA section it MUST read

     The Augmented BNF syntax [RFC5234] for the attribute is:
	  ice-pwd-att           = "ice-pwd" ":" password

The ABNF in draft-ietf-mmusic-trickle-ice-sip-14 is correct wrt usage of ice-pwd-att

Regards
Thomas


>
>>> In my reading, this would result in:
>>>
>>>    a=a=ice-pwd:asd88fgpdd777uzjYhagZg
>>>
>>> Is this what you want?
>> No, and with the above syntax we do not get the a=a=
>>
>>> If you want to use the syntax of draft-ietf-mmusic-ice-sip-sdp, why not do
>>> it directly? Something like:
>>>
>>> session-level-field = ice-pwd-att /
>>>                        Š
>>>                        Š
>>>
>>> ;ice-pwd-att as defined in [I-D.ietf-mmusic-ice-sip-sdp]
>>>
>>> Or, have I missed something?
>> The trickle-ice-sdpfrag syntax uses just a subset of SDP attributes and isn't  build as open as  the SDP syntax , the above doesn't work.
> I am not suggesting an open SDP syntax - I am suggesting the reference the specific syntax for the ice-pwd attribute.
>
> Regards,
>
> Christer
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 06/05/18 21:31, "Thomas Stach" <thomass.stach@gmail.com> wrote:
>
> All,
>
> during IESG review we got the below proposal by Adam for changing the
> ABNF to allow for more encoding flexibility.
>
> Unless somebody objects, I'd provide the proposed change by end of the
> week.
>
> It would affect the "session-level-fields" as proposed below and in a
> similar way the  "pseudo-media-descriptions" and
> "trickle-ice-attribute-fields"
>
> Excerpt from Adam'S IESG review:
>
> §9.2:
>
> The syntax for "session-level-fields", "pseudo-media-descriptions", and
> "trickle-ice-attribute-fields" include extremely strict rules around
> ordering of
> fields (e.g., including ice-ufrag before ice-pwd would be syntactically
> invalid). That level of strictness seems unlikely to lead to interoperable
> implementations.
>
> If the intention is to be rigid in this fashion, please add prominent
> prose
> that warns implementors that fields MUST appear in the order specified,
> and
> that all other orders are invalid and MUST be rejected.
>
> If that's *not* your intention (and I suspect it isn't), then please fix
> the
> syntax definition to allow for arbitrary ordering of attributes in the
> same way
> as SDP does. For example:
>
>       session-level-fields = *(session-level-field CRLF)
>
>       session-level-field = bundle-group-attribute /
>                             ice-lite-attribute /
>                             ice-pwd-attribute /
>                             ice-ufrag-attribute /
>                             ice-options-attribute /
>                             ice-pacing-attribute /
>                             end-of-candidates-attribute /
>                             extension-attribute-fields
>                                    ; for future extensions
>
>
> Regards
>
> Thomas
>
>
>