From gorry@erg.abdn.ac.uk Tue Feb 4 09:57:39 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89CE1A0127 for ; Tue, 4 Feb 2014 09:57:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.736 X-Spam-Level: X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 N6dK8pGF94GJ for ; Tue, 4 Feb 2014 09:57:38 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 77D931A011D for ; Tue, 4 Feb 2014 09:57:37 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 76CBE2B44CE; Tue, 4 Feb 2014 17:57:36 +0000 (GMT) Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id B6F922B4231 for ; Tue, 4 Feb 2014 17:57:34 +0000 (GMT) Message-ID: <52F12A0E.3060607@erg.abdn.ac.uk> Date: Tue, 04 Feb 2014 17:57:34 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: tsvwg WG Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Subject: [tsvwg] TSVWG Status X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 17:57:40 -0000 The list below shows the status of the working group documents as we see it. Please check below and comment on drafts using the list. Please do send any corrections/omissions to the chairs. Best wishes, Gorry, David & James (TSVWG Chairs) Feb 2014 ------------------------------------------------------------------- Recently published: draft-ietf-tsvwg-sctp-sack-immediately was published as RFC 7053. ------------------------------------------------------------------- IDs in RFC Editor Queue: http://www.rfc-editor.org/queue.html draft-ietf-tsvwg-byte-pkt-congest - Document Shepherd: Gorry ------------------------------------------------------------------- IDs in IESG processing: None. ------------------------------------------------------------------- WG Drafts with Chairs: --- Adding Congestion Notification to Protocols that Encapsulate IP draft-briscoe-tsvwg-ecn-encap-guidelines - Note would be needed to ieee-ietf-coord - WG Adoption call pending (early responses received). --- ‘Multicast UDP Guidelines’ as a BCP RFC - Document Shepherd: Gorry draft-shepherd-multicast-udp-guidelines - WG needs to consider draft(s) and identify reviewers. ------------------------------------------------------------------- Active WG Drafts: --- draft-ietf-tsvwg-rsvp-pcn - Document Shepherd: James Replaces: draft-karagiannis-pcn-tsvwg-rsvp-pcn DUE: New ID required to address RSVP model and then repeat WGLC --- draft-ietf-tsvwg-rsvp-app-id-vv-profiles Replaces: draft-polk-tsvwg-rsvp-app-id-vv-profiles DUE: Reviewers are needed to prepare for a WGLC. --- draft-ietf-tsvwg-port-use - Document Shepherd: Gorry Replaces: draft-touch-tsvwg-port-use-00 DUE: Please read sections and provide feedback! DUE: Next step WGLC --- draft-ietf-tsvwg-natsupp-tsvwg - Document Shepherd: James DUE: Authors please update following comments DUE: Align to related draft on SCTP NAT. DUE: Please comment on list --- draft-ietf-tsvwg-sctp-prpolicies replaces: draft-tuexen-tsvwg-sctp-prpolicies DUE: Discussion needed on list. --- draft-ietf-tsvwg-sctp-ndata replaces: draft-stewart-tsvwg-sctp-ndata-03 DUE: Discussion needed on list. --- draft-ietf-tsvwg-sctpnat Replaces: draft-ietf-behave-sctpnat-03.txt Former BEHAVE WG work item that defines SCTP NAT support DUE: Authors please update to align to related draft on SCTP NAT. --- draft-ietf-tsvwg-sctp-failover - Document Shepherd: James Replaces: draft-nishida-tsvwg-sctp-failover DUE: Please comment on list. --- draft-ietf-tsvwg-sctp-dtls-encaps - Document Shepherd: Gorry Replaces: draft-tuexen-tsvwg-sctp-dtls-encaps-01 DUE: Please comment on list. --- draft-ietf-tsvwg-intserv-multiple-tspec - Document Shepherd: David DUE: Discussion needed on list. --- draft-ietf-tsvwg-requirements-update-00 Replaces: draft-ietf-behave-requirements-update-00 Former BEHAVE WG work item intended for publication as a BCP DUE: Please comment on list --- draft-tsvwg-gre-in-udp-encap replaces: draft-yong-tsvwg-gre-in-udp-encap DUE: New ID required to address issues. ------------------------------------------------------------------ The following have received recent discussion at TSVWG meetings or on the list. Inclusion in the list below does not indicate support for these specific drafts and other contributions are also warmly welcomed. --------------------------------------------------------------- Authors request to be considered for adoption: draft-shepherd-multicast-udp-guidelines (see above) draft-briscoe-tsvwg-ecn-encap-guidelines (see above) draft-geib-tsvwg-diffserv-intercon (revised ID needed) draft-dhesikan-tsvwg-rtcweb-qos (revised ID needed) ------- From l.wood@surrey.ac.uk Tue Feb 4 16:00:45 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A26FF1A0196 for ; Tue, 4 Feb 2014 16:00:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ZlyQVJMLbf0h for ; Tue, 4 Feb 2014 16:00:43 -0800 (PST) Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id 319FB1A01A5 for ; Tue, 4 Feb 2014 16:00:43 -0800 (PST) Received: from [195.245.231.67:41011] by server-11.bemta-5.messagelabs.com id 54/C1-23886-A2F71F25; Wed, 05 Feb 2014 00:00:42 +0000 X-Env-Sender: l.wood@surrey.ac.uk X-Msg-Ref: server-16.tower-82.messagelabs.com!1391558441!35763530!1 X-Originating-IP: [131.227.200.43] X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17360 invoked from network); 5 Feb 2014 00:00:41 -0000 Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-16.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 5 Feb 2014 00:00:41 -0000 Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Wed, 5 Feb 2014 00:00:40 +0000 From: To: , Date: Wed, 5 Feb 2014 00:00:40 +0000 Thread-Topic: draft-ietf tsvwg-gre-in-udp-encap was RE: [tsvwg] TSVWG Status Thread-Index: AQHPIgVO7EwBuC5R1EO9zKgOQawucQ== Message-ID: <290E20B455C66743BE178C5C84F1240847E6334703@EXMB01CMS.surrey.ac.uk> References: <52F12A0E.3060607@erg.abdn.ac.uk> In-Reply-To: <52F12A0E.3060607@erg.abdn.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [tsvwg] draft-ietf tsvwg-gre-in-udp-encap was RE: TSVWG Status X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 00:00:45 -0000 draft-IETF-tsvwg-gre-in-udp-encap replaces: draft-yong-tsvwg-gre-in-udp-encap DUE: New ID required to address issues. http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-00 I still have issues with the UDP checksum text; zero checksums with IPv6 po= ses problems for other possible recipients - port/address pollution that th= e rest of the internet has to protect against, basically. (RFC6936 states a= nd details this problem, but gently; RFC6935 is all 'hey, tunnels performan= ce is great!' and ignore the problem) There was a long discussion on the mpls mailing list about the parallel mpl= s-in-udp draft and its checksum text. That draft text has been updated, dis= cussion is still ongoing. As there's author overlap between the mpls and gre drafts so editors are aw= are, I would expect to see similar updates here. regards Lloyd Wood http://about.me/lloydwood From lucy.yong@huawei.com Thu Feb 6 07:51:55 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BB51A03D0 for ; Thu, 6 Feb 2014 07:51:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.736 X-Spam-Level: X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 TFwBtIzBn4Wq for ; Thu, 6 Feb 2014 07:51:53 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3111D1A01E7 for ; Thu, 6 Feb 2014 07:51:53 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAV96407; Thu, 06 Feb 2014 15:51:51 +0000 (GMT) Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 6 Feb 2014 15:50:33 +0000 Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 6 Feb 2014 15:51:15 +0000 Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.21]) by dfweml704-chm.china.huawei.com ([169.254.6.202]) with mapi id 14.03.0158.001; Thu, 6 Feb 2014 07:51:03 -0800 From: Lucy yong To: "l.wood@surrey.ac.uk" , "gorry@erg.abdn.ac.uk" , "tsvwg@ietf.org" Thread-Topic: [tsvwg] draft-ietf tsvwg-gre-in-udp-encap was RE: TSVWG Status Thread-Index: AQHPIgVXZDHH2laWqE21+nwabPP5oJqoYBgQ Date: Thu, 6 Feb 2014 15:51:02 +0000 Message-ID: <2691CE0099834E4A9C5044EEC662BB9D45329BDB@dfweml701-chm.china.huawei.com> References: <52F12A0E.3060607@erg.abdn.ac.uk> <290E20B455C66743BE178C5C84F1240847E6334703@EXMB01CMS.surrey.ac.uk> In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334703@EXMB01CMS.surrey.ac.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.157.174] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: "draft-ietf-tsvwg-gre-in-udp-encap@tools.ietf.org" Subject: Re: [tsvwg] draft-ietf tsvwg-gre-in-udp-encap was RE: TSVWG Status X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 15:51:55 -0000 Hi Lloyd, Yes, we plan to update the draft before the cut-off days to address the con= cerns from you and Lars and are aware of all the discussions in mpls mailin= g list. We will do our best to fact in the conclusion/consent from the disc= ussions in the update. Thank you for the input. Regards, Lucy =20 -----Original Message----- From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.u= k Sent: Tuesday, February 04, 2014 6:01 PM To: gorry@erg.abdn.ac.uk; tsvwg@ietf.org Subject: [tsvwg] draft-ietf tsvwg-gre-in-udp-encap was RE: TSVWG Status draft-IETF-tsvwg-gre-in-udp-encap replaces: draft-yong-tsvwg-gre-in-udp-encap DUE: New ID required to address issues. http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-00 I still have issues with the UDP checksum text; zero checksums with IPv6 po= ses problems for other possible recipients - port/address pollution that th= e rest of the internet has to protect against, basically. (RFC6936 states a= nd details this problem, but gently; RFC6935 is all 'hey, tunnels performan= ce is great!' and ignore the problem) There was a long discussion on the mpls mailing list about the parallel mpl= s-in-udp draft and its checksum text. That draft text has been updated, dis= cussion is still ongoing. As there's author overlap between the mpls and gre drafts so editors are aw= are, I would expect to see similar updates here. regards Lloyd Wood http://about.me/lloydwood From internet-drafts@ietf.org Thu Feb 6 12:44:19 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC261A0475; Thu, 6 Feb 2014 12:44:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 9tXEgjamOmYe; Thu, 6 Feb 2014 12:44:18 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4401A01E6; Thu, 6 Feb 2014 12:44:17 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140206204417.8522.99751.idtracker@ietfa.amsl.com> Date: Thu, 06 Feb 2014 12:44:17 -0800 Cc: tsvwg@ietf.org Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-ndata-00.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 20:44:20 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : A New Data Chunk for Stream Control Transmission Protocol Authors : Randall R. Stewart Michael Tuexen Salvatore Loreto Robin Seggelmann Filename : draft-ietf-tsvwg-sctp-ndata-00.txt Pages : 10 Date : 2014-02-06 Abstract: The Stream Control Transmission Protocol (SCTP) is a message oriented transport protocol supporting arbitrary large user messages. However, the sender can not interleave different user messages which which causes head of line blocking at the sender side. To overcome this limitation, this document adds a new data chunk to SCTP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-ndata/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Fri Feb 7 07:50:37 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554DD1AC862; Fri, 7 Feb 2014 07:50:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 aI88Ld00PDgS; Fri, 7 Feb 2014 07:50:35 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBAC1AC497; Fri, 7 Feb 2014 07:50:35 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140207155035.5630.27301.idtracker@ietfa.amsl.com> Date: Fri, 07 Feb 2014 07:50:35 -0800 Cc: tsvwg@ietf.org Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-sctp-dtls-encaps-03.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 15:50:37 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : DTLS Encapsulation of SCTP Packets Authors : Michael Tuexen Randall R. Stewart Randell Jesup Salvatore Loreto Filename : draft-ietf-tsvwg-sctp-dtls-encaps-03.txt Pages : 7 Date : 2014-02-07 Abstract: The Stream Control Transmission Protocol (SCTP) is a transport protocol originally defined to run on top of the network protocols IPv4 or IPv6. This document specifies how SCTP can be used on top of the Datagram Transport Layer Security (DTLS) protocol. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-dtls-encaps/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-sctp-dtls-encaps-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From lucy.yong@huawei.com Fri Feb 7 08:26:32 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAD921A0585 for ; Fri, 7 Feb 2014 08:26:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.736 X-Spam-Level: X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 JX3G3haFb6Hu for ; Fri, 7 Feb 2014 08:26:31 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 66C241A0594 for ; Fri, 7 Feb 2014 08:26:31 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDI93963; Fri, 07 Feb 2014 16:26:30 +0000 (GMT) Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 7 Feb 2014 16:25:45 +0000 Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 7 Feb 2014 16:26:30 +0000 Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.21]) by dfweml706-chm.china.huawei.com ([169.254.8.193]) with mapi id 14.03.0158.001; Fri, 7 Feb 2014 08:26:24 -0800 From: Lucy yong To: "gorry@erg.abdn.ac.uk" , "tsvwg@ietf.org" Thread-Topic: propose the text change in draft-ietf-tsvwg-gre-in-udp Thread-Index: AQHPJCFXFYGgMgbPJEq6T+OuKXs9Xw== Date: Fri, 7 Feb 2014 16:26:24 +0000 Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4532A21C@dfweml701-chm.china.huawei.com> References: <52F12A0E.3060607@erg.abdn.ac.uk> <290E20B455C66743BE178C5C84F1240847E6334703@EXMB01CMS.surrey.ac.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.151.229] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: "draft-ietf-tsvwg-gre-in-udp-encap@tools.ietf.org" Subject: [tsvwg] propose the text change in draft-ietf-tsvwg-gre-in-udp X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 16:26:33 -0000 During WG adoption of the draft, we received comments about checksums and i= f this application follows the principles in RFC5405. Since then, there are= massive discussions on mpls mailing list on the same concern in mpls-in-ud= p. Based on the discussion consent/conclusion, authors could like propose f= ollowing changes in the gre-in-udp draft.=20 Replace: To simplify packet processing at the tunnel egress, packets destined to this assigned UDP destination port [TBD] SHOULD have their UDP checksum and Sequence flags set to zero because the egress tunnel only needs to identify this protocol. Although IPv6 [RFC2460] restricts the processing a packet with the UDP checksum of zero, [RFC6935] and [RFC6936] relax this constraint to allow the zero UDP checksum. With To simplify packet processing at the tunnel egress, packets destined to thi= s assigned UDP destination port [TBD] MAY have their UDP checksum set to ze= ro. In the environment where the UDP packets may be mis-delivered [RFC5405]= , UDP checksum SHOULD be used. For IPv6, the considerations described in de= tail in [RFC6935][RFC6936] MUST be examined if UDP checksum need to be disa= bled for performance or implementation concerns. The Sequence flags MUST se= t to zero. Replace: Note that the IPv6 header [RFC2460] contains a flow label field that may be used for load balancing in an IPv6 network [RFC6438]. Thus in an IPv6 network, either GRE-in-UDP or flow labels may be used in order to improve load balancing performance. Use of GRE-in-UDP encapsulation provides a unified hardware implementation for load balancing in an IP network independent of the IP version(s) in use. With: Note that the IPv6 header [RFC2460] contains a flow label field that may be used for load balancing in an IPv6 network [RFC6438]. Thus in an IPv6 network, either GRE-in-UDP or flow labels may be used in order to improve load balancing performance. Use of GRE-in-UDP encapsulation provides a unified hardware implementation for load balancing in an IP network independent of the IP version(s) in use. Howe= ver, if UDP checksum has to be used in an environment, a flow label based load balancing has advantage in term of performance and implementation. comments are welcome. Lucy on behalf of authors. =20 From gorry@erg.abdn.ac.uk Fri Feb 7 09:18:38 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B72751ACC87 for ; Fri, 7 Feb 2014 09:18:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.736 X-Spam-Level: X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 8lJG11Nvc7Sj for ; Fri, 7 Feb 2014 09:18:35 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5DA1A0203 for ; Fri, 7 Feb 2014 09:18:35 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id CF43D2B44D1; Fri, 7 Feb 2014 17:18:34 +0000 (GMT) Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 6B3492B4400; Fri, 7 Feb 2014 17:18:33 +0000 (GMT) Message-ID: <52F51569.8020501@erg.abdn.ac.uk> Date: Fri, 07 Feb 2014 17:18:33 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: tsvwg WG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: tsvwg chair Subject: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-dtls-encaps: To End 28th February 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 17:18:39 -0000 This email announces the start of a working group last call of draft-ietf-tsvwg-sctp-dtls-encaps-03, "DTLS Encapsulation of SCTP Packets". This document was discussed at the WG meeting in Vancouver and was thought at that meeting to be ready for WG review, this email starts this process by requesting review comments. Please send any comments, notes of support, or concerns to the TSVWG list. The draft is available at: http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps The last call will run for TWO weeks, ending 28th February 2014. James, David, and Gorry (TSVWG Chairs) tsvwg-chairs@ietf.org From david.black@emc.com Fri Feb 7 10:22:23 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2C81A04F5 for ; Fri, 7 Feb 2014 10:22:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.536 X-Spam-Level: X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, 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 TD-qTGao6Whe for ; Fri, 7 Feb 2014 10:22:22 -0800 (PST) Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 02A341A01B0 for ; Fri, 7 Feb 2014 10:22:21 -0800 (PST) Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s17IM6bl019784 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Feb 2014 13:22:07 -0500 X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s17IM6bl019784 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1391797328; bh=nP1NjM1tVNtUzgEZoOzpUKHbviw=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=n/ffXRxQGvHUYwrecS9f3d5sw9foBKHpR3HefdN6znAYJqXdyfTtYbYdfm06tlx2I 1eYJT7B/bhZvg2rlqu9sWPZXz9lXlZusSs1VjQX1A4gEgE494OUjJ6Y27O/kzHNoyV RgGg6LKya4tWkpiKxHn+iJDmJHYWkcXu75bZaaHs= X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com s17IM6bl019784 Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd53.lss.emc.com (RSA Interceptor); Fri, 7 Feb 2014 13:21:57 -0500 Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s17ILubd016406 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 7 Feb 2014 13:21:56 -0500 Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Fri, 7 Feb 2014 13:21:55 -0500 From: "Black, David" To: Lucy yong , "gorry@erg.abdn.ac.uk" , "tsvwg@ietf.org" Date: Fri, 7 Feb 2014 13:21:54 -0500 Thread-Topic: propose the text change in draft-ietf-tsvwg-gre-in-udp Thread-Index: AQHPJCFXFYGgMgbPJEq6T+OuKXs9X5qqC1OA Message-ID: <8D3D17ACE214DC429325B2B98F3AE712027105ABF3@MX15A.corp.emc.com> References: <52F12A0E.3060607@erg.abdn.ac.uk> <290E20B455C66743BE178C5C84F1240847E6334703@EXMB01CMS.surrey.ac.uk> <2691CE0099834E4A9C5044EEC662BB9D4532A21C@dfweml701-chm.china.huawei.com> In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D4532A21C@dfweml701-chm.china.huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com X-RSA-Classifications: public Cc: "draft-ietf-tsvwg-gre-in-udp-encap@tools.ietf.org" Subject: Re: [tsvwg] propose the text change in draft-ietf-tsvwg-gre-in-udp X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 18:22:23 -0000 Lucy, I think this text is a good start, however, I'm concerned that it leaves application of RFC 6935 and RFC 6936 as "an exercise to the reader": > To simplify packet processing at the tunnel egress, packets destined to t= his > assigned UDP destination port [TBD] MAY have their UDP checksum set to ze= ro. > In the environment where the UDP packets may be mis-delivered [RFC5405], = UDP > checksum SHOULD be used. For IPv6, the considerations described in detail= in > [RFC6935][RFC6936] MUST be examined if UDP checksum need to be disabled f= or > performance or implementation concerns. The Sequence flags MUST set to ze= ro. I don't have a problem with that text, but I also don't think that it suffi= ciently addresses the situation. Thanks, --David > -----Original Message----- > From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Lucy yong > Sent: Friday, February 07, 2014 11:26 AM > To: gorry@erg.abdn.ac.uk; tsvwg@ietf.org > Cc: draft-ietf-tsvwg-gre-in-udp-encap@tools.ietf.org > Subject: [tsvwg] propose the text change in draft-ietf-tsvwg-gre-in-udp >=20 > During WG adoption of the draft, we received comments about checksums and= if > this application follows the principles in RFC5405. Since then, there are > massive discussions on mpls mailing list on the same concern in mpls-in-u= dp. > Based on the discussion consent/conclusion, authors could like propose > following changes in the gre-in-udp draft. >=20 > Replace: >=20 > To simplify packet processing at the tunnel egress, packets destined > to this assigned UDP destination port [TBD] SHOULD have their UDP > checksum and Sequence flags set to zero because the egress tunnel > only needs to identify this protocol. Although IPv6 [RFC2460] > restricts the processing a packet with the UDP checksum of zero, > [RFC6935] and [RFC6936] relax this constraint to allow the zero UDP > checksum. >=20 > With > To simplify packet processing at the tunnel egress, packets destined to t= his > assigned UDP destination port [TBD] MAY have their UDP checksum set to ze= ro. > In the environment where the UDP packets may be mis-delivered [RFC5405], = UDP > checksum SHOULD be used. For IPv6, the considerations described in detail= in > [RFC6935][RFC6936] MUST be examined if UDP checksum need to be disabled f= or > performance or implementation concerns. The Sequence flags MUST set to ze= ro. >=20 > Replace: > Note that the IPv6 header [RFC2460] contains a flow label field that > may be used for load balancing in an IPv6 network [RFC6438]. Thus in > an IPv6 network, either GRE-in-UDP or flow labels may be used in > order to improve load balancing performance. Use of GRE-in-UDP > encapsulation provides a unified hardware implementation for load > balancing in an IP network independent of the IP version(s) in use. >=20 > With: > Note that the IPv6 header [RFC2460] contains a flow label field that > may be used for load balancing in an IPv6 network [RFC6438]. Thus in > an IPv6 network, either GRE-in-UDP or flow labels may be used in > order to improve load balancing performance. Use of GRE-in-UDP > encapsulation provides a unified hardware implementation for load > balancing in an IP network independent of the IP version(s) in use. > However, > if UDP checksum has to be used in an environment, a flow label based lo= ad > balancing has advantage in term of performance and implementation. >=20 > comments are welcome. >=20 > Lucy on behalf of authors. >=20 >=20 From gorry@erg.abdn.ac.uk Thu Feb 13 07:31:57 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACC81A02D7 for ; Thu, 13 Feb 2014 07:31:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.749 X-Spam-Level: X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 4MgZvfSS2rt6 for ; Thu, 13 Feb 2014 07:31:55 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id ED85A1A0215 for ; Thu, 13 Feb 2014 07:31:54 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 1FB452B451C; Thu, 13 Feb 2014 15:31:53 +0000 (GMT) Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2A3A92B4266 for ; Thu, 13 Feb 2014 15:31:52 +0000 (GMT) Message-ID: <52FCE567.5020502@erg.abdn.ac.uk> Date: Thu, 13 Feb 2014 15:31:51 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: tsvwg WG Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [tsvwg] TSVWG Agenda requests for IETF 89 Meeting X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 15:31:57 -0000 TSVWG has two slots allocated for London. If you have a draft you have revised recently and would like to be discussed at the meeting in London, please send your request for agenda time to the tsvwg chairs (tsvwg-chairs@ietf.org). Please include in the request, the title and file name of the draft, the speaker's name (and email), and how much time you think you will need. We will prioritise drafts that are working group items and drafts that have been actively discussed on the list. Drafts not discussed on the mailing list prior to the meeting, or drafts that do not appear to yet have support from the working group are unlikely to get time at the meeting. Regards, Gorry, James & David (TSVWG Co-Chairs) From nobody Thu Feb 13 10:23:47 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 658E11A03F6; Thu, 13 Feb 2014 10:23:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 f7GDnMlq-ndG; Thu, 13 Feb 2014 10:23:42 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C10B01A03D0; Thu, 13 Feb 2014 10:23:42 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140213182342.19399.18376.idtracker@ietfa.amsl.com> Date: Thu, 13 Feb 2014 10:23:42 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/WhznD-Fxwi2vmLjru29WC07_NLM Cc: tsvwg@ietf.org Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-gre-in-udp-encap-01.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 18:23:44 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : Generic UDP Encapsulation for IP Tunneling Authors : Edward Crabbe Lucy Yong Xiaohu Xu Filename : draft-ietf-tsvwg-gre-in-udp-encap-01.txt Pages : 13 Date : 2014-02-13 Abstract: This document describes a method of encapsulating arbitrary protocols within GRE and UDP headers. In this encapsulation, the source UDP port may be used as an entropy field for purposes of load balancing while the payload protocol may be identified by the GRE Protocol Type. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-gre-in-udp-encap-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Feb 14 03:54:43 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59F451A0239 for ; Fri, 14 Feb 2014 03:54:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] 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 rWN4ENl5CDnW for ; Fri, 14 Feb 2014 03:54:40 -0800 (PST) Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2201A0234 for ; Fri, 14 Feb 2014 03:54:37 -0800 (PST) Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s1EBsIX8011581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 14 Feb 2014 03:54:22 -0800 (PST) Message-ID: <52FE03EB.8020506@isi.edu> Date: Fri, 14 Feb 2014 03:54:19 -0800 From: Joe Touch User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: tsvwg@ietf.org References: <20140213182342.19399.18376.idtracker@ietfa.amsl.com> In-Reply-To: <20140213182342.19399.18376.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/hc9owpX20NIX1V7cQ8DSBIP14AU Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-gre-in-udp-encap-01.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 11:54:42 -0000 FWIW, Section 3 of this document should provide a more complete description of IPv4 header generation at the tunnel ingress, notably addressing ID generation as per RFC6864. There may be others issues in header processing; the current description seems more informal than I would expect from a protocol specification. Joe On 2/13/2014 10:23 AM, internet-drafts@ietf.org wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Transport Area Working Group Working Group of the IETF. > > Title : Generic UDP Encapsulation for IP Tunneling > Authors : Edward Crabbe > Lucy Yong > Xiaohu Xu > Filename : draft-ietf-tsvwg-gre-in-udp-encap-01.txt > Pages : 13 > Date : 2014-02-13 > > Abstract: > This document describes a method of encapsulating arbitrary > protocols within GRE and UDP headers. In this encapsulation, the > source UDP port may be used as an entropy field for purposes of load > balancing while the payload protocol may be identified by the GRE > Protocol Type. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/ > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-01 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-gre-in-udp-encap-01 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > From nobody Fri Feb 14 04:01:47 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8B21A0226 for ; Fri, 14 Feb 2014 04:01:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548] 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 Glp4vaug4x8K for ; Fri, 14 Feb 2014 04:01:41 -0800 (PST) Received: from tcmail33.telekom.de (tcmail33.telekom.de [80.149.113.247]) by ietfa.amsl.com (Postfix) with ESMTP id 6B52C1A021A for ; Fri, 14 Feb 2014 04:01:41 -0800 (PST) Received: from he113675.emea1.cds.t-internal.com ([10.134.99.28]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 14 Feb 2014 13:00:39 +0100 Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113675.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 14 Feb 2014 13:00:36 +0100 From: To: Date: Fri, 14 Feb 2014 13:00:35 +0100 Thread-Topic: New Version Notification - draft-geib-tsvwg-diffserv-intercon-05.txt Thread-Index: Ac8pc1tad4WagKHhSx6IaQc0J6v3bgACAumw Message-ID: Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/GZmxz1_mmb2fMB5VRlIe_N3tTKA Cc: tsvwg@ietf.org Subject: [tsvwg] WG: New Version Notification - draft-geib-tsvwg-diffserv-intercon-05.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 12:01:44 -0000 R29ycnksIGFsbCwNCg0KdmVyc2lvbiAtMDUgb2YgZGlmZnNlcnYtaW50ZXJjb24gc2F3IGEgbWFq b3IgcmV2aWV3LiBJdCBpcyBtb3JlIGZvY3VzZWQgb24gZXhwbGFpbmluZyB0aGUgcHJvcG9zZWQg c29sdXRpb24gYW5kIGhvdyBpdCBmaXRzIHdpdGggSUVURiBhbmQgb3RoZXIgc3RhbmRhcmRzLiAN Cg0KSSdkIGFwcHJlY2lhdGUgYSByZXZpZXcgYnkgYSB2b2x1bnRlZXIgYW5kIGNvbW1lbnRzIGlu IGdlbmVyYWwsIGFzIEknZCBsaWtlIHRvIGRpc2N1c3MgYWNjZXB0aW5nIHRoaXMgZG9jdW1lbnQg YXMgYSBXRyBkcmFmdCBhdCB0aGUgdXBjb21pbmcgbWVldGluZy4NCg0KUmVnYXJkcywNCg0KUnVl ZGlnZXINCg0KLS0tLS1VcnNwcsO8bmdsaWNoZSBOYWNocmljaHQtLS0tLQ0KVm9uOiBpbnRlcm5l dC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KR2Vz ZW5kZXQ6IEZyZWl0YWcsIDE0LiBGZWJydWFyIDIwMTQgMTE6NDcNCkFuOiBHZWliLCBSw7xkaWdl cjsgZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi1pbnRlcmNvbkB0b29scy5pZXRmLm9yZzsgbWxz LmlldGZAZ21haWwuY29tDQpCZXRyZWZmOiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gLSBkcmFm dC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA1LnR4dA0KDQoNCkEgbmV3IHZlcnNpb24g KC0wNSkgaGFzIGJlZW4gc3VibWl0dGVkIGZvciBkcmFmdC1nZWliLXRzdndnLWRpZmZzZXJ2LWlu dGVyY29uOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtZ2VpYi10 c3Z3Zy1kaWZmc2Vydi1pbnRlcmNvbi0wNS50eHQNCg0KDQpUaGUgSUVURiBkYXRhdHJhY2tlciBw YWdlIGZvciB0aGlzIEludGVybmV0LURyYWZ0IGlzOg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm Lm9yZy9kb2MvZHJhZnQtZ2VpYi10c3Z3Zy1kaWZmc2Vydi1pbnRlcmNvbi8NCg0KRGlmZiBmcm9t IHByZXZpb3VzIHZlcnNpb246DQpodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFm dC1nZWliLXRzdndnLWRpZmZzZXJ2LWludGVyY29uLTA1DQoNClBsZWFzZSBub3RlIHRoYXQgaXQg bWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24g dW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29s cy5pZXRmLm9yZy4NCg0KSUVURiBTZWNyZXRhcmlhdC4NCg0K From nobody Fri Feb 14 06:13:07 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9131A0298; Fri, 14 Feb 2014 06:13:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 7I95_Mma1MD6; Fri, 14 Feb 2014 06:12:59 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB581A028A; Fri, 14 Feb 2014 06:12:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.0.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140214141259.9414.66539.idtracker@ietfa.amsl.com> Date: Fri, 14 Feb 2014 06:12:59 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7FLwFyBeqaM8ggD07_sNqaRi9xY Cc: tsvwg@ietf.org Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-08.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 14:13:03 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Transport Area Working Group Working Group of the IETF. Title : Generic Aggregation of Resource ReSerVation Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains Authors : Georgios Karagiannis Anurag Bhargava Filename : draft-ietf-tsvwg-rsvp-pcn-08.txt Pages : 28 Date : 2014-02-14 Abstract: This document specifies extensions to Generic Aggregated RSVP RFC 4860 for support of the PCN Controlled Load (CL) and Single Marking (SM) edge behaviors over a Diffserv cloud using Pre- Congestion Notification. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rsvp-pcn-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Feb 14 06:26:12 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9402C1A0267 for ; Fri, 14 Feb 2014 06:26:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 0AprL3tExL8Z for ; Fri, 14 Feb 2014 06:26:03 -0800 (PST) Received: from out47-ams.mf.surf.net (out47-ams.mf.surf.net [145.0.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id DB23F1A027C for ; Fri, 14 Feb 2014 06:26:01 -0800 (PST) Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing2-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s1EEPxiG016959 for ; Fri, 14 Feb 2014 15:25:59 +0100 Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Fri, 14 Feb 2014 15:25:59 +0100 Received: from EXMBX23.ad.utwente.nl ([169.254.3.41]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Fri, 14 Feb 2014 15:25:58 +0100 From: To: Thread-Topic: submitted draft-ietf-tsvwg-rsvp-pcn-08.txt Thread-Index: Ac8pkKyBozy+GP/4S162ksZact1LMg== Date: Fri, 14 Feb 2014 14:25:57 +0000 Message-ID: References: <20140214141259.9414.66539.idtracker@ietfa.amsl.com> In-Reply-To: <20140214141259.9414.66539.idtracker@ietfa.amsl.com> Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mimectl: Produced By Microsoft Exchange V14.2.247.1 x-originating-ip: [86.91.134.3] Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42076DEXMBX23adutwent_" MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN) X-CanIt-Geo: ip=130.89.5.49; country=NL; region=15; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6 X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default) X-Canit-Stats-ID: 0vLqepXS3 - 022d0a6e06ef - 20140214 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/ZnYDSANOoo1F_8loIc1YyBgodKg Subject: [tsvwg] submitted draft-ietf-tsvwg-rsvp-pcn-08.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 14:26:06 -0000 --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42076DEXMBX23adutwent_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, Version 8 of the draft-ietf-tsvwg-rsvp-pcn draft has just been submitted, s= ee below! This version worked out all comments received during the tsvwg IETF 88 meet= ing (in Vancouver) regarding the need of better integrating the RSVP model into the RSVP over PCN signaling = protoicol. Francois contributed signifficantly to realise this version of the draft wi= th comments and text. A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp-pcn-08 Best regards, Georgios ________________________________ Van: tsvwg [tsvwg-bounces@ietf.org] namens internet-drafts@ietf.org [intern= et-drafts@ietf.org] Verzonden: vrijdag 14 februari 2014 15:12 To: i-d-announce@ietf.org Cc: tsvwg@ietf.org Onderwerp: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-08.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Transport Area Working Group Working Grou= p of the IETF. Title : Generic Aggregation of Resource ReSerVation Proto= col (RSVP) for IPv4 And IPv6 Reservations over PCN domains Authors : Georgios Karagiannis Anurag Bhargava Filename : draft-ietf-tsvwg-rsvp-pcn-08.txt Pages : 28 Date : 2014-02-14 Abstract: This document specifies extensions to Generic Aggregated RSVP RFC 4860 for support of the PCN Controlled Load (CL) and Single Marking (SM) edge behaviors over a Diffserv cloud using Pre- Congestion Notification. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp-pcn-08 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42076DEXMBX23adutwent_ Content-Type: text/html; charset="iso-8859-1" Content-ID: <00DC5BEC8D088E46B47DB999927ED8ED@exchange.utwente.nl> Content-Transfer-Encoding: quoted-printable

