IETF Logo Mail Archive

Re: [rtcweb] UDP transport problem

Ted Hardie <ted.ietf@gmail.com> Thu, 13 February 2014 22:32 UTC

Return-Path: <ted.ietf@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 B1AB01A0484 for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 14:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 dixN3-YhJ5q0 for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 14:32:36 -0800 (PST)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 42AFD1A0483 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 14:32:34 -0800 (PST)
Received: by mail-ig0-f176.google.com with SMTP id j1so13893892iga.3 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 14:32:33 -0800 (PST)
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=3ihaTYhaGNjJBl2tiKOiT2kDd8a6nR22tFqWVe6cK0o=; b=X28dbUgacSJEu33zMp4sM275lUT2xHJLSJJhHD0LleNRAAkhQ9aFHkzA0AC68xMTlF dprYHG/MAfsynCNU2072NC4M4ILp0mUIvMLcWORK4hMs5ZKuuGXRJxL25DGG9cklnOhQ B/S1LtEks5Do1T+EU+YGoY81JUeAZTT+hNJB4S52io0mheG6QSSuMitVQTxc+sWjq3uR 39v36+bRSqGbRXX2oqREQ3N0XGH41w1DGM5DE8/qWyisNuVW1kKisNgFXtpIKQFMb9uL xh1orTsehv4+GbJ3wNICGy8juEZsSA57KXJNGnTbmOfDBMH3KEtb1lTno8OwoR9shsgq U8Ww==
MIME-Version: 1.0
X-Received: by 10.42.129.9 with SMTP id o9mr3355955ics.38.1392330752957; Thu, 13 Feb 2014 14:32:32 -0800 (PST)
Received: by 10.42.237.206 with HTTP; Thu, 13 Feb 2014 14:32:32 -0800 (PST)
In-Reply-To: <CAD6AjGTbSJEV2cJj5QyLktyZPv8SJa7h-QHKVtdUXnF3K6xwHA@mail.gmail.com>
References: <CAD6AjGRiQ1UF5n3JG9HPRQFM+TD54Xz-dpTn5u9bX+__BMfesQ@mail.gmail.com> <CABkgnnVbZp7yBvpY1ARuaBXS=TOipY=BhXzrd=h5DY-76oF9Pw@mail.gmail.com> <CAD6AjGSxS4jNRGotsE_no0XhewvDqcVZ+Kmx1aMW9qorqSKR+w@mail.gmail.com> <52FD2FA4.8040701@alvestrand.no> <CAD6AjGTbSJEV2cJj5QyLktyZPv8SJa7h-QHKVtdUXnF3K6xwHA@mail.gmail.com>
Date: Thu, 13 Feb 2014 14:32:32 -0800
Message-ID: <CA+9kkMCjvBoMK2X6wE332Oe32v44K-hNgJC18yCXqgXEo7=cGw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Cb B <cb.list6@gmail.com>
Content-Type: multipart/alternative; boundary="20cf3010eb89f0a2af04f2514335"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/t574N3c0cyDUmezNpKAVlRjxh9k
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] UDP transport problem
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: Thu, 13 Feb 2014 22:32:37 -0000

On Thu, Feb 13, 2014 at 1:20 PM, Cb B <cb.list6@gmail.com> wrote:

>
> But that's not the point.  The question is can we include native SCTP
> as an option in  draft-ietf-rtcweb-transports?  What is the downside?
>
> CB
>

Howdy,

Given previous decisions of the working group, you would need to describe
how to provide confidentiality.  At the moment, I know only of TLS over
SCTP (which would reverse the current mapping) and SCTP over IPSec (which
would likely actually be IPSec/UDP); do you know of other methods which
would keep SCTP at the top layer of the protocol stack and still provide
confidentiality?

regarsd,

Ted

v2.23.0 | Report a Bug | By Email