Return-Path: 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 18919130E39 for ; Wed, 18 Jul 2018 08:59:09 -0700 (PDT) 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, 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 I_m1mwMJRMp6 for ; Wed, 18 Jul 2018 08:59:05 -0700 (PDT) Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE62B130DFE for ; Wed, 18 Jul 2018 08:59:04 -0700 (PDT) Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by EVMED02-UKBR.bt.com (10.216.161.32) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 18 Jul 2018 16:58:59 +0100 Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Wed, 18 Jul 2018 16:59:02 +0100 Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.1293.004; Wed, 18 Jul 2018 16:59:02 +0100 From: To: , CC: , Thread-Topic: Review of RFC6824bis - Multipath TCP Thread-Index: AdQerxiJ3zmxcKJgQ8Kus8ghK021hA== Date: Wed, 18 Jul 2018 15:59:01 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.216.161.45] Content-Type: multipart/alternative; boundary="_000_bdcb304e18274eadbfa22013c7a23883rew09926dag03bdomain1sy_" MIME-Version: 1.0 Archived-At: Subject: [multipathtcp] Review of RFC6824bis - Multipath TCP X-BeenThere: multipathtcp@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Multi-path extensions for TCP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2018 15:59:09 -0000 --_000_bdcb304e18274eadbfa22013c7a23883rew09926dag03bdomain1sy_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Xavier, Rahul, Thank-you very much for agreeing to review the document, it is much appreci= ated. (Rahul - I hope I got the right email address) The right document to review is https://tools.ietf.org/html/draft-ietf-mptc= p-rfc6824bis (-11) Please send comments to the mailing list multipathtcp@ie= tf.org (Don't worry about repeating issues that have already been raised. If you'r= e interested in tracking Christoph's working copy as the issues raised so f= ar are fixed, https://github.com/multipath-tcp/draft-ietf-mptcp-rfc6824bis/= pull/6. And https://github.com/multipath-tcp/draft-ietf-mptcp-rfc6824bis/i= ssues) Thank-you! Phil & Yoshi -- -----Original Message----- From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of phil= ip.eardley@bt.com Sent: 26 June 2018 03:33 To: multipathtcp@ietf.org Subject: Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis Hi, Just a reminder about the WGLC for the protocol bis. Please send comments, = Thanks! Phil & Yoshi -----Original Message----- From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of phil= ip.eardley@bt.com Sent: 05 June 2018 12:21 To: multipathtcp@ietf.org Subject: Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis As a reminder, this document Obsoletes: 6824 (if approved) and its Intended= status is Standards Track. As well as suggested changes or edits, positive review comments ("It's read= y") are also very valuable. -----Original Message----- From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of phil= ip.eardley@bt.com Sent: 05 June 2018 09:14 To: multipathtcp@ietf.org Subject: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis This starts a WG Last Call for draft-ietf-mptcp-rfc6824bis. Please send com= ments by the end of June. Please note there are three IPR disclosures (we're working on getting them = added to the rfc6824bis page): * two are inherited from RFC6824 https://datatracker.ietf.org/ipr/search/?= submit=3Ddraft&id=3Ddraft-ietf-mptcp-multiaddressed * one is inherited from draft-paasch-mptcp-syncookies (which got include in= rfc6824bis) https://datatracker.ietf.org/ipr/2678/ Thanks, Phil & Yoshi _______________________________________________ multipathtcp mailing list multipathtcp@ietf.org https://www.ietf.org/mailman/listinfo/multipathtcp _______________________________________________ multipathtcp mailing list multipathtcp@ietf.org https://www.ietf.org/mailman/listinfo/multipathtcp _______________________________________________ multipathtcp mailing list multipathtcp@ietf.org https://www.ietf.org/mailman/listinfo/multipathtcp --_000_bdcb304e18274eadbfa22013c7a23883rew09926dag03bdomain1sy_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Xavier, Rahul,

Thank-you very much for agreeing to review the document, it is muc= h appreciated.

(Rahul – I hope I got the right email address)

The right document to review is https:/= /tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis (-11) Please send comm= ents to the mailing list multipathtcp@ietf.org

(Don’t worry about repeating issues that ha= ve already been raised. If you’re interested in tracking Christoph= 217;s working copy as the issues raised so far are fixed, https://github.com/multipath-tcp/draft-ietf-mptcp-rfc6824bis/pull/6.  And https://github.com/multipath-tcp/draft-ietf-mptcp-rfc6824bis/issues)

 

Thank-you!

Phil & Yoshi

--

-----Original Message-----

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com

Sent: 26 June 2018 03:33

To: mult= ipathtcp@ietf.org

Subject: Re: [multipathtcp] WG Last Call for draf= t-ietf-mptcp-rfc6824bis

 

Hi,

Just a reminder about the WGLC for the protocol b= is. Please send comments, Thanks!

Phil & Yoshi

 

-----Original Message-----

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com

Sent: 05 June 2018 12:21

To: mult= ipathtcp@ietf.org

Subject: Re: [multipathtcp] WG Last Call for draf= t-ietf-mptcp-rfc6824bis

 

As a reminder, this document Obsoletes: 6824 (if = approved) and its Intended status is Standards Track.

 

As well as suggested changes or edits, positive r= eview comments ("It's ready") are also very valuable.

 

-----Original Message-----

From: multipathtcp [mailto:multipathtcp-bounces@ietf.org] On Behalf Of philip.eardley@bt.com

Sent: 05 June 2018 09:14

To: mult= ipathtcp@ietf.org

Subject: [multipathtcp] WG Last Call for draft-ie= tf-mptcp-rfc6824bis

 

This starts a WG Last Call for draft-ietf-mptcp-r= fc6824bis. Please send comments by the end of June.

 

Please note there are three IPR disclosures (we'r= e working on getting them added to the rfc6824bis page):

 

* two are inherited from RFC6824  https://datatracker.ietf.org/ipr/search/?submit=3Ddraft&id=3Ddraft-ietf= -mptcp-multiaddressed   

* one is inherited from draft-paasch-mptcp-syncoo= kies (which got include in rfc6824bis) https://datatracker.ietf= .org/ipr/2678/

 

Thanks,

Phil & Yoshi

_______________________________________________

multipathtcp mailing list

multipat= htcp@ietf.org

https://www.ietf.org/mailman/listinfo/multipathtcp

 

_______________________________________________

multipathtcp mailing list

multipat= htcp@ietf.org

https://www.ietf.org/mailman/listinfo/multipathtcp

 

_______________________________________________

multipathtcp mailing list

multipat= htcp@ietf.org

https://www.ietf.org/mailman/listinfo/multipathtcp

 

 =

 

--_000_bdcb304e18274eadbfa22013c7a23883rew09926dag03bdomain1sy_--