Hi all,

 

Version 8 of the draft-ietf-tsvwg-rsvp-pcn draft has just been subm= itted, see below!

 

This version worked out all comments received during the tsvwg IETF 88 m= eeting (in Vancouver) regarding the

need of better integrating the RSVP model into the RSVP over PCN signali= ng protoicol.

 

Francois contributed signifficantly to realise this version of the draft= with comments and text.

 

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp= -pcn-08

Best regards,

Georgios

 

 

 

Van: tsvwg [tsvwg-bounces@ietf.org] namens internet-drafts@ietf.= org [internet-drafts@ietf.org]
Verzonden: vrijdag 14 februari 2014 15:12
To: i-d-announce@ietf.org
Cc: tsvwg@ietf.org
Onderwerp: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
 This draft is a work item of the Transport Area Working Group Working= Group of the IETF.

        Title    &nb= sp;      : Generic Aggregation of Resource ReSerVa= tion Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains
        Authors    &= nbsp;    : Georgios Karagiannis
            &nb= sp;            = Anurag Bhargava
        Filename    =     : draft-ietf-tsvwg-rsvp-pcn-08.txt
        Pages    &nb= sp;      : 28
        Date    &nbs= p;       : 2014-02-14

Abstract:
   This document specifies extensions to Generic Aggregated RSVP<= br>    RFC 4860 for support of the PCN Controlled Load (CL) and Singl= e
   Marking (SM) edge behaviors over a Diffserv cloud using Pre-    Congestion Notification.





