Re: [rtcweb] New Version Notification for draft-jesup-rtcweb-data-01.txt

Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 03 November 2011 13:09 UTC

Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA91211E80F4 for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 06:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level:
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RqJFeNND1bTk for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 06:09:34 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5A36D11E80AC for <rtcweb@ietf.org>; Thu, 3 Nov 2011 06:09:34 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c26ae0000035b9-ba-4eb2928afe30
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 7E.DA.13753.A8292BE4; Thu, 3 Nov 2011 14:09:30 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Thu, 3 Nov 2011 14:09:10 +0100
Message-ID: <4EB29275.8000204@ericsson.com>
Date: Thu, 3 Nov 2011 14:09:09 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Randell Jesup <randell-ietf@jesup.org>
References: <20111031211134.8188.49554.idtracker@ietfa.amsl.com> <4EAF64FF.8020101@jesup.org> <02485FF93524F8408ECA9608E47D9F2007CACFFAC2@nambx05.corp.adobe.com> <4EB21DEF.5060606@jesup.org>
In-Reply-To: <4EB21DEF.5060606@jesup.org>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: Michael Tuexen <tuexen@fh-muenster.de>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] New Version Notification for draft-jesup-rtcweb-data-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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, 03 Nov 2011 13:09:35 -0000

On 2011-11-03 05:51, Randell Jesup wrote:
> On 11/2/2011 9:12 PM, Michael Thornburgh wrote:

>> o as you point out in section 5.3, running SCTP over DTLS, rather
>> than DTLS over SCTP, is desired so that all SCTP fields, not just
>> the user data, are secured. however, this configuration is
>> currently not defined by IETF and would have to be specified.
> 
> 
> Ok - though conceptually SCTP should be able to run over anything 
> presenting a UDP-like interface.   There are some fallouts, like no 
> multi-homing.  Can some others here (Magnus?) with better
> understanding of the exact RFC requirements state if it would be
> acceptable to reference a SCTP-over-DTLS draft, which should be
> fairly straightforward to create and move forward?

It is fine for this WG to request publication of a document with
normative references to internet drafts. What really happens is two
things. First we WG chairs + AD needs to determine if it is reasonable
to request publication without the normative reference being ready. That
depends on how clean the separation is. Secondly even if IESG approves
our document, the RFC can't be published until that draft also is
approved and ready to be published. This is fairly common and if you
look at the RFC-editors home page they have this clusters for documents
that await publication due to the normative reference not being ready.

When it comes to the actual usage of either of IP/UDP/SCTP/DTLS and
IP/UDP/DTLS/SCTP we have the same two dependencies on other WGs.

First we need a SCTP over foo document, which is TSVWG. The SCTP over
UDP is already an WG document and making some progress. For SCTP over
DTLS there would be need for a new document, or possibly get that
defined in the same as SCTP over UDP directly.

Secondly if one uses SDP one needs a definition of how one expresses
this on the media description line. That includes the "proto" identifier
itself and any additional information, like direction for establishing
the connection which would be similar to what COMEDIA defines for TCP
(RFC 4145).

>From a time perspective IP/UDP/SCTP/DTLS is the quicker road as the SCTP
over UDP is already in progress and DTLS over SCTP is defined.

So what exist here is really:

https://datatracker.ietf.org/doc/draft-ietf-mmusic-sctp-sdp/
https://datatracker.ietf.org/doc/rfc6083/ (DTLS over SCTP)
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-udp-encaps/


> 
> In response I have to say: put a protocol proposal on the table or 
> gather a group to do so, and do so ASAP, because if we don't get an 
> alternative, it *will* be either SCTP/DTLS/(ICE/UDP) or 
> pseudo-TCP/DTLS/(ICE/UDP), and I don't know what we'd do for the 
> unreliable congestion-controlled channels (maybe DCCP).

Personally view:

I think the choice will be between either

DTLS/SCTP/UDP or SCTP/DTLS/UDP

and

TCP/UDP + DCCP/UDP


> 
> If you do put forward a proposal, do you really believe it can be
> done, standardized, agreed to and implemented in the timeframe
> required? Specifying SCTP/DTLS seems relatively straightforward
> compared to standardizing a new protocol...  The timeframe for this
> is quite constrained already; one of the strongest arguments against
> SCTP would also be timeframe, except that SCTP gives us
> congestion-controlled unreliable data, which pseudo-TCP-over-DTLS
> doesn't - we'd have to use yet another unspecified mechanism for
> congestion control of the unreliable data channels.
> 

I personally don't think think this can be done in short time frames
within the IETF. The reason is that IETF will have to do the following
to get this going and in the end produce an RFC:

1. Write a Charter proposal for a WG in TSV.
2. Have a BOF on the need for creating a new transport protocol
3. Take in all the additional views from other proponents of transport
protocol evolution. I think that means combing Structure Streams with
SCTP + DCCP to build a new swiss army knife of a protocol
4. Agree on the new charter
5. Send it to IESG for approval
6. Have the IETF last call and deal with the comments.
7. Finally having a WG
8. Do a requirements phase
9. Design the new protocol in a committee
10. Have the new protocol receive wide review from OPS, Sec etc.
11. Improve spec by having N meeting cycles go by.
12. WG last call
13. IETF last call
14. IESG approval
15. RFC editor
16. RFC publication

Just the required process steps in the above is on the order of 3
months. My guess is that even if interest in this holds it is 3-4 years
before IETF can conclude on a new transport protocol.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------