Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis

Yoshifumi Nishida <nishida@sfc.wide.ad.jp> Wed, 04 July 2018 09:10 UTC

Return-Path: <nishida@sfc.wide.ad.jp>
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 BCC3E130E24 for <multipathtcp@ietfa.amsl.com>; Wed, 4 Jul 2018 02:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Level:
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, 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 aq_VyTiXnuia for <multipathtcp@ietfa.amsl.com>; Wed, 4 Jul 2018 02:10:55 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76050130DC1 for <multipathtcp@ietf.org>; Wed, 4 Jul 2018 02:10:55 -0700 (PDT)
Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id B095C278487 for <multipathtcp@ietf.org>; Wed, 4 Jul 2018 18:10:53 +0900 (JST)
Received: by mail-it0-f50.google.com with SMTP id j185-v6so6763219ite.1 for <multipathtcp@ietf.org>; Wed, 04 Jul 2018 02:10:53 -0700 (PDT)
X-Gm-Message-State: APt69E28OSfCLCMjE68F+scUqJVDOpOqadyX3iK0zFWlkd8cIbrFWN4s JH2tgQr1ds+amJcojqeGAoEonj9oxpbBhbilVFg=
X-Google-Smtp-Source: AAOMgpdOMU+s2oupgwinlKx5EEjRxS3Oto6cpwcbT2MZaOcxmfYl7o+S7YHXthJ4h2QgvZdKrqGSmoQXRQkGfGVmB2Y=
X-Received: by 2002:a02:2505:: with SMTP id g5-v6mr942049jag.130.1530695452374; Wed, 04 Jul 2018 02:10:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:7599:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 02:10:51 -0700 (PDT)
In-Reply-To: <419c12ae34ec45bd9ba3a0e5c8310624@rew09926dag03b.domain1.systemhost.net>
References: <0dd5e48298ed4b4fb7344630abc794b7@rew09926dag03b.domain1.systemhost.net> <39fbc9f18384473398fca38670c73cf6@rew09926dag03b.domain1.systemhost.net> <419c12ae34ec45bd9ba3a0e5c8310624@rew09926dag03b.domain1.systemhost.net>
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Date: Wed, 04 Jul 2018 02:10:51 -0700
X-Gmail-Original-Message-ID: <CAO249yeECvBxgu55zUQKBpkSQoO6683BPbOxSwad7NYLCz-R9Q@mail.gmail.com>
Message-ID: <CAO249yeECvBxgu55zUQKBpkSQoO6683BPbOxSwad7NYLCz-R9Q@mail.gmail.com>
To: "philip.eardley" <philip.eardley@bt.com>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b2bb11057028ce03"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/P6I-yYBv_JbWfC2CwZPStRbuwhQ>
Subject: Re: [multipathtcp] WG Last Call for draft-ietf-mptcp-rfc6824bis
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.26
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: Wed, 04 Jul 2018 09:10:59 -0000

We also expect the authors to respond the comments sent during WGLC as it
can trigger other comments.

Thanks,
--
Yoshi

On Wed, Jul 4, 2018 at 12:30 AM, <philip.eardley@bt.com> wrote:

> We urgently need your comments about this document.
>
> It's been in WG last call for just on 4 weeks, but I think the only
> comments so far are from the WG chairs - clearly we need more comments
> before the document can advance. We'd like to discuss and close issues
> before or during the IETF.
>
> So please can you dedicate some time to checking the document.
>
> Thanks,
> Phil & Yoshi
>
> -----Original Message-----
> From: Eardley,PL,Philip,TUD1 R
> Sent: 26 June 2018 08:33
> To: multipathtcp@ietf.org
> Subject: RE: 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
> philip.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
> 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: 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
> comments 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/i
> pr/search/?submit=draft&id=draft-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
>