The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/<= /a>

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp= -pcn-08


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42076DEXMBX23adutwent_-- From nobody Fri Feb 14 07:45:40 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2CC1A0293 for ; Fri, 14 Feb 2014 07:45:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.749 X-Spam-Level: X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 qvDMXVul1fb3 for ; Fri, 14 Feb 2014 07:45:36 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5A97D1A026E for ; Fri, 14 Feb 2014 07:45:36 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBD32131; Fri, 14 Feb 2014 15:45:34 +0000 (GMT) Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 14 Feb 2014 15:41:08 +0000 Received: from DFWEML702-CHM.china.huawei.com (10.193.5.72) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 14 Feb 2014 15:41:28 +0000 Received: from DFWEML701-CHM.china.huawei.com ([169.254.1.21]) by dfweml702-chm.china.huawei.com ([169.254.4.231]) with mapi id 14.03.0158.001; Fri, 14 Feb 2014 07:41:21 -0800 From: Lucy yong To: Joe Touch , "tsvwg@ietf.org" Thread-Topic: [tsvwg] I-D Action: draft-ietf-tsvwg-gre-in-udp-encap-01.txt Thread-Index: AQHPKOjQcQrAGZmDb0urWHnZibsvSZq1K0aA//+49IA= Date: Fri, 14 Feb 2014 15:41:20 +0000 Message-ID: <2691CE0099834E4A9C5044EEC662BB9D4532F1B4@dfweml701-chm.china.huawei.com> References: <20140213182342.19399.18376.idtracker@ietfa.amsl.com> <52FE03EB.8020506@isi.edu> In-Reply-To: <52FE03EB.8020506@isi.edu> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.148.108] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/suGgB003DphCXhR7YDv9jLewrvM Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-gre-in-udp-encap-01.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 15:45:39 -0000 SGkgSm9lLA0KDQpUaGFuayB5b3UgdmVyeSBtdWNoIGZvciB0aGUgZm9sbG93aW5nIGNvbW1lbnQu IFdlIHdpbGwgZXhwYW5kIGRlc2NyaXB0aW9uIGluIG5leHQgdmVyc2lvbi4gWW91ciBhZHZpY2Ug aXMgaGlnaGx5IGFwcHJlY2lhdGVkLg0KDQpSZWdhcmQsDQpMdWN5DQoNCi0tLS0tT3JpZ2luYWwg TWVzc2FnZS0tLS0tDQpGcm9tOiB0c3Z3ZyBbbWFpbHRvOnRzdndnLWJvdW5jZXNAaWV0Zi5vcmdd IE9uIEJlaGFsZiBPZiBKb2UgVG91Y2gNClNlbnQ6IEZyaWRheSwgRmVicnVhcnkgMTQsIDIwMTQg NTo1NCBBTQ0KVG86IHRzdndnQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3RzdndnXSBJLUQgQWN0 aW9uOiBkcmFmdC1pZXRmLXRzdndnLWdyZS1pbi11ZHAtZW5jYXAtMDEudHh0DQoNCkZXSVcsIFNl Y3Rpb24gMyBvZiB0aGlzIGRvY3VtZW50IHNob3VsZCBwcm92aWRlIGEgbW9yZSBjb21wbGV0ZSBk ZXNjcmlwdGlvbiBvZiBJUHY0IGhlYWRlciBnZW5lcmF0aW9uIGF0IHRoZSB0dW5uZWwgaW5ncmVz cywgbm90YWJseSBhZGRyZXNzaW5nIElEIGdlbmVyYXRpb24gYXMgcGVyIFJGQzY4NjQuDQoNClRo ZXJlIG1heSBiZSBvdGhlcnMgaXNzdWVzIGluIGhlYWRlciBwcm9jZXNzaW5nOyB0aGUgY3VycmVu dCBkZXNjcmlwdGlvbiBzZWVtcyBtb3JlIGluZm9ybWFsIHRoYW4gSSB3b3VsZCBleHBlY3QgZnJv bSBhIHByb3RvY29sIHNwZWNpZmljYXRpb24uDQoNCkpvZQ0KDQpPbiAyLzEzLzIwMTQgMTA6MjMg QU0sIGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyB3cm90ZToNCj4NCj4gQSBOZXcgSW50ZXJuZXQt RHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVj dG9yaWVzLg0KPiAgIFRoaXMgZHJhZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIFRyYW5zcG9ydCBB cmVhIFdvcmtpbmcgR3JvdXAgV29ya2luZyBHcm91cCBvZiB0aGUgSUVURi4NCj4NCj4gICAgICAg ICAgVGl0bGUgICAgICAgICAgIDogR2VuZXJpYyBVRFAgRW5jYXBzdWxhdGlvbiBmb3IgSVAgVHVu bmVsaW5nDQo+ICAgICAgICAgIEF1dGhvcnMgICAgICAgICA6IEVkd2FyZCBDcmFiYmUNCj4gICAg ICAgICAgICAgICAgICAgICAgICAgICAgTHVjeSBZb25nDQo+ICAgICAgICAgICAgICAgICAgICAg ICAgICAgIFhpYW9odSBYdQ0KPiAJRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi10c3Z3Zy1n cmUtaW4tdWRwLWVuY2FwLTAxLnR4dA0KPiAJUGFnZXMgICAgICAgICAgIDogMTMNCj4gCURhdGUg ICAgICAgICAgICA6IDIwMTQtMDItMTMNCj4NCj4gQWJzdHJhY3Q6DQo+ICAgICBUaGlzIGRvY3Vt ZW50IGRlc2NyaWJlcyBhIG1ldGhvZCBvZiBlbmNhcHN1bGF0aW5nIGFyYml0cmFyeQ0KPiAgICAg cHJvdG9jb2xzIHdpdGhpbiBHUkUgYW5kIFVEUCBoZWFkZXJzLiAgSW4gdGhpcyBlbmNhcHN1bGF0 aW9uLCB0aGUNCj4gICAgIHNvdXJjZSBVRFAgcG9ydCBtYXkgYmUgdXNlZCBhcyBhbiBlbnRyb3B5 IGZpZWxkIGZvciBwdXJwb3NlcyBvZiBsb2FkDQo+ICAgICBiYWxhbmNpbmcgd2hpbGUgdGhlIHBh eWxvYWQgcHJvdG9jb2wgbWF5IGJlIGlkZW50aWZpZWQgYnkgdGhlIEdSRQ0KPiAgICAgUHJvdG9j b2wgVHlwZS4NCj4NCj4NCj4gVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRo aXMgZHJhZnQgaXM6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWll dGYtdHN2d2ctZ3JlLWluLXVkcC1lbmNhcC8NCj4NCj4gVGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQg dmVyc2lvbiBhdmFpbGFibGUgYXQ6DQo+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0 LWlldGYtdHN2d2ctZ3JlLWluLXVkcC1lbmNhcC0wMQ0KPg0KPiBBIGRpZmYgZnJvbSB0aGUgcHJl dmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZj ZGlmZj91cmwyPWRyYWZ0LWlldGYtdHN2d2ctZ3JlLWluLXVkcC1lbmNhcC0wMQ0KPg0KPg0KPiBQ bGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUg dGltZSBvZiANCj4gc3VibWlzc2lvbiB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlm ZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPg0KPiBJbnRlcm5ldC1EcmFmdHMg YXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+IGZ0cDovL2Z0cC5pZXRm Lm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+DQoNCg== From nobody Mon Feb 17 10:00:41 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C5F1A03F6 for ; Mon, 17 Feb 2014 10:00:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.749 X-Spam-Level: X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 yQyZJKBdj5ZZ for ; Mon, 17 Feb 2014 10:00:37 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 72E3B1A0522 for ; Mon, 17 Feb 2014 10:00:37 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 44FED2B439A; Mon, 17 Feb 2014 18:00:34 +0000 (GMT) Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9C40D2B40D1 for ; Mon, 17 Feb 2014 18:00:33 +0000 (GMT) Message-ID: <53024E41.9090901@erg.abdn.ac.uk> Date: Mon, 17 Feb 2014 18:00:33 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: tsvwg WG References: <530232BD.4080508@erg.abdn.ac.uk> In-Reply-To: <530232BD.4080508@erg.abdn.ac.uk> X-Forwarded-Message-Id: <530232BD.4080508@erg.abdn.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/Lo7Uq-DChlu97XvIuQY74IAHOFs Subject: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 18:00:39 -0000 The authors of " Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted as TSVWG item. The IETF-88 meeting and following mailing list threads 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 they have sufficient energy to complete this work in TSVWG. * PLEASE send an email to this list if you think adopting this document in TSVWG is a good **OR** bad idea. * Please indicate if you are willing to REVIEW such a document during its development. Please send al notes of support/comments to the TSVWG list of chairs by the date above. Best wishes, Gorry, David and James. (TSVWG Co-Chairs) From nobody Mon Feb 17 15:48:15 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109F81A02A7; Mon, 17 Feb 2014 15:48:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.049 X-Spam-Level: X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 4WjRiGDO7ikx; Mon, 17 Feb 2014 15:48:09 -0800 (PST) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 23B0E1A05AB; Mon, 17 Feb 2014 15:48:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1761; q=dns/txt; s=iport; t=1392680880; x=1393890480; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=QoqWk12fundKaB/HrLol/DN8rhh9nUsC5AmVGElQyHg=; b=ZgzjjuTnmiabJGcYKzizeQqpx8T5Sh7bngACDfwmongiKI0nM4jC3MMG osdumeNOwwynm3HPIW1ayy74LMI45cv/8PuHjhTN0ai3Kp/iw0vUwvbt7 Rtmgbt6b7pfh4W/FG8aIVXdvVcqfW1p5GWuV1Z1GvEnxKHxDLpGugc8St 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhkFAMyeAlOtJV2a/2dsb2JhbABZgwY4V8BgFnSCJQEBAQQBAQFrHQEIOzILGwEGBQQBEogFDco+F44thRMEiRCPHIEykHGBb4E+gio X-IronPort-AV: E=Sophos;i="4.95,863,1384300800"; d="scan'208";a="21133022" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-5.cisco.com with ESMTP; 17 Feb 2014 23:48:00 +0000 Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1HNlxS3001507 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 17 Feb 2014 23:48:00 GMT Received: from xmb-aln-x08.cisco.com ([169.254.3.8]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 17 Feb 2014 17:47:59 -0600 From: "Charles Eckel (eckelcu)" To: "int-area@ietf.org" , "tsvwg@ietf.org" Thread-Topic: [Aeon] Time slots for AEON session at IETF 89 - Please indicate available via link below by Wed. Feb 19 Thread-Index: AQHPLDqvmtNJ9L8wukKWAsGpI1Inkg== Date: Mon, 17 Feb 2014 23:47:59 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [10.21.79.36] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/BUDMI5Mpq1FUEYkM7mKpbuB_PUQ Subject: [tsvwg] FW: [Aeon] Time slots for AEON session at IETF 89 - Please indicate available via link below by Wed. Feb 19 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2014 23:48:13 -0000 Just an FYI, we posted and presented the following draft at previous IETF meetings: A Framework for Signaling Flow Characteristics between Applications and the Network=20 (http://tools.ietf.org/html/draft-eckert-intarea-flow-metadata-framework-02 ) We have taken the feedback from this and created two new drafts, focusing on the problem statement and use cases, respectively: "Application Enabled Open Networking: Problem Statement and Requirements=B2= , draft-eckel-aeon-problem-statement-00 (http://tools.ietf.org/html/draft-eckel-aeon-problem-statement-00) "Application Enabled Open Networking Use Cases=B2, draft-eckel-aeon-use-cases-01 (http://tools.ietf.org/html/draft-eckel-aeon-use-cases-01) If you are interested in this area, you should consider subscribing to the AEON list and attending the meeting we are planning at IETF 89, as announced in the forwarded e-mail. Cheers, Charles On 2/17/14, 10:12 AM, "Charles Eckel (eckelcu)" wrote: >AEON list members and other interested parties, > >We plan to reserve an IESG breakout room to have an AEON meeting at IETF >89 in London. >Please indicate which of the potential time slots work for you no later >than Wednesday, Feb 19. >All time slots are 1 hour in duration. >The actual location and time will be announced on the AEON list. > > >Preliminary agenda is as follows: >1) problem statement draft >2) draft charter > >The agenda will be finalized via a separate thread on the AEON list as >well. >Here is the link to the poll: >http://www.doodle.com/fb8k5hyqap4iqyye > > >Cheers, >Charles > >_______________________________________________ >Aeon mailing list >Aeon@ietf.org >https://www.ietf.org/mailman/listinfo/aeon From nobody Mon Feb 17 23:22:39 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41F21A05E9 for ; Mon, 17 Feb 2014 23:22:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.798 X-Spam-Level: X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] 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 EQ_VnEd1_MtQ for ; Mon, 17 Feb 2014 23:22:34 -0800 (PST) Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 779C61A00FD for ; Mon, 17 Feb 2014 23:22:34 -0800 (PST) Received: from he113656.emea1.cds.t-internal.com ([10.134.99.16]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 18 Feb 2014 08:22:30 +0100 Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE113656.emea1.cds.t-internal.com ([10.134.99.16]) with mapi; Tue, 18 Feb 2014 08:22:30 +0100 From: To: Date: Tue, 18 Feb 2014 08:22:28 +0100 Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: Ac8sCj36mOM5oni4SWylJSX9qDPMawAb8SHw Message-ID: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/9Pi-p_iysZuqNoTswP6kxKZ7jEw Cc: tsvwg@ietf.org Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 07:22:37 -0000 Gorry, I support making this a WG draft. If my time allows, I will review it, but I can't promise doing that continu= ously. Regards, Ruediger -----Urspr=FCngliche Nachricht----- Von: tsvwg [mailto:tsvwg-bounces@ietf.org] Im Auftrag von Gorry Fairhurst Gesendet: Montag, 17. Februar 2014 19:01 An: tsvwg WG Betreff: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-enca= p-guidelines - to end 4th March 2014 The authors of " Guidelines for Adding Congestion Notification to Protocols= that Encapsulate IP"=20 (draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted as = TSVWG item. The IETF-88 meeting and following mailing list threads 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 they have sufficient energy to com= plete this work in TSVWG. * PLEASE send an email to this list if you think adopting this document in = TSVWG is a good **OR** bad idea. * Please indicate if you are willing to REVIEW such a document during its d= evelopment. Please send al notes of support/comments to the TSVWG list of chairs by the= date above. Best wishes, Gorry, David and James. (TSVWG Co-Chairs) From nobody Tue Feb 18 01:10:40 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52DA31A00AF for ; Tue, 18 Feb 2014 01:10:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.451 X-Spam-Level: X-Spam-Status: No, score=0.451 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, MIME_CHARSET_FARAWAY=2.45, 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 mP6ir7VzMIJ3 for ; Tue, 18 Feb 2014 01:10:36 -0800 (PST) Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA791A00A6 for ; Tue, 18 Feb 2014 01:10:36 -0800 (PST) Received: by mail-vc0-f170.google.com with SMTP id hu8so13075420vcb.29 for ; Tue, 18 Feb 2014 01:10: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=6xoSfycD+NqDPv/QW+1DXLeu8TdxQgNhFgHyZBa4fvs=; b=dYEKlQ7swiz0VcndMy7vDPfHvg+UtDh6ZA6uHf4yBH57R93glViFZoAbDPlhE9YX/9 i+YccaEyYuawRyn16jrTiQhbKTasSZGJtgEC4L+jG3nyzJTS5wnR8ItGC1h+j/7hh7JD uUxAlQ/yFWU1AaVD/qWiUrmxheWLfOuUggtZ0Z2oQ3b1p/e+5vVE66ObHz7P2Nv46sn9 thHBtQOru2lgm9k/zpBS4/bxcgwdM5ls1vy0dBtwL+IL6ut3ZkfBlqP7oM36KVeHr0ND FDtqrf16UpUCnl4Xtj8yZcGUzm2cGH/n2Nx+ntYC5YkmK5WC9+bhdiWjZcW16sLEm0al YRJg== MIME-Version: 1.0 X-Received: by 10.220.106.84 with SMTP id w20mr20361081vco.18.1392714633242; Tue, 18 Feb 2014 01:10:33 -0800 (PST) Received: by 10.58.100.212 with HTTP; Tue, 18 Feb 2014 01:10:33 -0800 (PST) In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk> References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> Date: Tue, 18 Feb 2014 17:10:33 +0800 Message-ID: From: lingli deng To: gorry@erg.abdn.ac.uk Content-Type: multipart/alternative; boundary=047d7b3435c0fceb7204f2aaa454 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/yp-qaTjEBloSS372UDB1tBoU-W8 Cc: tsvwg WG Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 09:10:38 -0000 --047d7b3435c0fceb7204f2aaa454 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable Hi Gorry, I support its adoption, and I am willing to review it. BR Lingli 2014-02-18 2:00 GMT+08:00 Gorry Fairhurst : > > The authors of " Guidelines for Adding Congestion Notification to > Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-guidelines) > request that this is adopted as TSVWG item. > > The IETF-88 meeting and following mailing list threads 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 they have sufficient energy to > complete this work in TSVWG. > > * PLEASE send an email to this list if you think adopting this document > in TSVWG is a good **OR** bad idea. > > * Please indicate if you are willing to REVIEW such a document during > its development. > > > Please send al notes of support/comments to the TSVWG list of chairs by > the date above. > > Best wishes, > > Gorry, David and James. > (TSVWG Co-Chairs) > > > --=20 =B5=CB=C1=E9=C0=F2/Lingli Deng =D6=D0=B9=FA=D2=C6=B6=AF=CD=A8=D0=C5=D1=D0=BE=BF=D4=BA/China Mobile Researc= h Institute e-mail: denglingli@chinamobile.com tel: 15801696688-3367 mobile: 13810597148 --047d7b3435c0fceb7204f2aaa454 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable
Hi Gorry,

