Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis
Rahul Arvind Jadhav <rahul.jadhav@huawei.com> Thu, 24 January 2019 07:32 UTC
Return-Path: <rahul.jadhav@huawei.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C22E1310D9; Wed, 23 Jan 2019 23:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 uuthHNXgPJ14; Wed, 23 Jan 2019 23:32:37 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 7B9D51310D4; Wed, 23 Jan 2019 23:32:37 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 3C94A140983F6C2DBC85; Thu, 24 Jan 2019 07:32:34 +0000 (GMT)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 24 Jan 2019 07:32:33 +0000
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1591.10; Thu, 24 Jan 2019 07:32:33 +0000
Received: from BLREML701-CAH.china.huawei.com (10.20.4.170) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1591.10 via Frontend Transport; Thu, 24 Jan 2019 07:32:33 +0000
Received: from BLREML503-MBX.china.huawei.com ([169.254.9.122]) by blreml701-cah.china.huawei.com ([::1]) with mapi id 14.03.0415.000; Thu, 24 Jan 2019 13:02:20 +0530
From: Rahul Arvind Jadhav <rahul.jadhav@huawei.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
CC: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: WG Last Call for draft-ietf-mptcp-rfc6824bis
Thread-Index: AdP8pPjqwq5n45WRS2ywhz4YK91ZcQAGiU/gK2+XbvACThSe4A==
Date: Thu, 24 Jan 2019 07:32:20 +0000
Message-ID: <982B626E107E334DBE601D979F31785C5DD7B0AC@BLREML503-MBX.china.huawei.com>
References: <0dd5e48298ed4b4fb7344630abc794b7@rew09926dag03b.domain1.systemhost.net> <39fbc9f18384473398fca38670c73cf6@rew09926dag03b.domain1.systemhost.net> <LOXP123MB08058C264F95151299160EF4EB860@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <LOXP123MB08058C264F95151299160EF4EB860@LOXP123MB0805.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-IN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.157.44]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/WtPK19JTnq6vrzXRiq_cl95jTlA>
Subject: Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jan 2019 07:32:39 -0000
The last two diffs have improved the draft and as someone who had previously reviewed the draft, I would like to say "It's ready". Wish to see the implementation. Thanks for working on it. Best, Rahul > -----Original Message----- > From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of > philip.eardley@bt.com > Sent: 12 January 2019 21:57 > To: multipathtcp@ietf.org > Cc: tsvwg@ietf.org > Subject: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis > > Hi, > This starts a WG last call for draft-ietf-mptcp-rfc6824bis. Comments by the > end of January please. As well as suggested changes or edits, positive review > comments ("It's ready") are also very valuable. > > The comments from the previous WGLC have been addressed, and since > there were a few changes we're checking with another WGLC. > As a reminder, this document Obsoletes: 6824 (if approved) and its Intended > status is Standards Track. > Christoph is working on approval for releasing the code for the bis > implementation. We hoped this would happen in the autumn, but there is > now no clear timescale and so we're proposing to move ahead now. > > Best wishes, > Phil & Yoshi > > > _______________________________________________ > multipathtcp mailing list > multipathtcp@ietf.org > https://www.ietf.org/mailman/listinfo/multipathtcp
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Yoshifumi Nishida
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- [multipathtcp] WG Last Call for draft-ietf-mptcp-… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Alan Ford
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- [multipathtcp] FW: WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Alan Ford
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Christoph Paasch
- [multipathtcp] WG Last Call for draft-ietf-mptcp-… philip.eardley
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… Rahul Arvind Jadhav
- Re: [multipathtcp] WG Last Call for draft-ietf-mp… philip.eardley