[multipathtcp] Alexey Melnikov's No Objection on draft-ietf-mptcp-rfc6824bis-15: (with COMMENT)

Alexey Melnikov via Datatracker <noreply@ietf.org> Thu, 16 May 2019 06:59 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: multipathtcp@ietf.org
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6D012010D; Wed, 15 May 2019 23:59:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Alexey Melnikov via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mptcp-rfc6824bis@ietf.org, Philip Eardley <philip.eardley@bt.com>, mptcp-chairs@ietf.org, philip.eardley@bt.com, multipathtcp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <155798996222.30583.6264603897187689127.idtracker@ietfa.amsl.com>
Date: Wed, 15 May 2019 23:59:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/qYYWBTl5nawWhiCoC48JabzFm7U>
Subject: [multipathtcp] Alexey Melnikov's No Objection on draft-ietf-mptcp-rfc6824bis-15: (with COMMENT)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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, 16 May 2019 06:59:22 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-mptcp-rfc6824bis-15: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-mptcp-rfc6824bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I probably would be “Yes”, if I am to finish reading this document before the
telechat.

A couple of small things:

“Appendix E.  Changes from RFC6184”

 - Did you intent to write RFC6824 here?

Section 2.4 uses “DSS”, while section 2.6 uses “DATA_SEQUENCE_SIGNAL”. If I
understood correctly they are the same thing. I suggest you use consistent
terminology.

I agree with Alissa that the meaning of extensibility flag (and its interaction
with versionning) should be clarified.