I support its adop= tion, and I am willing to review it.

BR
= Lingli


2014-02-18 2:00 GMT+08:00 Gorry Fairhurst <gorry@erg.abdn.ac.uk>= :

The authors of " Guidelines for Adding Congestion Notification to
Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-g= uidelines) request that this is adopted as TSVWG item.

The IETF-88 meeting and following mailing list threads indicated some WG &n= bsp;support for this, so we are now ready to make a formal decision and thi= s email is to allow people to confirm that they have sufficient energy to c= omplete this work in TSVWG.

* PLEASE send an email to this list if you think adopting this document
in TSVWG is a good **OR** bad idea.

* Please indicate if you are willing to REVIEW such a document during
its development.


Please send al notes of support/comments to the TSVWG list of chairs by
the date above.

Best wishes,

Gorry, David and James.
(TSVWG Co-Chairs)





--
=B5=CB=C1=E9=C0=F2/Ling= li Deng
=D6=D0=B9=FA=D2=C6=B6=AF=CD=A8=D0=C5=D1=D0=BE=BF=D4=BA/China Mob= ile Research Institute
e-mail: denglingli@chinamobile.com
tel: 15801696688-3367
mobile: 13810597148
--047d7b3435c0fceb7204f2aaa454-- From nobody Tue Feb 18 01:50:53 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4501A032B for ; Tue, 18 Feb 2014 01:50:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.298 X-Spam-Level: X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 d33Nj90hgeSN for ; Tue, 18 Feb 2014 01:50:41 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D035E1A0126 for ; Tue, 18 Feb 2014 01:50:40 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBG09092; Tue, 18 Feb 2014 09:50:37 +0000 (GMT) Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 18 Feb 2014 09:50:28 +0000 Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 18 Feb 2014 09:50:35 +0000 Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Tue, 18 Feb 2014 17:50:27 +0800 From: "Zhulei (A)" To: lingli deng , "gorry@erg.abdn.ac.uk" Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: AQHPLAo62icm/rnNnEKtB1n8XmGhfpq6NF2AgACQwY0= Date: Tue, 18 Feb 2014 09:50:26 +0000 Message-ID: <470F27D1263A1B4EB73491ED995DE625258977B9@NKGEML512-MBS.china.huawei.com> References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk>, In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.202.10.4] Content-Type: multipart/alternative; boundary="_000_470F27D1263A1B4EB73491ED995DE625258977B9NKGEML512MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/rXAb0PkQohQ6t585KSOowr5u6YQ Cc: tsvwg WG Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2014 09:50:46 -0000 --_000_470F27D1263A1B4EB73491ED995DE625258977B9NKGEML512MBSchi_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGkgQ2hhaXJzIGFuZCBhbGwsDQoNCg0KDQpJIHN1cHBvcnQgZG8gYWRvcHRpb24gdG8gZHJhZnQt YnJpc2NvZS10c3Z3Zy1lY24tZW5jYXAtZ3VpZGVsaW5lcy4NCg0KDQoNCkJyLA0KDQpaaHUgTGVp DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQq3orz+yMs6IHRzdndnIFt0c3Z3 Zy1ib3VuY2VzQGlldGYub3JnXSC0+rHtIGxpbmdsaSBkZW5nIFtkZW5nbGluZ2xpQGdtYWlsLmNv bV0NCreiy83KsbzkOiAyMDE0xOoy1MIxOMjVIDE3OjEwDQrK1bz+yMs6IGdvcnJ5QGVyZy5hYmRu LmFjLnVrDQqzrcvNOiB0c3Z3ZyBXRw0K1vfM4jogUmU6IFt0c3Z3Z10gRndkOiBDQUxMIEZPUiBB RE9QVElPTiBUU1ZXRzogZHJhZnQtYnJpc2NvZS10c3Z3Zy1lY24tZW5jYXAtZ3VpZGVsaW5lcyAt IHRvIGVuZCA0dGggTWFyY2ggMjAxNA0KDQpIaSBHb3JyeSwNCg0KSSBzdXBwb3J0IGl0cyBhZG9w dGlvbiwgYW5kIEkgYW0gd2lsbGluZyB0byByZXZpZXcgaXQuDQoNCkJSDQpMaW5nbGkNCg0KDQoy MDE0LTAyLTE4IDI6MDAgR01UKzA4OjAwIEdvcnJ5IEZhaXJodXJzdCA8Z29ycnlAZXJnLmFiZG4u YWMudWs8bWFpbHRvOmdvcnJ5QGVyZy5hYmRuLmFjLnVrPj46DQoNClRoZSBhdXRob3JzIG9mICIg R3VpZGVsaW5lcyBmb3IgQWRkaW5nIENvbmdlc3Rpb24gTm90aWZpY2F0aW9uIHRvDQpQcm90b2Nv bHMgdGhhdCBFbmNhcHN1bGF0ZSBJUCIgKGRyYWZ0LWJyaXNjb2UtdHN2d2ctZWNuLWVuY2FwLWd1 aWRlbGluZXMpIHJlcXVlc3QgdGhhdCB0aGlzIGlzIGFkb3B0ZWQgYXMgVFNWV0cgaXRlbS4NCg0K VGhlIElFVEYtODggbWVldGluZyBhbmQgZm9sbG93aW5nIG1haWxpbmcgbGlzdCB0aHJlYWRzIGlu ZGljYXRlZCBzb21lIFdHICBzdXBwb3J0IGZvciB0aGlzLCBzbyB3ZSBhcmUgbm93IHJlYWR5IHRv IG1ha2UgYSBmb3JtYWwgZGVjaXNpb24gYW5kIHRoaXMgZW1haWwgaXMgdG8gYWxsb3cgcGVvcGxl IHRvIGNvbmZpcm0gdGhhdCB0aGV5IGhhdmUgc3VmZmljaWVudCBlbmVyZ3kgdG8gY29tcGxldGUg dGhpcyB3b3JrIGluIFRTVldHLg0KDQoqIFBMRUFTRSBzZW5kIGFuIGVtYWlsIHRvIHRoaXMgbGlz dCBpZiB5b3UgdGhpbmsgYWRvcHRpbmcgdGhpcyBkb2N1bWVudA0KaW4gVFNWV0cgaXMgYSBnb29k ICoqT1IqKiBiYWQgaWRlYS4NCg0KKiBQbGVhc2UgaW5kaWNhdGUgaWYgeW91IGFyZSB3aWxsaW5n IHRvIFJFVklFVyBzdWNoIGEgZG9jdW1lbnQgZHVyaW5nDQppdHMgZGV2ZWxvcG1lbnQuDQoNCg0K UGxlYXNlIHNlbmQgYWwgbm90ZXMgb2Ygc3VwcG9ydC9jb21tZW50cyB0byB0aGUgVFNWV0cgbGlz dCBvZiBjaGFpcnMgYnkNCnRoZSBkYXRlIGFib3ZlLg0KDQpCZXN0IHdpc2hlcywNCg0KR29ycnks IERhdmlkIGFuZCBKYW1lcy4NCihUU1ZXRyBDby1DaGFpcnMpDQoNCg0KDQoNCg0KLS0NCrXLwenA 8i9MaW5nbGkgRGVuZw0K1tC5+tLGtq/NqNDF0dC+v9S6L0NoaW5hIE1vYmlsZSBSZXNlYXJjaCBJ bnN0aXR1dGUNCmUtbWFpbDogZGVuZ2xpbmdsaUBjaGluYW1vYmlsZS5jb208bWFpbHRvOmRlbmds aW5nbGlAY2hpbmFtb2JpbGUuY29tPg0KdGVsOiAxNTgwMTY5NjY4OC0zMzY3DQptb2JpbGU6IDEz ODEwNTk3MTQ4DQo= --_000_470F27D1263A1B4EB73491ED995DE625258977B9NKGEML512MBSchi_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi Chairs and all,

 

I support do adoption to draft-briscoe-tsvwg-ecn-encap-guidelines.

 

Br,

Zhu Lei

=B7=A2=BC=FE=C8=CB: tsvwg [tsvwg-bounces@i= etf.org] =B4=FA=B1=ED lingli deng [denglingli@gmail.com]
=B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA2=D4=C218=C8=D5 17:10
=CA=D5=BC=FE=C8=CB: gorry@erg.abdn.ac.uk
=B3=AD=CB=CD: tsvwg WG
=D6=F7=CC=E2: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-brisco= e-tsvwg-ecn-encap-guidelines - to end 4th March 2014

Hi Gorry,

I support its adoption, and I am willing to review it.

BR
Lingli


2014-02-18 2:00 GMT+08:00 Gorry Fairhurst <gorry@erg.abd= n.ac.uk>:

The authors of " Guidelines for Adding Congestion Notification to
Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-g= uidelines) request that this is adopted as TSVWG item.

The IETF-88 meeting and following mailing list threads indicated some WG &n= bsp;support for this, so we are now ready to make a formal decision and thi= s email is to allow people to confirm that they have sufficient energy to c= omplete this work in TSVWG.

* PLEASE send an email to this list if you think adopting this document
in TSVWG is a good **OR** bad idea.

* Please indicate if you are willing to REVIEW such a document during
its development.


Please send al notes of support/comments to the TSVWG list of chairs by
the date above.

Best wishes,

Gorry, David and James.
(TSVWG Co-Chairs)





--
=B5=CB=C1=E9=C0=F2/Lingli Deng
=D6=D0=B9=FA=D2=C6=B6=AF=CD=A8=D0=C5=D1=D0=BE=BF=D4=BA/China Mobile Researc= h Institute
e-mail: den= glingli@chinamobile.com
tel: 15801696688-3367
mobile: 13810597148
--_000_470F27D1263A1B4EB73491ED995DE625258977B9NKGEML512MBSchi_-- From nobody Tue Feb 18 17:25:16 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE92D1A01FC for ; Tue, 18 Feb 2014 17:25:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.749 X-Spam-Level: X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 A6kQShcfsmTh for ; Tue, 18 Feb 2014 17:25:13 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 077B01A00F5 for ; Tue, 18 Feb 2014 17:25:12 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDS60126; Wed, 19 Feb 2014 01:25:09 +0000 (GMT) Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:24:59 +0000 Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:25:08 +0000 Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.27]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 19 Feb 2014 09:25:02 +0800 From: Weixinpeng To: "gorry@erg.abdn.ac.uk" , tsvwg WG Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: AQHPLAo82icm/rnNnEKtB1n8XmGhfpq7yg1Q Date: Wed, 19 Feb 2014 01:25:01 +0000 Message-ID: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.76.176] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/EorTPS2ribwHuPWDq2a7-RL5eMY Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 01:25:15 -0000 Hi Gorry and all, I support this document and I think adopting this document in TSVWG is a go= od idea. Best Regards, Xinpeng Wei >-----Original Message----- >From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Gorry Fairhurst >Sent: Tuesday, February 18, 2014 2:01 AM >To: tsvwg WG >Subject: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: >draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 > > >The authors of " Guidelines for Adding Congestion Notification to Protocol= s >that Encapsulate IP" >(draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted as >TSVWG item. > >The IETF-88 meeting and following mailing list threads 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 they have sufficient energy to >complete this work in TSVWG. > >* PLEASE send an email to this list if you think adopting this document in >TSVWG is a good **OR** bad idea. > >* Please indicate if you are willing to REVIEW such a document during its >development. > > >Please send al notes of support/comments to the TSVWG list of chairs by th= e >date above. > >Best wishes, > >Gorry, David and James. >(TSVWG Co-Chairs) > From nobody Tue Feb 18 17:30:39 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1C3C1A020D for ; Tue, 18 Feb 2014 17:30:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.748 X-Spam-Level: X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 W6ura3ry0khf for ; Tue, 18 Feb 2014 17:30:35 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0B31A0024 for ; Tue, 18 Feb 2014 17:30:35 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBG70740; Wed, 19 Feb 2014 01:30:31 +0000 (GMT) Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:30:20 +0000 Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 19 Feb 2014 01:30:29 +0000 Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.27]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Wed, 19 Feb 2014 09:30:24 +0800 From: Weixinpeng To: "tsvwg@ietf.org" Thread-Topic: A new version draft about network based congestion control. Thread-Index: Ac8tEieo8WPpWv5rQFCpN7Q5ZCN1oQ== Date: Wed, 19 Feb 2014 01:30:24 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.76.176] Content-Type: multipart/alternative; boundary="_000_C5C3BB522B1DDF478AA09545169155B46D7EB64Bnkgeml507mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/IjKkiMwOZKN022n5JLqOBgQQT6c Subject: [tsvwg] A new version draft about network based congestion control. X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 01:30:38 -0000 --_000_C5C3BB522B1DDF478AA09545169155B46D7EB64Bnkgeml507mbxchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, A new version draft about network based congestion control has been submitt= ed. In this document we add the congestion control in NFV scenario. Any comments on this draft are welcomed. http://www.ietf.org/internet-drafts/draft-wei-tsvwg-tunnel-congestion-feedb= ack-01.txt BR Xipeng Wei --_000_C5C3BB522B1DDF478AA09545169155B46D7EB64Bnkgeml507mbxchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

A new version draft about netwo= rk based congestion control has been submitted. In this document we add the= congestion control in NFV scenario.

Any comments on this draft are = welcomed.

 

