Re: [rtcweb] Unsupported PPID (Re: draft-ietf-rtcweb-data-channel failure handling description)

Martin Thomson <martin.thomson@gmail.com> Tue, 26 August 2014 22:01 UTC

Return-Path: <martin.thomson@gmail.com>
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 2A49F1A016C for <rtcweb@ietfa.amsl.com>; Tue, 26 Aug 2014 15:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_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 fNMJjX57U2h9 for <rtcweb@ietfa.amsl.com>; Tue, 26 Aug 2014 15:01:03 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A8551A01BA for <rtcweb@ietf.org>; Tue, 26 Aug 2014 15:01:02 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id gi9so13070954lab.2 for <rtcweb@ietf.org>; Tue, 26 Aug 2014 15:01:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yeUHDcavtjwJf0diPec+41OpB0XOUmRNr6/owqBqyZs=; b=HeEDPnGcTDGtPTlgdJI53E1IlbzKgh6yLuUxuDvpedOno+xqq00Xh0pDcPuY+qrfPt Mqb2p/1zKhXtgjUdNGb6t0nGAWcchoBSYejPrMo6U0VocZPwQ+KzUCHdwTulK0Ya7+Ro TgmRckp+OsxfBHFz2VPkb/4+U6asm2SLz8eeW7k2AoPQikEiJgkc8VEKtVJsYVQYZLGg 3/wzroFJflbjXMwvY6zNcnh2+eVRVdBD6loxOzMxorGqlPNcT1aCfxz/ZWcK7VEl0LJg MnpFi11Z6coRO67JZkJkTXKi+DEPTtLhvz2FCNW2e8qgWhlLinnLi1RHMSNveQcgxQuy ejUA==
MIME-Version: 1.0
X-Received: by 10.152.87.139 with SMTP id ay11mr8567294lab.38.1409090460822; Tue, 26 Aug 2014 15:01:00 -0700 (PDT)
Received: by 10.25.166.75 with HTTP; Tue, 26 Aug 2014 15:01:00 -0700 (PDT)
In-Reply-To: <53FCFFC4.1090502@alum.mit.edu>
References: <20140811181357.613.72705.idtracker@ietfa.amsl.com> <53EEFDD3.6040607@omnitor.se> <53F1E05D.9040804@alvestrand.no> <5AC6FE2A-23B1-4BDE-ABE0-2D64AE750F60@lurchi.franken.de> <CABkgnnW05HW2kdEH49GfSTe1unCeqKUWguUqd29iMjOc1z5BAg@mail.gmail.com> <53FCFFC4.1090502@alum.mit.edu>
Date: Tue, 26 Aug 2014 15:01:00 -0700
Message-ID: <CABkgnnWvqBukv5zjB_=H7Jtz2KA+A36ZxTxnTL6dSFD7mT4qQQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/wXW1AhyqsecI-tqePqdiBS_6y5M
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Unsupported PPID (Re: draft-ietf-rtcweb-data-channel failure handling description)
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, 26 Aug 2014 22:01:04 -0000

On 26 August 2014 14:44, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> One approach would be to define DATA_CHANNEL_CLOSE, and specify that it be
> used just before reset when the close is graceful.

Or define a DATA_CHANNEL_ERROR, which would let you explain why.
Assuming that SCTP doesn't suffer from the same problems TCP does with
sending just prior to a close.