Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and sctp-sack-immediately
"Becke, Martin" <martin.becke@uni-due.de> Wed, 19 December 2012 14:25 UTC
Return-Path: <martin.becke@uni-due.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E82A921F857A for <tsvwg@ietfa.amsl.com>; Wed, 19 Dec 2012 06:25:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMK5JaeQWCO8 for <tsvwg@ietfa.amsl.com>; Wed, 19 Dec 2012 06:25:55 -0800 (PST)
Received: from mailoutzim.uni-due.de (mailoutzim.uni-due.de [132.252.185.16]) by ietfa.amsl.com (Postfix) with ESMTP id 06BF121F8558 for <tsvwg@ietf.org>; Wed, 19 Dec 2012 06:25:54 -0800 (PST)
Received: from HT02.win.uni-due.de (virt098.zim.uni-duisburg-essen.de [132.252.185.98]) by mailoutzim.uni-due.de (8.13.1/8.13.1) with ESMTP id qBJEPqnT002255; Wed, 19 Dec 2012 15:25:52 +0100
Received: from ccr02.win.uni-due.de ([169.254.2.147]) by HT02.win.uni-due.de ([132.252.190.234]) with mapi id 14.02.0318.004; Wed, 19 Dec 2012 15:25:52 +0100
From: "Becke, Martin" <martin.becke@uni-due.de>
To: "<gorry@erg.abdn.ac.uk> <gorry@erg.abdn.ac.uk>" <gorry@erg.abdn.ac.uk>
Thread-Topic: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and sctp-sack-immediately
Thread-Index: AQHN2TYMK7i9ELVHs0iWZjhVfp+hQZggJk6A
Date: Wed, 19 Dec 2012 14:25:51 +0000
Message-ID: <A33D17830EBE774E8AEFAED600DD54E26B0192A6@ccr02.win.uni-due.de>
References: <1747245efc625354ccb67504cf31a2d5.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <1747245efc625354ccb67504cf31a2d5.squirrel@www.erg.abdn.ac.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [132.252.151.202]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <96E6530406834747A388EF5BA5B08DCE@win.uni-due.de>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Virus-Scanned: Clam Anti Virus - http://www.clamav.net
X-Spam-Scanned: SpamAssassin: 3.002004 - http://www.spamassassin.org
X-Scanned-By: MIMEDefang 2.57 on 132.252.185.16
Cc: "<tsvwg@ietf.org>" <tsvwg@ietf.org>, Sebastian Werner <sebastian.werner@iem.uni-due.de>
Subject: Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and sctp-sack-immediately
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 14:25:56 -0000
Hi Gorry, 1) This draft is important in the context of the RTCWeb/WebRTC discussion. If the RTCWeb/WebRTC solution comes up with SCTP and DTLS we need an agreement here. The WG should discuss about the best way, I would like to see the ID in the WG. We (especially Sebastian) implement the current discussed RTCWeb stack in the Omnet++/Inet Environment. 2) For my feeling the motivation for this kind of extension is strong enough. Furthermore I see no drawbacks, but the approach provides a possible improvement without changing the nature of the protocol. That is why I support the adoption of this draft. Martin Am 13.12.2012 um 14:30 schrieb <gorry@erg.abdn.ac.uk> <gorry@erg.abdn.ac.uk>: > This email starts a WG call for adoption for 2 potential TSVWG work items > proposing minor extensions to SCTP: This adoption call will conclude 3rd > January 2013. > > 1) SCTP/DTLS > > The authors of "draft-tuexen-tsvwg-sctp-dtls-encaps-01" request that this > is adopted as TSVWG item. > > The IETF-85 meeting indicated some WG support for this, so we are now > ready to make a formal decision and this email is to allow people to > confirm that there is sufficient energy to complete this work in TSVWG. > > 2) SCTP SACK Immediately > > The authors of "draft-tuexen-tsvwg-sctp-sack-immediately" request that > this is adopted as TSVWG item. > > This draft was discussed at a number of previous IETFs and the IETF-85 > meeting indicated some WG support for this, so we are now ready to make a > formal decision and this email is to allow people to confirm that there is > sufficient energy to complete this work in TSVWG. > > > PLEASE send an email to this list: > > * if you think adopting either/both of these documents in TSVWG is a good > or bad idea. > > * if you have implemented or plan to implement these extensions. > > * Please also indicate if you are willing to REVIEW either/both documents > during its development. > > Best wishes, > > Gorry, David and James. > (TSVWG Co-Chairs) > >
- Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and s… Salvatore Loreto
- [tsvwg] ADOPTION CALL: sctp-dtls-encaps and sctp-… gorry
- [tsvwg] ADOPTION CALL: sctp-dtls-encaps and sctp-… gorry
- Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and s… Thomas Dreibholz
- Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and s… Becke, Martin
- Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and s… Irene Rüngeler
- Re: [tsvwg] ADOPTION CALL: sctp-dtls-encaps and s… Anna Brunstrom