http://w= ww.ietf.org/internet-drafts/draft-wei-tsvwg-tunnel-congestion-feedback-01.t= xt

 

BR

Xipeng Wei

--_000_C5C3BB522B1DDF478AA09545169155B46D7EB64Bnkgeml507mbxchi_-- From nobody Tue Feb 18 20:02:11 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF9D1A0310 for ; Tue, 18 Feb 2014 20:02:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=no 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 PTZ6M9xI8aJm for ; Tue, 18 Feb 2014 20:02:08 -0800 (PST) Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF361A0309 for ; Tue, 18 Feb 2014 20:02:08 -0800 (PST) Received: by mail-pb0-f45.google.com with SMTP id un15so17733067pbc.32 for ; Tue, 18 Feb 2014 20:02:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=52p0mkNDs1zZu+hxNQH1guHrRr8ctNq4Tv0k/0+KiMU=; b=n3IlN3qxMs/kOMGG/mRFFoNQJWFLjE9GwkH+lqs7NWWXuMM51PJXvSbMJlcAAJpUzR Ab+qdKoQpSbc84uiM0oUR6T484vrm5qJcrj9mFltrYN0DdwhJ/UpWmYNuWD5htKfhpIw JYsIH4jwX89+1vIB9uXmAQaFTPvI2mqru0lPN7kRnKZVQhyVM302NnwVpVHN0DUOaXMg yLbFVUaJ8xXzSLV8zqgtsk/6jcd5tCV/vK3lgph2+wVxRUssDB1WAMO2ePRTU+I10n0i iEvxBcThNMmQ0V2PmEl337Mq6ihFcgtmcfaiggQInJPMvdopfHEAN6ApGm16oZJf2DE+ sm3A== X-Received: by 10.66.149.231 with SMTP id ud7mr37702390pab.8.1392782524885; Tue, 18 Feb 2014 20:02:04 -0800 (PST) Received: from [192.168.178.23] ([111.69.192.200]) by mx.google.com with ESMTPSA id x5sm61227557pbw.26.2014.02.18.20.02.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 20:02:04 -0800 (PST) Message-ID: <53042CAA.3030902@gmail.com> Date: Wed, 19 Feb 2014 17:01:46 +1300 From: Brian E Carpenter Organization: University of Auckland User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Ruediger.Geib@telekom.de References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/426lZ0tWNGAz_x6_Z7RpzPn8YqA Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org Subject: Re: [tsvwg] WG: New Version Notification - draft-geib-tsvwg-diffserv-intercon-05.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 04:02:09 -0000 R=C3=BCdiger, I don't have time for a full review before London, but I think the goals of the document are now much clearer and it's probably as good a proposal as is possible in the somewhat messy real world. Of course a pair of providers could always negotiate a more detailed interconnect agreement if they wanted, but this seems like a reasonable default approach. Regards Brian On 15/02/2014 01:00, Ruediger.Geib@telekom.de wrote: > Gorry, all, >=20 > version -05 of diffserv-intercon saw a major review. It is more focused= on explaining the proposed solution and how it fits with IETF and other = standards.=20 >=20 > I'd appreciate a review by a volunteer and comments in general, as I'd = like to discuss accepting this document as a WG draft at the upcoming mee= ting. >=20 > Regards, >=20 > Ruediger >=20 > -----Urspr=C3=BCngliche Nachricht----- > Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20 > Gesendet: Freitag, 14. Februar 2014 11:47 > An: Geib, R=C3=BCdiger; draft-geib-tsvwg-diffserv-intercon@tools.ietf.o= rg; mls.ietf@gmail.com > Betreff: New Version Notification - draft-geib-tsvwg-diffserv-intercon-= 05.txt >=20 >=20 > A new version (-05) has been submitted for draft-geib-tsvwg-diffserv-in= tercon: > http://www.ietf.org/internet-drafts/draft-geib-tsvwg-diffserv-intercon-= 05.txt >=20 >=20 > The IETF datatracker page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-geib-tsvwg-diffserv-intercon/ >=20 > Diff from previous version: > http://www.ietf.org/rfcdiff?url2=3Ddraft-geib-tsvwg-diffserv-intercon-0= 5 >=20 > Please note that it may take a couple of minutes from the time of submi= ssion until the htmlized version and diff are available at tools.ietf.org= =2E >=20 > IETF Secretariat. >=20 From nobody Wed Feb 19 00:46:24 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D131A0389 for ; Wed, 19 Feb 2014 00:46:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-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 z5gBhjDWejj0 for ; Wed, 19 Feb 2014 00:46:19 -0800 (PST) Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 965B11A0080 for ; Wed, 19 Feb 2014 00:46:19 -0800 (PST) Received: from [10.0.27.100] (cust-integra-122-165.antanet.ch [80.75.122.165]) by trammell.ch (Postfix) with ESMTPSA id 142371A0CCA for ; Wed, 19 Feb 2014 09:45:46 +0100 (CET) From: Brian Trammell Content-Type: multipart/signed; boundary="Apple-Mail=_E7845CBE-0B49-4D21-8BDC-193A5B7B04A1"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Wed, 19 Feb 2014 09:45:45 +0100 References: To: tsvwg WG Message-Id: <55D21093-91BE-4CE2-B605-5B972120D01D@trammell.ch> Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/kXfEcn_L6lTD2d3HuT2VlYAMcyY Subject: [tsvwg] CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 08:46:21 -0000 --Apple-Mail=_E7845CBE-0B49-4D21-8BDC-193A5B7B04A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 hi Gorry, all, I support adoption, and can review. Cheers, Brian On 17 Feb 2014, at 19:00, Gorry Fairhurst wrote: >=20 > The authors of " Guidelines for Adding Congestion Notification to > Protocols that Encapsulate IP" = (draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted = as TSVWG item. >=20 > The IETF-88 meeting and following mailing list threads 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 they have sufficient = energy to complete this work in TSVWG. >=20 > * PLEASE send an email to this list if you think adopting this = document > in TSVWG is a good **OR** bad idea. >=20 > * Please indicate if you are willing to REVIEW such a document during > its development. >=20 >=20 > Please send al notes of support/comments to the TSVWG list of chairs = by > the date above. >=20 > Best wishes, >=20 > Gorry, David and James. > (TSVWG Co-Chairs) >=20 --Apple-Mail=_E7845CBE-0B49-4D21-8BDC-193A5B7B04A1 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJTBG85AAoJENt3nsOmbNJc1tcH/25Ta/VjiNfTTjUj8Y98YTLI SAEz7qsHm6mP5zaY2pxcurdFVuScNCxtJEP4Oq0UZSG9rZTczhGf9qPKDEPqIWy9 rHazs9AgNbiwdanoTGY1/lEINDWrDXazhrcpvdVIl5gJlyU9YWy3iQAQ937Fm5wn 0YKuoY9EioBGZkcxsuu1z3j6b+oQH9PZoHmjuIcqatHvm2uAYQ5KEqZKRrL+a9ZB EMD6KXfwiIgN1E9yjof/LIBgcNvqZ39YwQ4vloA4dVC90xDBLgCwqdI8STEzetCW MnPyDlJypXCVHkdG5crODP1wTZ+juFBMCwCgWe9dyvXTnBjqnagXjfRCyv9rIyE= =ger0 -----END PGP SIGNATURE----- --Apple-Mail=_E7845CBE-0B49-4D21-8BDC-193A5B7B04A1-- From nobody Wed Feb 19 03:39:52 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7041A0591 for ; Wed, 19 Feb 2014 03:39:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.15 X-Spam-Level: X-Spam-Status: No, score=-3.15 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-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 R88ZbfBGMMEz for ; Wed, 19 Feb 2014 03:39:49 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 201C01A0590 for ; Wed, 19 Feb 2014 03:39:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 8F92D106D61; Wed, 19 Feb 2014 12:39:45 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBggxbKZ1NKF; Wed, 19 Feb 2014 12:39:45 +0100 (CET) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 71523106D64; Wed, 19 Feb 2014 12:39:35 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.233]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 19 Feb 2014 12:39:35 +0100 From: Dirk Kutscher To: Brian Trammell , tsvwg WG Thread-Topic: [tsvwg] CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: AQHPLU8gKRezKggRLUi4w2n9Pm06J5q8czRA Date: Wed, 19 Feb 2014 11:39:34 +0000 Message-ID: <82AB329A76E2484D934BBCA77E9F5249639B59CD@PALLENE.office.hd> References: <55D21093-91BE-4CE2-B605-5B972120D01D@trammell.ch> In-Reply-To: <55D21093-91BE-4CE2-B605-5B972120D01D@trammell.ch> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.198] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/FZbzqySpgfG4ItzyUQMq_MoTX50 Subject: Re: [tsvwg] CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 11:39:51 -0000 Hi Gorry, all, I support adopting the document and would be willing to review it. Best regards, Dirk > -----Original Message----- > From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Brian Trammell > Sent: Mittwoch, 19. Februar 2014 09:46 > To: tsvwg WG > Subject: [tsvwg] CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn- > encap-guidelines - to end 4th March 2014 >=20 > hi Gorry, all, >=20 > I support adoption, and can review. >=20 > Cheers, >=20 > Brian >=20 > On 17 Feb 2014, at 19:00, Gorry Fairhurst wrote: >=20 > > > > The authors of " Guidelines for Adding Congestion Notification to > > Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-guideline= s) > request that this is adopted as TSVWG item. > > > > The IETF-88 meeting and following mailing list threads indicated some W= G > support for this, so we are now ready to make a formal decision and this > email is to allow people to confirm that they have sufficient energy to > complete this work in TSVWG. > > > > * PLEASE send an email to this list if you think adopting this > > document in TSVWG is a good **OR** bad idea. > > > > * Please indicate if you are willing to REVIEW such a document during > > its development. > > > > > > Please send al notes of support/comments to the TSVWG list of chairs > > by the date above. > > > > Best wishes, > > > > Gorry, David and James. > > (TSVWG Co-Chairs) > > >=20 From nobody Wed Feb 19 07:24:07 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E761A04F7 for ; Wed, 19 Feb 2014 07:24:05 -0800 (PST) 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 L3MuCcd7z77b for ; Wed, 19 Feb 2014 07:24:04 -0800 (PST) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 066051A0206 for ; Wed, 19 Feb 2014 07:24:03 -0800 (PST) Received: by mail-wg0-f54.google.com with SMTP id l18so459961wgh.9 for ; Wed, 19 Feb 2014 07:24:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QLBFSfEsF1QT5uYXY5wWRARGYoeKI/zO/bwe5lMeO+g=; b=AYqFJaCg6v2SmHK9X4toL2z1vtcUyoLG7bZFN2TO4KgbTxvL6nlIaGKeF1+vR1toN8 X5WGCpHtBFLBloxjIaX9xsztHsIZY4/dqe9XPzA0PgoJZyoBGZk6mJ9nIxUlt8i76O8C +7dF5M9SkMj06toua3DInXQRH7F9ZXGFmINAb9fCjtUrxkypeI+UcRp5jO5YuEXepuFg 1OJmbXfCEm+EyI320yITNRHydRgFmj5H6w/JZfkfWCEzVTKT7JiwjNhAyQYEfdF+5cyu Ra6IDzvTQ8bN1o2ChBLS+BKqC3ztBKXPnQ2KVwFrVjB8MfH9uxj8+VUnZLz/yfC5eYeo XT/Q== X-Received: by 10.180.9.71 with SMTP id x7mr1961816wia.55.1392823440209; Wed, 19 Feb 2014 07:24:00 -0800 (PST) Received: from black.lan ([94.195.199.23]) by mx.google.com with ESMTPSA id hy8sm1306872wjb.2.2014.02.19.07.23.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Feb 2014 07:23:55 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=iso-8859-1 From: Piers O'Hanlon In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk> Date: Wed, 19 Feb 2014 15:23:53 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> To: gorry@erg.abdn.ac.uk X-Mailer: Apple Mail (2.1283) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/7lZZUqkuCzZcKbLzD0TRsGPqvsM Cc: tsvwg WG Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 15:24:06 -0000 I support adoption of this draft. Regards, Piers On 17 Feb 2014, at 18:00, Gorry Fairhurst wrote: >=20 > The authors of " Guidelines for Adding Congestion Notification to > Protocols that Encapsulate IP" = (draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted = as TSVWG item. >=20 > The IETF-88 meeting and following mailing list threads 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 they have sufficient = energy to complete this work in TSVWG. >=20 > * PLEASE send an email to this list if you think adopting this = document > in TSVWG is a good **OR** bad idea. >=20 > * Please indicate if you are willing to REVIEW such a document during > its development. >=20 >=20 > Please send al notes of support/comments to the TSVWG list of chairs = by > the date above. >=20 > Best wishes, >=20 > Gorry, David and James. > (TSVWG Co-Chairs) >=20 >=20 From nobody Wed Feb 19 07:29:08 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F521A0206 for ; Wed, 19 Feb 2014 07:29:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 L6E7bcyCD1QX for ; Wed, 19 Feb 2014 07:29:04 -0800 (PST) Received: from out66-ams.mf.surf.net (out66-ams.mf.surf.net [145.0.1.66]) by ietfa.amsl.com (Postfix) with ESMTP id F380D1A032C for ; Wed, 19 Feb 2014 07:29:03 -0800 (PST) Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing3-ams.mf.surf.net (8.14.4/8.14.4/Debian-4) with ESMTP id s1JFTeC0002838; Wed, 19 Feb 2014 16:29:40 +0100 Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 19 Feb 2014 16:29:03 +0100 Received: from EXMBX23.ad.utwente.nl ([169.254.3.208]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Wed, 19 Feb 2014 16:28:58 +0100 From: To: Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: AQHPLAo8akpLe0Iq5U60PJjbFeDDK5q8pFmAgAARvruAAABy2Q== Date: Wed, 19 Feb 2014 15:28:58 +0000 Message-ID: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk>, In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mimectl: Produced By Microsoft Exchange V14.2.247.1 x-originating-ip: [86.91.134.3] Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42EE09EXMBX23adutwent_" MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN) X-CanIt-Geo: No geolocation information available for 130.89.5.49 X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default) X-Canit-Stats-ID: 0bLsftEVq - 9f10f7190841 - 20140219 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/XcVfuNBKj3ep-Am7W6vpLOUToVw Cc: tsvwg@ietf.org Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 15:29:07 -0000 --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42EE09EXMBX23adutwent_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Gorry, I also support the adoption of this draft and I am also willing to review t= he draft in the future! Best regards, Georgios ________________________________ Van: tsvwg [tsvwg-bounces@ietf.org] namens Piers O'Hanlon [p.ohanlon@gmail.= com] Verzonden: woensdag 19 februari 2014 16:23 To: gorry@erg.abdn.ac.uk Cc: tsvwg WG Onderwerp: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ec= n-encap-guidelines - to end 4th March 2014 I support adoption of this draft. Regards, Piers On 17 Feb 2014, at 18:00, Gorry Fairhurst wrote: > > The authors of " Guidelines for Adding Congestion Notification to > Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-guidelines)= request that this is adopted as TSVWG item. > > The IETF-88 meeting and following mailing list threads indicated some WG = support for this, so we are now ready to make a formal decision and this e= mail is to allow people to confirm that they have sufficient energy to comp= lete this work in TSVWG. > > * PLEASE send an email to this list if you think adopting this document > in TSVWG is a good **OR** bad idea. > > * Please indicate if you are willing to REVIEW such a document during > its development. > > > Please send al notes of support/comments to the TSVWG list of chairs by > the date above. > > Best wishes, > > Gorry, David and James. > (TSVWG Co-Chairs) > > --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42EE09EXMBX23adutwent_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable

Hi Gorry,

 

I also support the adoption of this draft and I am also willing to revie= w the draft in the future!

 

Best regards,

Georgios

 

 

 

Van: tsvwg [tsvwg-bounces@ietf.org] namens Piers O'Hanlon [p.oha= nlon@gmail.com]
Verzonden: woensdag 19 februari 2014 16:23
To: gorry@erg.abdn.ac.uk
Cc: tsvwg WG
Onderwerp: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-t= svwg-ecn-encap-guidelines - to end 4th March 2014

I support adoption of this draft.

Regards,

Piers

On 17 Feb 2014, at 18:00, Gorry Fairhurst wrote:

