Re: [tsvwg] New Version Notification for draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt

<mohamed.boucadair@orange.com> Fri, 20 December 2019 07:37 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 1A99A120129 for <tsvwg@ietfa.amsl.com>; Thu, 19 Dec 2019 23:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] 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 ulYSJCNWMggU for <tsvwg@ietfa.amsl.com>; Thu, 19 Dec 2019 23:37:52 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAD3812006E for <tsvwg@ietf.org>; Thu, 19 Dec 2019 23:37:51 -0800 (PST)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 47fLFB23bQz8tFG; Fri, 20 Dec 2019 08:37:50 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.29]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id 47fLF93hyfz2xCF; Fri, 20 Dec 2019 08:37:49 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM21.corporate.adroot.infra.ftgroup ([fe80::d42b:2e80:86c2:5905%18]) with mapi id 14.03.0468.000; Fri, 20 Dec 2019 08:37:49 +0100
From: <mohamed.boucadair@orange.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] New Version Notification for draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
Thread-Index: AQHU+37EVVaFnUDT+EiZlElmjjQGrKfEGNBQ
Date: Fri, 20 Dec 2019 07:37:48 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330313EF16D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155620706460.23438.15285479573015945377.idtracker@ietfa.amsl.com> <5CC1D770.60809@erg.abdn.ac.uk>
In-Reply-To: <5CC1D770.60809@erg.abdn.ac.uk>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Y5B0xbTkjz2WOik7J4cCDW2R378>
Subject: Re: [tsvwg] New Version Notification for draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 20 Dec 2019 07:37:54 -0000

Hi Gorry, Chairs, all,

Given the content was extracted from a WG-adopted I-D, wouldn't be appropriate to publish this piece as draft-ietf-tsvwg-*?

Also, can we move the definition of RES/REQ from the udp-options I-D to this one?

Thank you.  

Cheers,
Med

> -----Message d'origine-----
> De : tsvwg [mailto:tsvwg-bounces@ietf.org] De la part de Gorry Fairhurst
> Envoyé : jeudi 25 avril 2019 17:51
> À : tsvwg@ietf.org
> Objet : Re: [tsvwg] New Version Notification for draft-fairhurst-tsvwg-udp-
> options-dplpmtud-00.txt
> 
> 
> Following discussions at the last IETF with my co-chairs, I was asked to
> resubmit the UDP Options text for DPLPMTUD as a separate draft.  This
> removes dependencies on completing the UDP-Options work before the
> DPLPMTUD I-D can be published, which is hoped to allow earlier publication.
> 
> This will allow new methods to be developed to work with DPLPMTUD in
> pararllel with the completion of the work on UDP-Options.
> 
> We'll publish a new revision of the DPLPMTUD draft shortly that removes
> this text.
> 
> Gorry
> 
> Best wishes, Gorry and Tom.
> > A new version of I-D, draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
> > has been successfully submitted by Godred Fairhurst and posted to the
> > IETF repository.
> >
> > Name:		draft-fairhurst-tsvwg-udp-options-dplpmtud
> > Revision:	00
> > Title:		Datagram PLPMTUD for UDP Options
> > Document date:	2019-04-25
> > Group:		Individual Submission
> > Pages:		8
> > URL:            https://www.ietf.org/internet-drafts/draft-fairhurst-
> tsvwg-udp-options-dplpmtud-00.txt
> > Status:         https://datatracker.ietf.org/doc/draft-fairhurst-tsvwg-
> udp-options-dplpmtud/
> > Htmlized:       https://tools.ietf.org/html/draft-fairhurst-tsvwg-udp-
> options-dplpmtud-00
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-fairhurst-
> tsvwg-udp-options-dplpmtud
> >
> >
> > Abstract:
> >     This document describes how a UDP Options sender may implement
> >     Datagram Packetization Layer Path Maximum Transmission Unit Discovery
> >     (DPLPMTUD) as a robust method for Path Maximum Transmission Unit
> >     Discovery.
> >
> >
> >
> >
> > 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.
> >
> > The IETF Secretariat