IETF Logo Mail Archive

Re: [MMUSIC] draft-ejzak-mmusic-msrp-usage-data-channel

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Sun, 26 October 2014 17:27 UTC

Return-Path: <Raju.Makaraju@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 230DA1A0252 for <mmusic@ietfa.amsl.com>; Sun, 26 Oct 2014 10:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 gNpuXZp_EUnU for <mmusic@ietfa.amsl.com>; Sun, 26 Oct 2014 10:27:22 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-01.alcatel-lucent.com [135.245.18.29]) (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 BD24E1A01AE for <mmusic@ietf.org>; Sun, 26 Oct 2014 10:27:22 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (unknown [135.5.2.63]) by Websense Email Security Gateway with ESMTPS id ED11667294E; Sun, 26 Oct 2014 17:27:16 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id s9QHRJ2g025445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Oct 2014 13:27:19 -0400
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Sun, 26 Oct 2014 13:27:19 -0400
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ejzak-mmusic-msrp-usage-data-channel
Thread-Index: AQHP7t66dy5ZGL+nPEG/1c9gL4hdCZw+EJjQgATDl4D//8+KcA==
Date: Sun, 26 Oct 2014 17:27:18 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E5F1678@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B266CF1@FR712WXCHMBA11.zeu.alcatel-lucent.com> <54492D34.5030705@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17828E5EE3CF@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D4C9DC9@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D4C9DC9@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/oplRwLvbarg-gpf-hkA6ygLq55w
Subject: Re: [MMUSIC] draft-ejzak-mmusic-msrp-usage-data-channel
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: Sun, 26 Oct 2014 17:27:24 -0000

Hi Christer,

> > <Raju>
> > Correct. In theory a simple answer of "a=dcamp:2" is sufficient
> (especially since we are now going to
> > make "subprotocol" as optional) to indicating acceptance of that
> particular data channel.
> > However, to make it consistent with rest of the SDP style, we will change
> the text to indicate subprotocol
> > parameter MUST be included in answer with an optional label (matching or
> non-matching). They may appear in any order.
> 
> I am not sure whether you need to say anything about this.
> 
> How to create the answer is a generic text, and there is already procedure
> text in section 5.1.1 draft-ejzak-mmusic-data-channel-sdpneg-01 for this.

<Raju>
I agree that the procedural text belongs to draft-ejzak-mmusic-data-channel-sdpneg.
However, some clarifications are missing there as well. So, we will add it to that draft.
</Raju>

Thanks
Raju

v2.23.0 | Report a Bug | By Email