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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Tue, 04 March 2014 15:50 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 95A8A1A0117 for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001] 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 d_e0oxuqfrj0 for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:50:27 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 3191A1A00F5 for <rtcweb@ietf.org>; Tue, 4 Mar 2014 07:50:27 -0800 (PST)
Received: from dhcp-9fd9.meeting.ietf.org (dhcp-9fd9.meeting.ietf.org [31.133.159.217]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 284A41C0E97FE; Tue, 4 Mar 2014 16:50:23 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5315F4FB.4000908@alum.mit.edu>
Date: Tue, 4 Mar 2014 15:50:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A893BB20-B646-4E31-8F71-115062114C89@lurchi.franken.de>
References: <A44844EB-07A4-488F-9D2D-9BEDFF9512AC@iii.ca> <5315F4FB.4000908@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/RFLi1DXCSx9Uxn4MBdbpDUsmNts
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 15:50:29 -0000

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
> 
> I guess it may mean sending an Outgoing SSN Reset Request, or an Incoming SSN Reset Request, or both.
> 
> (If there was a notion of a Data Channel Protocol, then it could have a channel reset request, that mapped to the appropriate corresponding SCTP actions.)
> 
> 	Thanks,
> 	Paul
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>