[manet] Fwd: New Version Notification for draft-ietf-manet-dlep-latency-extension-05.txt

[Lou Berger <[e-mail]>]

Hi all,

     This update attempts to address the open issues on the draft.  The 
nits have been addressed, but a couple of comments did not result in 
text changes.  Specifically:

WRT https://mailarchive.ietf.org/arch/msg/manet/ptFmjBUMhhir2Lzu0wv1IfJjezI

> * Regarding "The use of the Latency Range Extension SHOULD be 
> configurable", an
> operational comment: What is the default (enabled or disabled)?
I don't feel strongly about this, but I did not make a change here as 
(a) it isn't really an issue that impacts interop and (b) the WG didn't 
state an opinion on this.
> * In what cases does this not need be configurable (i.e., is it a MUST)?
As I understand it it is a choice and implementation and deployment 
scenario.  I did not change to a MUST as this would be a technical 
change that would need WG input and I personally didn't see it as a 
significant concern.

Of course, I defer to the WG.

> * Error checking: what happens if the Latency data item defined in RFC 
> 8175 falls outside the range of
> the Latency Range data item herein defined?
I spent more time consider this the related comment of the other review 
listed below,  DLEP RC 8175, notably section 6,  does not place an 
restriction on metric values.  I didn't think it appropriate for this 
extension to change this practice/precedent. Some of us discussed adding 
more guidance, e.g., something along the lines of "the receiver 
SHOULD/MAY ignore .. (when there is an inconsistency)..."  but concluded 
that this would (a) not really be meaningful to implementations and (b) 
perhaps more importantly, be consistent with the rest of the metrics 
defined in 8175.

> (i.e., I understand that should not happen but I may be wrong). And 
> what if Latency Range is included without
> Latency being included?

The document does not modify 8175, so the rules on presence and 
processing of the Latency extension remains as specified there.

WRT https://mailarchive.ietf.org/arch/msg/manet/qxJ-AxMEK3cRJucHnM9UimhXrUI

> ** Section 3.  How do the maximum and minimum latency fields relate?  For
> example, what happens if a receiver gets a message where the maximum latency is
> smaller than the minimum latency.


>
> ** Section 3.  How do the latency data item and the latency range item relate?
> For example, what happens if a receiver gets a message that has both a latency
> data item and a latency range data item, and the reported latency is outside of
> the latency range?

These comments are is similar to the error checking comment above and 
has the same response (and no resulting text change.)  This includes not 
wanting to do something that would be inconsistent with RFC8175 which is 
quite on handling of received metrics.

Please respond/discuss if you think these response are not correct if 
additional changes are needed to the document.

Thank you!
Lou
-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-manet-dlep-latency-extension-05.txt
Date: 	Wed, 20 Nov 2019 01:43:55 -0800
From: 	[e-mail]
To: 	Lou Berger <[e-mail]>, Bow-Nan Cheng <[e-mail]>




A new version of I-D, draft-ietf-manet-dlep-latency-extension-05.txt
has been successfully submitted by Lou Berger and posted to the
IETF repository.

Name: draft-ietf-manet-dlep-latency-extension
Revision: 05
Title: Dynamic Link Exchange Protocol (DLEP) Latency Range
Extension
Document date: 2019-11-20
Group: manet
Pages: 5
URL: 
https://www.ietf.org/internet-drafts/draft-ietf-manet-dlep-latency-extension-05.txt
Status: 
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-latency-extension/
Htmlized: 
https://tools.ietf.org/html/draft-ietf-manet-dlep-latency-extension-05
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-latency-extension
Diff: 
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-latency-extension-05

Abstract:
This document defines an extension to the Dynamic Link Exchange
Protocol (DLEP) to provide the range of latency that can be
experienced on a link.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat