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

"Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com> Fri, 24 October 2014 15:26 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 E39E31A1A2D for <mmusic@ietfa.amsl.com>; Fri, 24 Oct 2014 08:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.31
X-Spam-Level:
X-Spam-Status: No, score=-1.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_15=0.6, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 eXplrIiBYSl2 for <mmusic@ietfa.amsl.com>; Fri, 24 Oct 2014 08:26:39 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpatc-esg-01.alcatel-lucent.com [135.245.18.27]) (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 6936D1A0115 for <mmusic@ietf.org>; Fri, 24 Oct 2014 08:26:39 -0700 (PDT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65]) by Websense Email Security Gateway with ESMTPS id B1E46EFB1874; Fri, 24 Oct 2014 15:26:35 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id s9OFQbsN007695 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 11:26:38 -0400
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Fri, 24 Oct 2014 11:26:38 -0400
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: 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+EJjQgABWxQCAAPUTgA==
Date: Fri, 24 Oct 2014 15:26:37 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E5EF911@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <949EF20990823C4C85C18D59AA11AD8B266CF1@FR712WXCHMBA11.zeu.alcatel-lucent.com> <54492D34.5030705@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17828E5EE3CF@US70UWXCHMBA02.zam.alcatel-lucent.com> <544966CE.2080709@alum.mit.edu>
In-Reply-To: <544966CE.2080709@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
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/qzyp6nICR8YvXGFjs6hKQ0Ac-XI
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: Fri, 24 Oct 2014 15:26:41 -0000

>> Suppose the intent is to close one MSRP session and immediately open a
> >> new one. Is it permissible to simply update the SDP to describe the new
> >> MSRP session, reusing the channel number, without first doing an O/A to
> >> confirm the closure of the old one?
> > <Raju>
> > The intent is not to reuse a datachannel (same or a different subprotocol)
> > before close. We will clarify that such a reuse is not supported.
> > The problem with such reuse is, previous datachannel MUST be reset before
> > it is used for new subprotocol, else the data from previous data channel
> use
> > will interfere with the new data channel use.
> 
> My question is: Can I just close it in-band (with a reset) and then send
> an offer for the new usage of the channel?

<Raju>
No. To reuse a closed data channel, a new SDP offer/answer, to convey the 
data channel closure (which excludes the corresponding a=dcmap and may include
other new data channels via new a=dcmaps), must be done. This can be done either 
in a new offer initiated from this end or in an SDP answer this end generates.
The reason for this is to avoid various race conditions between SDP offer/answer
and SCTP reset arrival times.
Also, this is not a limiting thing as a new data channel can easily be created 
using a new stream id, range is for which is large, without restarting underlying
SCTP/DTLS association.

If you agree I will update draft-ejzak-mmusic-data-channel-sdpneg and
draft-ejzak-mmusic-msrp-usage-data-channel with these clarifications.
</Raju>

BR
Raju