Re: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018

"Proshin, Maksim" <mproshin@mera.ru> Mon, 08 January 2018 13:02 UTC

Return-Path: <mproshin@mera.ru>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73C7012785F for <tsvwg@ietfa.amsl.com>; Mon, 8 Jan 2018 05:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 MfrqGxiwM-Zp for <tsvwg@ietfa.amsl.com>; Mon, 8 Jan 2018 05:02:48 -0800 (PST)
Received: from mail.mera.ru (mail.mera.ru [188.130.168.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9A221242F5 for <tsvwg@ietf.org>; Mon, 8 Jan 2018 05:02:48 -0800 (PST)
Received: from mbx03.merann.ru ([192.168.50.73]) by mail.mera.ru with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) (Exim 4.89) (envelope-from <mproshin@mera.ru>) id 1eYX5h-0003mD-RB; Mon, 08 Jan 2018 16:03:49 +0300
Received: from e16srv03.merann.ru (192.168.50.33) by mbx03.merann.ru (192.168.50.73) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 8 Jan 2018 16:02:43 +0300
Received: from e16srv03.merann.ru (2001:67c:2344:50::33) by e16srv03.merann.ru (2001:67c:2344:50::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.845.34; Mon, 8 Jan 2018 16:02:43 +0300
Received: from e16srv03.merann.ru ([fe80::4855:646a:d15e:75f3]) by e16srv03.merann.ru ([fe80::4855:646a:d15e:75f3%12]) with mapi id 15.01.0845.039; Mon, 8 Jan 2018 16:02:43 +0300
From: "Proshin, Maksim" <mproshin@mera.ru>
To: "David.Black@dell.com" <David.Black@dell.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
Thread-Index: AQHTiIBCsyjl2mE4nkaio0Ly1dyIEKNp76Sc
Date: Mon, 08 Jan 2018 13:02:43 +0000
Message-ID: <650fb7bc27884328b9bfcc9016fa8b73@mera.ru>
References: <CE03DB3D7B45C245BCA0D243277949362FE164EB@MX307CL04.corp.emc.com>, <CA+-pjPzDKO4bHrgJCR+Azd5GPLUUr+oTjRwD-VLydLj0tbZwLg@mail.gmail.com>
In-Reply-To: <CA+-pjPzDKO4bHrgJCR+Azd5GPLUUr+oTjRwD-VLydLj0tbZwLg@mail.gmail.com>
Accept-Language: en-US, ru-RU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [176.213.4.1]
x-inside-org: True
Content-Type: multipart/alternative; boundary="_000_650fb7bc27884328b9bfcc9016fa8b73meraru_"
MIME-Version: 1.0
X-Source-IF-Name: mail.mera.ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/2-4Zm7AbRpQwtRTKGQpzlkqnHvE>
Subject: Re: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 13:02:51 -0000

Hi,


As I said during TSVWG session at IETF100, I'd like to see it adopted and I also plan to review it.



BR, Maksim

________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Date: Thu, Dec 14, 2017 at 11:27 PM
Subject: [tsvwg] Adoption call: draft-fairhurst-tsvwg-datagram-plpmtud-02 to end 10th January 2018
To: "tsvwg@ietf.org<mailto:tsvwg@ietf.org>" <tsvwg@ietf.org<mailto:tsvwg@ietf.org>>



I'm tardy in getting to this action item from the TSVWG meeting in Singapore ...



The TSVWG chairs are considering adoption of the draft

"Packetization Layer Path MTU Discovery for Datagram Transports".



This draft has been discussed at the previous IETF meeting and on the list, and the chairs are now looking for input from the group to help inform whether TSVWG should adopt this draft.



* Please send an email to this list if you would like to see this work adopted in TSVWG, or you have comments on the suitability for adoption.



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



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



Best wishes,



David and Wes.

(TSVWG Co-Chairs) [Gorry is recused from this adoption decision, as he is an author of this draft.]

[The time period for this adoption call is longer than usual to allow for the winter holidays - may yours be joyous!]



Abstract



   This document describes a robust method for Path MTU Discovery

   (PMTUD) for datagram Packetization layers.  The method allows a

   Packetization layer (or a datagram application that uses it) to probe

   an network path with progressively larger packets to determine a

   maximum packet size.  The document describes as an extension to RFC

   1191 and RFC 8201, which specify ICMP-based Path MTU Discovery for

   IPv4 and IPv6.  This provides functionally for datagram transports

   that is equivalent to the Packetization layer PMTUD specification for

   TCP, specified in RFC4821.