[MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question

Christian Groves <Christian.Groves@nteczone.com> Tue, 30 September 2014 12:13 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 541701A0687 for <mmusic@ietfa.amsl.com>; Tue, 30 Sep 2014 05:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id E0l_ogCIpBXY for <mmusic@ietfa.amsl.com>; Tue, 30 Sep 2014 05:13:05 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD751A0461 for <mmusic@ietf.org>; Tue, 30 Sep 2014 05:13:05 -0700 (PDT)
Received: from ppp118-209-181-100.lns20.mel8.internode.on.net ([]:53992 helo=[]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1XYwHU-0005DX-83 for mmusic@ietf.org; Tue, 30 Sep 2014 22:11:48 +1000
Message-ID: <542A9E4B.2050608@nteczone.com>
Date: Tue, 30 Sep 2014 22:12:59 +1000
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: mmusic mailing list <mmusic@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ciYA6pevbE8nXDVAMySdoI1t8ys
Subject: [MMUSIC] draft-ietf-mmusic-sctp-sdp-07 SCTP SDP syntax question
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 30 Sep 2014 12:13:07 -0000

Hello Salvatore,

There seems to be several issues with the updated syntax:

1) Cl.4.1 Media Description: With the updated syntax the ability to have 
more than one usage of the SCTP association has been lost as "sctp-fmt" 
is a single value. Also "space" should be SP to be consistent with RFC4566.

To address these I suggest the following update:
sctp-m-line = %x6d "=" ("application" space sctp-port space "SCTP" 1*(SP 
sctp-fmt) CRLF) / ("application" space sctp-port space "SCTP/DTLS" 1*(SP 
sctp-fmt) CRLF) / ("application" space udp-port space "DTLS/SCTP" 1*(SP 
sctp-fmt) CRLF) sctp-port = port

sctp-fmt = association-usage

association-usage = token

2) Cl. 4.1.1 sctp-port: The syntax for sctp-port indicates the dual use 
of "=", i.e.

sctp-port-attr = "a=sctp-port=" portnumber
port-number = port

That doesn't appear to be consistent with the example in clause 4 which has:
a=sctp-port 4060

To match that the syntax needs to be updated, something like:

sctp-port-attr = "a=sctp-port" SP portnumber
port-number = port
I'm not sure why "portnumber" is used when "port" is commonly used in 
clause 4.1?

The syntax could be simplified to:
sctp-port-attr = "a=sctp-port" SP port

3) Cl.4.1.2: There appears to be a formal space (SP) missing from the 
syntax between association-usage and max-message-size.

sctpmap-attr = "a=fmtp:" association-usage [max-message-size]

should be:
sctpmap-attr = "a=fmtp:" association-usage [SP max-message-size]

The current syntax allows an fmtp usage with no max-message-size 
parameter, e.g. "a=fmtp:bfcp". Should this be allowed?

4) Cl.4.1.2: The last sentence of the 1st paragraph and the first 
sentence of the second paragraph appears to be a repeat.

5) Cl.4.1.2: "If the parameter is not present, the implementation should 
provide a
default, with a suggested value of 64K." Is this 64,000 or is 65,535 bytes?

6) Cl.4, 4.1 and 10 refer to the <fmt> sub-field. These should be 
updated to refer to the <sctp-fmt> field.

7) Cl.10: How will this registry relate to the “WebSocket Subprotocol 
Name Registry” 

8) Cl.8.2: What's the significance of the the "*" in the examples in 
terms of "association usage"?

Regards, Christian