[DMM] Genart telechat review of draft-ietf-dmm-mag-multihoming-04

Robert Sparks <rjsparks@nostrum.com> Tue, 25 July 2017 21:36 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: dmm@ietf.org
Delivered-To: dmm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B961252BA; Tue, 25 Jul 2017 14:36:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: gen-art@ietf.org
Cc: ietf@ietf.org, dmm@ietf.org, draft-ietf-dmm-mag-multihoming.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.57.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150101858235.26256.6969152365134554054@ietfa.amsl.com>
Date: Tue, 25 Jul 2017 14:36:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/X_gGeeHAHTrAt3WT_rdhazyzkr4>
Subject: [DMM] Genart telechat review of draft-ietf-dmm-mag-multihoming-04
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jul 2017 21:36:22 -0000

Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dmm-mag-multihoming-04
Reviewer: Robert Sparks
Review Date: 2017-07-25
IETF LC End Date: 2017-06-16
IESG Telechat date: 2017-08-03

Summary: Ready with nits that should be addressed before publication as Proposed Standard

Thanks for addressing most of the points in my review of -03.

There are still a couple of things that I think need attention:

* In the second bullet of section 3.2 there is a sentence that does not make sense.
   Look at "or at When operating" in this sentence:
    "Packet distribution can be done
      either at the transport level, e.g. using MPTCP or at When
      operating at the IP packet level, different packets distribution
      algorithms are possible."

* I still find the definitions of Interface Label and Binding Identifier confusing.
   I suspect they _both_ need to be carefully rewritten to make sure they are
   definitions of the terms, and not descriptions of the interactions of the two
   fields. Why is the Interface Label definition talking so much about binding?
   As currently written, that last sentence of the Binding Identifier
   definition says  the document says the mobile access gateway assigns
   a single unique binding identifier for each of its interfaces.