IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Tue, 26 August 2014 21:22 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 63AC81A0367 for <rtcweb@ietfa.amsl.com>; Tue, 26 Aug 2014 14:22:16 -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 QvD7AWfwGSoC for <rtcweb@ietfa.amsl.com>; Tue, 26 Aug 2014 14:22:14 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B374B1A8842 for <rtcweb@ietf.org>; Tue, 26 Aug 2014 14:22:13 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id el20so15756693lab.17 for <rtcweb@ietf.org>; Tue, 26 Aug 2014 14:22:12 -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=75XaUHBFHSm7jVbV0d2TBwNjbsbDHaUuv+rv/KnEooc=; b=xuXzEII5Oolkqhkc2njNiaIFliIOxb8qFOE+HiqvSmL5ynqg9P4zqKwktD3uslhJ0+ 5myJ5DBvQg7Ra507l1tgXLJ2QCN1Dtyht7ws9K0F8u7Am/NBLYVhd9kvFX/xuJUHVUCx 0Yjuk0OHGd0kOnpFXPeu0Piy62XtZNHu8bSK0yQ9Asrj0KfERCpBJaqKZQakX503IYM7 /29S+eSd2jsKag230tqHtSkCqOhtrpooz5g8zcIP9/IvXaWFawJjbguuW3S7w2PHc8R5 ceDyR/DB4fwv6/0zoGowRT2VvdfYqVycKAZRuisMXTfo0Zr1mRM2AtuJQsIQHEK/Jz02 zqsA==
MIME-Version: 1.0
X-Received: by 10.112.199.161 with SMTP id jl1mr9485464lbc.59.1409088131948; Tue, 26 Aug 2014 14:22:11 -0700 (PDT)
Received: by 10.25.166.75 with HTTP; Tue, 26 Aug 2014 14:22:11 -0700 (PDT)
In-Reply-To: <5AC6FE2A-23B1-4BDE-ABE0-2D64AE750F60@lurchi.franken.de>
References: <20140811181357.613.72705.idtracker@ietfa.amsl.com> <53EEFDD3.6040607@omnitor.se> <53F1E05D.9040804@alvestrand.no> <5AC6FE2A-23B1-4BDE-ABE0-2D64AE750F60@lurchi.franken.de>
Date: Tue, 26 Aug 2014 14:22:11 -0700
Message-ID: <CABkgnnW05HW2kdEH49GfSTe1unCeqKUWguUqd29iMjOc1z5BAg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/F4SrrwOEu3QOY3B-O9O6JS4hJOM
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 21:22:16 -0000

On 26 August 2014 13:36, Michael Tuexen
<Michael.Tuexen@lurchi.franken.de> wrote:
> What I don't understand how ignoring gives you extensibility. If one sides sends a new PPID, and
> the other sides ignores it, the sender (at the SCTP level) thinks that the message was received
> without any problem, since SCTP doesn't take the PPID into account. So user messages are lost.

I think that the use of a new PPID can be negotiated prior to use, so
there aren't big problems with any action recommended here.  Resetting
the stream might work, assuming that we can distinguish between an
error and a graceful close correctly, that is.

v2.23.0 | Report a Bug | By Email