IETF Logo Mail Archive

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

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 23 October 2014 20:36 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 76D291AD359 for <mmusic@ietfa.amsl.com>; Thu, 23 Oct 2014 13:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 nE08orEkQmYE for <mmusic@ietfa.amsl.com>; Thu, 23 Oct 2014 13:36:31 -0700 (PDT)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BD981AD358 for <mmusic@ietf.org>; Thu, 23 Oct 2014 13:36:31 -0700 (PDT)
Received: from resomta-po-14v.sys.comcast.net ([96.114.154.238]) by resqmta-po-12v.sys.comcast.net with comcast id 6kb91p00258ss0Y01kcXeh; Thu, 23 Oct 2014 20:36:31 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-po-14v.sys.comcast.net with comcast id 6kcW1p00C3Ge9ey01kcWAp; Thu, 23 Oct 2014 20:36:31 +0000
Message-ID: <544966CE.2080709@alum.mit.edu>
Date: Thu, 23 Oct 2014 16:36:30 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <949EF20990823C4C85C18D59AA11AD8B266CF1@FR712WXCHMBA11.zeu.alcatel-lucent.com> <54492D34.5030705@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17828E5EE3CF@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E5EE3CF@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1414096591; bh=9GuPiaOHWX1ZokZIsU0JUo3ccDGfQ4PdFp+pgte7rqw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=t/hJUgM/iaQ8CcIGQ6QmlFvzDYMfK4cuPgtmCxP/Z1ve7qXDIEs71FbW/91YOXjwJ mmhN9dClFfu+78rrAeu/Kcg/k2shlngRp7Qz/p6ISEt64qVZcxT2hzt/fsWf7Qqwos RD15rXmD4wj2flTqt1uhnCjTRXZyAjTMlApMgT+WP75iIoO1rd7v48N4eKhTGuBUkU jKFDYm1NG5aBDWYVtkN72Rb6g7nmlZNeEeUevrz6aeDbnAzzJ83Q5LQ26j+fUThUSk nLicNORVLiIEOPnZvSBSuoXRUVhRwh+OZh1XtFiml3qhqeawloC/1ThvyFcwnBWzdv WBljzbDksB9DA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/hmcsEG1hxDmVOqKXyJbSZz8EXtw
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: Thu, 23 Oct 2014 20:36:32 -0000

On 10/23/14 4:11 PM, Makaraju, Maridi Raju (Raju) wrote:

>> 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?

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email