[DMM] Mirja Kühlewind's No Objection on draft-ietf-dmm-pmipv6-dlif-06: (with COMMENT)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Thu, 19 March 2020 09:47 UTC

Return-Path: <noreply@ietf.org>
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 583663A2602; Thu, 19 Mar 2020 02:47:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dmm-pmipv6-dlif@ietf.org, dmm-chairs@ietf.org, dmm@ietf.org, Dapeng Liu <max.ldp@alibaba-inc.com>, max.ldp@alibaba-inc.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.121.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Message-ID: <158461123033.13529.17028438404934146154@ietfa.amsl.com>
Date: Thu, 19 Mar 2020 02:47:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/u3FbBVj4h6ETdVTUyFmw4OGW_iA>
Subject: [DMM] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?q?etf-dmm-pmipv6-dlif-06=3A_=28with_COMMENT=29?=
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 19 Mar 2020 09:47:11 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-dmm-pmipv6-dlif-06: 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:


Thanks for addressing my discuss and adding section 3.6. I know that the text
there is inline with RFC6275 and therefore I'm clearing my discuss. However I
just notice that its says

" The node MAY continue to send these
           messages at this slower rate indefinitely."

I think allowing to send something indefinitely is always a bad idea. This is a
MAY but given there is no alternative provided, I guess it's not unlikely that
people will implement it this way. It's always better to have a defined
termination condition. This could be something like "SHOULD stop sending after
X <timeunit> and log an error" where X <timeunit> is a super high value in e.g.
days. This would implicitly also allow to send indefinitely because it's a
SHOULD but would make it less likely people implement that. I personal would
however even recommend a MUST.

In any case, as RFC6275 has exactly the same sentence, so I'm not blocking on
this, but maybe still worth reconsidering...

Old comments: I fully understand why the authors decided to not make changes
but keeping these as for the record:

4) As section 3.6 talks mainly about implementation details, I suggest to move
this section into the appendix.

7) One overall editorial comment which might be too late to address: I would
have found it more easy to read if you would have first introduced the new
messages and then used the concrete message names in the description in section