>
> The authors of " Guidelines for Adding Congestion Notification to=
> Protocols that Encapsulate IP" (draft-briscoe-tsvwg-ecn-encap-gui= delines) request that this is adopted as TSVWG item.
>
> The IETF-88 meeting and following mailing list threads indicated some = WG  support for this, so we are now ready to make a formal decision an= d this email is to allow people to confirm that they have sufficient energy= to complete this work in TSVWG.
>
> * PLEASE send an email to this list if you think adopting this documen= t
> in TSVWG is a good **OR** bad idea.
>
> * Please indicate if you are willing to REVIEW such a document during<= br> > its development.
>
>
> Please send al notes of support/comments to the TSVWG list of chairs b= y
> the date above.
>
> Best wishes,
>
> Gorry, David and James.
> (TSVWG Co-Chairs)
>
>

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F42EE09EXMBX23adutwent_-- From nobody Wed Feb 19 09:27:44 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7B81A0249 for ; Wed, 19 Feb 2014 09:27:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.501 X-Spam-Level: X-Spam-Status: No, score=-17.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 3MJYSHkEXAHS for ; Wed, 19 Feb 2014 09:27:41 -0800 (PST) Received: from phx-mipot-001.corp.ebay.com (phx-mipot-001.corp.ebay.com [216.113.172.64]) by ietfa.amsl.com (Postfix) with ESMTP id 202F51A01CF for ; Wed, 19 Feb 2014 09:27:41 -0800 (PST) DomainKey-Signature: s=paypalcorp; d=paypal.com; c=nofws; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:CC: Subject:Thread-Topic:Thread-Index:Date:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:user-agent: x-originating-ip:Content-Type:Content-ID: Content-Transfer-Encoding:MIME-Version:X-CFilter; b=qOk/WxanT1IYKCUvkFJqN8fRGzuGcOuuvzDqqRehfCYvhulYH3qKlrJc gVBX7XSMURXxgfnY5K5TrkS3vg+DOkqnGBrNSZwjeiVevJz9UBFULKFrl pxT/6hSTle9wIsuu2fA8heQATTIT5/pN5nxI/7MB9IMm7gIJZRmmP3w9o k=; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paypal.com; i=@paypal.com; q=dns/txt; s=paypalcorp; t=1392830859; x=1424366859; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=fuG/LUfSlBR2YQMvnH+zT8IYQxLL2+DTfWql2nRRtzc=; b=s2YKIFiXUFxkM+3f1znfYDW2fOA47jIPz0Z2rZwAGscuGK+dYUQC8Bcy vCY/V36HqJp1xzFzmtVw6BtLcv9VgbrBfqF6272WP+WJvkF+aR5oA0D3W McgU7KuLsSR+FkqUuObdaG+ICUhEBvW+KqNb5NuhMrGyM3w8moifQEFJH Y=; X-EBay-Corp: Yes X-IronPort-AV: E=Sophos;i="4.97,506,1389772800"; d="scan'208";a="164368445" Received: from phx-vteml-002.corp.ebay.com (HELO PHX-EXMHT-002.corp.ebay.com) ([10.58.40.101]) by phx-mipot-001.corp.ebay.com with ESMTP; 19 Feb 2014 09:27:38 -0800 Received: from PHX-EXRDA-S11.corp.ebay.com ([169.254.16.18]) by PHX-EXMHT-002.corp.ebay.com ([10.58.12.72]) with mapi id 14.03.0174.001; Wed, 19 Feb 2014 10:27:37 -0700 From: "Bannai, Vinay" To: Piers O'Hanlon , "gorry@erg.abdn.ac.uk" Thread-Topic: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 Thread-Index: AQHPLApATz6jzYI1jk+8k9NFVS1tTpq9KnWA//+cdIA= Date: Wed, 19 Feb 2014 17:27:37 +0000 Message-ID: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.9.131030 x-originating-ip: [10.241.16.197] Content-Type: text/plain; charset="us-ascii" Content-ID: <78D3C2FD58FD6C488FC79D9BE6C5F4DE@corp.ebay.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-CFilter: Scanned Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/nN542T6evaF4TZQw4o2a2SUps18 Cc: tsvwg WG Subject: Re: [tsvwg] Fwd: CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 17:27:42 -0000 Support the draft.=20 On 2/19/14, 7:23 AM, "Piers O'Hanlon" wrote: >I support adoption of this draft. > >Regards, > >Piers > >On 17 Feb 2014, at 18:00, Gorry Fairhurst wrote: > >>=20 >> The authors of " Guidelines for Adding Congestion Notification to >> Protocols that Encapsulate IP" >>(draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted >>as TSVWG item. >>=20 >> The IETF-88 meeting and following mailing list threads 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 they have sufficient >>energy to complete this work in TSVWG. >>=20 >> * PLEASE send an email to this list if you think adopting this document >> in TSVWG is a good **OR** bad idea. >>=20 >> * Please indicate if you are willing to REVIEW such a document during >> its development. >>=20 >>=20 >> Please send al notes of support/comments to the TSVWG list of chairs by >> the date above. >>=20 >> Best wishes, >>=20 >> Gorry, David and James. >> (TSVWG Co-Chairs) >>=20 >>=20 > From nobody Thu Feb 20 22:33:59 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3723A1A0438 for ; Thu, 20 Feb 2014 22:33:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 jzuOTo5IKxSX for ; Thu, 20 Feb 2014 22:33:53 -0800 (PST) Received: from out23-ams.mf.surf.net (out23-ams.mf.surf.net [145.0.1.23]) by ietfa.amsl.com (Postfix) with ESMTP id 083911A0441 for ; Thu, 20 Feb 2014 22:33:52 -0800 (PST) Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing1-ams.mf.surf.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id s1L6XldP008258 for ; Fri, 21 Feb 2014 07:33:47 +0100 Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Fri, 21 Feb 2014 07:33:55 +0100 Received: from EXMBX23.ad.utwente.nl ([169.254.3.208]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Fri, 21 Feb 2014 07:33:47 +0100 From: To: Thread-Topic: main changes in draft-ietf-tsvwg-rsvp-pcn-08.txt Thread-Index: Ac8uzuAHRO0BKaQsQHGKTpXjs1SUmA== Date: Fri, 21 Feb 2014 06:33:46 +0000 Message-ID: References: <20140214141259.9414.66539.idtracker@ietfa.amsl.com>, In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mimectl: Produced By Microsoft Exchange V14.2.247.1 x-originating-ip: [86.91.134.3] Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F431339EXMBX23adutwent_" MIME-Version: 1.0 X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN) X-CanIt-Geo: ip=130.89.5.49; country=NL; region=15; city=Enschede; latitude=52.2195; longitude=6.8912; http://maps.google.com/maps?q=52.2195,6.8912&z=6 X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default) X-Canit-Stats-ID: 0uLsSxLG8 - 5c50977d7f33 - 20140221 (trained as not-spam) X-Scanned-By: CanIt (www . roaringpenguin . com) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/2oV8akMxM6cpBNFYWuyKNrYtBhw Subject: [tsvwg] main changes in draft-ietf-tsvwg-rsvp-pcn-08.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2014 06:33:57 -0000 --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F431339EXMBX23adutwent_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, The main changes in this version of the RSVP over PCN draft, compared to v0= 7, are addressing the comments provided by Francois Le Faucheur, Bob Brisco= e and James Polk, during the IETF'88 tsvwg meeting. The main changes are: =3D> The PCN Decision Point (in charge of admission control) is located at = the PCN-egress-node, instead of locating the Decision Point at the PCN-ingr= ess-node, while: o) complying to RFC6661 and RFC6662 (PCN edge behavior drafts) o) support signaling requirements for messages between Decision Point and P= CN-Ingress-Nodes (complying to Section 3 of RFC6663) =3D> The E2E RSVP reservations are not anymore subject to admission control= over the aggregate reservations. This means that several procedures of [RFC4860] are significantly simplified in this document: o) unlike [RFC4860], the generic aggregate RSVP reservations need not be admitted in the PCN core. o) unlike [RFC4860], the RSVP aggregated traffic does not need to be tunnelled between Aggregator and Deaggregator, see Section 2.3. o) unlike [RFC4860], the Deaggregator need not perform admission control of E2E reservations over the aggregate RSVP reservations. o) unlike [RFC4860], there is no need for dynamic adjustment of the RSVP generic aggregated reservation size, see Section 2.6. =3D> Several sections have been modified in order to realised the above men= tioned changes. For details, please see: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp-pcn-08 Best regards, Georgios ________________________________ Van: Karagiannis, G. (EWI) Verzonden: vrijdag 14 februari 2014 15:25 To: tsvwg@ietf.org Onderwerp: submitted draft-ietf-tsvwg-rsvp-pcn-08.txt Hi all, Version 8 of the draft-ietf-tsvwg-rsvp-pcn draft has just been submitted, s= ee below! This version worked out all comments received during the tsvwg IETF 88 meet= ing (in Vancouver) regarding the need of better integrating the RSVP model into the RSVP over PCN signaling = protoicol. Francois contributed signifficantly to realise this version of the draft wi= th comments and text. A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp-pcn-08 Best regards, Georgios ________________________________ Van: tsvwg [tsvwg-bounces@ietf.org] namens internet-drafts@ietf.org [intern= et-drafts@ietf.org] Verzonden: vrijdag 14 februari 2014 15:12 To: i-d-announce@ietf.org Cc: tsvwg@ietf.org Onderwerp: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-08.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Transport Area Working Group Working Grou= p of the IETF. Title : Generic Aggregation of Resource ReSerVation Proto= col (RSVP) for IPv4 And IPv6 Reservations over PCN domains Authors : Georgios Karagiannis Anurag Bhargava Filename : draft-ietf-tsvwg-rsvp-pcn-08.txt Pages : 28 Date : 2014-02-14 Abstract: This document specifies extensions to Generic Aggregated RSVP RFC 4860 for support of the PCN Controlled Load (CL) and Single Marking (SM) edge behaviors over a Diffserv cloud using Pre- Congestion Notification. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp-pcn-08 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ --_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F431339EXMBX23adutwent_ Content-Type: text/html; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable

Hi all,

 

The main changes in this version of the RSVP over PCN draft, compared to= v07, are addressing the comments provided by Francois Le Faucheur, Bob Bri= scoe and James Polk, during the IETF'88 tsvwg meeting.

The main changes are:

=3D> The PCN Decision Point (in charge of admission control) is located = at the PCN-egress-node, instead of locating the Decision Point at the PCN-i= ngress-node, while:
o) complying to RFC6661 and RFC6662 (PCN edge behavior drafts)
o) support signaling requirements for messages between Decision Point and P= CN-Ingress-Nodes (complying to Section 3 of RFC6663)

=3D> The E2E RSVP reservations are not anymore subject to admission cont= rol over the aggregate reservations. This means that several
procedures of [RFC4860] are significantly simplified in this document:

o) unlike [RFC4860], the generic aggregate RSVP reservations need
not be admitted in the PCN core.

o) unlike [RFC4860], the RSVP aggregated traffic does not need to
be tunnelled between Aggregator and Deaggregator, see Section
2.3.

o) unlike [RFC4860], the Deaggregator need not perform admission
control of E2E reservations over the aggregate RSVP
reservations.

o) unlike [RFC4860], there is no need for dynamic adjustment of
the RSVP generic aggregated reservation size, see Section 2.6.

=3D> Several sections have been modified in order to realised the above = mentioned changes. For details, please see:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp= -pcn-08

Best regards,

Georgios

 

Van: Karagiannis, G. (EWI)
Verzonden: vrijdag 14 februari 2014 15:25
To: tsvwg@ietf.org
Onderwerp: submitted draft-ietf-tsvwg-rsvp-pcn-08.txt

Hi all,

 

Version 8 of the draft-ietf-tsvwg-rsvp-pcn draft has just been subm= itted, see below!

 

This version worked out all comments received during the tsvwg IETF 88 m= eeting (in Vancouver) regarding the

need of better integrating the RSVP model into the RSVP over PCN signali= ng protoicol.

 

Francois contributed signifficantly to realise this version of the draft= with comments and text.

 

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp= -pcn-08

Best regards,

Georgios

 

 

 

Van: tsvwg [tsvwg-bounces@ietf.org] namens internet-drafts@ietf.= org [internet-drafts@ietf.org]
Verzonden: vrijdag 14 februari 2014 15:12
To: i-d-announce@ietf.org
Cc: tsvwg@ietf.org
Onderwerp: [tsvwg] I-D Action: draft-ietf-tsvwg-rsvp-pcn-08.txt


A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
 This draft is a work item of the Transport Area Working Group Working= Group of the IETF.

        Title    &nb= sp;      : Generic Aggregation of Resource ReSerVa= tion Protocol (RSVP) for IPv4 And IPv6 Reservations over PCN domains
        Authors    &= nbsp;    : Georgios Karagiannis
            &nb= sp;            = Anurag Bhargava
        Filename    =     : draft-ietf-tsvwg-rsvp-pcn-08.txt
        Pages    &nb= sp;      : 28
        Date    &nbs= p;       : 2014-02-14

Abstract:
   This document specifies extensions to Generic Aggregated RSVP<= br>    RFC 4860 for support of the PCN Controlled Load (CL) and Singl= e
   Marking (SM) edge behaviors over a Diffserv cloud using Pre-    Congestion Notification.





The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rsvp-pcn/<= /a>

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rsvp-pcn-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-rsvp= -pcn-08


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

