Re: [MMUSIC] New draft version: draft-ietf-mmusic-data-channel-sdpneg-01

Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@alcatel-lucent.com> Tue, 10 March 2015 15:23 UTC

Return-Path: <juergen.stoetzer-bradler@alcatel-lucent.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968E81A00E8 for <mmusic@ietfa.amsl.com>; Tue, 10 Mar 2015 08:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.11
X-Spam-Level:
X-Spam-Status: No, score=-5.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, J_CHICKENPOX_74=0.6, J_CHICKENPOX_75=0.6, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 XBjC6YSIoaaY for <mmusic@ietfa.amsl.com>; Tue, 10 Mar 2015 08:23:35 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B77271A001B for <mmusic@ietf.org>; Tue, 10 Mar 2015 08:21:57 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 02E7FD8AD1665 for <mmusic@ietf.org>; Tue, 10 Mar 2015 15:21:52 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t2AFLrGR021336 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Tue, 10 Mar 2015 16:21:55 +0100
Received: from [149.204.68.136] (135.239.27.39) by FR711WXCHHUB02.zeu.alcatel-lucent.com (135.239.2.112) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 10 Mar 2015 16:21:53 +0100
Message-ID: <54FF0C10.7040206@alcatel-lucent.com>
Date: Tue, 10 Mar 2015 16:21:52 +0100
From: Juergen Stoetzer-Bradler <Juergen.Stoetzer-Bradler@alcatel-lucent.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <54FD7E59.6020309@alcatel-lucent.com> <54FDBD60.8060900@alum.mit.edu>
In-Reply-To: <54FDBD60.8060900@alum.mit.edu>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms040507010506080002050404"
X-Originating-IP: [135.239.27.39]
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jt8B2Hl2fKOARZhTDp9oD-Rh3JA>
Subject: Re: [MMUSIC] New draft version: draft-ietf-mmusic-data-channel-sdpneg-01
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, 10 Mar 2015 15:23:38 -0000

Paul,

Thank you for further comments.
Please see my remarks inserted below.

Thanks,
Juergen

On 09.03.2015 16:33, Paul Kyzivat wrote:
> Juergen,
>
> In general this is good. I have a few remaining comments:
>
> Section 5.2.2 says:
>
>    ... If an SDP offer contains both of
>    these parameters then such an SDP offer will be rejected.
>
> The use of "will" is confusing - it isn't normative. IMO it should either use "MUST" or else it 
> should say such usage is undefined.

[Juergen] The intention is indeed to request the answerer to reject sch an SDP offer.
Thus we could say:
"... If an SDP offer contains both of these parameters then such an SDP offer MUST be rejected."

>
> Then:
>
>    The SDP answer shall echo the same subprotocol, max-retr, max-time,
>    ordered parameters, if those were present in the offer, and may
>
> Again, "shall" is non-normative. IMO this should be SHALL or MUST.

[Juergen] Agreed. Would propose to say:
"The SDP answer SHALL echo the same subprotocol, max-retr, max-time, ordered parameters, ..."

>
> Then:
>
>    Data channel types defined in [I-D.ietf-rtcweb-data-protocol] are
>    mapped to SDP in the following manner:
>
>    DATA_CHANNEL_RELIABLE
>          a=dcmap:2 subprotocol="BFCP";label="channel 2"
>    ...
>
> "This is a bit unclear because these are *examples* using BFCP. (It also uses 'ordered=0' rather 
> than 'ordered=false'. I think it would be clearer as:
>
>    Data channel types defined in [I-D.ietf-rtcweb-data-protocol] are
>    mapped to SDP a=dcmap parameters in the following manner:
>
>    DATA_CHANNEL_RELIABLE
>          ordered=true
>
>    DATA_CHANNEL_RELIABLE_UNORDERED
>          ordered=false
>
>    DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT
>          ordered=true;max-retr=NNN
>
>    DATA_CHANNEL_PARTIAL_RELIABLE_REXMIT_UNORDERED
>          ordered=false;max-retr=NNN
>
>    DATA_CHANNEL_PARTIAL_RELIABLE_TIMED
>          ordered=true;max-time=NNN
>
>    DATA_CHANNEL_PARTIAL_RELIABLE_TIMED_UNORDERED
>          ordered=false;max-time=NNN
>
> ('ordered=true' is default and may be omitted.)"

[Juergen] We fully agree an will update the text as you propose in next draft -02.

>
>     Thanks,
>     Paul
>
[snip]