IETF Logo Mail Archive

Re: [rtcweb] Notes from Data discussion today - reset channel?

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 04 March 2014 16:19 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED2F71A023E for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 08:19:54 -0800 (PST)
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 f-06yNTW75i7 for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 08:19:53 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 493D21A024E for <rtcweb@ietf.org>; Tue, 4 Mar 2014 08:19:53 -0800 (PST)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by QMTA11.westchester.pa.mail.comcast.net with comcast id ZTGK1n0030cZkys5BUKqa3; Tue, 04 Mar 2014 16:19:50 +0000
Received: from dhcp-a663.meeting.ietf.org ([31.133.166.99]) by omta10.westchester.pa.mail.comcast.net with comcast id ZUHf1n00V2904qf3WUHhDh; Tue, 04 Mar 2014 16:17:48 +0000
Message-ID: <5315FCA2.8010802@alum.mit.edu>
Date: Tue, 04 Mar 2014 16:17:38 +0000
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.3.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
References: <A44844EB-07A4-488F-9D2D-9BEDFF9512AC@iii.ca> <5315F4FB.4000908@alum.mit.edu> <A893BB20-B646-4E31-8F71-115062114C89@lurchi.franken.de>
In-Reply-To: <A893BB20-B646-4E31-8F71-115062114C89@lurchi.franken.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393949990; bh=Kmrj+LRPPR1QO7F0G70LNtPPVgiqCuUNcqHrlqHw2Ik=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=q6rp9JVmJd199z/KwdWWvUexULMyrw3FPhLXDXLNmTFj0bQBoONVHs/NXrraH68sd DIcNpfNUWwYSxF2lGXM2A9GBuPu71Tp6qaHf2LFnEAkRxeHmdHgihspll7Lob2x+0h 6piQGjgKod2smoWrdMAvxClc/njCG5yHmaOyMye7loHI1WIb3wJ2Q9RiChGIaksK+6 oyVXfb27MG8cYeHwXJ5oIoG1UEEZcf1yIMFOj0FzuJlAa9lfKSm73afOKMyS3NIFay Rr1sIbcEFA+v8bCkIs+qGRMJKU6sICRKFki7Aot379kkbzhbLdRuABL6zI2oOGAlLR QzBtMD0N3ZEAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/z68mNiXvcr229mbBdOddzXVOpLM
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Notes from Data discussion today - reset channel?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 16:19:55 -0000

On 3/4/14 3:50 PM, Michael Tuexen wrote:
> On 04 Mar 2014, at 15:44, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>
>> On 3/4/14 11:32 AM, Cullen Jennings wrote:
>>
>>> Issue #5
>>> - part of the issue here is there is a protocol on top of SCTP
>>> - change to text say “reset channel”
>>
>> I understand what an SCTP stream reset is.
>>
>> I can guess what "reset channel" means, but AFAIK it isn't defined anywhere.
> More precise language: Close the channel. This is described in
> http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-07#section-6.7
>
> Best regards
> Michael

OK. Close enough I guess. (Close - Reset)

	Sorry,
	Paul

v2.23.0 | Report a Bug | By Email