--_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F431339EXMBX23adutwent_-- From nobody Wed Feb 26 06:47:34 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95161A02F5 for ; Wed, 26 Feb 2014 06:47:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.849 X-Spam-Level: X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 oMuLHUHDVftI for ; Wed, 26 Feb 2014 06:47:19 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 643CB1A00CD for ; Wed, 26 Feb 2014 06:47:19 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id C05E62B4555; Wed, 26 Feb 2014 14:47:17 +0000 (GMT) Received: from ERG-research.local (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id D38B92B43BE for ; Wed, 26 Feb 2014 14:47:16 +0000 (GMT) Message-ID: <530DFE74.5000505@erg.abdn.ac.uk> Date: Wed, 26 Feb 2014 14:47:16 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: tsvwg@ietf.org References: <52F51569.8020501@erg.abdn.ac.uk> In-Reply-To: <52F51569.8020501@erg.abdn.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/18uzQ50AcB7Fkhd7hhkiYkVHsT8 Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-dtls-encaps: To End 28th February 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 14:47:23 -0000 A gentle reminder, I've seen no notes of support, or comments on this document during the WGLC so far. Could people please send comments to the list if they think this is ready to publish? Gorry On 07/02/2014 17:18, Gorry Fairhurst wrote: > This email announces the start of a working group last call > of draft-ietf-tsvwg-sctp-dtls-encaps-03, > "DTLS Encapsulation of SCTP Packets". This document was > discussed at the WG meeting in Vancouver and was thought at that > meeting to be ready for WG review, this email starts this process by > requesting review comments. > > Please send any comments, notes of support, or concerns to the TSVWG list. > > The draft is available at: > http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps > > The last call will run for TWO weeks, ending 28th February 2014. > > James, David, and Gorry > (TSVWG Chairs) > tsvwg-chairs@ietf.org > From nobody Wed Feb 26 08:22:18 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01BF61A0100 for ; Wed, 19 Feb 2014 00:26:25 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.748 X-Spam-Level: X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] 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 sNP1Zg3ce7VL for ; Wed, 19 Feb 2014 00:26:22 -0800 (PST) Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 0991A1A0080 for ; Wed, 19 Feb 2014 00:26:22 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 6F2F0D93AE; Wed, 19 Feb 2014 09:26:18 +0100 (MET) X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11Y-ANkZyKHk; Wed, 19 Feb 2014 09:26:18 +0100 (MET) Received: from [10.0.27.100] (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id EC8ADD93A4; Wed, 19 Feb 2014 09:26:17 +0100 (MET) Content-Type: multipart/signed; boundary="Apple-Mail=_5B784F80-692E-408D-BBB3-223744975814"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Brian Trammell In-Reply-To: <53024E41.9090901@erg.abdn.ac.uk> Date: Wed, 19 Feb 2014 09:26:16 +0100 Message-Id: References: <530232BD.4080508@erg.abdn.ac.uk> <53024E41.9090901@erg.abdn.ac.uk> To: Gorry Fairhurst X-Mailer: Apple Mail (2.1827) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/JpAoYm0fnhKwgYbrYvF5hwn4d24 X-Mailman-Approved-At: Wed, 26 Feb 2014 08:22:07 -0800 Cc: tsvwg WG Subject: Re: [tsvwg] CALL FOR ADOPTION TSVWG: draft-briscoe-tsvwg-ecn-encap-guidelines - to end 4th March 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 08:26:25 -0000 --Apple-Mail=_5B784F80-692E-408D-BBB3-223744975814 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 hi Gorry, all, I support adoption, and can review. Cheers, Brian On 17 Feb 2014, at 19:00, Gorry Fairhurst wrote: >=20 > The authors of " Guidelines for Adding Congestion Notification to > Protocols that Encapsulate IP" = (draft-briscoe-tsvwg-ecn-encap-guidelines) request that this is adopted = as TSVWG item. >=20 > The IETF-88 meeting and following mailing list threads 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 they have sufficient = energy to complete this work in TSVWG. >=20 > * PLEASE send an email to this list if you think adopting this = document > in TSVWG is a good **OR** bad idea. >=20 > * Please indicate if you are willing to REVIEW such a document during > its development. >=20 >=20 > Please send al notes of support/comments to the TSVWG list of chairs = by > the date above. >=20 > Best wishes, >=20 > Gorry, David and James. > (TSVWG Co-Chairs) >=20 --Apple-Mail=_5B784F80-692E-408D-BBB3-223744975814 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJTBGqoAAoJENt3nsOmbNJcKUoH/iMDbRZKGew+jhUyJ05N1PUS gQt90+Eo1P4EwbYAx2lTyYQN8wyRXBlMm+Li3xJzE009k4gToBnds7LJ2EeOwIwo rHTfDwuWuPoAj/GbRefB2+G/+eIDVVGizUYrw2DZd22n467A1Bc4BoHMwDsEbiL7 G6BykOOH3nHo7nq4qH0mvzNqHF8Kam2TBHeJX2jH38W+NHOMFibOwIPGO1t+gj5h Okx2Z04QZ7vF7yPm+dl47AcuuJv9vAIZFtNcMzIpYkJZlUFSXQ91WOu43I4ogpfy HyD6EQ7nnhEh1u+jSD8nurI4LeZ4iR0Dz2B84aSn/uEOd8X/51czJ288sFr0Sjo= =HnUB -----END PGP SIGNATURE----- --Apple-Mail=_5B784F80-692E-408D-BBB3-223744975814-- From nobody Wed Feb 26 11:13:36 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55EF51A0806; Wed, 26 Feb 2014 11:13:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-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 ZpZWqV0rwBd1; Wed, 26 Feb 2014 11:13:20 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id DFFC11A07FF; Wed, 26 Feb 2014 11:13:15 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id B326F7FC2C7; Wed, 26 Feb 2014 11:13:14 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20140226191314.B326F7FC2C7@rfc-editor.org> Date: Wed, 26 Feb 2014 11:13:14 -0800 (PST) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/uTpYvETmJBvP3Pinv7JStnkGOFs Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org Subject: [tsvwg] BCP 41, RFC 7141 on Byte and Packet Congestion Notification X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 19:13:25 -0000 A new Request for Comments is now available in online RFC libraries. BCP 41 RFC 7141 Title: Byte and Packet Congestion Notification Author: B. Briscoe, J. Manner Status: Best Current Practice Stream: IETF Date: February 2014 Mailbox: bob.briscoe@bt.com, jukka.manner@aalto.fi Pages: 48 Characters: 123953 Updates: 2309 I-D Tag: draft-ietf-tsvwg-byte-pkt-congest-12.txt URL: http://www.rfc-editor.org/rfc/rfc7141.txt This document provides recommendations of best current practice for dropping or marking packets using any active queue management (AQM) algorithm, including random early detection (RED), BLUE, pre- congestion notification (PCN) and newer schemes such as CoDel (Controlled Delay) and PIE (Proportional Integral controller Enhanced). We give three strong recommendations: (1) packet size should be taken into account when transports detect and respond to congestion indications, (2) packet size should not be taken into account when network equipment creates congestion signals (marking, dropping), and therefore (3) in the specific case of RED, the byte- mode packet drop variant that drops fewer small packets should not be used. This memo updates RFC 2309 to deprecate deliberate preferential treatment of small packets in AQM algorithms. This document is a product of the Transport Area Working Group Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Wed Feb 26 11:33:28 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 490B81A01E4; Wed, 26 Feb 2014 11:33:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.449 X-Spam-Level: X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-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 V6Jdz3vK3Dbj; Wed, 26 Feb 2014 11:33:14 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id B5B2D1A01F6; Wed, 26 Feb 2014 11:33:14 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 4F7D57FC387; Wed, 26 Feb 2014 11:33:13 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20140226193313.4F7D57FC387@rfc-editor.org> Date: Wed, 26 Feb 2014 11:33:13 -0800 (PST) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/KsvsOzFwX-oWGyvPyU1iA8LisqU Cc: drafts-update-ref@iana.org, tsvwg@ietf.org Subject: [tsvwg] Correction: BCP 41, RFC 7141 on Byte and Packet Congestion Notification X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2014 19:33:19 -0000 A new Request for Comments is now available in online RFC libraries. BCP 41 RFC 7141 Title: Byte and Packet Congestion Notification Author: B. Briscoe, J. Manner Status: Best Current Practice Stream: IETF Date: February 2014 Mailbox: bob.briscoe@bt.com, jukka.manner@aalto.fi Pages: 41 Characters: 103344 Updates: RFC 2309, RFC 2914 See Also: BCP 41 I-D Tag: draft-ietf-tsvwg-byte-pkt-congest-12.txt URL: http://www.rfc-editor.org/rfc/rfc7141.txt This document provides recommendations of best current practice for dropping or marking packets using any active queue management (AQM) algorithm, including random early detection (RED), BLUE, pre- congestion notification (PCN) and newer schemes such as CoDel (Controlled Delay) and PIE (Proportional Integral controller Enhanced). We give three strong recommendations: (1) packet size should be taken into account when transports detect and respond to congestion indications, (2) packet size should not be taken into account when network equipment creates congestion signals (marking, dropping), and therefore (3) in the specific case of RED, the byte- mode packet drop variant that drops fewer small packets should not be used. This memo updates RFC 2309 to deprecate deliberate preferential treatment of small packets in AQM algorithms. This document is a product of the Transport Area Working Group Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/search For downloading RFCs, see http://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Thu Feb 27 00:14:26 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52FB81A005A for ; Thu, 27 Feb 2014 00:14:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3yVk5kIqiX7J for ; Thu, 27 Feb 2014 00:14:22 -0800 (PST) Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 759E21A00CF for ; Thu, 27 Feb 2014 00:14:21 -0800 (PST) X-AuditID: c1b4fb38-b7f418e000001099-2f-530ef3db226b Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id D2.0E.04249.BD3FE035; Thu, 27 Feb 2014 09:14:19 +0100 (CET) Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.56) with Microsoft SMTP Server id 14.2.347.0; Thu, 27 Feb 2014 09:14:19 +0100 Message-ID: <530EF3DB.9020303@ericsson.com> Date: Thu, 27 Feb 2014 09:14:19 +0100 From: Magnus Westerlund User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: tsvwg WG References: <52F51569.8020501@erg.abdn.ac.uk> In-Reply-To: <52F51569.8020501@erg.abdn.ac.uk> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFJMWRmVeSWpSXmKPExsUyM+Jvje7tz3zBBhemKloce3OXzYHRY8mS n0wBjFFcNimpOZllqUX6dglcGR19X9gL3mpUrH61mrWBcaNCFyMHh4SAicS+3fJdjJxAppjE hXvr2boYuTiEBI4wSkw7fJ8FwlnOKHHs8QFGkCpeAW2J3+8/sYDYLAKqEkfnXmUHsdkELCRu /mhkA7FFBYIldh74DVUvKHFy5hOwehEBWYnOcy1gtrBAjMTeSa+YQWwhAV2Jq+2/wXo5BfQk zr6cwAxxnLhET2MQSJgZKDzlagsjhC0v0bx1NlSrtkRDUwfrBEbBWUi2zULSMgtJywJG5lWM HMWpxUm56UYGmxiB4Xdwy2+LHYyX/9ocYpTmYFES5/341jlISCA9sSQ1OzW1ILUovqg0J7X4 ECMTB6dUA+OWM5cVdK5JmEzu2O7Itu/Z3p3l/vKcczU1506dUhzN8Tv4qvozo6anKlf9DtzY Xbh40bMDV8S6VtjwJi62375EM+/Q/gVpB8IXb92ufbUxkM2utOr8d2mpY786ayYuk3yxXe1M mrz4jqe3Yh/fTmY035vz/tl8Nv2Loj4/jm0p2Xj+x4nYC8E8SizFGYmGWsxFxYkAkFvXqg0C AAA= Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/c8ZHiiULnpHSwJXKUMu2hkR4eFA Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-dtls-encaps: To End 28th February 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 08:14:24 -0000 On 2014-02-07 18:18, Gorry Fairhurst wrote: > This email announces the start of a working group last call > of draft-ietf-tsvwg-sctp-dtls-encaps-03, > "DTLS Encapsulation of SCTP Packets". This document was > discussed at the WG meeting in Vancouver and was thought at that > meeting to be ready for WG review, this email starts this process by > requesting review comments. > > Please send any comments, notes of support, or concerns to the TSVWG list. > > The draft is available at: > http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps > > The last call will run for TWO weeks, ending 28th February 2014. > > James, David, and Gorry > (TSVWG Chairs) > tsvwg-chairs@ietf.org > WG, I have review the draft and think it is mostly ready but there are some issue I would like to bring to your attention for discussion. 1) Section 1.1 The Stream Control Transmission Protocol (SCTP) as defined in [RFC4960] is a transport protocol running on top of the network protocols IPv4 or IPv6. This document specifies how SCTP is used on top of the Datagram Transport Layer Security (DTLS) protocol defined in [RFC6347]. This encapsulation is used for example within the RTCWeb protocol suite (see [I-D.ietf-rtcweb-overview] for an overview) for transporting non-media data between browsers. The architecture of this stack is described in [I-D.ietf-rtcweb-data-channel]. I would like to rewrite this to: The Stream Control Transmission Protocol (SCTP) as defined in [RFC4960] is a transport protocol running on top of the network protocols IPv4 [RFC0791] or IPv6 [RFC2460]. This document specifies how SCTP is used on top of the Datagram Transport Layer Security (DTLS) protocol defined in [RFC6347]. This encapsulation is used for example within the WebRTC protocol suite (see [I-D.ietf-rtcweb- overview] for an overview) for transporting non-RTP [RFC3550] data between browsers. The architecture of this stack is described in [I-D.ietf-rtcweb-data-channel]. Changes are: - References for IP - RTCWEB -> WebRTC - non-media to non-RTP data 2) Section 1.3: I think there are a need for some terms not yet mentioned to have references to where they are defined. The terms I consider needing references are: - PPID - TCP - TLS MTU would be good also. 3) Section 4: The DTLS implementation MUST be based on [RFC6347]. What happens when RFC 6347 is obsoleted? And that obsoletion can be based on two cases, either the whole DTLS version is being replaced or the RFC just updated for the same DTLS version. The later case I definitely should be less locked in. For the DTLS version it is a question of interoperability. Thus I think one probably should word this as: The DTLS implementation MUST be based on DTLS 1.2 [RFC6347]. Then one could add supporting future versions of DTLS is RECOMMENDED if defined. 4) Section 4: If path MTU discovery is performed by the DTLS layer, the method described in [RFC4821] MUST be used. For probe packets, the extension defined in [RFC6520] MUST be used. If path MTU discovery is performed by the SCTP layer and IPv4 is used as the network layer protocol, the DTLS implementation MUST allow the DTLS user to enforce that the corresponding IPv4 packet is sent with the DF bit set. Although this is stated, there are no requirement that I find in the specification that says that you MUST implement a PMTUD method. My understanding is that IP/UDP/DTLS/SCTP is going to have a misserable time working if one ends up with IP fragments in other cases than for PMTUD probing packets. Thus, I think there needs to be a requirement on implementing some type of PMTUD method that works in this setting. I propose: An implementation of SCTP over DTLS MUST implement and use a path MTU discovery method that functions without ICMP to provide SCTP with a MTU estimate. An implementation of "Packetization Layer Path MTU Discovery" [RFC4821] either in SCTP or DTLS is RECOMMENDED. I do note that this text is not suitable in any of the existing sections. Maybe a new section between 3 and 4 for general considerations. 5) Section 7. It is not obvious that this do not create new security issues. To me an obvious candidate for causing potential issues is the requirement on SCTP to be able to function without ICMP. Are there behaviors introduced that are a result of not receiving ICMP because they are not provided to SCTP, which compared to SCTP over IP would not exist. At the same time I do realize that it protects the SCTP stack from some attack vectors through ICMP. Cheers Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From nobody Thu Feb 27 00:49:34 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E901A00AD for ; Thu, 27 Feb 2014 00:49:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.103 X-Spam-Level: X-Spam-Status: No, score=0.103 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=no 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 oEHzAbNiC-s2 for ; Thu, 27 Feb 2014 00:49:28 -0800 (PST) Received: from mailms.fh-muenster.de (mail.fh-muenster.de [212.201.120.190]) by ietfa.amsl.com (Postfix) with ESMTP id 407A11A0370 for ; Thu, 27 Feb 2014 00:49:28 -0800 (PST) Received: from [212.201.121.69] (unknown [212.201.121.69]) (Authenticated sender: ruengele) by mailms.fh-muenster.de (Postfix) with ESMTPSA id 500CF282175; Thu, 27 Feb 2014 09:49:21 +0100 (CET) Content-Type: multipart/alternative; boundary="Apple-Mail=_9F8E6E0E-F3CB-452D-A692-590B9E00B46E" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: =?iso-8859-1?Q?Irene_R=FCngeler?= In-Reply-To: <530DFE74.5000505@erg.abdn.ac.uk> Date: Thu, 27 Feb 2014 09:49:23 +0100 Message-Id: References: <52F51569.8020501@erg.abdn.ac.uk> <530DFE74.5000505@erg.abdn.ac.uk> To: tsvwg@ietf.org X-Mailer: Apple Mail (2.1510) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/l2kLWcHBRRiXbBnpmPifuU96aFU Cc: "gorry@erg.abdn.ac.uk" Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-dtls-encaps: To End 28th February 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 08:49:30 -0000 --Apple-Mail=_9F8E6E0E-F3CB-452D-A692-590B9E00B46E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi all, I read the draft and support it. It is very important for the encryption = of the non-media streams in WebRTC. Regards Irene Am 26.02.2014 um 15:47 schrieb Gorry Fairhurst : > A gentle reminder, I've seen no notes of support, or comments on this = document during the WGLC so far. >=20 > Could people please send comments to the list if they think this is = ready to publish? >=20 > Gorry >=20 > On 07/02/2014 17:18, Gorry Fairhurst wrote: >> This email announces the start of a working group last call >> of draft-ietf-tsvwg-sctp-dtls-encaps-03, >> "DTLS Encapsulation of SCTP Packets". This document was >> discussed at the WG meeting in Vancouver and was thought at that >> meeting to be ready for WG review, this email starts this process by >> requesting review comments. >>=20 >> Please send any comments, notes of support, or concerns to the TSVWG = list. >>=20 >> The draft is available at: >> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps >>=20 >> The last call will run for TWO weeks, ending 28th February 2014. >>=20 >> James, David, and Gorry >> (TSVWG Chairs) >> tsvwg-chairs@ietf.org >>=20 >=20 ***************************************** Dr. Irene R=FCngeler=20 Fachhochschule M=FCnster, Abt. Steinfurt=20 FB Elektrotechnik und Informatik=20 Labor f=FCr Netzwerkprogrammierung, Datenbanklabor=20 Bismarckstr. 11=20 Tel.: 02551-962561=20 Fax: 02551-962563=20 EMail: I.Ruengeler@fh-muenster.de --Apple-Mail=_9F8E6E0E-F3CB-452D-A692-590B9E00B46E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = all,

I read the draft and support it. It is very = important for the encryption of the non-media streams in = WebRTC.

Regards

Irene

Am 26.02.2014 um 15:47 schrieb Gorry Fairhurst = <gorry@erg.abdn.ac.uk>:
A gentle = reminder, I've seen no notes of support, or comments on this document = during the WGLC so far.

Could people please send comments to the = list if they think this is ready to publish?

Gorry

On = 07/02/2014 17:18, Gorry Fairhurst wrote:
This= email announces the start of a working group last call
of = draft-ietf-tsvwg-sctp-dtls-encaps-03,
"DTLS Encapsulation of SCTP = Packets". This document was
discussed at the WG meeting in Vancouver = and was thought at that
meeting to be ready for WG review, this email = starts this process by
requesting review comments.

Please send = any comments, notes of support, or concerns to the TSVWG = list.

The draft is available at:
http= ://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps

The = last call will run for TWO weeks, ending 28th February = 2014.

James, David, and Gorry
(TSVWG = Chairs)
tsvwg-chairs@ietf.org



*****************************************

Dr. Irene R=FCngeler 
Fachhochschule M=FCnster, Abt. = Steinfurt 
FB Elektrotechnik und = Informatik 
Labor f=FCr = Netzwerkprogrammierung, Datenbanklabor 
Bismarckstr. 11 
Tel.: = 02551-962561 
Fax: = 02551-962563 
EMail: I.Ruengeler@fh-muenster.de<= /font>





= --Apple-Mail=_9F8E6E0E-F3CB-452D-A692-590B9E00B46E-- From nobody Thu Feb 27 12:47:33 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382021A064D for ; Thu, 27 Feb 2014 12:47:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 gKy03Ir65c-M for ; Thu, 27 Feb 2014 12:47:30 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 32D741A064A for ; Thu, 27 Feb 2014 12:47:30 -0800 (PST) Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 7ABF72B451D; Thu, 27 Feb 2014 20:47:27 +0000 (GMT) Received: from ra-gorry.erg.abdn.ac.uk (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 860CD2B4039; Thu, 27 Feb 2014 20:47:26 +0000 (GMT) Message-ID: <530FA45E.40809@erg.abdn.ac.uk> Date: Thu, 27 Feb 2014 20:47:26 +0000 From: Gorry Fairhurst Organization: The University of Aberdeen is a charity registered in Scotland, No SC013683. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: tsvwg@ietf.org, touch@isi.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/wSrrJpqBv8bofgmDv8zIDflHyTc Subject: [tsvwg] draft-ietf-tsvwg-port-use-03.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: gorry@erg.abdn.ac.uk List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2014 20:47:32 -0000 I have a few comments/questions on draft-ietf-tsvwg-port-use-03.txt, please see below. Gorry ---- 7.1: -Is there a possibility to mention SIP in this section on using dynamic ports? 7.1: - The bullet starting: "Is this service independently useful" the draft then talks immediately about an "entire group", maybe it requires a mention that the requested assignment may refer to one of a gout of related services? 7.2 bullet 2: Second bullet does not have an example. Would the NPN mechanism in http serve as a suitable example of negotiating within a protocol or can something better be suggested? 7.4 para 1, 1st sentence: The first introductory sentence is very broad and I can't quite work out what this means. Could you expand/rephrase? 7.4 last but one para: /as we discussed/As discussed/ - this could be more consistent language? 7.5 para 1, 1st sentence: /to support versioning/for services that support versioning/ - wording unclear? 7.6 /UDP services should be bandwith-limited/UDP services should be rate-limited [RFC5405]/ /UDP services should include congestion detection ... / Can we refer to [RFC5405]? /UDP services should not be used ... / Can we refer to [RFC5405]? ... I suspect all these protocol-related issues need to be related back to the BCP that defines how to use UDP or its successor in the BCP series. References - Reading this again, I suspect that the associated IANA guidance may actually be normative? e.g. RFC2780 is BCP and RFC6335 may also be normative? From nobody Thu Feb 27 22:36:20 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3C021A0411 for ; Thu, 27 Feb 2014 22:36:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.447 X-Spam-Level: X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] 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 Ptf9ck-jlOqb for ; Thu, 27 Feb 2014 22:36:17 -0800 (PST) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id CAA741A02D3 for ; Thu, 27 Feb 2014 22:36:17 -0800 (PST) Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s1S6ZT5M014515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 27 Feb 2014 22:35:40 -0800 (PST) Message-ID: <53102E31.9080804@isi.edu> Date: Thu, 27 Feb 2014 22:35:29 -0800 From: Joe Touch User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: gorry@erg.abdn.ac.uk, tsvwg@ietf.org References: <530FA45E.40809@erg.abdn.ac.uk> In-Reply-To: <530FA45E.40809@erg.abdn.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: touch@isi.edu Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/VxERNkNUdRI3TDVYx5lx7I_W7U0 Subject: Re: [tsvwg] draft-ietf-tsvwg-port-use-03.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 06:36:19 -0000 Hi, Gorry, On 2/27/2014 12:47 PM, Gorry Fairhurst wrote: > > I have a few comments/questions on draft-ietf-tsvwg-port-use-03.txt, > please see below. > > Gorry > > ---- > > > 7.1: > -Is there a possibility to mention SIP in this section on using dynamic > ports? Sure. > 7.1: > - The bullet starting: > "Is this service independently useful" > the draft then talks immediately about an "entire group", maybe it > requires a mention that the requested assignment may refer to one of a > gout of related services? Yes; it was implied in the way the bullet is worded, but it'd be better to say that. However, it might be part of a group request or it might be a supplement to an existing service. Either way, the bullet point is relevant. I'll clarify that. > 7.2 bullet 2: > Second bullet does not have an example. Would the NPN mechanism in http > serve as a suitable example of negotiating within a protocol or can > something better be suggested? It might be; I'm open to other suggestions. I do think it would be useful to include suggestions, though. > 7.4 para 1, 1st sentence: > The first introductory sentence is very broad and I can't quite work out > what this means. Could you expand/rephrase? The current is: Services represent a potential system vulnerability. Given the current state of cybersecurity in the Internet, we recommend that: But it's really that: Just as a service is a way to obtain information or processing from a host over a network, an service can also be the opening through which to attack that host. ... > 7.4 last but one para: > /as we discussed/As discussed/ OK. > - this could be more consistent language? Not sure what you mean - a scrub of the document to avoid first-person is certainly needed. Was there anything else? > 7.5 para 1, 1st sentence: > /to support versioning/for services that support versioning/ > - wording unclear? Current text: Current IANA assignments are expected to support versioning [RFC6335]. Is this more clear? Current IANA assignments are expected to support the use of multiple versions on the same assigned port, typically through in-band indication of the service version [RFC6335]. > 7.6 > /UDP services should be bandwith-limited/UDP services should be > rate-limited [RFC5405]/ Yes. > /UDP services should include congestion detection ... / > Can we refer to [RFC5405]? Yes. > /UDP services should not be used ... / > Can we refer to [RFC5405]? Yes. > ... I suspect all these protocol-related issues need to be related back > to the BCP that defines how to use UDP or its successor in the BCP series. I think the ones you found are the only ones that relate back to how to use UDP. If you think there are others, please let me know. > References > > - Reading this again, I suspect that the associated IANA guidance may > actually be normative? > e.g. RFC2780 is BCP and RFC6335 may also be normative? Yeah - I need to scrub the norm/inform list and correct a bunch of those. I'll wait until after the IETF to do these updates, to see if anyone else has additional input or additional clarification. Let me know if the above works. Joe From nobody Fri Feb 28 00:12:04 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 831EA1A007A for ; Fri, 28 Feb 2014 00:12:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.448 X-Spam-Level: X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, 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 rbjUDFHRYaT9 for ; Fri, 28 Feb 2014 00:11:58 -0800 (PST) Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id EDA2F1A0021 for ; Fri, 28 Feb 2014 00:11:57 -0800 (PST) Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 95A5F2B451D; Fri, 28 Feb 2014 08:11:55 +0000 (GMT) Received: from 88.96.136.84 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 28 Feb 2014 08:11:55 -0000 Message-ID: <4cfdabf3617559f16974c10bef3e767f.squirrel@www.erg.abdn.ac.uk> In-Reply-To: <53102E31.9080804@isi.edu> References: <530FA45E.40809@erg.abdn.ac.uk> <53102E31.9080804@isi.edu> Date: Fri, 28 Feb 2014 08:11:55 -0000 From: gorry@erg.abdn.ac.uk To: "Joe Touch" User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/fAwu1NN0f8br9g4dn8Hk-MdVFEo Cc: gorry@erg.abdn.ac.uk, tsvwg@ietf.org Subject: Re: [tsvwg] draft-ietf-tsvwg-port-use-03.txt X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 08:12:00 -0000 This all seems good to me - thanks for the quick answer. Gorry > Hi, Gorry, > > On 2/27/2014 12:47 PM, Gorry Fairhurst wrote: >> >> I have a few comments/questions on draft-ietf-tsvwg-port-use-03.txt, >> please see below. >> >> Gorry >> >> ---- >> >> >> 7.1: >> -Is there a possibility to mention SIP in this section on using dynamic >> ports? > > Sure. > >> 7.1: >> - The bullet starting: >> "Is this service independently useful" >> the draft then talks immediately about an "entire group", maybe it >> requires a mention that the requested assignment may refer to one of a >> gout of related services? > > Yes; it was implied in the way the bullet is worded, but it'd be better > to say that. However, it might be part of a group request or it might be > a supplement to an existing service. Either way, the bullet point is > relevant. I'll clarify that. > OK >> 7.2 bullet 2: >> Second bullet does not have an example. Would the NPN mechanism in http >> serve as a suitable example of negotiating within a protocol or can >> something better be suggested? > > It might be; I'm open to other suggestions. I do think it would be > useful to include suggestions, though. > >> 7.4 para 1, 1st sentence: >> The first introductory sentence is very broad and I can't quite work out >> what this means. Could you expand/rephrase? > > The current is: > > Services represent a potential system vulnerability. Given the > current state of cybersecurity in the Internet, we recommend that: > > But it's really that: > > Just as a service is a way to obtain information or processing from > a host over a network, an service can also be the opening through > which to attack that host. ... > Aha, OK >> 7.4 last but one para: >> /as we discussed/As discussed/ > > OK. > >> - this could be more consistent language? > > Not sure what you mean - a scrub of the document to avoid first-person > is certainly needed. Was there anything else? > No >> 7.5 para 1, 1st sentence: >> /to support versioning/for services that support versioning/ >> - wording unclear? > > Current text: > > Current IANA assignments are expected to support versioning > [RFC6335]. > > Is this more clear? > > Current IANA assignments are expected to support the use of > multiple versions on the same assigned port, typically through > in-band indication of the service version [RFC6335]. > Works for me. >> 7.6 >> /UDP services should be bandwith-limited/UDP services should be >> rate-limited [RFC5405]/ > > Yes. > >> /UDP services should include congestion detection ... / >> Can we refer to [RFC5405]? > > Yes. > >> /UDP services should not be used ... / >> Can we refer to [RFC5405]? > > Yes. > >> ... I suspect all these protocol-related issues need to be related back >> to the BCP that defines how to use UDP or its successor in the BCP >> series. > > I think the ones you found are the only ones that relate back to how to > use UDP. If you think there are others, please let me know. > I don't know of others >> References >> >> - Reading this again, I suspect that the associated IANA guidance may >> actually be normative? >> e.g. RFC2780 is BCP and RFC6335 may also be normative? > > Yeah - I need to scrub the norm/inform list and correct a bunch of those. > > I'll wait until after the IETF to do these updates, to see if anyone > else has additional input or additional clarification. > > Let me know if the above works. > > Joe > Thanks, Gorry From nobody Fri Feb 28 13:24:32 2014 Return-Path: X-Original-To: tsvwg@ietfa.amsl.com Delivered-To: tsvwg@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33BF31A01F6 for ; Fri, 28 Feb 2014 13:24:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.547, SPF_HELO_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 UVy0fQbYJeZx for ; Fri, 28 Feb 2014 13:24:27 -0800 (PST) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id B64021A0316 for ; Fri, 28 Feb 2014 13:24:26 -0800 (PST) Received: from [192.168.1.200] (p548181E4.dip0.t-ipconnect.de [84.129.129.228]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id BF2BF1C0ACD58; Fri, 28 Feb 2014 22:24:22 +0100 (CET) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) From: Michael Tuexen In-Reply-To: <530EF3DB.9020303@ericsson.com> Date: Fri, 28 Feb 2014 22:24:21 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8F68A39F-7E0C-495E-89D9-3AD38DE72572@lurchi.franken.de> References: <52F51569.8020501@erg.abdn.ac.uk> <530EF3DB.9020303@ericsson.com> To: Magnus Westerlund X-Mailer: Apple Mail (2.1874) Archived-At: http://mailarchive.ietf.org/arch/msg/tsvwg/jQYefsxsOU8nYjmuXCzKoSN4710 Cc: tsvwg WG Subject: Re: [tsvwg] WGLC for draft-ietf-tsvwg-sctp-dtls-encaps: To End 28th February 2014 X-BeenThere: tsvwg@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Transport Area Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 21:24:30 -0000 On 27 Feb 2014, at 09:14, Magnus Westerlund = wrote: > On 2014-02-07 18:18, Gorry Fairhurst wrote: >> This email announces the start of a working group last call >> of draft-ietf-tsvwg-sctp-dtls-encaps-03, >> "DTLS Encapsulation of SCTP Packets". This document was >> discussed at the WG meeting in Vancouver and was thought at that >> meeting to be ready for WG review, this email starts this process by >> requesting review comments. >>=20 >> Please send any comments, notes of support, or concerns to the TSVWG = list. >>=20 >> The draft is available at: >> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-dtls-encaps >>=20 >> The last call will run for TWO weeks, ending 28th February 2014. >>=20 >> James, David, and Gorry >> (TSVWG Chairs) >> tsvwg-chairs@ietf.org >>=20 >=20 > WG, >=20 > I have review the draft and think it is mostly ready but there are = some > issue I would like to bring to your attention for discussion. Hi Magnus, thank you very much for your review. Please see my comments in-line. Best regards Michael >=20 > 1) Section 1.1 >=20 > The Stream Control Transmission Protocol (SCTP) as defined in > [RFC4960] is a transport protocol running on top of the network > protocols IPv4 or IPv6. This document specifies how SCTP is used on > top of the Datagram Transport Layer Security (DTLS) protocol defined > in [RFC6347]. This encapsulation is used for example within the > RTCWeb protocol suite (see [I-D.ietf-rtcweb-overview] for an > overview) for transporting non-media data between browsers. The > architecture of this stack is described in > [I-D.ietf-rtcweb-data-channel]. >=20 > I would like to rewrite this to: >=20 > The Stream Control Transmission Protocol (SCTP) as defined in > [RFC4960] is a transport protocol running on top of the network > protocols IPv4 [RFC0791] or IPv6 [RFC2460]. This document specifies > how SCTP is used on top of the Datagram Transport Layer Security > (DTLS) protocol defined in [RFC6347]. This encapsulation is used > for example within the WebRTC protocol suite (see [I-D.ietf-rtcweb- > overview] for an overview) for transporting non-RTP [RFC3550] data > between browsers. The architecture of this stack is described in > [I-D.ietf-rtcweb-data-channel]. >=20 > Changes are: > - References for IP Added as Informative References > - RTCWEB -> WebRTC Done. > - non-media to non-RTP data Changed to non-(S)RTP data to be consistent with the data channel IDs. >=20 > 2) Section 1.3: >=20 > I think there are a need for some terms not yet mentioned to have > references to where they are defined. The terms I consider needing > references are: > - PPID > - TCP > - TLS >=20 > MTU would be good also. I removed TCP and TLS since they are not used in the document. For all remaining acronyms (DTLS, MTU, PPID, SCTP) I added references. >=20 > 3) Section 4: >=20 > The DTLS implementation MUST be based on [RFC6347]. >=20 > What happens when RFC 6347 is obsoleted? And that obsoletion can be > based on two cases, either the whole DTLS version is being replaced or > the RFC just updated for the same DTLS version. The later case I > definitely should be less locked in. For the DTLS version it is a > question of interoperability. Thus I think one probably should word = this as: >=20 > The DTLS implementation MUST be based on DTLS 1.2 [RFC6347]. >=20 > Then one could add supporting future versions of DTLS is RECOMMENDED = if > defined. OK. The reads The DTLS implementation MUST be based on DTLS 1.2 . The support of future versions of DTLS is RECOMMENDED if defined >=20 > 4) Section 4: >=20 > If path MTU discovery is performed by the DTLS layer, the method > described in [RFC4821] MUST be used. For probe packets, the > extension defined in [RFC6520] MUST be used. >=20 > If path MTU discovery is performed by the SCTP layer and IPv4 is = used > as the network layer protocol, the DTLS implementation MUST allow = the > DTLS user to enforce that the corresponding IPv4 packet is sent with > the DF bit set. >=20 > Although this is stated, there are no requirement that I find in the > specification that says that you MUST implement a PMTUD method. My > understanding is that IP/UDP/DTLS/SCTP is going to have a misserable > time working if one ends up with IP fragments in other cases than for > PMTUD probing packets. Thus, I think there needs to be a requirement = on > implementing some type of PMTUD method that works in this setting. It is stated in Section 5 of draft-ietf-rtcweb-data-channel that PMTU discovery MUST be done by SCTP. >=20 > I propose: >=20 > An implementation of SCTP over DTLS MUST implement and use a path > MTU discovery method that functions without ICMP to provide SCTP > with a MTU estimate. An implementation of "Packetization Layer Path > MTU Discovery" [RFC4821] either in SCTP or DTLS is RECOMMENDED. >=20 > I do note that this text is not suitable in any of the existing > sections. Maybe a new section between 3 and 4 for general = considerations. Added exactly there... I also added based on comments to one of the data channel documents: The DTLS implementation SHOULD allow the DTLS user to control the = DSCP value used for IP packets being sent. >=20 > 5) Section 7. >=20 > It is not obvious that this do not create new security issues. To me = an > obvious candidate for causing potential issues is the requirement on > SCTP to be able to function without ICMP. Are there behaviors = introduced > that are a result of not receiving ICMP because they are not provided = to > SCTP, which compared to SCTP over IP would not exist. At the same time = I > do realize that it protects the SCTP stack from some attack vectors > through ICMP. The processing of ICMP is important to protect non-SCTP capable hosts. But when using SCTP/DTLS, you are running about a connection oriented protocol and therefore you can't just send SCTP packets to a host. So I think this is very different. If you think these should be = mentioned explicitly, I can add such text. >=20 > Cheers >=20 > Magnus Westerlund >=20 > ---------------------------------------------------------------------- > Services, Media and Network features, Ericsson Research EAB/TXM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > F=E4r=F6gatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- >=20 >=20