
From nobody Wed May  1 12:43:11 2019
Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD971201B8; Wed,  1 May 2019 12:43:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Warren Kumari via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-multi-hop-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Warren Kumari <warren@kumari.net>
Message-ID: <155673978383.1000.10791525289283413645.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2019 12:43:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/bKjVyY7wWbAF2DlzQMllnyhwbpE>
Subject: [manet] Warren Kumari's No Objection on draft-ietf-manet-dlep-multi-hop-extension-06: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 19:43:04 -0000

Warren Kumari has entered the following ballot position for
draft-ietf-manet-dlep-multi-hop-extension-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:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-multi-hop-extension/



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

Thank you for writing this -- I learnt a bunch while reading it.

I have a few minor comments:
1: "This document refers to forwarding by intermediate modems as 'multi-hop
forwarding'.  example using . DLEP Destination messages" There is a random ".
exmaple using ." in the above.

2: "The Hop Count Data Item is used by a modem to indicate the number of modem
that transmits/sends data to reach a particular destination, ..." This is
really hard to parse - I think you need "number of modem*s*" and
s/transmits/transmit/". Or, perhaps something like "The Hop Count Data Item is
used by a modem to indicate the number of modems that data will transit to
reach ..."?

3: Question: "The data item also contains an indication of when a destination
which currently has a hop count of greater than one (1) could be made directly
reachable by a modem, e.g., by re-aiming an antenna." -- how can a modem know
this? Unless it knows physically where a destination is, what the antenna
information is, what objects might be between the antenna and destination
exist, etc I cannot see how this might work -- but, then again, I know very
little about this technology, so I'm happy to be educated...

4: IANA is likely to have questions about "Hop Control Actions Registry", like
what the registration policy is, etc...



From nobody Wed May  1 13:40:14 2019
Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 12647120094; Wed,  1 May 2019 13:40:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-multi-hop-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155674321306.791.1391699664410908649.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2019 13:40:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/IwR8tJL5HhTMmxiauEmllYyRE5g>
Subject: [manet] Roman Danyliw's Discuss on draft-ietf-manet-dlep-multi-hop-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 20:40:13 -0000

Roman Danyliw has entered the following ballot position for
draft-ietf-manet-dlep-multi-hop-extension-06: Discuss

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-manet-dlep-multi-hop-extension/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This extension (much like draft-ietf-manet-dlep-pause-extension) seems to
provide a mechanism to direct a modem to drop traffic in an unauthenticated
fashion -- for directly connected networks via the terminate action; and for
multi-hop networks via the suppress action.

For example, per the mobile scenario in Section 4 of RFC8175, a compromised
laptop in the switch could use this extension instruct the modem to drop
packets without authentication.

I saw in Warren’s comment ballet on draft-ietf-manet-dlep-pause-extension
(https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-pause-extension/ballot/)
that

“Lou will add:
  Implementations of the extension defined in this document MUST support
   configuration of TLS usage, as describe in <xref target="RFC8175"/>,
   in order to protect configurations where injection attacks are
   possible, i.e., when the link between a modem and router is not
   otherwise protected.”

I believe the same caveat is needed in this draft as they are enabling similar
behavior.  Please correct me if I’m conflating the capabilities of this
extension with the pause extension.


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

A few questions and an editorial nit.

(1) Section 1.  Editorial.  There is a sentence fragment “example using.” which
likely needs to be removed.

(2) Section 2.  Per “The use of the Multi-Hop Forwarding Extension SHOULD be
configurable”, what is meant by configurable?

(3) Section 3.2.2 and 3.2.3.  The Terminate and Direct Connection messages are
not supposed to be (MUST NO) be sent in a Session Update Message.  How should
the modem behave if it receives one anyway?



From nobody Wed May  1 18:59:15 2019
Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 649CF1202A7; Wed,  1 May 2019 18:59:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-multi-hop-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <155676234540.2806.2619122792728039226.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2019 18:59:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/S_s0i5MB1DJqL_D0ASQ80kjm24U>
Subject: [manet] Benjamin Kaduk's No Objection on draft-ietf-manet-dlep-multi-hop-extension-06: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2019 01:59:06 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-manet-dlep-multi-hop-extension-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:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-multi-hop-extension/



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

I support Roman's Discuss.

I think that there's room in the document to add some of the
clarifications made in response to the TSV-art review, especially
regarding the "exception cases" responsible for SHOULD-level
requirements as opposed to MUST-level requirements.

Section 1

   forwarding in intermediate modems.  This document refers to
   forwarding by intermediate modems as 'multi-hop forwarding'.  example
   using . DLEP Destination messages can be used to report such

nit: there seems to be some formatting issue or extraneous pasted text
here.

   It is important to note that the use of the hop control mechanism
   defined in this can result in connectivity changes and even loss of
   the ability to reach one or more destinations.  The defined mechanism

nit: missing word ("this document", perhaps?)

   will report such connectivity changes, but the details of what a
   router does or how it reacts to such are out scope of this document.

nit: maybe s/to such/to such reports/?

Section 2

   The use of the Multi-Hop Forwarding Extension SHOULD be configurable.
   To indicate that the extension is to be used, an implementation MUST
   include the Multi-Hop Forwarding Extension Type Value in the
   Extensions Supported Data Item.  [...]

Is the configurability for exposing that the feature is available (in
the Extensions Supported data item)?  (Independently of that answer?) I
don't think the second MUST is appropriate, as it is just duplicating a
requirement from RFC 8175.

Section 3.1

   The Hop Count Data Item is used by a modem to indicate the number of
   modem that transmits/sends data to reach a particular destination,

nit: "modems" plural and "transmit/send" to match.

   The Hop Count Data Item SHOULD be carried in the Destination Up,
   Destination Update, Destination Announce Response, and Link
   Characteristics Response Messages when the Hop Count to a destination
   is greater than one (1).

I'm not sure that the response to the tsv-art review addressed the key
question, namely: should this data item be carried in messages other
than the four listed here?  The current text makes no statement either
way, but the reviewer seemed to think that the intent was to suggest
that it did not make sense to carry the Hop Count Data Item in messages
not listed here.  Is that incorrect?

   A router receiving a Hop Count Data Item can use this information in
   its forwarding and routing decisions, and specific use is out of
   scope of this document.  The absence of the Hop Count Data Item MUST
   be interpreted by the router as a Hop Count value of one (1).

This "MUST" may not be forward-looking, in the case where some future
extension supersedes this one and so a message lacks a Hop Count Data
Item but has some other indicator of a greater-than-one hop count.  To
phrase it differently, in some sense this text is attempting to place a
constraint on implementations that do not implement this specification.
Perhaps the declarative "is interpreted" is less problematic.

Section 3.2

                                                        The modem MUST
   also notify the router of each destination that is not identified in
   the Link Characteristics Response Message and has a changed Hop Count
   impacted via a Destination Update Message.

nit: "changed" and "impacted" seem redundant.

For both the Session Update and Link Characteristic Request cases, we
only talk about Destination Down and Destination Update messages.  Is
there any case where we might need to send a Destination Up message in
response to the changes effected by a Hop Control Data Item (or is that
requirement already imposed by RFC 8175 in a part that I didn't read)?

Section 3.2.4

   A modem which receives the Suppress Forwarding Data Item in a Session
   Update Message MUST suppress multi-hop forwarding on a device wide
   basis.  This means that data traffic originating from the modem's
   peer router SHALL only be sent by the modem to destinations that are
   one modem hop away, and that any data traffic received by the modem
   from another modem that is not destined to the peer router SHALL be
   dropped.  [...]

nit(?): I'm not sure I understand the meaning of "destined to the peer
router", here.  It feels more natural if I instead say "destined to
itself", but perhaps this is because I am using "peer" to refer to
modem-level peering and this is instead intended to reflect a
relationship between the modem and router components of a single DLEP
entity.

Section 4

I don't think that "The extension does not inherently introduce any
additional threats above those documented in [RFC8175]." is really
correct -- as Roman notes, we are setting up control messages to change
the configuration of the radio hardware in ways not envisioned by RFC
8175 (i.e., "re-aiming the antenna"), as well as the explicit software
"suppress" controls.

                                        With the Link Characteristics
   Request Message, this risk is implicit.  With the Hop Control
   mechanism defined in this document it is more likely.  From a

nit: I don't think "implicit" conveys quite the intended meaning;
perhaps "implicit and small" is better.

   security perspective, implementations should be aware of this
   increased risk and may choose to implement additional configuration
   control mechanisms to ensure that the Hop Control mechanism is only
   used under conditions intended by the network operator.

(It seems like in practice this will mean the TLS requirement Roman
mentions, for almost all environments, though perhaps I am missing some
details.)

Section 5.3

I agree with Barry that some guidance to the expert is probably in
order.



From nobody Sun May  5 17:40:18 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E60771200F7 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 17:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 2-zpHwO-M6l7 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 17:40:10 -0700 (PDT)
Received: from gproxy6-pub.mail.unifiedlayer.com (outbound-ss-348.hostmonster.com [74.220.202.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3396120041 for <manet@ietf.org>; Sun,  5 May 2019 17:40:09 -0700 (PDT)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy6.mail.unifiedlayer.com (Postfix) with ESMTP id 592241E0721 for <manet@ietf.org>; Sun,  5 May 2019 18:40:06 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id NRfqhAIvKVLCbNRfqhaD4S; Sun, 05 May 2019 18:40:06 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=1q4I8uCBIa3Ol5/0n6mH3CXLIwS1QSLgK4TbONJ4XAw=; b=un11AiYTUIBcf+GJgBGHKLHwO5 0wIJjeHGOrc8t7KQzivA+VRLfluBKKqgVCoUFQWNQ3e2icPjYLuYfEGpLlKtQmKrX5oq/FhxynG4s /8fFP21dM65zepikBIU2l+6AN;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:51474 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hNRfp-001xXr-Sm; Sun, 05 May 2019 18:40:05 -0600
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Ratliff, Stanley" <sratliff@idirect.net>, The IESG <iesg@ietf.org>
Cc: "draft-ietf-manet-dlep-pause-extension@ietf.org" <draft-ietf-manet-dlep-pause-extension@ietf.org>, "manet@ietf.org" <manet@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>, Bob Briscoe <ietf@bobbriscoe.net>
References: <155437815884.30894.8011482899811561433.idtracker@ietfa.amsl.com> <bcd469e9-2d36-3fc7-0d41-56d26bb32aca@labn.net> <8c18420b622f405eb0d4adcf844b315d@idirect.net> <HE1PR0701MB25225A4933D7C72B7B19FB1895510@HE1PR0701MB2522.eurprd07.prod.outlook.com> <36cb484b-f2a5-0f13-5210-e0b67b4a4231@labn.net> <HE1PR0701MB2522FFFAC71265215BB63346952F0@HE1PR0701MB2522.eurprd07.prod.outlook.com>
From: Lou Berger <lberger@labn.net>
Openpgp: preference=signencrypt
Autocrypt: addr=lberger@labn.net; prefer-encrypt=mutual; keydata= mQENBERW5dYBCAC1Bjgr/mVovBhi1rbqkowJShVtvLitNEGOTd6RtmwO7FPebg61J9+kRFTz 1wt869yiAjtQO1EtQs26QFTH5ZDZJU/LDAOzxTi12mpBic+AWI8W0yrB1C+KOZ0gw2p7Vnfj EKc3ohwkCICHTnZ3blO8Mslb4qHGxDm7Uy3luRjvH1ZDifuZvfFHcHVw2dJyGwLg2MhXCqpo OyUqFN0tlGqz1TOCAy3/IMG6OdNK27DGF5+vJyIqek/2xkIVDOLgzVCek3dARLqPP37W1Lx2 uXJUsgcJ7t7om5AEV2LTFrafvAvJbKLT9RZ0fgF4LXeRTIVlFXKkvYJFgygW+r4JCTvHABEB AAG0HUxvdSBCZXJnZXIgPGxiZXJnZXJAbGFibi5uZXQ+iQGHBBABAgBxBQJEVuXyMBSAAAAA ACAAB3ByZWZlcnJlZC1lbWFpbC1lbmNvZGluZ0BwZ3AuY29tcGdwbWltZQcLCQgHAwIKAhkB GRhsZGFwOi8va2V5c2VydmVyLnBncC5jb20FGwMAAAADFgIBBR4BAAAABBUICQoACgkQgbLN W8HBX9eB9QgAl8/lFnNh43at51P//sRX8cDg33C/biok8st8Fff0Y/6p+6HkYKQcxiuZuOLr HHtBFxTdMGfFrlJIFob/N6m92CwVwoTRZu8QIe68DLewd+72PIEzvlSy/iTq3e91XqfGWCE7 oqw7H/weJJlB7yzPWXra/BwgPD+WkTxUiKeG2F2HzBTQfBQ6VpHiMqW6AL0jcCh/Drya93ZA aAdWfW2ywVPqIKETZIk04SBsZCw9WESB2If/NqeZu/DNwBg4FsXCrfp3WfMSTkYmfT3zcU11 MpKcv20YUpG8Jf9lyMY1DgMHHdpUHdjo/fuLz4aVSQvt8EygRSzCxGWOWb89bUosAbkBDQRE VuXXAQgApBEy7m0+xMm4SEcQtFi/UQQqjVOllc2227M1ypbcEMRa46Tq6p0P5QBM9C9pxjAl tyI2m3hzvBxBJNnjknXTp875DGyj/yDwj9VeA18Tj9q6PRsJIxAnGKBgWO0yGdZLpsp0AN5n kMamxdVFGYojzUiwkPBayST6sEUp33o4xHsx99TA2bFxZRj6k0igWgdrPVq4qeEgD1l7Cl3f pj96owzm+7wecswAts2b545gfR4/V/Vx3VUebETR/LwMDecXokP5fiDAIRHhEUi/+FXcwg6w 6jtPilFcJ64HJP6P81OUdfeMDUxvSmbeRqXaZrbRN+hF6XfWODTKepsqPaX8TQARAQABiQEi BBgBAgAMBQJEVuXXBRsMAAAAAAoJEIGyzVvBwV/XUcMH/2eB6dvsP52su9KgaDHqsgPbxF21 AQL9oDCheN+AJKD3Eouj/d/MbQdsp/M/pjgTAqB3G4/rtoyJw+BDjnvZwdUe4HQ656IPZOub e10sOgq1taJQZtQIl+mWKURMGlIihScYeuGfi/1RzMqXeCcFW63n5POVG55FzU8B7DBwQ2oJ Zy7NL0YVbT0ROXGson6WHLhzGnVP8CjHq5TN5co/FH/2BntaQIdSaOmTqN+vy38KkRsYa3cx k9eTbP99ypebZclmw6kxlOZGl9DBp4qNkTn/7LgQ7iZNVyESs9rSE7hQXnmfM+C+TCpeZo62 8AwC5SYEqa5YlkpgsP0NIEMAIoU=
Message-ID: <116fd2c7-2175-ffa8-d51d-25dabf5ca429@labn.net>
Date: Sun, 5 May 2019 20:40:04 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <HE1PR0701MB2522FFFAC71265215BB63346952F0@HE1PR0701MB2522.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hNRfp-001xXr-Sm
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net (fs2.dc.labn.net) [72.66.11.201]:51474
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/Bkf9mttafw246n8jueWR2BAgnvU>
Subject: Re: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 00:40:12 -0000

Hi Magnus/Bob,
	I've updated the intro to try to address your points, while also trying
to bring in Stan's point, :

   The base DLEP specification does not include any data plane flow
   control capability.  The extension defined in this document supports
   flow control of data traffic based on explicit messages sent via DLEP
   by a modem to indicate when a router should hold off sending traffic,
   and when it should resume.  This functionality parallels the flow
   control mechanism found in PPP over Ethernet (PPPoE) per [RFC5578].
   The extension also optionally supports DSCP (differentiated services
   codepoint) aware flow control for use by DiffServ-aware modems.  (For
   general background on Differentiated Services see [RFC2475].)  This
   functionality is very similar to that provided by Ethernet Priority
   flow control, see [IEEE.802.1Q_2014].  The extension defined in this
   document is referred to as "Control Plane Based Pause".  Other flow
   control methods are possible with DLEP, e.g., see
   [I-D.ietf-manet-dlep-da-credit-extension] and
   [I-D.ietf-manet-dlep-credit-flow-control].

Please let me/us know what you think.

Lou


On 4/11/19 8:12 AM, Magnus Westerlund wrote:
> Hi,
> 
> I don't have a text proposal. I think if you work with Bob to detail out
> the use case and
> clarifications on the limitations with the protocol that should solve my
> issue here.
> 
> Cheers
> 
> Magnus
> 
> On 2019-04-11 13:47, Lou Berger wrote:
>> Magnus,
>>
>> On 4/5/2019 5:11 AM, Magnus Westerlund wrote:
>>> Hi,
>>>
>>> Thanks for the replies.
>>>
>>> I think the main point here is if one should treat router + modem as one
>>> common queue when it comes to meeting PHBs or treat them as two in
>>> sequence queues. If one treat them as two queues then you get the same
>>> behavior as two routers in sequence. And that is acceptable from one
>>> angle, but it also results in additional jitter and latencies.
>> I think Stan's response already covered the above. From my perspective, 
>> I agree with stan that a modem that reports DSCPs should be expected to 
>> honor them like any other transit IP device (router, middlebox, etc.).  
>> I think that the following is possible in the non-diffserv modem aware 
>> case - but another approach would be to not deploy such limited modems 
>> in a network that requires DSCP support - just like you wouldn't deploy 
>> a router that doesn't support a particular PHB in network that expects 
>> to support it.
>>
>>> If we take the Expedited Forwarding PHB (RFC 3246) treating this as two
>>> queue results in that the error is E_a1 (router) + E_a2 (mode) rather
>>> than a E_a for the combined queue. The question is if E_a actually will
>>> be smaller than E_a1+E_a2 when one uses this type of control? In the
>>> combined case if the modem queue is so shallow that E_a2 << E_a1 as well
>>> as that time for performing the DLEP signalling is so short that the
>>> main variations ends up being in the router queue where one can apply
>>> suitable policies to control queue load to prevent violation of the
>>> targets.
>>> I think my main concern will be what happens if one attempts to
>>> implement L4S dual queues or DETNET and have DLEP in the path. Will this
>>> require additional extensions to provide more detailed flow control
>>> information so that lower latency or more deterministic behavior can be
>>> achieved?
>> Quite likely -- I think this is not the flow control you'd want with 
>> DetNet (I can't speak to L4S), i'd personally use something like what's 
>> covered in ietf-manet-dlep-da-credit-extension.
>>
>>
>>> I noticed that TSVART reviewer Bob Briscoe asked for a use case
>>> description of the case when the main queue is pushed to the router. I
>>> think that appears to be a good idea. I think what I am wondering is if
>>> there need to be some applicability statement here due the limitations
>>> of the technology?
>> I certainly have no objection to such, particularly given 
>> ietf-manet-dlep-da-credit-extension.  If you have any suggested text, 
>> that would be helpful.  Otherwise, as I mentioned in response to Bob, if 
>> really needed I can work with the Shepherd/WG on some applicability text.
>>
>> Lou
>>
>>> Cheers
>>>
>>> Magnus
>>>
>>>
> 


From nobody Sun May  5 18:01:14 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88E3F1202C4 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 18:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 ONJ7v_L-cQRh for <manet@ietfa.amsl.com>; Sun,  5 May 2019 18:01:05 -0700 (PDT)
Received: from outbound-ss-879.bluehost.com (outbound-ss-879.bluehost.com [69.89.30.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D679120440 for <manet@ietf.org>; Sun,  5 May 2019 17:58:21 -0700 (PDT)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 6CA531E0C28 for <manet@ietf.org>; Sun,  5 May 2019 18:58:17 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id NRxRhAP4EVLCbNRxRhaJ5m; Sun, 05 May 2019 18:58:17 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=EgUUTas6rGeQ/ErVOORTxtUI823bBatOOYSAthrjnkg=; b=OYrT6p8kkIelfw7eYKIrF26DAL 1lRdN28e7216wNDcMQR9/9BcqQxMh7etuCk1+LcZ8vW4K7lW2XqP1ZirQnX/+9GYGare1vaHHAn4L bFEZJOj9ozf2v/Mr2og3j3Fsg;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:52894 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hNRxR-00229W-1L; Sun, 05 May 2019 18:58:17 -0600
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-pause-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, manet@ietf.org
References: <155493243926.22516.16080901486479388697.idtracker@ietfa.amsl.com>
From: Lou Berger <lberger@labn.net>
Openpgp: preference=signencrypt
Autocrypt: addr=lberger@labn.net; prefer-encrypt=mutual; keydata= mQENBERW5dYBCAC1Bjgr/mVovBhi1rbqkowJShVtvLitNEGOTd6RtmwO7FPebg61J9+kRFTz 1wt869yiAjtQO1EtQs26QFTH5ZDZJU/LDAOzxTi12mpBic+AWI8W0yrB1C+KOZ0gw2p7Vnfj EKc3ohwkCICHTnZ3blO8Mslb4qHGxDm7Uy3luRjvH1ZDifuZvfFHcHVw2dJyGwLg2MhXCqpo OyUqFN0tlGqz1TOCAy3/IMG6OdNK27DGF5+vJyIqek/2xkIVDOLgzVCek3dARLqPP37W1Lx2 uXJUsgcJ7t7om5AEV2LTFrafvAvJbKLT9RZ0fgF4LXeRTIVlFXKkvYJFgygW+r4JCTvHABEB AAG0HUxvdSBCZXJnZXIgPGxiZXJnZXJAbGFibi5uZXQ+iQGHBBABAgBxBQJEVuXyMBSAAAAA ACAAB3ByZWZlcnJlZC1lbWFpbC1lbmNvZGluZ0BwZ3AuY29tcGdwbWltZQcLCQgHAwIKAhkB GRhsZGFwOi8va2V5c2VydmVyLnBncC5jb20FGwMAAAADFgIBBR4BAAAABBUICQoACgkQgbLN W8HBX9eB9QgAl8/lFnNh43at51P//sRX8cDg33C/biok8st8Fff0Y/6p+6HkYKQcxiuZuOLr HHtBFxTdMGfFrlJIFob/N6m92CwVwoTRZu8QIe68DLewd+72PIEzvlSy/iTq3e91XqfGWCE7 oqw7H/weJJlB7yzPWXra/BwgPD+WkTxUiKeG2F2HzBTQfBQ6VpHiMqW6AL0jcCh/Drya93ZA aAdWfW2ywVPqIKETZIk04SBsZCw9WESB2If/NqeZu/DNwBg4FsXCrfp3WfMSTkYmfT3zcU11 MpKcv20YUpG8Jf9lyMY1DgMHHdpUHdjo/fuLz4aVSQvt8EygRSzCxGWOWb89bUosAbkBDQRE VuXXAQgApBEy7m0+xMm4SEcQtFi/UQQqjVOllc2227M1ypbcEMRa46Tq6p0P5QBM9C9pxjAl tyI2m3hzvBxBJNnjknXTp875DGyj/yDwj9VeA18Tj9q6PRsJIxAnGKBgWO0yGdZLpsp0AN5n kMamxdVFGYojzUiwkPBayST6sEUp33o4xHsx99TA2bFxZRj6k0igWgdrPVq4qeEgD1l7Cl3f pj96owzm+7wecswAts2b545gfR4/V/Vx3VUebETR/LwMDecXokP5fiDAIRHhEUi/+FXcwg6w 6jtPilFcJ64HJP6P81OUdfeMDUxvSmbeRqXaZrbRN+hF6XfWODTKepsqPaX8TQARAQABiQEi BBgBAgAMBQJEVuXXBRsMAAAAAAoJEIGyzVvBwV/XUcMH/2eB6dvsP52su9KgaDHqsgPbxF21 AQL9oDCheN+AJKD3Eouj/d/MbQdsp/M/pjgTAqB3G4/rtoyJw+BDjnvZwdUe4HQ656IPZOub e10sOgq1taJQZtQIl+mWKURMGlIihScYeuGfi/1RzMqXeCcFW63n5POVG55FzU8B7DBwQ2oJ Zy7NL0YVbT0ROXGson6WHLhzGnVP8CjHq5TN5co/FH/2BntaQIdSaOmTqN+vy38KkRsYa3cx k9eTbP99ypebZclmw6kxlOZGl9DBp4qNkTn/7LgQ7iZNVyESs9rSE7hQXnmfM+C+TCpeZo62 8AwC5SYEqa5YlkpgsP0NIEMAIoU=
Message-ID: <84e2a05c-7729-d02e-3536-f6429476cc91@labn.net>
Date: Sun, 5 May 2019 20:58:15 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <155493243926.22516.16080901486479388697.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hNRxR-00229W-1L
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net (fs2.dc.labn.net) [72.66.11.201]:52894
X-Source-Auth: lberger@labn.net
X-Email-Count: 14
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/Uu99exccDg0F6vr_6Jc5O-V214Y>
Subject: Re: [manet] Roman Danyliw's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 01:01:09 -0000

Hi,
	Please see below.

On 4/10/19 5:40 PM, Roman Danyliw via Datatracker wrote:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-manet-dlep-pause-extension-06: Discuss
> 
> 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-manet-dlep-pause-extension/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Unauthenticated shutdown of the network seems exceedingly dangerous.  An
> expansion of the implementation scenarios described in Section 4 of RFC8175 and
> the architecture laid out in Figure 1 of RFC8175 appears to be:
> 
> (a) single direct connect (1x modem + 1x router)
> (b) single dedicated switch (1x modem + 1x switch + 1x router)
I think (a) and (b) are the normal expected configuration, but of course
defer to the WG and DLEP authors.

> (c) multiple connect (>1x modem + >=0 switches + 1x router)
I think this is allowed.

> (d) mobile environment (>=1x modem + switch + router + other devices in the
> switch) 
DLEP runs on the wired side, i.e., always between a modem and a local
router - never over a wireless network.  At least as I understand it.

>
(e) networked deployment (as stated in RFC8175/anything more
> complicated)
I don't think so.

> 
> I believe that the safest thing is that using TLS with this extension should be
> a MUST.  If that is problematic, then I’d only soften it to (text that amounts
> to) “in environments and deployment scenarios (a) and (b), TLS SHOULD be used. 
> In all other environments, TLS MUST be used.”
> 
I think this comment is really WRT base DLEP 8175 and that this
extension should be consistent with 8175.

> Warren: I believe that your neighbor scenario is likely scenario (c).
> 
how so?  when would a neighbor ever share a connection between a CPE
(modem) and a user's router?

> As the current security considerations say, using TLS in scenario (a) won’t
> help if the modem gets compromised.  In the above recommendation, there is an
> assumption that the switch(s) isn’t compromised (and that should be documented).
> 
Added to draft.

> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> (0) I support Warren and Magnus’s DISCUSS positions.
> 
> (1) Section 3.1.  Per the Query Parameters data item, what is the router
> behavior when it receives:
> 
> ** Num Queues = 0
> ** Num Queues <> the queues sent?
> 

This is covered by the current text:

      Queue Parameter Sub Data Items are an unordered list composed of
      sub data items with a common format.  The format of the Queue
Parameter Sub
      Data Item is patterned after the standard DLEP data item format,
      see <xref target="RFC8175"/> Section 11.3.  Any errors
      or inconsistencies encountered in parsing Sub Data Items are
      handled in the same fashion as any other Data Item parsing error
      encountered in DLEP.

> (2) Section 3.1.  Nit.  The size of the Reserved field is not indicated in the
> text (like the other fields)
corrected!

> 
> (3) Section 3.1.1, Please provide a section reference into RFC8175 on error
> parsing.
I've added text extracted from 8175:

      In particular, the receiving implementation MUST issue a
      Session Termination Message containing a Status Data Item with
      status code set to 130 'Invalid Data' and transition to the
      Session Termination state.


> 
> (4) Section 3.2  Per “Each Pause Data Item identifies the traffic to be
> suppressed by the Queue Index defined by Section 3.1”, am I reading it right
> that a Queue Parameter Data Item needs to be sent before a Pause is sent?  If
> so, I’m not sure that is said anywhere and should be.  Furthermore, how does a
> router behave if it does get a Pause message prior to getting a Parameter Data
> Item message?

This isn't possible as defined since it states in the Queue Parameter
section:
   This data item MUST be
  included in a Session Initialization Response Message that also
  contains the Control Plane Based Pause Extension Type Value in the
  Extensions Supported Data Item.

and this exchange takes place before data can be sent.

> 
> (5) Section 3.3  Related to comment-4, How does a router behave if it gets a
> Restart message prior to getting a Parameter Data Item or Pause message?
> 

same response.

Thanks for the comments. Please let me know if you still have any
outstanding comments/DISCUSSes..

Lou
> 
> 


From nobody Sun May  5 18:22:23 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716FE12008C for <manet@ietfa.amsl.com>; Sun,  5 May 2019 18:22:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.099
X-Spam-Level: ***
X-Spam-Status: No, score=3.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_SUMOF=5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 m7CnkinxVXH4 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 18:22:19 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A999120048 for <manet@ietf.org>; Sun,  5 May 2019 18:22:19 -0700 (PDT)
Received: from CMGW (unknown [10.9.0.13]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 272C3400A7 for <manet@ietf.org>; Sun,  5 May 2019 19:22:18 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id NSKghKQ7peyBxNSKghjxF2; Sun, 05 May 2019 19:22:18 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=P41/6n5+IUQUNAhyju3R/a0g1OhEg/m8RGWfDH0FnaE=; b=2KMTTqi6LBmgtv2jV2gc7TLkgW zHhvyyL7jEUDu7gJoKTKZLimec6zs5d2UldNWVbXiZ3gRJQ6GOKQgGyj5li3rM2VvufmNOmMNjN4S SkRJBuBEsoAfJNUMxV1mupbaQ;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:54954 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hNSKf-0028FW-TR; Sun, 05 May 2019 19:22:17 -0600
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-pause-extension@ietf.org, manet@ietf.org, manet-chairs@ietf.org
References: <155494445891.22757.7399588752085896470.idtracker@ietfa.amsl.com>
From: Lou Berger <lberger@labn.net>
Openpgp: preference=signencrypt
Autocrypt: addr=lberger@labn.net; prefer-encrypt=mutual; keydata= mQENBERW5dYBCAC1Bjgr/mVovBhi1rbqkowJShVtvLitNEGOTd6RtmwO7FPebg61J9+kRFTz 1wt869yiAjtQO1EtQs26QFTH5ZDZJU/LDAOzxTi12mpBic+AWI8W0yrB1C+KOZ0gw2p7Vnfj EKc3ohwkCICHTnZ3blO8Mslb4qHGxDm7Uy3luRjvH1ZDifuZvfFHcHVw2dJyGwLg2MhXCqpo OyUqFN0tlGqz1TOCAy3/IMG6OdNK27DGF5+vJyIqek/2xkIVDOLgzVCek3dARLqPP37W1Lx2 uXJUsgcJ7t7om5AEV2LTFrafvAvJbKLT9RZ0fgF4LXeRTIVlFXKkvYJFgygW+r4JCTvHABEB AAG0HUxvdSBCZXJnZXIgPGxiZXJnZXJAbGFibi5uZXQ+iQGHBBABAgBxBQJEVuXyMBSAAAAA ACAAB3ByZWZlcnJlZC1lbWFpbC1lbmNvZGluZ0BwZ3AuY29tcGdwbWltZQcLCQgHAwIKAhkB GRhsZGFwOi8va2V5c2VydmVyLnBncC5jb20FGwMAAAADFgIBBR4BAAAABBUICQoACgkQgbLN W8HBX9eB9QgAl8/lFnNh43at51P//sRX8cDg33C/biok8st8Fff0Y/6p+6HkYKQcxiuZuOLr HHtBFxTdMGfFrlJIFob/N6m92CwVwoTRZu8QIe68DLewd+72PIEzvlSy/iTq3e91XqfGWCE7 oqw7H/weJJlB7yzPWXra/BwgPD+WkTxUiKeG2F2HzBTQfBQ6VpHiMqW6AL0jcCh/Drya93ZA aAdWfW2ywVPqIKETZIk04SBsZCw9WESB2If/NqeZu/DNwBg4FsXCrfp3WfMSTkYmfT3zcU11 MpKcv20YUpG8Jf9lyMY1DgMHHdpUHdjo/fuLz4aVSQvt8EygRSzCxGWOWb89bUosAbkBDQRE VuXXAQgApBEy7m0+xMm4SEcQtFi/UQQqjVOllc2227M1ypbcEMRa46Tq6p0P5QBM9C9pxjAl tyI2m3hzvBxBJNnjknXTp875DGyj/yDwj9VeA18Tj9q6PRsJIxAnGKBgWO0yGdZLpsp0AN5n kMamxdVFGYojzUiwkPBayST6sEUp33o4xHsx99TA2bFxZRj6k0igWgdrPVq4qeEgD1l7Cl3f pj96owzm+7wecswAts2b545gfR4/V/Vx3VUebETR/LwMDecXokP5fiDAIRHhEUi/+FXcwg6w 6jtPilFcJ64HJP6P81OUdfeMDUxvSmbeRqXaZrbRN+hF6XfWODTKepsqPaX8TQARAQABiQEi BBgBAgAMBQJEVuXXBRsMAAAAAAoJEIGyzVvBwV/XUcMH/2eB6dvsP52su9KgaDHqsgPbxF21 AQL9oDCheN+AJKD3Eouj/d/MbQdsp/M/pjgTAqB3G4/rtoyJw+BDjnvZwdUe4HQ656IPZOub e10sOgq1taJQZtQIl+mWKURMGlIihScYeuGfi/1RzMqXeCcFW63n5POVG55FzU8B7DBwQ2oJ Zy7NL0YVbT0ROXGson6WHLhzGnVP8CjHq5TN5co/FH/2BntaQIdSaOmTqN+vy38KkRsYa3cx k9eTbP99ypebZclmw6kxlOZGl9DBp4qNkTn/7LgQ7iZNVyESs9rSE7hQXnmfM+C+TCpeZo62 8AwC5SYEqa5YlkpgsP0NIEMAIoU=
Message-ID: <e20c4e6d-b36f-690c-2049-4bc81f5cd37a@labn.net>
Date: Sun, 5 May 2019 21:22:16 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <155494445891.22757.7399588752085896470.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hNSKf-0028FW-TR
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net (fs2.dc.labn.net) [72.66.11.201]:54954
X-Source-Auth: lberger@labn.net
X-Email-Count: 8
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Org: HG=bhcustomer;ORG=bluehost;
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/X8Kph5MC4cA78gEwrA1t0XsCZ8A>
Subject: Re: [manet] Benjamin Kaduk's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 01:22:21 -0000

Hi,
	My apologies, I thought I responded to this, but can't seem to find the
response (hopefully my responses are consistent if I did!).

On 4/10/19 9:00 PM, Benjamin Kaduk via Datatracker wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-manet-dlep-pause-extension-06: Discuss
> 
> 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-manet-dlep-pause-extension/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> Section 3.1 defines 'Scale' as a four-bit unsigned integer field but only the
> values 0-3 are assigned, leaving 4-16k usable.  How will future values be
> assigned?
> 

A future revision or update of this document.  We discussed a IANA
registry, but thought it overkill as future additions seem quite unlikely.

> In Section 3.1.1:
> 
>    DS Field Qn:
> 
>       The data item contains a sequence of 8 bit DS Fields.  The number
>       of DS Fields present MUST equal the sum of all Num DSCPs field
>       values.
> 
> Perhaps I'm misreading, but I thought the Num DSCPs Qn field was global
> for this queue index, so there would just be one of them and no need to
> take a sum.

It's just saying that more than one DSCP can match to a single queue
index value.


> 
> In Section 3.3:
> 
>    A router which receives the Restart Data Item SHOULD resume
>    transmission of the identified traffic to the modem.
> 
> Why is this only a "SHOULD"?

to cover the case where the router is choosing not to send data, e.g.,
due to lack of available data or other policy such as traffic rate shaping.

> 
> Section 4
> 
>                                  The extension does not inherently
>    introduce any additional vulnerabilities above those documented in
>    [RFC8175].  [...]
> 
> As noted by others, this sentence is just not true.
> I will not duplicate the suggestions for additional considerations that
> need to be documented.  

Please see comments / discussion elsewhere on this.

> In particular, I agree with Roman that the use
> of TLS needs to be mandatory, especially since this protocol is
> nominally only defined for use with radio links.


As covered elsewhere, in particular this is really a comment on base
DLEP and I think this extension should be consistent with that document.
(Consider an example from when 8175 was issued, consider the case where
the modem and router use MACsec, 802.1X and 802.1 AE, why is TLS needed
as well.)

> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Section 3.1
> 
>                                 Any errors or inconsistencies
>    encountered in parsing Sub Data Items are handled in the same fashion
>    as any other Data Item parsing error encountered in DLEP.
> 
> I had a hard time finding the indicated behavior in RFC 8175 -- "error"
> does not appear at all (and "erroneous" only twice, for IP address
> processing, v4 and v6); "parse" only appears once (in the Session
> Initialization State); "inconsistent" apprears several times but I did
> not see one that seemed to be a generic catch-all case.  It's probably
> worth putting in a section reference or changing the text to use
> keywords that are searchable in RFC 8175.
> 
I've added the typical text from 8175to remove any ambiguity:

      In particular, the receiving implementation MUST issue a
      Session Termination Message containing a Status Data Item with
      status code set to 130 'Invalid Data' and transition to the
      Session Termination state.

> Section 3.1.1
> 
>    Queue Size Qn:
> 
>       A 24-bit unsigned integer representing the size, in the octet
>       scale indicated by the Scale field, of the queue supporting
>       traffic with the DSCPs associated with the queue index.
> 
> Is there any value in including a specific sentinel value that indicates
> that the modem cannot or does not wish to state the size of the
> corresponding queue?

As here is no requirement for the modem to set this, I'm not sure if
there would be any value in such.

> 
> Section 3.2
> 
>    A router which receives the Pause Data Item MUST cease sending the
>    identified traffic to the modem.  This may of course translate into
>    the router's queues exceeding their own thresholds.  If a received
>    Pause Data Item contains a Queue Index value other than 255, or a
>    queue index established by a Session Initialization or Session Update
>    Message, the router MUST terminate the session with a Status Data
>    Item indicating Invalid Data.
> 
> This would be a nit, but actually has serious functional consequences:
> remove the comma after "255".  The current text says that if the router
> receives a queue index established by a Session Initialization message,
> the router MUST terminate the session, which does not seem to be the
> intent!

done.

> 
> Section 3.3
> 
>    The Restart Data Item is used by a modem to indicate to its peer that
>    transmission of previously suppressed traffic may be resumed.  An
>    example of when a modem might send this data item is when an internal
>    queue length drops below a particular threshold.
> 
> This seems like a fine place to suggest the application of hysteresis
> (i.e., that the "particular threshold" here might be lower than the one
> indicated in Section 3.2).
> 
> Section 5.x
> 
> It's not clear to me what value there is in repeating the registration
> policy of the registries from which codepoints are being allocated.
> IANA will apply the correct policy, and the reader of this document
> doesn't need to care what policy was applied.

This section will get revised as part of final processing so defer to
both IANA and the RFC editor on this.

Thanks!
Lou
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> 


From nobody Sun May  5 18:59:49 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E23120092; Sun,  5 May 2019 18:59:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: manet@ietf.org
Message-ID: <155710798011.5217.16421585576069566541@ietfa.amsl.com>
Date: Sun, 05 May 2019 18:59:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/lPzun0EE6LmCiA8TCzmoumIYXQc>
Subject: [manet] I-D Action: draft-ietf-manet-dlep-multi-hop-extension-07.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 01:59:40 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks WG of the IETF.

        Title           : Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension
        Authors         : Bow-Nan Cheng
                          Lou Berger
	Filename        : draft-ietf-manet-dlep-multi-hop-extension-07.txt
	Pages           : 11
	Date            : 2019-05-05

Abstract:
   This document defines an extension to the Dynamic Link Exchange
   Protocol (DLEP) that enables the reporting and control of Multi-Hop
   Forwarding by DLEP capable modems.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-multi-hop-extension/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-manet-dlep-multi-hop-extension-07
https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-multi-hop-extension-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-multi-hop-extension-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun May  5 19:01:41 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3072F120041 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 19:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 WpSE9ZAGm6s1 for <manet@ietfa.amsl.com>; Sun,  5 May 2019 19:01:38 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB3B1120092 for <manet@ietf.org>; Sun,  5 May 2019 19:01:38 -0700 (PDT)
Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 4BB1340883 for <manet@ietf.org>; Sun,  5 May 2019 19:42:32 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id NSeGhAtgYVLCbNSeGhanPV; Sun, 05 May 2019 19:42:32 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: $(_cmae_reason
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=fvuHzqOMpUhrKo2v8qTgseqbDPBtWEnFWXTbyjO7ohw=; b=EK2RtAgf4/LrLz9OQ/1YHlA7Vd m66WItQcbZNzTREHzOENzTT36WSfyH4oBjLGtjy+6IfbXatE85DQviy7rmqy/M6hirqr8Ot1WRX/4 OI786ki4w/0qfcn0GOXavqDyo;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:56620 helo=fs2.dc.labn.net) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hNSeF-002DKH-PZ; Sun, 05 May 2019 19:42:31 -0600
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: manet@ietf.org, manet-chairs@ietf.org, draft-ietf-manet-dlep-multi-hop-extension@ietf.org
References: <155674321306.791.1391699664410908649.idtracker@ietfa.amsl.com>
From: Lou Berger <lberger@labn.net>
Openpgp: preference=signencrypt
Autocrypt: addr=lberger@labn.net; prefer-encrypt=mutual; keydata= mQENBERW5dYBCAC1Bjgr/mVovBhi1rbqkowJShVtvLitNEGOTd6RtmwO7FPebg61J9+kRFTz 1wt869yiAjtQO1EtQs26QFTH5ZDZJU/LDAOzxTi12mpBic+AWI8W0yrB1C+KOZ0gw2p7Vnfj EKc3ohwkCICHTnZ3blO8Mslb4qHGxDm7Uy3luRjvH1ZDifuZvfFHcHVw2dJyGwLg2MhXCqpo OyUqFN0tlGqz1TOCAy3/IMG6OdNK27DGF5+vJyIqek/2xkIVDOLgzVCek3dARLqPP37W1Lx2 uXJUsgcJ7t7om5AEV2LTFrafvAvJbKLT9RZ0fgF4LXeRTIVlFXKkvYJFgygW+r4JCTvHABEB AAG0HUxvdSBCZXJnZXIgPGxiZXJnZXJAbGFibi5uZXQ+iQGHBBABAgBxBQJEVuXyMBSAAAAA ACAAB3ByZWZlcnJlZC1lbWFpbC1lbmNvZGluZ0BwZ3AuY29tcGdwbWltZQcLCQgHAwIKAhkB GRhsZGFwOi8va2V5c2VydmVyLnBncC5jb20FGwMAAAADFgIBBR4BAAAABBUICQoACgkQgbLN W8HBX9eB9QgAl8/lFnNh43at51P//sRX8cDg33C/biok8st8Fff0Y/6p+6HkYKQcxiuZuOLr HHtBFxTdMGfFrlJIFob/N6m92CwVwoTRZu8QIe68DLewd+72PIEzvlSy/iTq3e91XqfGWCE7 oqw7H/weJJlB7yzPWXra/BwgPD+WkTxUiKeG2F2HzBTQfBQ6VpHiMqW6AL0jcCh/Drya93ZA aAdWfW2ywVPqIKETZIk04SBsZCw9WESB2If/NqeZu/DNwBg4FsXCrfp3WfMSTkYmfT3zcU11 MpKcv20YUpG8Jf9lyMY1DgMHHdpUHdjo/fuLz4aVSQvt8EygRSzCxGWOWb89bUosAbkBDQRE VuXXAQgApBEy7m0+xMm4SEcQtFi/UQQqjVOllc2227M1ypbcEMRa46Tq6p0P5QBM9C9pxjAl tyI2m3hzvBxBJNnjknXTp875DGyj/yDwj9VeA18Tj9q6PRsJIxAnGKBgWO0yGdZLpsp0AN5n kMamxdVFGYojzUiwkPBayST6sEUp33o4xHsx99TA2bFxZRj6k0igWgdrPVq4qeEgD1l7Cl3f pj96owzm+7wecswAts2b545gfR4/V/Vx3VUebETR/LwMDecXokP5fiDAIRHhEUi/+FXcwg6w 6jtPilFcJ64HJP6P81OUdfeMDUxvSmbeRqXaZrbRN+hF6XfWODTKepsqPaX8TQARAQABiQEi BBgBAgAMBQJEVuXXBRsMAAAAAAoJEIGyzVvBwV/XUcMH/2eB6dvsP52su9KgaDHqsgPbxF21 AQL9oDCheN+AJKD3Eouj/d/MbQdsp/M/pjgTAqB3G4/rtoyJw+BDjnvZwdUe4HQ656IPZOub e10sOgq1taJQZtQIl+mWKURMGlIihScYeuGfi/1RzMqXeCcFW63n5POVG55FzU8B7DBwQ2oJ Zy7NL0YVbT0ROXGson6WHLhzGnVP8CjHq5TN5co/FH/2BntaQIdSaOmTqN+vy38KkRsYa3cx k9eTbP99ypebZclmw6kxlOZGl9DBp4qNkTn/7LgQ7iZNVyESs9rSE7hQXnmfM+C+TCpeZo62 8AwC5SYEqa5YlkpgsP0NIEMAIoU=
Message-ID: <669dc091-7ab6-db0b-f1a6-8f4d62faab73@labn.net>
Date: Sun, 5 May 2019 21:42:30 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <155674321306.791.1391699664410908649.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hNSeF-002DKH-PZ
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net (fs2.dc.labn.net) [72.66.11.201]:56620
X-Source-Auth: lberger@labn.net
X-Email-Count: 12
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Org: HG=bhcustomer;ORG=bluehost;
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/WCJljfX_nHCLWIIu_6iv9io3hQA>
Subject: Re: [manet] Roman Danyliw's Discuss on draft-ietf-manet-dlep-multi-hop-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 02:01:40 -0000

Hi,
	Please see below.

On 5/1/19 4:40 PM, Roman Danyliw via Datatracker wrote:
> Roman Danyliw has entered the following ballot position for
> draft-ietf-manet-dlep-multi-hop-extension-06: Discuss
> 
> 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-manet-dlep-multi-hop-extension/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> This extension (much like draft-ietf-manet-dlep-pause-extension) seems to
> provide a mechanism to direct a modem to drop traffic in an unauthenticated
> fashion -- for directly connected networks via the terminate action; and for
> multi-hop networks via the suppress action.
> 
> For example, per the mobile scenario in Section 4 of RFC8175, a compromised
> laptop in the switch could use this extension instruct the modem to drop
> packets without authentication.
> 
> I saw in Warren’s comment ballet on draft-ietf-manet-dlep-pause-extension
> (https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-pause-extension/ballot/)
> that
> 
> “Lou will add:
>   Implementations of the extension defined in this document MUST support
>    configuration of TLS usage, as describe in <xref target="RFC8175"/>,
>    in order to protect configurations where injection attacks are
>    possible, i.e., when the link between a modem and router is not
>    otherwise protected.”
> 
> I believe the same caveat is needed in this draft as they are enabling similar
> behavior.  Please correct me if I’m conflating the capabilities of this
> extension with the pause extension.
> 

On one hand I think it is reasonable to have the security sections match
between the two.  On the other, I think it really seems this IESG is
unhappy with the language  approved for 8175.  Given this, I'll go ahead
and add the requested test.


> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> A few questions and an editorial nit.
> 
> (1) Section 1.  Editorial.  There is a sentence fragment “example using.” which
> likely needs to be removed.
> 
> (2) Section 2.  Per “The use of the Multi-Hop Forwarding Extension SHOULD be
> configurable”, what is meant by configurable?
> 
> (3) Section 3.2.2 and 3.2.3.  The Terminate and Direct Connection messages are
> not supposed to be (MUST NO) be sent in a Session Update Message.  How should
> the modem behave if it receives one anyway?
> 

base DLEP 8175 resets a session on any type of parsing error. I'm
personally not a fan of this, but it *is* what RFC8175 says...

Thanks,
Lou

> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
> 


From nobody Mon May  6 00:56:41 2019
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6F9F120049; Mon,  6 May 2019 00:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 XCMg_xF7aXDJ; Mon,  6 May 2019 00:56:30 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150078.outbound.protection.outlook.com [40.107.15.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F19120033; Mon,  6 May 2019 00:56:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CsYfBS7Fm/oOlF6Tq491O0OYCCOh6WtYSsww7sjCihE=; b=W1wFUNSs4TJxkzp/zElZJGqq39WQkPp3mtxAeFWh2FTPLs7oqGKtyyokWyNd2mOswmAhO5F5dr2ZEHYhxKq2B+VAd9uxVHmoU+PYUZXfEypwBv3PEZwgZ5ryagfT6i9v0a0mh3Sde+Vp4zPTcdx64hKXBVP3KRqfAeVG7GP3epI=
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com (10.168.128.149) by HE1PR0701MB2265.eurprd07.prod.outlook.com (10.168.30.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.13; Mon, 6 May 2019 07:56:26 +0000
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::b161:fb77:e4ea:4723]) by HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::b161:fb77:e4ea:4723%3]) with mapi id 15.20.1856.008; Mon, 6 May 2019 07:56:26 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Lou Berger <lberger@labn.net>, "Ratliff, Stanley" <sratliff@idirect.net>,  The IESG <iesg@ietf.org>
CC: "draft-ietf-manet-dlep-pause-extension@ietf.org" <draft-ietf-manet-dlep-pause-extension@ietf.org>, "manet@ietf.org" <manet@ietf.org>, Bob Briscoe <ietf@bobbriscoe.net>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Thread-Topic: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
Thread-Index: AQHU6tuJoEU8aqyRmUir+1XuKzIGuQ==
Date: Mon, 6 May 2019 07:56:26 +0000
Message-ID: <HE1PR0701MB2522441A2CC6524B41EF88E395300@HE1PR0701MB2522.eurprd07.prod.outlook.com>
References: <155437815884.30894.8011482899811561433.idtracker@ietfa.amsl.com> <bcd469e9-2d36-3fc7-0d41-56d26bb32aca@labn.net> <8c18420b622f405eb0d4adcf844b315d@idirect.net> <HE1PR0701MB25225A4933D7C72B7B19FB1895510@HE1PR0701MB2522.eurprd07.prod.outlook.com> <36cb484b-f2a5-0f13-5210-e0b67b4a4231@labn.net> <HE1PR0701MB2522FFFAC71265215BB63346952F0@HE1PR0701MB2522.eurprd07.prod.outlook.com> <116fd2c7-2175-ffa8-d51d-25dabf5ca429@labn.net>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; 
x-originating-ip: [192.176.1.82]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 26f9f157-f646-4dae-3d87-08d6d1f8576d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR0701MB2265; 
x-ms-traffictypediagnostic: HE1PR0701MB2265:
x-microsoft-antispam-prvs: <HE1PR0701MB2265392BBB20F03E8F1C7C6195300@HE1PR0701MB2265.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0029F17A3F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(136003)(366004)(396003)(346002)(376002)(199004)(189003)(51444003)(51914003)(25786009)(305945005)(66066001)(44832011)(74316002)(486006)(256004)(3846002)(14454004)(33656002)(478600001)(86362001)(446003)(6116002)(55016002)(26005)(5660300002)(316002)(52536014)(9686003)(76176011)(6436002)(71190400001)(71200400001)(7696005)(8936002)(561944003)(66476007)(66556008)(186003)(66446008)(66946007)(73956011)(99286004)(64756008)(110136005)(54906003)(2906002)(7736002)(53546011)(53936002)(229853002)(6246003)(66574012)(68736007)(476003)(4326008)(102836004)(81166006)(81156014)(8676002)(76116006)(6506007); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2265; H:HE1PR0701MB2522.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: fO8Qx6bM6vumYIqtvpI06cQ+Ee1WpoHS3ZEujFGzM3oWXNEYJ9PZJfxQSKk9WZwjo8X7Jn3SadF9aVZTeCZX2x1TsSEdxee0JY9DV/MusSWZRBLKl8ql/I0bjScVh6n2AghFsTQIDrG3uinmAkNzeuLX05IjhXfHP+fzD9uCZuvZHt1yW+NaKh7pqJMda0rs+CwnBT05QdF3LHKBK9Goz9DO5hkMnMrg4mazGSlmCZWzgSr0Oei22bE19TNTPbUvnDZYYdBkzQxIpn429nJkKB0I7jadIdTzTVGr8u6+73oiTBn3MhdSqFrQJFUGiB3w8QVIarvlioe6AW88uMYSgZmE90z1OhuRRqnMt3nNZbD/3NPmU1CpmpUXtOUvwkZrBsp6dV2TqyGRsO/38qGACzcMsHyqYSJm+37l7qSO4Mw=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 26f9f157-f646-4dae-3d87-08d6d1f8576d
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 May 2019 07:56:26.6143 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2265
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/Cd8BnD6DPc8BntKN1lzvVPHcg0U>
Subject: Re: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 07:56:33 -0000

Thanks Lou,=0A=
=0A=
I think that clarifies my issue. I will clear with the assumption that=0A=
you will include this.=0A=
=0A=
Thanks=0A=
=0A=
Magnus=0A=
=0A=
On 2019-05-06 02:40, Lou Berger wrote:=0A=
> Hi Magnus/Bob,=0A=
> 	I've updated the intro to try to address your points, while also trying=
=0A=
> to bring in Stan's point, :=0A=
>=0A=
>    The base DLEP specification does not include any data plane flow=0A=
>    control capability.  The extension defined in this document supports=
=0A=
>    flow control of data traffic based on explicit messages sent via DLEP=
=0A=
>    by a modem to indicate when a router should hold off sending traffic,=
=0A=
>    and when it should resume.  This functionality parallels the flow=0A=
>    control mechanism found in PPP over Ethernet (PPPoE) per [RFC5578].=0A=
>    The extension also optionally supports DSCP (differentiated services=
=0A=
>    codepoint) aware flow control for use by DiffServ-aware modems.  (For=
=0A=
>    general background on Differentiated Services see [RFC2475].)  This=0A=
>    functionality is very similar to that provided by Ethernet Priority=0A=
>    flow control, see [IEEE.802.1Q_2014].  The extension defined in this=
=0A=
>    document is referred to as "Control Plane Based Pause".  Other flow=0A=
>    control methods are possible with DLEP, e.g., see=0A=
>    [I-D.ietf-manet-dlep-da-credit-extension] and=0A=
>    [I-D.ietf-manet-dlep-credit-flow-control].=0A=
>=0A=
> Please let me/us know what you think.=0A=
>=0A=
> Lou=0A=
>=0A=
>=0A=
> On 4/11/19 8:12 AM, Magnus Westerlund wrote:=0A=
>> Hi,=0A=
>>=0A=
>> I don't have a text proposal. I think if you work with Bob to detail out=
=0A=
>> the use case and=0A=
>> clarifications on the limitations with the protocol that should solve my=
=0A=
>> issue here.=0A=
>>=0A=
>> Cheers=0A=
>>=0A=
>> Magnus=0A=
>>=0A=
>> On 2019-04-11 13:47, Lou Berger wrote:=0A=
>>> Magnus,=0A=
>>>=0A=
>>> On 4/5/2019 5:11 AM, Magnus Westerlund wrote:=0A=
>>>> Hi,=0A=
>>>>=0A=
>>>> Thanks for the replies.=0A=
>>>>=0A=
>>>> I think the main point here is if one should treat router + modem as o=
ne=0A=
>>>> common queue when it comes to meeting PHBs or treat them as two in=0A=
>>>> sequence queues. If one treat them as two queues then you get the same=
=0A=
>>>> behavior as two routers in sequence. And that is acceptable from one=
=0A=
>>>> angle, but it also results in additional jitter and latencies.=0A=
>>> I think Stan's response already covered the above. From my perspective,=
 =0A=
>>> I agree with stan that a modem that reports DSCPs should be expected to=
 =0A=
>>> honor them like any other transit IP device (router, middlebox, etc.). =
 =0A=
>>> I think that the following is possible in the non-diffserv modem aware =
=0A=
>>> case - but another approach would be to not deploy such limited modems =
=0A=
>>> in a network that requires DSCP support - just like you wouldn't deploy=
 =0A=
>>> a router that doesn't support a particular PHB in network that expects =
=0A=
>>> to support it.=0A=
>>>=0A=
>>>> If we take the Expedited Forwarding PHB (RFC 3246) treating this as tw=
o=0A=
>>>> queue results in that the error is E_a1 (router) + E_a2 (mode) rather=
=0A=
>>>> than a E_a for the combined queue. The question is if E_a actually wil=
l=0A=
>>>> be smaller than E_a1+E_a2 when one uses this type of control? In the=
=0A=
>>>> combined case if the modem queue is so shallow that E_a2 << E_a1 as we=
ll=0A=
>>>> as that time for performing the DLEP signalling is so short that the=
=0A=
>>>> main variations ends up being in the router queue where one can apply=
=0A=
>>>> suitable policies to control queue load to prevent violation of the=0A=
>>>> targets.=0A=
>>>> I think my main concern will be what happens if one attempts to=0A=
>>>> implement L4S dual queues or DETNET and have DLEP in the path. Will th=
is=0A=
>>>> require additional extensions to provide more detailed flow control=0A=
>>>> information so that lower latency or more deterministic behavior can b=
e=0A=
>>>> achieved?=0A=
>>> Quite likely -- I think this is not the flow control you'd want with =
=0A=
>>> DetNet (I can't speak to L4S), i'd personally use something like what's=
 =0A=
>>> covered in ietf-manet-dlep-da-credit-extension.=0A=
>>>=0A=
>>>=0A=
>>>> I noticed that TSVART reviewer Bob Briscoe asked for a use case=0A=
>>>> description of the case when the main queue is pushed to the router. I=
=0A=
>>>> think that appears to be a good idea. I think what I am wondering is i=
f=0A=
>>>> there need to be some applicability statement here due the limitations=
=0A=
>>>> of the technology?=0A=
>>> I certainly have no objection to such, particularly given =0A=
>>> ietf-manet-dlep-da-credit-extension.  If you have any suggested text, =
=0A=
>>> that would be helpful.  Otherwise, as I mentioned in response to Bob, i=
f =0A=
>>> really needed I can work with the Shepherd/WG on some applicability tex=
t.=0A=
>>>=0A=
>>> Lou=0A=
>>>=0A=
>>>> Cheers=0A=
>>>>=0A=
>>>> Magnus=0A=
>>>>=0A=
>>>>=0A=
>=0A=
-- =0A=
=0A=
Magnus Westerlund =0A=
=0A=
----------------------------------------------------------------------=0A=
Network Architecture & Protocols, Ericsson Research=0A=
----------------------------------------------------------------------=0A=
Ericsson AB                 | Phone  +46 10 7148287=0A=
Torshamnsgatan 23           | Mobile +46 73 0949079=0A=
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com=0A=
----------------------------------------------------------------------=0A=
=0A=


From nobody Mon May  6 00:57:07 2019
Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3884012011D; Mon,  6 May 2019 00:56:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-pause-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <155712940922.6675.10736168556345995881.idtracker@ietfa.amsl.com>
Date: Mon, 06 May 2019 00:56:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/6j5ZWoqGAI5NpGB2pORmHeqYvJE>
Subject: [manet] Magnus Westerlund's No Objection on draft-ietf-manet-dlep-pause-extension-06
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 07:56:58 -0000

Magnus Westerlund has entered the following ballot position for
draft-ietf-manet-dlep-pause-extension-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:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-pause-extension/


There are no remarks associated with this position.





From nobody Mon May  6 03:49:21 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC7BC1200DE for <manet@ietfa.amsl.com>; Mon,  6 May 2019 03:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 fazaoZKYC2dO for <manet@ietfa.amsl.com>; Mon,  6 May 2019 03:49:15 -0700 (PDT)
Received: from outbound-ss-879.bluehost.com (outbound-ss-879.bluehost.com [69.89.30.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0E781200BA for <manet@ietf.org>; Mon,  6 May 2019 03:49:15 -0700 (PDT)
Received: from CMGW (unknown [10.9.0.13]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id BD76F1E0BE8 for <manet@ietf.org>; Mon,  6 May 2019 04:49:14 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id NbBKhNXVfeyBxNbBKhn11s; Mon, 06 May 2019 04:49:14 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=WDTm8CiKS2rRo81Psb0DXFP8LOtB2edJhXJnCW4IXJw=; b=I/bXkXZimDBv7pvLwjJ7Q5s8QN Zrfr5K9hQP8KQFtrmD+4xguize5rQFfz7Vby2l8Hi0wElp/60i439a6mLRrfUCNK20sq54B8ZYnMe UBTXfnVKhP70WJV8HnZfh5rQM;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:39078 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hNbBK-0001PG-8Y; Mon, 06 May 2019 04:49:14 -0600
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Ratliff, Stanley" <sratliff@idirect.net>, The IESG <iesg@ietf.org>
Cc: "draft-ietf-manet-dlep-pause-extension@ietf.org" <draft-ietf-manet-dlep-pause-extension@ietf.org>, "manet@ietf.org" <manet@ietf.org>, Bob Briscoe <ietf@bobbriscoe.net>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
References: <155437815884.30894.8011482899811561433.idtracker@ietfa.amsl.com> <bcd469e9-2d36-3fc7-0d41-56d26bb32aca@labn.net> <8c18420b622f405eb0d4adcf844b315d@idirect.net> <HE1PR0701MB25225A4933D7C72B7B19FB1895510@HE1PR0701MB2522.eurprd07.prod.outlook.com> <36cb484b-f2a5-0f13-5210-e0b67b4a4231@labn.net> <HE1PR0701MB2522FFFAC71265215BB63346952F0@HE1PR0701MB2522.eurprd07.prod.outlook.com> <116fd2c7-2175-ffa8-d51d-25dabf5ca429@labn.net> <HE1PR0701MB2522441A2CC6524B41EF88E395300@HE1PR0701MB2522.eurprd07.prod.outlook.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <0caf7d03-c751-4cbc-2506-99ff95d4dbc2@labn.net>
Date: Mon, 6 May 2019 06:49:13 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <HE1PR0701MB2522441A2CC6524B41EF88E395300@HE1PR0701MB2522.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hNbBK-0001PG-8Y
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([IPv6:::1]) [72.66.11.201]:39078
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/FtcplRcJ0QiEu0bB9wHgO_8lVuo>
Subject: Re: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 10:49:18 -0000

Thanks Magnus.   I'll upload a rev with the change today (was waiting on 
AD/Shepherd, but now assume they will ask for the upload)...

Lou

On 5/6/2019 3:56 AM, Magnus Westerlund wrote:
> Thanks Lou,
>
> I think that clarifies my issue. I will clear with the assumption that
> you will include this.
>
> Thanks
>
> Magnus
>
> On 2019-05-06 02:40, Lou Berger wrote:
>> Hi Magnus/Bob,
>> 	I've updated the intro to try to address your points, while also trying
>> to bring in Stan's point, :
>>
>>     The base DLEP specification does not include any data plane flow
>>     control capability.  The extension defined in this document supports
>>     flow control of data traffic based on explicit messages sent via DLEP
>>     by a modem to indicate when a router should hold off sending traffic,
>>     and when it should resume.  This functionality parallels the flow
>>     control mechanism found in PPP over Ethernet (PPPoE) per [RFC5578].
>>     The extension also optionally supports DSCP (differentiated services
>>     codepoint) aware flow control for use by DiffServ-aware modems.  (For
>>     general background on Differentiated Services see [RFC2475].)  This
>>     functionality is very similar to that provided by Ethernet Priority
>>     flow control, see [IEEE.802.1Q_2014].  The extension defined in this
>>     document is referred to as "Control Plane Based Pause".  Other flow
>>     control methods are possible with DLEP, e.g., see
>>     [I-D.ietf-manet-dlep-da-credit-extension] and
>>     [I-D.ietf-manet-dlep-credit-flow-control].
>>
>> Please let me/us know what you think.
>>
>> Lou
>>
>>
>> On 4/11/19 8:12 AM, Magnus Westerlund wrote:
>>> Hi,
>>>
>>> I don't have a text proposal. I think if you work with Bob to detail out
>>> the use case and
>>> clarifications on the limitations with the protocol that should solve my
>>> issue here.
>>>
>>> Cheers
>>>
>>> Magnus
>>>
>>> On 2019-04-11 13:47, Lou Berger wrote:
>>>> Magnus,
>>>>
>>>> On 4/5/2019 5:11 AM, Magnus Westerlund wrote:
>>>>> Hi,
>>>>>
>>>>> Thanks for the replies.
>>>>>
>>>>> I think the main point here is if one should treat router + modem as one
>>>>> common queue when it comes to meeting PHBs or treat them as two in
>>>>> sequence queues. If one treat them as two queues then you get the same
>>>>> behavior as two routers in sequence. And that is acceptable from one
>>>>> angle, but it also results in additional jitter and latencies.
>>>> I think Stan's response already covered the above. From my perspective,
>>>> I agree with stan that a modem that reports DSCPs should be expected to
>>>> honor them like any other transit IP device (router, middlebox, etc.).
>>>> I think that the following is possible in the non-diffserv modem aware
>>>> case - but another approach would be to not deploy such limited modems
>>>> in a network that requires DSCP support - just like you wouldn't deploy
>>>> a router that doesn't support a particular PHB in network that expects
>>>> to support it.
>>>>
>>>>> If we take the Expedited Forwarding PHB (RFC 3246) treating this as two
>>>>> queue results in that the error is E_a1 (router) + E_a2 (mode) rather
>>>>> than a E_a for the combined queue. The question is if E_a actually will
>>>>> be smaller than E_a1+E_a2 when one uses this type of control? In the
>>>>> combined case if the modem queue is so shallow that E_a2 << E_a1 as well
>>>>> as that time for performing the DLEP signalling is so short that the
>>>>> main variations ends up being in the router queue where one can apply
>>>>> suitable policies to control queue load to prevent violation of the
>>>>> targets.
>>>>> I think my main concern will be what happens if one attempts to
>>>>> implement L4S dual queues or DETNET and have DLEP in the path. Will this
>>>>> require additional extensions to provide more detailed flow control
>>>>> information so that lower latency or more deterministic behavior can be
>>>>> achieved?
>>>> Quite likely -- I think this is not the flow control you'd want with
>>>> DetNet (I can't speak to L4S), i'd personally use something like what's
>>>> covered in ietf-manet-dlep-da-credit-extension.
>>>>
>>>>
>>>>> I noticed that TSVART reviewer Bob Briscoe asked for a use case
>>>>> description of the case when the main queue is pushed to the router. I
>>>>> think that appears to be a good idea. I think what I am wondering is if
>>>>> there need to be some applicability statement here due the limitations
>>>>> of the technology?
>>>> I certainly have no objection to such, particularly given
>>>> ietf-manet-dlep-da-credit-extension.  If you have any suggested text,
>>>> that would be helpful.  Otherwise, as I mentioned in response to Bob, if
>>>> really needed I can work with the Shepherd/WG on some applicability text.
>>>>
>>>> Lou
>>>>
>>>>> Cheers
>>>>>
>>>>> Magnus
>>>>>
>>>>>


From nobody Mon May  6 08:08:57 2019
Return-Path: <sratliff@idirect.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E241F1201B4 for <manet@ietfa.amsl.com>; Mon,  6 May 2019 08:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 L6hFhl-eaZma for <manet@ietfa.amsl.com>; Mon,  6 May 2019 08:08:52 -0700 (PDT)
Received: from us-smtp-delivery-174.mimecast.com (us-smtp-delivery-174.mimecast.com [63.128.21.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D7F31201A8 for <manet@ietf.org>; Mon,  6 May 2019 08:08:52 -0700 (PDT)
Received: from webmail.idirect.net (198.180.159.2 [198.180.159.2]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-258-jk-iWV4_NCG1k_fDuoeWHA-1; Mon, 06 May 2019 11:08:47 -0400
Received: from vausditchmc3.idirect.net (10.250.251.203) by vausditchmc3.idirect.net (10.250.251.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 6 May 2019 11:08:47 -0400
Received: from vausditchmc3.idirect.net ([fe80::a089:5025:3057:5d51]) by vausditchmc3.idirect.net ([fe80::a089:5025:3057:5d51%13]) with mapi id 15.01.1713.004; Mon, 6 May 2019 11:08:47 -0400
From: "Ratliff, Stanley" <sratliff@idirect.net>
To: Lou Berger <lberger@labn.net>, Magnus Westerlund <magnus.westerlund@ericsson.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-manet-dlep-pause-extension@ietf.org" <draft-ietf-manet-dlep-pause-extension@ietf.org>, "manet@ietf.org" <manet@ietf.org>, Bob Briscoe <ietf@bobbriscoe.net>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>
Thread-Topic: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
Thread-Index: AQHU6tuDcoy41n6e4kuNlesEyZ+fpKZeYAaAgAAFMPA=
Date: Mon, 6 May 2019 15:08:47 +0000
Message-ID: <0fac9fb26cd44a8e8b14b5e394ec6824@idirect.net>
References: <155437815884.30894.8011482899811561433.idtracker@ietfa.amsl.com> <bcd469e9-2d36-3fc7-0d41-56d26bb32aca@labn.net> <8c18420b622f405eb0d4adcf844b315d@idirect.net> <HE1PR0701MB25225A4933D7C72B7B19FB1895510@HE1PR0701MB2522.eurprd07.prod.outlook.com> <36cb484b-f2a5-0f13-5210-e0b67b4a4231@labn.net> <HE1PR0701MB2522FFFAC71265215BB63346952F0@HE1PR0701MB2522.eurprd07.prod.outlook.com> <116fd2c7-2175-ffa8-d51d-25dabf5ca429@labn.net> <HE1PR0701MB2522441A2CC6524B41EF88E395300@HE1PR0701MB2522.eurprd07.prod.outlook.com> <0caf7d03-c751-4cbc-2506-99ff95d4dbc2@labn.net>
In-Reply-To: <0caf7d03-c751-4cbc-2506-99ff95d4dbc2@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.250.251.20]
MIME-Version: 1.0
X-MC-Unique: jk-iWV4_NCG1k_fDuoeWHA-1
X-Mimecast-Spam-Score: 0
Content-Type: multipart/alternative; boundary="MCBoundary=_11905061108482911"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/wZxlR-zKBCDSR0GKwN68uGjbvKk>
Subject: Re: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 15:08:56 -0000

--MCBoundary=_11905061108482911
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

TG91LCANCg0KWXVwLCB5b3UgYXNzdW1lZCBjb3JyZWN0bHkuIFRoYW5rcyBmb3IgYWxsIG9mIHlv
dXIgaGFyZCB3b3JrLiBBbmQgdGhhbmsgeW91LCBNYWdudXMsIGZvciBtYWtpbmcgdGhlIGRyYWZ0
IGJldHRlci4gDQoNClJlZ2FyZHMsDQpTdGFuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCj4gRnJvbTogTG91IEJlcmdlciBbbWFpbHRvOmxiZXJnZXJAbGFibi5uZXRdDQo+IFNlbnQ6
IE1vbmRheSwgTWF5IDA2LCAyMDE5IDY6NDkgQU0NCj4gVG86IE1hZ251cyBXZXN0ZXJsdW5kIDxt
YWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20+OyBSYXRsaWZmLA0KPiBTdGFubGV5IDxzcmF0
bGlmZkBpZGlyZWN0Lm5ldD47IFRoZSBJRVNHIDxpZXNnQGlldGYub3JnPg0KPiBDYzogZHJhZnQt
aWV0Zi1tYW5ldC1kbGVwLXBhdXNlLWV4dGVuc2lvbkBpZXRmLm9yZzsgbWFuZXRAaWV0Zi5vcmc7
IEJvYg0KPiBCcmlzY29lIDxpZXRmQGJvYmJyaXNjb2UubmV0PjsgbWFuZXQtY2hhaXJzQGlldGYu
b3JnDQo+IFN1YmplY3Q6IFJlOiBbbWFuZXRdIE1hZ251cyBXZXN0ZXJsdW5kJ3MgRGlzY3VzcyBv
biBkcmFmdC1pZXRmLW1hbmV0LWRsZXAtDQo+IHBhdXNlLWV4dGVuc2lvbi0wNjogKHdpdGggRElT
Q1VTUykNCj4gDQo+ICoqKldBUk5JTkchIFRISVMgRU1BSUwgT1JJR0lOQVRFUyBGUk9NIE9VVFNJ
REUgVlQgSURJUkVDVC4qKioNCj4gDQo+IFRoYW5rcyBNYWdudXMuIMKgIEknbGwgdXBsb2FkIGEg
cmV2IHdpdGggdGhlIGNoYW5nZSB0b2RheSAod2FzIHdhaXRpbmcgb24NCj4gQUQvU2hlcGhlcmQs
IGJ1dCBub3cgYXNzdW1lIHRoZXkgd2lsbCBhc2sgZm9yIHRoZSB1cGxvYWQpLi4uDQo+IA0KPiBM
b3UNCj4gDQo+IE9uIDUvNi8yMDE5IDM6NTYgQU0sIE1hZ251cyBXZXN0ZXJsdW5kIHdyb3RlOg0K
PiA+IFRoYW5rcyBMb3UsDQo+ID4NCj4gPiBJIHRoaW5rIHRoYXQgY2xhcmlmaWVzIG15IGlzc3Vl
LiBJIHdpbGwgY2xlYXIgd2l0aCB0aGUgYXNzdW1wdGlvbiB0aGF0DQo+ID4geW91IHdpbGwgaW5j
bHVkZSB0aGlzLg0KPiA+DQo+ID4gVGhhbmtzDQo+ID4NCj4gPiBNYWdudXMNCj4gPg0KPiA+IE9u
IDIwMTktMDUtMDYgMDI6NDAsIExvdSBCZXJnZXIgd3JvdGU6DQo+ID4+IEhpIE1hZ251cy9Cb2Is
DQo+ID4+IAlJJ3ZlIHVwZGF0ZWQgdGhlIGludHJvIHRvIHRyeSB0byBhZGRyZXNzIHlvdXIgcG9p
bnRzLCB3aGlsZSBhbHNvDQo+ID4+IHRyeWluZyB0byBicmluZyBpbiBTdGFuJ3MgcG9pbnQsIDoN
Cj4gPj4NCj4gPj4gICAgIFRoZSBiYXNlIERMRVAgc3BlY2lmaWNhdGlvbiBkb2VzIG5vdCBpbmNs
dWRlIGFueSBkYXRhIHBsYW5lIGZsb3cNCj4gPj4gICAgIGNvbnRyb2wgY2FwYWJpbGl0eS4gIFRo
ZSBleHRlbnNpb24gZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IHN1cHBvcnRzDQo+ID4+ICAgICBm
bG93IGNvbnRyb2wgb2YgZGF0YSB0cmFmZmljIGJhc2VkIG9uIGV4cGxpY2l0IG1lc3NhZ2VzIHNl
bnQgdmlhIERMRVANCj4gPj4gICAgIGJ5IGEgbW9kZW0gdG8gaW5kaWNhdGUgd2hlbiBhIHJvdXRl
ciBzaG91bGQgaG9sZCBvZmYgc2VuZGluZyB0cmFmZmljLA0KPiA+PiAgICAgYW5kIHdoZW4gaXQg
c2hvdWxkIHJlc3VtZS4gIFRoaXMgZnVuY3Rpb25hbGl0eSBwYXJhbGxlbHMgdGhlIGZsb3cNCj4g
Pj4gICAgIGNvbnRyb2wgbWVjaGFuaXNtIGZvdW5kIGluIFBQUCBvdmVyIEV0aGVybmV0IChQUFBv
RSkgcGVyIFtSRkM1NTc4XS4NCj4gPj4gICAgIFRoZSBleHRlbnNpb24gYWxzbyBvcHRpb25hbGx5
IHN1cHBvcnRzIERTQ1AgKGRpZmZlcmVudGlhdGVkIHNlcnZpY2VzDQo+ID4+ICAgICBjb2RlcG9p
bnQpIGF3YXJlIGZsb3cgY29udHJvbCBmb3IgdXNlIGJ5IERpZmZTZXJ2LWF3YXJlIG1vZGVtcy4g
IChGb3INCj4gPj4gICAgIGdlbmVyYWwgYmFja2dyb3VuZCBvbiBEaWZmZXJlbnRpYXRlZCBTZXJ2
aWNlcyBzZWUgW1JGQzI0NzVdLikgIFRoaXMNCj4gPj4gICAgIGZ1bmN0aW9uYWxpdHkgaXMgdmVy
eSBzaW1pbGFyIHRvIHRoYXQgcHJvdmlkZWQgYnkgRXRoZXJuZXQgUHJpb3JpdHkNCj4gPj4gICAg
IGZsb3cgY29udHJvbCwgc2VlIFtJRUVFLjgwMi4xUV8yMDE0XS4gIFRoZSBleHRlbnNpb24gZGVm
aW5lZCBpbiB0aGlzDQo+ID4+ICAgICBkb2N1bWVudCBpcyByZWZlcnJlZCB0byBhcyAiQ29udHJv
bCBQbGFuZSBCYXNlZCBQYXVzZSIuICBPdGhlciBmbG93DQo+ID4+ICAgICBjb250cm9sIG1ldGhv
ZHMgYXJlIHBvc3NpYmxlIHdpdGggRExFUCwgZS5nLiwgc2VlDQo+ID4+ICAgICBbSS1ELmlldGYt
bWFuZXQtZGxlcC1kYS1jcmVkaXQtZXh0ZW5zaW9uXSBhbmQNCj4gPj4gICAgIFtJLUQuaWV0Zi1t
YW5ldC1kbGVwLWNyZWRpdC1mbG93LWNvbnRyb2xdLg0KPiA+Pg0KPiA+PiBQbGVhc2UgbGV0IG1l
L3VzIGtub3cgd2hhdCB5b3UgdGhpbmsuDQo+ID4+DQo+ID4+IExvdQ0KPiA+Pg0KPiA+Pg0KPiA+
PiBPbiA0LzExLzE5IDg6MTIgQU0sIE1hZ251cyBXZXN0ZXJsdW5kIHdyb3RlOg0KPiA+Pj4gSGks
DQo+ID4+Pg0KPiA+Pj4gSSBkb24ndCBoYXZlIGEgdGV4dCBwcm9wb3NhbC4gSSB0aGluayBpZiB5
b3Ugd29yayB3aXRoIEJvYiB0byBkZXRhaWwNCj4gPj4+IG91dCB0aGUgdXNlIGNhc2UgYW5kIGNs
YXJpZmljYXRpb25zIG9uIHRoZSBsaW1pdGF0aW9ucyB3aXRoIHRoZQ0KPiA+Pj4gcHJvdG9jb2wg
dGhhdCBzaG91bGQgc29sdmUgbXkgaXNzdWUgaGVyZS4NCj4gPj4+DQo+ID4+PiBDaGVlcnMNCj4g
Pj4+DQo+ID4+PiBNYWdudXMNCj4gPj4+DQo+ID4+PiBPbiAyMDE5LTA0LTExIDEzOjQ3LCBMb3Ug
QmVyZ2VyIHdyb3RlOg0KPiA+Pj4+IE1hZ251cywNCj4gPj4+Pg0KPiA+Pj4+IE9uIDQvNS8yMDE5
IDU6MTEgQU0sIE1hZ251cyBXZXN0ZXJsdW5kIHdyb3RlOg0KPiA+Pj4+PiBIaSwNCj4gPj4+Pj4N
Cj4gPj4+Pj4gVGhhbmtzIGZvciB0aGUgcmVwbGllcy4NCj4gPj4+Pj4NCj4gPj4+Pj4gSSB0aGlu
ayB0aGUgbWFpbiBwb2ludCBoZXJlIGlzIGlmIG9uZSBzaG91bGQgdHJlYXQgcm91dGVyICsgbW9k
ZW0NCj4gPj4+Pj4gYXMgb25lIGNvbW1vbiBxdWV1ZSB3aGVuIGl0IGNvbWVzIHRvIG1lZXRpbmcg
UEhCcyBvciB0cmVhdCB0aGVtDQo+IGFzDQo+ID4+Pj4+IHR3byBpbiBzZXF1ZW5jZSBxdWV1ZXMu
IElmIG9uZSB0cmVhdCB0aGVtIGFzIHR3byBxdWV1ZXMgdGhlbiB5b3UNCj4gPj4+Pj4gZ2V0IHRo
ZSBzYW1lIGJlaGF2aW9yIGFzIHR3byByb3V0ZXJzIGluIHNlcXVlbmNlLiBBbmQgdGhhdCBpcw0K
PiA+Pj4+PiBhY2NlcHRhYmxlIGZyb20gb25lIGFuZ2xlLCBidXQgaXQgYWxzbyByZXN1bHRzIGlu
IGFkZGl0aW9uYWwgaml0dGVyIGFuZA0KPiBsYXRlbmNpZXMuDQo+ID4+Pj4gSSB0aGluayBTdGFu
J3MgcmVzcG9uc2UgYWxyZWFkeSBjb3ZlcmVkIHRoZSBhYm92ZS4gRnJvbSBteQ0KPiA+Pj4+IHBl
cnNwZWN0aXZlLCBJIGFncmVlIHdpdGggc3RhbiB0aGF0IGEgbW9kZW0gdGhhdCByZXBvcnRzIERT
Q1BzDQo+ID4+Pj4gc2hvdWxkIGJlIGV4cGVjdGVkIHRvIGhvbm9yIHRoZW0gbGlrZSBhbnkgb3Ro
ZXIgdHJhbnNpdCBJUCBkZXZpY2UNCj4gKHJvdXRlciwgbWlkZGxlYm94LCBldGMuKS4NCj4gPj4+
PiBJIHRoaW5rIHRoYXQgdGhlIGZvbGxvd2luZyBpcyBwb3NzaWJsZSBpbiB0aGUgbm9uLWRpZmZz
ZXJ2IG1vZGVtDQo+ID4+Pj4gYXdhcmUgY2FzZSAtIGJ1dCBhbm90aGVyIGFwcHJvYWNoIHdvdWxk
IGJlIHRvIG5vdCBkZXBsb3kgc3VjaA0KPiA+Pj4+IGxpbWl0ZWQgbW9kZW1zIGluIGEgbmV0d29y
ayB0aGF0IHJlcXVpcmVzIERTQ1Agc3VwcG9ydCAtIGp1c3QgbGlrZQ0KPiA+Pj4+IHlvdSB3b3Vs
ZG4ndCBkZXBsb3kgYSByb3V0ZXIgdGhhdCBkb2Vzbid0IHN1cHBvcnQgYSBwYXJ0aWN1bGFyIFBI
Qg0KPiA+Pj4+IGluIG5ldHdvcmsgdGhhdCBleHBlY3RzIHRvIHN1cHBvcnQgaXQuDQo+ID4+Pj4N
Cj4gPj4+Pj4gSWYgd2UgdGFrZSB0aGUgRXhwZWRpdGVkIEZvcndhcmRpbmcgUEhCIChSRkMgMzI0
NikgdHJlYXRpbmcgdGhpcw0KPiA+Pj4+PiBhcyB0d28gcXVldWUgcmVzdWx0cyBpbiB0aGF0IHRo
ZSBlcnJvciBpcyBFX2ExIChyb3V0ZXIpICsgRV9hMg0KPiA+Pj4+PiAobW9kZSkgcmF0aGVyIHRo
YW4gYSBFX2EgZm9yIHRoZSBjb21iaW5lZCBxdWV1ZS4gVGhlIHF1ZXN0aW9uIGlzDQo+ID4+Pj4+
IGlmIEVfYSBhY3R1YWxseSB3aWxsIGJlIHNtYWxsZXIgdGhhbiBFX2ExK0VfYTIgd2hlbiBvbmUg
dXNlcyB0aGlzDQo+ID4+Pj4+IHR5cGUgb2YgY29udHJvbD8gSW4gdGhlIGNvbWJpbmVkIGNhc2Ug
aWYgdGhlIG1vZGVtIHF1ZXVlIGlzIHNvDQo+ID4+Pj4+IHNoYWxsb3cgdGhhdCBFX2EyIDw8IEVf
YTEgYXMgd2VsbCBhcyB0aGF0IHRpbWUgZm9yIHBlcmZvcm1pbmcgdGhlDQo+ID4+Pj4+IERMRVAg
c2lnbmFsbGluZyBpcyBzbyBzaG9ydCB0aGF0IHRoZSBtYWluIHZhcmlhdGlvbnMgZW5kcyB1cCBi
ZWluZw0KPiA+Pj4+PiBpbiB0aGUgcm91dGVyIHF1ZXVlIHdoZXJlIG9uZSBjYW4gYXBwbHkgc3Vp
dGFibGUgcG9saWNpZXMgdG8NCj4gPj4+Pj4gY29udHJvbCBxdWV1ZSBsb2FkIHRvIHByZXZlbnQg
dmlvbGF0aW9uIG9mIHRoZSB0YXJnZXRzLg0KPiA+Pj4+PiBJIHRoaW5rIG15IG1haW4gY29uY2Vy
biB3aWxsIGJlIHdoYXQgaGFwcGVucyBpZiBvbmUgYXR0ZW1wdHMgdG8NCj4gPj4+Pj4gaW1wbGVt
ZW50IEw0UyBkdWFsIHF1ZXVlcyBvciBERVRORVQgYW5kIGhhdmUgRExFUCBpbiB0aGUgcGF0aC4N
Cj4gPj4+Pj4gV2lsbCB0aGlzIHJlcXVpcmUgYWRkaXRpb25hbCBleHRlbnNpb25zIHRvIHByb3Zp
ZGUgbW9yZSBkZXRhaWxlZA0KPiA+Pj4+PiBmbG93IGNvbnRyb2wgaW5mb3JtYXRpb24gc28gdGhh
dCBsb3dlciBsYXRlbmN5IG9yIG1vcmUNCj4gPj4+Pj4gZGV0ZXJtaW5pc3RpYyBiZWhhdmlvciBj
YW4gYmUgYWNoaWV2ZWQ/DQo+ID4+Pj4gUXVpdGUgbGlrZWx5IC0tIEkgdGhpbmsgdGhpcyBpcyBu
b3QgdGhlIGZsb3cgY29udHJvbCB5b3UnZCB3YW50DQo+ID4+Pj4gd2l0aCBEZXROZXQgKEkgY2Fu
J3Qgc3BlYWsgdG8gTDRTKSwgaSdkIHBlcnNvbmFsbHkgdXNlIHNvbWV0aGluZw0KPiA+Pj4+IGxp
a2Ugd2hhdCdzIGNvdmVyZWQgaW4gaWV0Zi1tYW5ldC1kbGVwLWRhLWNyZWRpdC1leHRlbnNpb24u
DQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+PiBJIG5vdGljZWQgdGhhdCBUU1ZBUlQgcmV2aWV3ZXIg
Qm9iIEJyaXNjb2UgYXNrZWQgZm9yIGEgdXNlIGNhc2UNCj4gPj4+Pj4gZGVzY3JpcHRpb24gb2Yg
dGhlIGNhc2Ugd2hlbiB0aGUgbWFpbiBxdWV1ZSBpcyBwdXNoZWQgdG8gdGhlDQo+ID4+Pj4+IHJv
dXRlci4gSSB0aGluayB0aGF0IGFwcGVhcnMgdG8gYmUgYSBnb29kIGlkZWEuIEkgdGhpbmsgd2hh
dCBJIGFtDQo+ID4+Pj4+IHdvbmRlcmluZyBpcyBpZiB0aGVyZSBuZWVkIHRvIGJlIHNvbWUgYXBw
bGljYWJpbGl0eSBzdGF0ZW1lbnQgaGVyZQ0KPiA+Pj4+PiBkdWUgdGhlIGxpbWl0YXRpb25zIG9m
IHRoZSB0ZWNobm9sb2d5Pw0KPiA+Pj4+IEkgY2VydGFpbmx5IGhhdmUgbm8gb2JqZWN0aW9uIHRv
IHN1Y2gsIHBhcnRpY3VsYXJseSBnaXZlbg0KPiA+Pj4+IGlldGYtbWFuZXQtZGxlcC1kYS1jcmVk
aXQtZXh0ZW5zaW9uLiAgSWYgeW91IGhhdmUgYW55IHN1Z2dlc3RlZA0KPiA+Pj4+IHRleHQsIHRo
YXQgd291bGQgYmUgaGVscGZ1bC4gIE90aGVyd2lzZSwgYXMgSSBtZW50aW9uZWQgaW4gcmVzcG9u
c2UNCj4gPj4+PiB0byBCb2IsIGlmIHJlYWxseSBuZWVkZWQgSSBjYW4gd29yayB3aXRoIHRoZSBT
aGVwaGVyZC9XRyBvbiBzb21lDQo+IGFwcGxpY2FiaWxpdHkgdGV4dC4NCj4gPj4+Pg0KPiA+Pj4+
IExvdQ0KPiA+Pj4+DQo+ID4+Pj4+IENoZWVycw0KPiA+Pj4+Pg0KPiA+Pj4+PiBNYWdudXMNCj4g
Pj4+Pj4NCj4gPj4+Pj4NCg0KVGhpcyBlbGVjdHJvbmljIG1lc3NhZ2UgYW5kIGFueSBmaWxlcyB0
cmFuc21pdHRlZCB3aXRoIGl0IGNvbnRhaW5zIGluZm9ybWF0aW9uIGZyb20gaURpcmVjdCwgd2hp
Y2ggbWF5IGJlIHByaXZpbGVnZWQsIHByb3ByaWV0YXJ5IGFuZC9vciBjb25maWRlbnRpYWwuIEl0
IGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRp
dHkgdG8gd2hvbSB0aGV5IGFyZSBhZGRyZXNzZWQuIA0KSWYgeW91IGFyZSBub3QgdGhlIG9yaWdp
bmFsIHJlY2lwaWVudCBvciB0aGUgcGVyc29uIHJlc3BvbnNpYmxlIGZvciBkZWxpdmVyaW5nIHRo
ZSBlbWFpbCB0byB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBiZSBhZHZpc2VkIHRoYXQgeW91IGhh
dmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgYW5kIHRoYXQgYW55IHVzZSwgZGlzc2Vt
aW5hdGlvbiwgZm9yd2FyZGluZywgcHJpbnRpbmcsIG9yIGNvcHlpbmcgb2YgDQp0aGlzIGVtYWls
IGlzIHN0cmljdGx5IHByb2hpYml0ZWQuIElmIHlvdSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVy
cm9yLCBwbGVhc2UgZGVsZXRlIGl0IGFuZCBpbW1lZGlhdGVseSBub3RpZnkgdGhlIHNlbmRlci4N
Cg==
--MCBoundary=_11905061108482911
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><style type=3D"text/css">.style1 {font-family: "Times New Roman=
";}</style></head><body>Lou, <BR>
<BR>
Yup, you assumed correctly. Thanks for all of your hard work. And thank you=
, Magnus, for making the draft better. <BR>
<BR>
Regards,<BR>
Stan<BR>
<BR>
&gt; -----Original Message-----<BR>
&gt; From: Lou Berger [mailto:lberger@labn.net]<BR>
&gt; Sent: Monday, May 06, 2019 6:49 AM<BR>
&gt; To: Magnus Westerlund &lt;magnus.westerlund@ericsson.com&gt;; Ratliff,=
<BR>
&gt; Stanley &lt;sratliff@idirect.net&gt;; The IESG &lt;iesg@ietf.org&gt;<B=
R>
&gt; Cc: draft-ietf-manet-dlep-pause-extension@ietf.org; manet@ietf.org; Bo=
b<BR>
&gt; Briscoe &lt;ietf@bobbriscoe.net&gt;; <a href=3D"mailto:manet-chairs@ie=
tf.org">manet-chairs@ietf.org</a><BR>
&gt; Subject: Re: [manet] Magnus Westerlund's Discuss on draft-ietf-manet-d=
lep-<BR>
&gt; pause-extension-06: (with DISCUSS)<BR>
&gt; <BR>
&gt; ***WARNING! THIS EMAIL ORIGINATES FROM OUTSIDE VT IDIRECT.***<BR>
&gt; <BR>
&gt; Thanks Magnus. &nbsp; I'll upload a rev with the change today (was wai=
ting on<BR>
&gt; AD/Shepherd, but now assume they will ask for the upload)...<BR>
&gt; <BR>
&gt; Lou<BR>
&gt; <BR>
&gt; On 5/6/2019 3:56 AM, Magnus Westerlund wrote:<BR>
&gt; &gt; Thanks Lou,<BR>
&gt; &gt;<BR>
&gt; &gt; I think that clarifies my issue. I will clear with the assumption=
 that<BR>
&gt; &gt; you will include this.<BR>
&gt; &gt;<BR>
&gt; &gt; Thanks<BR>
&gt; &gt;<BR>
&gt; &gt; Magnus<BR>
&gt; &gt;<BR>
&gt; &gt; On 2019-05-06 02:40, Lou Berger wrote:<BR>
&gt; &gt;&gt; Hi Magnus/Bob,<BR>
&gt; &gt;&gt; =09I've updated the intro to try to address your points, whil=
e also<BR>
&gt; &gt;&gt; trying to bring in Stan's point, :<BR>
&gt; &gt;&gt;<BR>
&gt; &gt;&gt;     The base DLEP specification does not include any data pla=
ne flow<BR>
&gt; &gt;&gt;     control capability.  The extension defined in this docume=
nt supports<BR>
&gt; &gt;&gt;     flow control of data traffic based on explicit messages s=
ent via DLEP<BR>
&gt; &gt;&gt;     by a modem to indicate when a router should hold off send=
ing traffic,<BR>
&gt; &gt;&gt;     and when it should resume.  This functionality parallels =
the flow<BR>
&gt; &gt;&gt;     control mechanism found in PPP over Ethernet (PPPoE) per =
[RFC5578].<BR>
&gt; &gt;&gt;     The extension also optionally supports DSCP (differentiat=
ed services<BR>
&gt; &gt;&gt;     codepoint) aware flow control for use by DiffServ-aware m=
odems.  (For<BR>
&gt; &gt;&gt;     general background on Differentiated Services see [RFC247=
5].)  This<BR>
&gt; &gt;&gt;     functionality is very similar to that provided by Etherne=
t Priority<BR>
&gt; &gt;&gt;     flow control, see [IEEE.802.1Q_2014].  The extension defi=
ned in this<BR>
&gt; &gt;&gt;     document is referred to as &quot;Control Plane Based Paus=
e&quot;.  Other flow<BR>
&gt; &gt;&gt;     control methods are possible with DLEP, e.g., see<BR>
&gt; &gt;&gt;     [I-D.ietf-manet-dlep-da-credit-extension] and<BR>
&gt; &gt;&gt;     [I-D.ietf-manet-dlep-credit-flow-control].<BR>
&gt; &gt;&gt;<BR>
&gt; &gt;&gt; Please let me/us know what you think.<BR>
&gt; &gt;&gt;<BR>
&gt; &gt;&gt; Lou<BR>
&gt; &gt;&gt;<BR>
&gt; &gt;&gt;<BR>
&gt; &gt;&gt; On 4/11/19 8:12 AM, Magnus Westerlund wrote:<BR>
&gt; &gt;&gt;&gt; Hi,<BR>
&gt; &gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt; I don't have a text proposal. I think if you work with Bo=
b to detail<BR>
&gt; &gt;&gt;&gt; out the use case and clarifications on the limitations wi=
th the<BR>
&gt; &gt;&gt;&gt; protocol that should solve my issue here.<BR>
&gt; &gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt; Cheers<BR>
&gt; &gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt; Magnus<BR>
&gt; &gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt; On 2019-04-11 13:47, Lou Berger wrote:<BR>
&gt; &gt;&gt;&gt;&gt; Magnus,<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt; On 4/5/2019 5:11 AM, Magnus Westerlund wrote:<BR>
&gt; &gt;&gt;&gt;&gt;&gt; Hi,<BR>
&gt; &gt;&gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; Thanks for the replies.<BR>
&gt; &gt;&gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; I think the main point here is if one should trea=
t router + modem<BR>
&gt; &gt;&gt;&gt;&gt;&gt; as one common queue when it comes to meeting PHBs=
 or treat them<BR>
&gt; as<BR>
&gt; &gt;&gt;&gt;&gt;&gt; two in sequence queues. If one treat them as two =
queues then you<BR>
&gt; &gt;&gt;&gt;&gt;&gt; get the same behavior as two routers in sequence.=
 And that is<BR>
&gt; &gt;&gt;&gt;&gt;&gt; acceptable from one angle, but it also results in=
 additional jitter and<BR>
&gt; latencies.<BR>
&gt; &gt;&gt;&gt;&gt; I think Stan's response already covered the above. Fr=
om my<BR>
&gt; &gt;&gt;&gt;&gt; perspective, I agree with stan that a modem that repo=
rts DSCPs<BR>
&gt; &gt;&gt;&gt;&gt; should be expected to honor them like any other trans=
it IP device<BR>
&gt; (router, middlebox, etc.).<BR>
&gt; &gt;&gt;&gt;&gt; I think that the following is possible in the non-dif=
fserv modem<BR>
&gt; &gt;&gt;&gt;&gt; aware case - but another approach would be to not dep=
loy such<BR>
&gt; &gt;&gt;&gt;&gt; limited modems in a network that requires DSCP suppor=
t - just like<BR>
&gt; &gt;&gt;&gt;&gt; you wouldn't deploy a router that doesn't support a p=
articular PHB<BR>
&gt; &gt;&gt;&gt;&gt; in network that expects to support it.<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; If we take the Expedited Forwarding PHB (RFC 3246=
) treating this<BR>
&gt; &gt;&gt;&gt;&gt;&gt; as two queue results in that the error is E_a1 (r=
outer) + E_a2<BR>
&gt; &gt;&gt;&gt;&gt;&gt; (mode) rather than a E_a for the combined queue. =
The question is<BR>
&gt; &gt;&gt;&gt;&gt;&gt; if E_a actually will be smaller than E_a1+E_a2 wh=
en one uses this<BR>
&gt; &gt;&gt;&gt;&gt;&gt; type of control? In the combined case if the mode=
m queue is so<BR>
&gt; &gt;&gt;&gt;&gt;&gt; shallow that E_a2 &lt;&lt; E_a1 as well as that t=
ime for performing the<BR>
&gt; &gt;&gt;&gt;&gt;&gt; DLEP signalling is so short that the main variati=
ons ends up being<BR>
&gt; &gt;&gt;&gt;&gt;&gt; in the router queue where one can apply suitable =
policies to<BR>
&gt; &gt;&gt;&gt;&gt;&gt; control queue load to prevent violation of the ta=
rgets.<BR>
&gt; &gt;&gt;&gt;&gt;&gt; I think my main concern will be what happens if o=
ne attempts to<BR>
&gt; &gt;&gt;&gt;&gt;&gt; implement L4S dual queues or DETNET and have DLEP=
 in the path.<BR>
&gt; &gt;&gt;&gt;&gt;&gt; Will this require additional extensions to provid=
e more detailed<BR>
&gt; &gt;&gt;&gt;&gt;&gt; flow control information so that lower latency or=
 more<BR>
&gt; &gt;&gt;&gt;&gt;&gt; deterministic behavior can be achieved?<BR>
&gt; &gt;&gt;&gt;&gt; Quite likely -- I think this is not the flow control =
you'd want<BR>
&gt; &gt;&gt;&gt;&gt; with DetNet (I can't speak to L4S), i'd personally us=
e something<BR>
&gt; &gt;&gt;&gt;&gt; like what's covered in ietf-manet-dlep-da-credit-exte=
nsion.<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; I noticed that TSVART reviewer Bob Briscoe asked =
for a use case<BR>
&gt; &gt;&gt;&gt;&gt;&gt; description of the case when the main queue is pu=
shed to the<BR>
&gt; &gt;&gt;&gt;&gt;&gt; router. I think that appears to be a good idea. I=
 think what I am<BR>
&gt; &gt;&gt;&gt;&gt;&gt; wondering is if there need to be some applicabili=
ty statement here<BR>
&gt; &gt;&gt;&gt;&gt;&gt; due the limitations of the technology?<BR>
&gt; &gt;&gt;&gt;&gt; I certainly have no objection to such, particularly g=
iven<BR>
&gt; &gt;&gt;&gt;&gt; ietf-manet-dlep-da-credit-extension.  If you have any=
 suggested<BR>
&gt; &gt;&gt;&gt;&gt; text, that would be helpful.  Otherwise, as I mention=
ed in response<BR>
&gt; &gt;&gt;&gt;&gt; to Bob, if really needed I can work with the Shepherd=
/WG on some<BR>
&gt; applicability text.<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt; Lou<BR>
&gt; &gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; Cheers<BR>
&gt; &gt;&gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt; Magnus<BR>
&gt; &gt;&gt;&gt;&gt;&gt;<BR>
&gt; &gt;&gt;&gt;&gt;&gt;<BR>

<br /><br />
<p style=3D"font-family: Verdana; font-size:10pt; color:#666666;">
This electronic message and any files transmitted with it contains informat=
ion from iDirect, which may be privileged, proprietary and/or confidential.=
 It is intended solely for the use of the individual or entity to whom they=
 are addressed. If you are not the original recipient or the person respons=
ible for delivering the email to the intended recipient, be advised that yo=
u have received this email in error, and that any use, dissemination, forwa=
rding, printing, or copying of this email is strictly prohibited. If you re=
ceived this email in error, please delete it and immediately notify the sen=
der.</p>

</body></html>

--MCBoundary=_11905061108482911--


From nobody Mon May  6 11:27:05 2019
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13EE1120111; Mon,  6 May 2019 11:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 aEaMJZ82MGyn; Mon,  6 May 2019 11:27:02 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ACD1120086; Mon,  6 May 2019 11:27:02 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id n17so16282686edb.0; Mon, 06 May 2019 11:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=RanSjWzJ7wk3NR6AOUm1mRjT5hWvviyl/CIOEr2OdYg=; b=CLi2zC1ujqkdVwh8LDwFjDrgHB0cVM5JPpU5q8Zgf4c7XNPi3GZE7p6BOWDKrRXu6K 61tGSpL9W1nzuKLCtgKq0Yn79STokEXA9iBVNdBIAHoiMAaIZYQzvknUJXCXVJ4PM+xS Q61eKHvLZwiveWOGkXZXKf3BvgJR0ZabOl1EvvUeMBoaky4CUnSBIWl+xSjOVa1Nz4ba HtL/s6+bQ+2f6hb+GhBAl7IpBWRa9OPAGEm8hNypu5Gbd1B7wmyRDPyqZxIRcjJitpRl GAZAo5YOEJHNTIB6d5KNOKMx+4+QrCHgHfCxCKxifA8g1Fjiy5ithWRVz67Z8MEEgUA5 TKQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=RanSjWzJ7wk3NR6AOUm1mRjT5hWvviyl/CIOEr2OdYg=; b=MjfGo+vpffGwdBF32FQzrxL8uiyxu0KInwB53jo24OmQb/fnmK9fJzbHXhoJOsrjfQ jfWtlyhZ/uNcXbdOpAhlskhY6drJ3J5ZQElr/Xj33pRSat4i62dUxGsrS+eszjkJzyF7 STNblHJeseYuSorsGNqZeDDwDkp66pTiIPO14McR7VKFldAVXkcL8HoURPwh3Bc2K5k1 Y12i612WXexHAAOV5SuUbSdmbY6RTmH1RZNm04OJTnUt2UZu8i73l9kuEiKsDgTG/dbE Fq7L9WkjYYDAMUFV00Zo4tlMZ3+i4gnNilJOAwgZvKNjGVNvAOWJebvafOAQNeGAibYa HrVQ==
X-Gm-Message-State: APjAAAWeYkJaKCIqHmXLpFImrNmisE90tvLtRJSNkZyUP6TL+ISXoCC6 cXyKYWhI6FFiLcj1tXc8eqc8/l+bJ9KxXiCcZRje39mv
X-Google-Smtp-Source: APXvYqx9IUaygasEcVxeDdEr1KI3towehaGOtaQg39KSO7kDHFcDrXdWYe1uk8f5t2J4+8F3Hp8UoSXfhY/n08r8P5E=
X-Received: by 2002:a50:9738:: with SMTP id c53mr27025104edb.156.1557167220776;  Mon, 06 May 2019 11:27:00 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 6 May 2019 14:26:59 -0400
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CAMMESsztHn9ufGfKbvxniyLK8u_54a0mn4vJ5_ZUpH7t9Q=U2w@mail.gmail.com>
References: <155492518369.22601.15786320586524280536.idtracker@ietfa.amsl.com> <CAMMESswp1BrNmOA1ariTegokJQOaGpi5YRGiVy3DYXiuxUGLwQ@mail.gmail.com> <6CBEC07D-A6E3-455C-87F8-6CB2DC0C1BDF@cooperw.in> <CAMMESsztHn9ufGfKbvxniyLK8u_54a0mn4vJ5_ZUpH7t9Q=U2w@mail.gmail.com>
MIME-Version: 1.0
Date: Mon, 6 May 2019 14:26:59 -0400
Message-ID: <CAMMESszKk8ycnANbPvm_Q7-nu4hMGDB-xVwPNe0rsDTTHW0EUQ@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Cc: Stan Ratliff <sratliff@idirect.net>, manet-chairs@ietf.org, IESG <iesg@ietf.org>,  draft-ietf-manet-dlep-pause-extension@ietf.org, manet@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000ce52d05883c3f87"
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/q87kHipp-lo7yFmozcyISqfFmc0>
Subject: Re: [manet] Alissa Cooper's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 18:27:04 -0000

--0000000000000ce52d05883c3f87
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Alissa:

Hi!

Do my answers satisfy your DISCUSS question?  If not, what are your
expectations?

Thanks!

Alvaro.

On April 11, 2019 at 9:49:39 AM, Alvaro Retana (aretana.ietf@gmail.com)
wrote:

On April 11, 2019 at 9:06:50 AM, Alissa Cooper (alissa@cooperw.in) wrote:

Is there any scope limitation to the functionality that could potentially
be characterized as further "development of DLEP"? I ask because from a
quick read of the base specification, it doesn=E2=80=99t look like pause/re=
sume was
contemplated, and as you note this was not explicitly called out in the
charter whereas credit windowing was. I=E2=80=99m wondering what the bounda=
ry is
around the functionality DLEP is expected to provide as a protocol.

In short, I believe the boundary is simply =E2=80=9Cwhatever the users need=
=E2=80=9D.

When we re-chartered (a couple of years ago), the WG thought that credit
windowing would be the focus (there was a document in progress, etc.), but
that has changed to include this extension, and others.  The community
working on DLEP is a very close-knit group with related (it not
significantly overlapping) users =E2=80=94 the focus of the work then follo=
ws what
their users require.

At some point we should think about generalizing the charter.

Thanks!

Alvaro.

--0000000000000ce52d05883c3f87
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div style=3D"font-family:Helve=
tica,Arial;font-size:13px">Alissa:</div><div style=3D"font-family:Helvetica=
,Arial;font-size:13px"><br></div><div style=3D"font-family:Helvetica,Arial;=
font-size:13px">Hi!</div><div style=3D"font-family:Helvetica,Arial;font-siz=
e:13px"><br></div><div style=3D"font-family:Helvetica,Arial;font-size:13px"=
>Do my answers satisfy your DISCUSS question?=C2=A0 If not, what are your e=
xpectations?</div><div style=3D"font-family:Helvetica,Arial;font-size:13px"=
><br></div><div style=3D"font-family:Helvetica,Arial;font-size:13px">Thanks=
!</div><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></div>=
<div style=3D"font-family:Helvetica,Arial;font-size:13px">Alvaro.</div> <br=
><p class=3D"airmail_on">On April 11, 2019 at 9:49:39 AM, Alvaro Retana (<a=
 href=3D"mailto:aretana.ietf@gmail.com">aretana.ietf@gmail.com</a>) wrote:<=
/p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div style=3D"word-w=
rap:break-word"><div></div><div>




<title></title>



<div style=3D"margin:0px"><font face=3D"Helvetica">On April 11, 2019
at 9:06:50 AM, Alissa Cooper (<a href=3D"mailto:alissa@cooperw.in">alissa@c=
ooperw.in</a>)
wrote:</font></div>
<div style=3D"margin:0px"><font face=3D"Helvetica"><br></font></div>
<div>
<div>
<blockquote type=3D"cite" class=3D"clean_bq" style=3D"font-variant-caps:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px">
<div>
<div style=3D"color:rgb(0,0,0);font-variant-caps:normal;letter-spacing:norm=
al;text-align:start;text-indent:0px;text-transform:none;white-space:normal;=
word-spacing:0px">
<span><font face=3D"Helvetica">Is there any scope limitation to the
functionality that could potentially be characterized as further
&quot;development of DLEP&quot;? I ask because from a quick read of the bas=
e
specification, it doesn=E2=80=99t look like pause/resume was contemplated,
and as you note this was not explicitly called out in the charter
whereas credit windowing was. I=E2=80=99m wondering what the boundary is
around the functionality DLEP is expected to provide as a
protocol.</font></span></div>
</div>
</blockquote>
</div>
<p><font face=3D"Helvetica">In short, I believe the boundary is
simply =E2=80=9Cwhatever the users need=E2=80=9D.</font></p>
<p><font face=3D"Helvetica">When we re-chartered (a couple of years
ago), the WG thought that credit windowing would be the focus
(there was a document in progress, etc.), but that has changed to
include this extension, and others.=C2=A0 The community working on
DLEP is a very close-knit group with related (it not significantly
overlapping) users =E2=80=94 the focus of the work then follows what their
users require.</font></p>
<p><font face=3D"Helvetica">At some point we should think about
generalizing the charter.</font></p>
<p><font face=3D"Helvetica">Thanks!</font></p>
<p><font face=3D"Helvetica">Alvaro.</font></p>
</div>


</div></div></span></blockquote> <div class=3D"gmail_signature"></div></bod=
y></html>

--0000000000000ce52d05883c3f87--


From nobody Mon May  6 11:35:13 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A906120126; Mon,  6 May 2019 11:35:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: manet@ietf.org
Message-ID: <155716771200.27421.6890915606015369161@ietfa.amsl.com>
Date: Mon, 06 May 2019 11:35:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/d47RW20mNtdR_Q-eZ0dtGYc7JIA>
Subject: [manet] I-D Action: draft-ietf-manet-dlep-pause-extension-07.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 18:35:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks WG of the IETF.

        Title           : DLEP Control Plane Based Pause Extension
        Authors         : Bow-Nan Cheng
                          David Wiggins
                          Lou Berger
	Filename        : draft-ietf-manet-dlep-pause-extension-07.txt
	Pages           : 13
	Date            : 2019-05-06

Abstract:
   This document defines an extension to the Dynamic Link Exchange
   Protocol (DLEP) that enables a modem to use DLEP messages to pause
   and resume data traffic coming from its peer router.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-pause-extension/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-manet-dlep-pause-extension-07
https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-pause-extension-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-pause-extension-07


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon May  6 15:00:08 2019
Return-Path: <rdd@cert.org>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003A712008B; Mon,  6 May 2019 14:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 4EJjZBiBEuLA; Mon,  6 May 2019 14:59:55 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CC8B12001E; Mon,  6 May 2019 14:59:55 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x46LxsPq011584; Mon, 6 May 2019 17:59:54 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu x46LxsPq011584
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1557179994; bh=4OBOenMVDalITnCKU9oWgH/MEKHWLkW5OG+S2Hn6b/g=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=p852pA6nIuq1/kWas5a5oLUCDj0LTj6zDZiSAObsNOqMHlb0yExdc0CAHa8r2DrPy 8NaeFHFYWQfFOrLx0rsum9rYV97K8ethMitBxR0hsoBcv2adQat/n4co3HVLB3dXgF JB0FTeSKUsLWMp/2nLNCyJJocVB5hU2OUpLD04Ro=
Received: from CASSINA.ad.sei.cmu.edu (cassina.ad.sei.cmu.edu [10.64.28.249]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x46Lxo8m029725; Mon, 6 May 2019 17:59:50 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASSINA.ad.sei.cmu.edu ([10.64.28.249]) with mapi id 14.03.0439.000; Mon, 6 May 2019 17:59:49 -0400
From: Roman Danyliw <rdd@cert.org>
To: Lou Berger <lberger@labn.net>
CC: "manet@ietf.org" <manet@ietf.org>, "draft-ietf-manet-dlep-multi-hop-extension@ietf.org" <draft-ietf-manet-dlep-multi-hop-extension@ietf.org>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>, The IESG <iesg@ietf.org>
Thread-Topic: [manet] Roman Danyliw's Discuss on draft-ietf-manet-dlep-multi-hop-extension-06: (with DISCUSS and COMMENT)
Thread-Index: AQHVAF4gSBLH8Iegc0+ZpaGVOqOgzqZdnEEAgAEQ3cA=
Date: Mon, 6 May 2019 21:59:48 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B3358E34@marathon>
References: <155674321306.791.1391699664410908649.idtracker@ietfa.amsl.com> <669dc091-7ab6-db0b-f1a6-8f4d62faab73@labn.net>
In-Reply-To: <669dc091-7ab6-db0b-f1a6-8f4d62faab73@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.22.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/O5RE9HoRvFlQ2kWFk9s9QimpTxc>
Subject: Re: [manet] Roman Danyliw's Discuss on draft-ietf-manet-dlep-multi-hop-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 21:59:58 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWVzZyBbbWFpbHRvOmll
c2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIExvdSBCZXJnZXINCj4gU2VudDogU3Vu
ZGF5LCBNYXkgNSwgMjAxOSA5OjQzIFBNDQo+IFRvOiBSb21hbiBEYW55bGl3IDxyZGRAY2VydC5v
cmc+OyBUaGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4NCj4gQ2M6IG1hbmV0QGlldGYub3JnOyBkcmFm
dC1pZXRmLW1hbmV0LWRsZXAtbXVsdGktaG9wLWV4dGVuc2lvbkBpZXRmLm9yZzsNCj4gbWFuZXQt
Y2hhaXJzQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBbbWFuZXRdIFJvbWFuIERhbnlsaXcncyBE
aXNjdXNzIG9uIGRyYWZ0LWlldGYtbWFuZXQtZGxlcC0NCj4gbXVsdGktaG9wLWV4dGVuc2lvbi0w
NjogKHdpdGggRElTQ1VTUyBhbmQgQ09NTUVOVCkNCj4gDQo+IEhpLA0KPiAJUGxlYXNlIHNlZSBi
ZWxvdy4NCj4gDQo+IE9uIDUvMS8xOSA0OjQwIFBNLCBSb21hbiBEYW55bGl3IHZpYSBEYXRhdHJh
Y2tlciB3cm90ZToNCj4gPiBSb21hbiBEYW55bGl3IGhhcyBlbnRlcmVkIHRoZSBmb2xsb3dpbmcg
YmFsbG90IHBvc2l0aW9uIGZvcg0KPiA+IGRyYWZ0LWlldGYtbWFuZXQtZGxlcC1tdWx0aS1ob3At
ZXh0ZW5zaW9uLTA2OiBEaXNjdXNzDQo+ID4NCj4gPiBXaGVuIHJlc3BvbmRpbmcsIHBsZWFzZSBr
ZWVwIHRoZSBzdWJqZWN0IGxpbmUgaW50YWN0IGFuZCByZXBseSB0byBhbGwNCj4gPiBlbWFpbCBh
ZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0byBj
dXQNCj4gPiB0aGlzIGludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KPiA+DQo+ID4N
Cj4gPiBQbGVhc2UgcmVmZXIgdG8NCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRl
bWVudC9kaXNjdXNzLWNyaXRlcmlhLmh0bWwNCj4gPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91
dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9zaXRpb25zLg0KPiA+DQo+ID4NCj4gPiBUaGUg
ZG9jdW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5k
IGhlcmU6DQo+ID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1t
YW5ldC1kbGVwLW11bHRpLWhvcC1leHRlbg0KPiA+IHNpb24vDQo+ID4NCj4gPg0KPiA+DQo+ID4g
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPiA+IERJU0NVU1M6DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+DQo+ID4g
VGhpcyBleHRlbnNpb24gKG11Y2ggbGlrZSBkcmFmdC1pZXRmLW1hbmV0LWRsZXAtcGF1c2UtZXh0
ZW5zaW9uKSBzZWVtcw0KPiA+IHRvIHByb3ZpZGUgYSBtZWNoYW5pc20gdG8gZGlyZWN0IGEgbW9k
ZW0gdG8gZHJvcCB0cmFmZmljIGluIGFuDQo+ID4gdW5hdXRoZW50aWNhdGVkIGZhc2hpb24gLS0g
Zm9yIGRpcmVjdGx5IGNvbm5lY3RlZCBuZXR3b3JrcyB2aWEgdGhlDQo+ID4gdGVybWluYXRlIGFj
dGlvbjsgYW5kIGZvciBtdWx0aS1ob3AgbmV0d29ya3MgdmlhIHRoZSBzdXBwcmVzcyBhY3Rpb24u
DQo+ID4NCj4gPiBGb3IgZXhhbXBsZSwgcGVyIHRoZSBtb2JpbGUgc2NlbmFyaW8gaW4gU2VjdGlv
biA0IG9mIFJGQzgxNzUsIGENCj4gPiBjb21wcm9taXNlZCBsYXB0b3AgaW4gdGhlIHN3aXRjaCBj
b3VsZCB1c2UgdGhpcyBleHRlbnNpb24gaW5zdHJ1Y3QgdGhlDQo+ID4gbW9kZW0gdG8gZHJvcCBw
YWNrZXRzIHdpdGhvdXQgYXV0aGVudGljYXRpb24uDQo+ID4NCj4gPiBJIHNhdyBpbiBXYXJyZW7i
gJlzIGNvbW1lbnQgYmFsbGV0IG9uDQo+ID4gZHJhZnQtaWV0Zi1tYW5ldC1kbGVwLXBhdXNlLWV4
dGVuc2lvbg0KPiA+IChodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRm
LW1hbmV0LWRsZXAtcGF1c2UtZXh0ZW5zaW8NCj4gPiBuL2JhbGxvdC8pDQo+ID4gdGhhdA0KPiA+
DQo+ID4g4oCcTG91IHdpbGwgYWRkOg0KPiA+ICAgSW1wbGVtZW50YXRpb25zIG9mIHRoZSBleHRl
bnNpb24gZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50IE1VU1QNCj4gc3VwcG9ydA0KPiA+ICAgIGNv
bmZpZ3VyYXRpb24gb2YgVExTIHVzYWdlLCBhcyBkZXNjcmliZSBpbiA8eHJlZiB0YXJnZXQ9IlJG
QzgxNzUiLz4sDQo+ID4gICAgaW4gb3JkZXIgdG8gcHJvdGVjdCBjb25maWd1cmF0aW9ucyB3aGVy
ZSBpbmplY3Rpb24gYXR0YWNrcyBhcmUNCj4gPiAgICBwb3NzaWJsZSwgaS5lLiwgd2hlbiB0aGUg
bGluayBiZXR3ZWVuIGEgbW9kZW0gYW5kIHJvdXRlciBpcyBub3QNCj4gPiAgICBvdGhlcndpc2Ug
cHJvdGVjdGVkLuKAnQ0KPiA+DQo+ID4gSSBiZWxpZXZlIHRoZSBzYW1lIGNhdmVhdCBpcyBuZWVk
ZWQgaW4gdGhpcyBkcmFmdCBhcyB0aGV5IGFyZSBlbmFibGluZw0KPiA+IHNpbWlsYXIgYmVoYXZp
b3IuICBQbGVhc2UgY29ycmVjdCBtZSBpZiBJ4oCZbSBjb25mbGF0aW5nIHRoZQ0KPiA+IGNhcGFi
aWxpdGllcyBvZiB0aGlzIGV4dGVuc2lvbiB3aXRoIHRoZSBwYXVzZSBleHRlbnNpb24uDQo+ID4N
Cj4gDQo+IE9uIG9uZSBoYW5kIEkgdGhpbmsgaXQgaXMgcmVhc29uYWJsZSB0byBoYXZlIHRoZSBz
ZWN1cml0eSBzZWN0aW9ucyBtYXRjaA0KPiBiZXR3ZWVuIHRoZSB0d28uICBPbiB0aGUgb3RoZXIs
IEkgdGhpbmsgaXQgcmVhbGx5IHNlZW1zIHRoaXMgSUVTRyBpcyB1bmhhcHB5DQo+IHdpdGggdGhl
IGxhbmd1YWdlICBhcHByb3ZlZCBmb3IgODE3NS4gIEdpdmVuIHRoaXMsIEknbGwgZ28gYWhlYWQg
YW5kIGFkZCB0aGUNCj4gcmVxdWVzdGVkIHRlc3QuDQoNClRoYW5rcy4NCg0KPiA+DQo+ID4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KPiA+IENPTU1FTlQ6DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+DQo+ID4gQSBm
ZXcgcXVlc3Rpb25zIGFuZCBhbiBlZGl0b3JpYWwgbml0Lg0KPiA+DQo+ID4gKDEpIFNlY3Rpb24g
MS4gIEVkaXRvcmlhbC4gIFRoZXJlIGlzIGEgc2VudGVuY2UgZnJhZ21lbnQg4oCcZXhhbXBsZQ0K
PiA+IHVzaW5nLuKAnSB3aGljaCBsaWtlbHkgbmVlZHMgdG8gYmUgcmVtb3ZlZC4NCj4gPg0KPiA+
ICgyKSBTZWN0aW9uIDIuICBQZXIg4oCcVGhlIHVzZSBvZiB0aGUgTXVsdGktSG9wIEZvcndhcmRp
bmcgRXh0ZW5zaW9uDQo+ID4gU0hPVUxEIGJlIGNvbmZpZ3VyYWJsZeKAnSwgd2hhdCBpcyBtZWFu
dCBieSBjb25maWd1cmFibGU/DQo+ID4NCj4gPiAoMykgU2VjdGlvbiAzLjIuMiBhbmQgMy4yLjMu
ICBUaGUgVGVybWluYXRlIGFuZCBEaXJlY3QgQ29ubmVjdGlvbg0KPiA+IG1lc3NhZ2VzIGFyZSBu
b3Qgc3VwcG9zZWQgdG8gYmUgKE1VU1QgTk8pIGJlIHNlbnQgaW4gYSBTZXNzaW9uIFVwZGF0ZQ0K
PiA+IE1lc3NhZ2UuICBIb3cgc2hvdWxkIHRoZSBtb2RlbSBiZWhhdmUgaWYgaXQgcmVjZWl2ZXMg
b25lIGFueXdheT8NCj4gPg0KPiANCj4gYmFzZSBETEVQIDgxNzUgcmVzZXRzIGEgc2Vzc2lvbiBv
biBhbnkgdHlwZSBvZiBwYXJzaW5nIGVycm9yLiBJJ20gcGVyc29uYWxseQ0KPiBub3QgYSBmYW4g
b2YgdGhpcywgYnV0IGl0ICppcyogd2hhdCBSRkM4MTc1IHNheXMuLi4NCg0KVW5kZXJzdG9vZC4g
IFRoYW5rcyBmb3IgdGhlIGNsYXJpdHkuDQoNClJvbWFuDQoNCj4gVGhhbmtzLA0KPiBMb3UNCj4g
DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiA+IG1hbmV0IG1haWxpbmcgbGlzdA0KPiA+IG1hbmV0QGlldGYub3JnDQo+ID4gaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYW5ldA0KPiA+DQoNCg==


From nobody Mon May  6 15:41:05 2019
Return-Path: <kaduk@mit.edu>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0186120103; Mon,  6 May 2019 15:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 qVyzihKWK470; Mon,  6 May 2019 15:41:00 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7915D1200C4; Mon,  6 May 2019 15:41:00 -0700 (PDT)
Received: from kduck.mit.edu (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x46Meuql029489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 6 May 2019 18:40:58 -0400
Date: Mon, 6 May 2019 17:40:56 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Lou Berger <lberger@labn.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-manet-dlep-pause-extension@ietf.org,  manet@ietf.org, manet-chairs@ietf.org
Message-ID: <20190506224055.GX19509@kduck.mit.edu>
References: <155494445891.22757.7399588752085896470.idtracker@ietfa.amsl.com> <e20c4e6d-b36f-690c-2049-4bc81f5cd37a@labn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e20c4e6d-b36f-690c-2049-4bc81f5cd37a@labn.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/Y4BrqPj5QmAPZxSSZpZjqIZQFAk>
Subject: Re: [manet] Benjamin Kaduk's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 22:41:03 -0000

On Sun, May 05, 2019 at 09:22:16PM -0400, Lou Berger wrote:
> Hi,
> 	My apologies, I thought I responded to this, but can't seem to find the
> response (hopefully my responses are consistent if I did!).
> 
> On 4/10/19 9:00 PM, Benjamin Kaduk via Datatracker wrote:
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-manet-dlep-pause-extension-06: Discuss
> > 
> > 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-manet-dlep-pause-extension/
> > 
> > 
> > 
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> > 
> > Section 3.1 defines 'Scale' as a four-bit unsigned integer field but only the
> > values 0-3 are assigned, leaving 4-16k usable.  How will future values be
> > assigned?
> > 
> 
> A future revision or update of this document.  We discussed a IANA
> registry, but thought it overkill as future additions seem quite unlikely.

Okay.  The Discuss was just to make sure it was considered in some fashion;
we do have a bunch of documents that explictly note "additional values are
to be allocated by updates to this specification" but I do not insist on
it.

> > In Section 3.1.1:
> > 
> >    DS Field Qn:
> > 
> >       The data item contains a sequence of 8 bit DS Fields.  The number
> >       of DS Fields present MUST equal the sum of all Num DSCPs field
> >       values.
> > 
> > Perhaps I'm misreading, but I thought the Num DSCPs Qn field was global
> > for this queue index, so there would just be one of them and no need to
> > take a sum.
> 
> It's just saying that more than one DSCP can match to a single queue
> index value.

Okay, if I'm looking at the figure properly then this is just an editorial
issue, then:

        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |  Queue Index  |             Queue Size Qn                     |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       | Num DSCPs Qn  |  DS Field Qn  |              ...              :
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       :                          ...                  |  DS Field Qn  |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

So we have the chunk of stuff for a given queue (index), and the size of
that queue, then a separate array/length for the DS values.  The various DS
values that can match this queue index are the contents of this array, but
this is the only array in the sub data item describing this queue index.
If that's correct, then isn't the description of "DS Field Qn" just "The
sub data item contains a sequence of 8 bit DS Fields for this queue index.
The number of DS Fields present MUST equal this value."?

> 
> > 
> > In Section 3.3:
> > 
> >    A router which receives the Restart Data Item SHOULD resume
> >    transmission of the identified traffic to the modem.
> > 
> > Why is this only a "SHOULD"?
> 
> to cover the case where the router is choosing not to send data, e.g.,
> due to lack of available data or other policy such as traffic rate shaping.

Okay.  Frequently documents will give the reader some hint as to what the
exceptional cases might be, but I will not insist on it here.


> > 
> > Section 4
> > 
> >                                  The extension does not inherently
> >    introduce any additional vulnerabilities above those documented in
> >    [RFC8175].  [...]
> > 
> > As noted by others, this sentence is just not true.
> > I will not duplicate the suggestions for additional considerations that
> > need to be documented.  
> 
> Please see comments / discussion elsewhere on this.

Sorry, most of these threads have aged out of my cache; could you give me a
hint about whose ballot thread to look in, or a link?

> > In particular, I agree with Roman that the use
> > of TLS needs to be mandatory, especially since this protocol is
> > nominally only defined for use with radio links.
> 
> 
> As covered elsewhere, in particular this is really a comment on base
> DLEP and I think this extension should be consistent with that document.
> (Consider an example from when 8175 was issued, consider the case where
> the modem and router use MACsec, 802.1X and 802.1 AE, why is TLS needed
> as well.)

Perhaps.  I think it's highly dependent on whether DLEP is only conveyed
over wired links and the physical scope of those links, though -- my
understanding is that most of the IESG was treating this protocol as
running over the radio link.

> > 
> > 
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> > 
> > Section 3.1
> > 
> >                                 Any errors or inconsistencies
> >    encountered in parsing Sub Data Items are handled in the same fashion
> >    as any other Data Item parsing error encountered in DLEP.
> > 
> > I had a hard time finding the indicated behavior in RFC 8175 -- "error"
> > does not appear at all (and "erroneous" only twice, for IP address
> > processing, v4 and v6); "parse" only appears once (in the Session
> > Initialization State); "inconsistent" apprears several times but I did
> > not see one that seemed to be a generic catch-all case.  It's probably
> > worth putting in a section reference or changing the text to use
> > keywords that are searchable in RFC 8175.
> > 
> I've added the typical text from 8175to remove any ambiguity:
> 
>       In particular, the receiving implementation MUST issue a
>       Session Termination Message containing a Status Data Item with
>       status code set to 130 'Invalid Data' and transition to the
>       Session Termination state.

Thanks.

> > Section 3.1.1
> > 
> >    Queue Size Qn:
> > 
> >       A 24-bit unsigned integer representing the size, in the octet
> >       scale indicated by the Scale field, of the queue supporting
> >       traffic with the DSCPs associated with the queue index.
> > 
> > Is there any value in including a specific sentinel value that indicates
> > that the modem cannot or does not wish to state the size of the
> > corresponding queue?
> 
> As here is no requirement for the modem to set this, I'm not sure if
> there would be any value in such.
> 
> > 
> > Section 3.2
> > 
> >    A router which receives the Pause Data Item MUST cease sending the
> >    identified traffic to the modem.  This may of course translate into
> >    the router's queues exceeding their own thresholds.  If a received
> >    Pause Data Item contains a Queue Index value other than 255, or a
> >    queue index established by a Session Initialization or Session Update
> >    Message, the router MUST terminate the session with a Status Data
> >    Item indicating Invalid Data.
> > 
> > This would be a nit, but actually has serious functional consequences:
> > remove the comma after "255".  The current text says that if the router
> > receives a queue index established by a Session Initialization message,
> > the router MUST terminate the session, which does not seem to be the
> > intent!
> 
> done.
> 
> > 
> > Section 3.3
> > 
> >    The Restart Data Item is used by a modem to indicate to its peer that
> >    transmission of previously suppressed traffic may be resumed.  An
> >    example of when a modem might send this data item is when an internal
> >    queue length drops below a particular threshold.
> > 
> > This seems like a fine place to suggest the application of hysteresis
> > (i.e., that the "particular threshold" here might be lower than the one
> > indicated in Section 3.2).
> > 
> > Section 5.x
> > 
> > It's not clear to me what value there is in repeating the registration
> > policy of the registries from which codepoints are being allocated.
> > IANA will apply the correct policy, and the reader of this document
> > doesn't need to care what policy was applied.
> 
> This section will get revised as part of final processing so defer to
> both IANA and the RFC editor on this.

Sounds good!

Thanks,

Ben


From nobody Tue May  7 07:42:19 2019
Return-Path: <lberger@labn.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 579CA120043 for <manet@ietfa.amsl.com>; Tue,  7 May 2019 07:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.1
X-Spam-Level: ***
X-Spam-Status: No, score=3.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_SUMOF=5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 4Xt_KobceQpP for <manet@ietfa.amsl.com>; Tue,  7 May 2019 07:42:15 -0700 (PDT)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 960FB120157 for <manet@ietf.org>; Tue,  7 May 2019 07:42:12 -0700 (PDT)
Received: from cmgw10.unifiedlayer.com (unknown [10.9.0.10]) by gproxy8.mail.unifiedlayer.com (Postfix) with ESMTP id C47F41ADBD5 for <manet@ietf.org>; Tue,  7 May 2019 08:34:59 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id O1BLhqAlmsFwgO1BLhqmQ4; Tue, 07 May 2019 08:34:59 -0600
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=P/gUeBIu c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=IkcTkHD0fZMA:10:nop_charset_1 a=xqWC_Br6kY4A:10:nop_ipv6 a=E5NmQfObTbMA:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=48vgC7mUAAAA:8 a=RC5-ijVT858AEFDaw74A:9 a=SCG8YGdjpUg6_aZu:21 a=GA4wWs8jr_PHhDo7:21 a=QEXdDO2ut3YA:10:nop_charset_2 a=mYAOWqAtFUkA:10:demote_hacked_domain_1 a=1dbGxDndw2gA:10:demote_hacked_domain_7 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Pr0i2UxKucL2S+Xg/GWhY1TtdkFzFEpnQ2AYdCtDkog=; b=0XTXX+pREVzawZGWVB+0mf7Vl9 8NneDP/oX9FXM63dR1vtcIFizDeXfFh3fjBdwoFDkm1dfYJxwY6ypHSSrOAJZiUnM//n8XEVRcU3/ H0+zciToYcrAwVGH1Nv/nn5ga;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:46282 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1hO1BL-003637-6U; Tue, 07 May 2019 08:34:59 -0600
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-manet-dlep-pause-extension@ietf.org,  manet@ietf.org, manet-chairs@ietf.org
References: <155494445891.22757.7399588752085896470.idtracker@ietfa.amsl.com> <e20c4e6d-b36f-690c-2049-4bc81f5cd37a@labn.net> <20190506224055.GX19509@kduck.mit.edu>
From: Lou Berger <lberger@labn.net>
Message-ID: <10c43c45-877d-842d-b527-8ff0dd9cb600@labn.net>
Date: Tue, 7 May 2019 10:34:57 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190506224055.GX19509@kduck.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1hO1BL-003637-6U
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([IPv6:::1]) [72.66.11.201]:46282
X-Source-Auth: lberger@labn.net
X-Email-Count: 9
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/wTvvicprI3drxFmvhaQZSV0TRrk>
Subject: Re: [manet] Benjamin Kaduk's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2019 14:42:18 -0000

Please see responses below...

On 5/6/2019 6:40 PM, Benjamin Kaduk wrote:
> On Sun, May 05, 2019 at 09:22:16PM -0400, Lou Berger wrote:
>> Hi,
>> 	My apologies, I thought I responded to this, but can't seem to find the
>> response (hopefully my responses are consistent if I did!).
>>
>> On 4/10/19 9:00 PM, Benjamin Kaduk via Datatracker wrote:
>>> Benjamin Kaduk has entered the following ballot position for
>>> draft-ietf-manet-dlep-pause-extension-06: Discuss
>>>
>>> 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-manet-dlep-pause-extension/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> Section 3.1 defines 'Scale' as a four-bit unsigned integer field but only the
>>> values 0-3 are assigned, leaving 4-16k usable.  How will future values be
>>> assigned?
>>>
>> A future revision or update of this document.  We discussed a IANA
>> registry, but thought it overkill as future additions seem quite unlikely.
> Okay.  The Discuss was just to make sure it was considered in some fashion;
> we do have a bunch of documents that explictly note "additional values are
> to be allocated by updates to this specification" but I do not insist on
> it.
>
>>> In Section 3.1.1:
>>>
>>>     DS Field Qn:
>>>
>>>        The data item contains a sequence of 8 bit DS Fields.  The number
>>>        of DS Fields present MUST equal the sum of all Num DSCPs field
>>>        values.
>>>
>>> Perhaps I'm misreading, but I thought the Num DSCPs Qn field was global
>>> for this queue index, so there would just be one of them and no need to
>>> take a sum.
>> It's just saying that more than one DSCP can match to a single queue
>> index value.
> Okay, if I'm looking at the figure properly then this is just an editorial
> issue, then:
>
>          0                   1                   2                   3
>          0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>         |  Queue Index  |             Queue Size Qn                     |
>         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>         | Num DSCPs Qn  |  DS Field Qn  |              ...              :
>         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>         :                          ...                  |  DS Field Qn  |
>         +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> So we have the chunk of stuff for a given queue (index), and the size of
> that queue, then a separate array/length for the DS values.  The various DS
> values that can match this queue index are the contents of this array, but
> this is the only array in the sub data item describing this queue index.
> If that's correct, then isn't the description of "DS Field Qn" just "The
> sub data item contains a sequence of 8 bit DS Fields for this queue index.
> The number of DS Fields present MUST equal this value."?

Yes - I'm fine with a specific text revision if you have one.


>
>>> In Section 3.3:
>>>
>>>     A router which receives the Restart Data Item SHOULD resume
>>>     transmission of the identified traffic to the modem.
>>>
>>> Why is this only a "SHOULD"?
>> to cover the case where the router is choosing not to send data, e.g.,
>> due to lack of available data or other policy such as traffic rate shaping.
> Okay.  Frequently documents will give the reader some hint as to what the
> exceptional cases might be, but I will not insist on it here.
>
>
>>> Section 4
>>>
>>>                                   The extension does not inherently
>>>     introduce any additional vulnerabilities above those documented in
>>>     [RFC8175].  [...]
>>>
>>> As noted by others, this sentence is just not true.
>>> I will not duplicate the suggestions for additional considerations that
>>> need to be documented.
>> Please see comments / discussion elsewhere on this.
> Sorry, most of these threads have aged out of my cache; could you give me a
> hint about whose ballot thread to look in, or a link?

Perhaps it's just best to point you at the current text and see if 
you're okay with it -- see

https://tools.ietf.org/html/draft-ietf-manet-dlep-pause-extension-07#section-4

and let me/us know if you still have any unresolved comments.


>>> In particular, I agree with Roman that the use
>>> of TLS needs to be mandatory, especially since this protocol is
>>> nominally only defined for use with radio links.
>>
>> As covered elsewhere, in particular this is really a comment on base
>> DLEP and I think this extension should be consistent with that document.
>> (Consider an example from when 8175 was issued, consider the case where
>> the modem and router use MACsec, 802.1X and 802.1 AE, why is TLS needed
>> as well.)
> Perhaps.  I think it's highly dependent on whether DLEP is only conveyed
> over wired links and the physical scope of those links, though -- my
> understanding is that most of the IESG was treating this protocol as
> running over the radio link.

umm, DLEP is *NEVER* expected to run over the air.  This is covered in 
RFC8175 and is not impacted by this extension.

Thanks,

Lou

>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> Section 3.1
>>>
>>>                                  Any errors or inconsistencies
>>>     encountered in parsing Sub Data Items are handled in the same fashion
>>>     as any other Data Item parsing error encountered in DLEP.
>>>
>>> I had a hard time finding the indicated behavior in RFC 8175 -- "error"
>>> does not appear at all (and "erroneous" only twice, for IP address
>>> processing, v4 and v6); "parse" only appears once (in the Session
>>> Initialization State); "inconsistent" apprears several times but I did
>>> not see one that seemed to be a generic catch-all case.  It's probably
>>> worth putting in a section reference or changing the text to use
>>> keywords that are searchable in RFC 8175.
>>>
>> I've added the typical text from 8175to remove any ambiguity:
>>
>>        In particular, the receiving implementation MUST issue a
>>        Session Termination Message containing a Status Data Item with
>>        status code set to 130 'Invalid Data' and transition to the
>>        Session Termination state.
> Thanks.
>
>>> Section 3.1.1
>>>
>>>     Queue Size Qn:
>>>
>>>        A 24-bit unsigned integer representing the size, in the octet
>>>        scale indicated by the Scale field, of the queue supporting
>>>        traffic with the DSCPs associated with the queue index.
>>>
>>> Is there any value in including a specific sentinel value that indicates
>>> that the modem cannot or does not wish to state the size of the
>>> corresponding queue?
>> As here is no requirement for the modem to set this, I'm not sure if
>> there would be any value in such.
>>
>>> Section 3.2
>>>
>>>     A router which receives the Pause Data Item MUST cease sending the
>>>     identified traffic to the modem.  This may of course translate into
>>>     the router's queues exceeding their own thresholds.  If a received
>>>     Pause Data Item contains a Queue Index value other than 255, or a
>>>     queue index established by a Session Initialization or Session Update
>>>     Message, the router MUST terminate the session with a Status Data
>>>     Item indicating Invalid Data.
>>>
>>> This would be a nit, but actually has serious functional consequences:
>>> remove the comma after "255".  The current text says that if the router
>>> receives a queue index established by a Session Initialization message,
>>> the router MUST terminate the session, which does not seem to be the
>>> intent!
>> done.
>>
>>> Section 3.3
>>>
>>>     The Restart Data Item is used by a modem to indicate to its peer that
>>>     transmission of previously suppressed traffic may be resumed.  An
>>>     example of when a modem might send this data item is when an internal
>>>     queue length drops below a particular threshold.
>>>
>>> This seems like a fine place to suggest the application of hysteresis
>>> (i.e., that the "particular threshold" here might be lower than the one
>>> indicated in Section 3.2).
>>>
>>> Section 5.x
>>>
>>> It's not clear to me what value there is in repeating the registration
>>> policy of the registries from which codepoints are being allocated.
>>> IANA will apply the correct policy, and the reader of this document
>>> doesn't need to care what policy was applied.
>> This section will get revised as part of final processing so defer to
>> both IANA and the RFC editor on this.
> Sounds good!
>
> Thanks,
>
> Ben
>


From nobody Tue May  7 08:57:33 2019
Return-Path: <session-request@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C4512011D; Tue,  7 May 2019 08:57:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: aretana.ietf@gmail.com, manet@ietf.org, sratliff@idirect.net, manet-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155724465155.21185.5163330835167532905.idtracker@ietfa.amsl.com>
Date: Tue, 07 May 2019 08:57:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/zWI5hA4OAausnNL10ZNccInotBk>
Subject: [manet] manet - New Meeting Session Request for IETF 105
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2019 15:57:32 -0000

A new meeting session request has just been submitted by Stan Ratliff, a Chair of the manet working group.


---------------------------------------------------------
Working Group Name: Mobile Ad-hoc Networks
Area Name: Routing Area
Session Requester: Stan Ratliff

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority:  dtn teas detnet ipwave
 Second Priority:  babel lsr roll



People who must be present:
  Stan Ratliff
  Justin Dean
  Alvaro Retana

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Fri May 10 07:04:11 2019
Return-Path: <noreply@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D529112001E; Fri, 10 May 2019 07:04:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-manet-dlep-pause-extension@ietf.org, Stan Ratliff <sratliff@idirect.net>, aretana.ietf@gmail.com, manet-chairs@ietf.org, sratliff@idirect.net, manet@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <155749704986.2814.10311010897802498754.idtracker@ietfa.amsl.com>
Date: Fri, 10 May 2019 07:04:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/xA1xnGZFc5gnrd6bCC0SQa1OfJk>
Subject: [manet] Alissa Cooper's No Objection on draft-ietf-manet-dlep-pause-extension-07: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 14:04:10 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-manet-dlep-pause-extension-07: 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-manet-dlep-pause-extension/



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

DISCUSS cleared, leaving in my previous COMMENT:

I support the DISCUSS positions of Warren and Magnus.

I'm unclear on why this specification is necessary, i.e. why the use of
existing transport protocols and processing of DSCPs do not suffice to achieve
what this specification is aiming to achieve. Is that explained in another
document somewhere?

= Section 1 =

"Various flow control methods are possible, e.g.,
   see [I-D.ietf-manet-dlep-da-credit-extension]."

The referenced document does not specify a flow control method. Maybe
draft-ietf-manet-dlep-credit-flow-control is what was intended?



From nobody Fri May 10 07:05:12 2019
Return-Path: <alissa@cooperw.in>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702F212001E; Fri, 10 May 2019 07:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=cyafwf6Z; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Y0GKP6oi
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 uq-yimwbR5Ph; Fri, 10 May 2019 07:05:03 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 654161201DB; Fri, 10 May 2019 07:04:50 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 83F352217D; Fri, 10 May 2019 10:04:49 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 10 May 2019 10:04:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm3; bh=Z9y+V65audoRqHS/2pYUvNz HAXKFEkBAm0epfWNc/Rs=; b=cyafwf6ZPQj/eEk+EghmKGgVjx0FM/FdYAHMeSn c/R/LN4/HBrAs/gtTlBBgReX1MOborPvCycNUE3vGmv3boERlASZ22O73D2LfbG/ EbFJoDdhdNeyXVKpa+2UMWEKJvxcx/EPdCU6GCNMhzXz/CYkSJGA2vQkd7VtDNju neJftRroZUoLkpzE51hshgaZ2Tj1+ZuQFcMbySSEPYoEyiWgVS+qgFkLjK7SFGco FDeCMLr23FmxB0KUYrbX30MgBSVgTW3wPbAOWTx0pCoSuUi2NR+uXVMo2lkczYH/ URL0giA5Fb57207HDN9RznxA3xAHe8EOHL6/+ER8UEcHhIA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Z9y+V6 5audoRqHS/2pYUvNzHAXKFEkBAm0epfWNc/Rs=; b=Y0GKP6oio0KFRRymcFd0UM FzJgZrG8JAMzUWaUpJ9lzv+D6aGhm8bcz4pUYSKVQVLH4kedslw4rRONFZgEnUZg Hq1zwk1FefgPZeSB2YzWs41HlCF1Ji8iCJ7uL3c41ih7GXG+e9bzgdORhtAkIHzF 3YnJAZ1MM+x5lmvAd2aXHONfvZsT2N+RxP1OPOPA+Vh3BG75rtJnhNEOtPB/xlqH A2leZbIUWykUd00eh6K4dQf1DfGlBskcjYg7nxzvgCXBk1picWJw9GlaIxgwz8RF AMHuZirukYIe5vexwbOroj9xceouF+pyouhp8YQ7NvGjXnNG/N3Sujz0yKlFqMiw ==
X-ME-Sender: <xms:AYXVXOWLpLJUMnv9x51EQEb9iAGTabsaLWfrJS-lQxZRGJMJTaaweg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeekgdejgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhkfgtggfuffgjvfhfofesrgdtmherhhdtjeenucfhrhhomheptehlihhsshgr ucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucfkphepudejfe drfeekrdduudejrdekjeenucfrrghrrghmpehmrghilhhfrhhomheprghlihhsshgrsegt ohhophgvrhifrdhinhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:AYXVXGchwGldvBPBS5_Ii835st0KRO7wn-ipPF10bdwMVD61q2YOAA> <xmx:AYXVXPbdj5EiTBskWDWfD8mBzqpL4eXfUQJrTacx5d4bnC5PtHieVQ> <xmx:AYXVXKPwpetjqK9zkFgOu2vlB1wPImwwRR4y9xVfeVRAHASJYBNmRg> <xmx:AYXVXFlb3DAsEgq_jcNBhonuf_MrzRjrWrUgI3O2SPEpRRwAMbOlBg>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.87]) by mail.messagingengine.com (Postfix) with ESMTPA id 955FC10379; Fri, 10 May 2019 10:04:47 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <BEDBDD3E-6FE2-41CD-9474-7C955B578AF1@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2769B660-4FCD-4D69-8DA1-B73E293B02B8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 10 May 2019 10:04:45 -0400
In-Reply-To: <CAMMESszKk8ycnANbPvm_Q7-nu4hMGDB-xVwPNe0rsDTTHW0EUQ@mail.gmail.com>
Cc: Stan Ratliff <sratliff@idirect.net>, manet-chairs@ietf.org, IESG <iesg@ietf.org>, draft-ietf-manet-dlep-pause-extension@ietf.org, manet@ietf.org
To: Alvaro Retana <aretana.ietf@gmail.com>
References: <155492518369.22601.15786320586524280536.idtracker@ietfa.amsl.com> <CAMMESswp1BrNmOA1ariTegokJQOaGpi5YRGiVy3DYXiuxUGLwQ@mail.gmail.com> <6CBEC07D-A6E3-455C-87F8-6CB2DC0C1BDF@cooperw.in> <CAMMESsztHn9ufGfKbvxniyLK8u_54a0mn4vJ5_ZUpH7t9Q=U2w@mail.gmail.com> <CAMMESszKk8ycnANbPvm_Q7-nu4hMGDB-xVwPNe0rsDTTHW0EUQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/ow7K2suB09w-I-Hn_fUcMvxpxGo>
Subject: Re: [manet] Alissa Cooper's Discuss on draft-ietf-manet-dlep-pause-extension-06: (with DISCUSS and COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 14:05:05 -0000

--Apple-Mail=_2769B660-4FCD-4D69-8DA1-B73E293B02B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I cleared, but it would be good to think about a charter update to =
capture the full scope of the work the group is expecting to do.

Thanks,
Alissa

> On May 6, 2019, at 2:26 PM, Alvaro Retana <aretana.ietf@gmail.com> =
wrote:
>=20
> Alissa:
>=20
> Hi!
>=20
> Do my answers satisfy your DISCUSS question?  If not, what are your =
expectations?
>=20
> Thanks!
>=20
> Alvaro.
>=20
> On April 11, 2019 at 9:49:39 AM, Alvaro Retana (aretana.ietf@gmail.com =
<mailto:aretana.ietf@gmail.com>) wrote:
>=20
>> On April 11, 2019 at 9:06:50 AM, Alissa Cooper (alissa@cooperw.in =
<mailto:alissa@cooperw.in>) wrote:
>>=20
>>> Is there any scope limitation to the functionality that could =
potentially be characterized as further "development of DLEP"? I ask =
because from a quick read of the base specification, it doesn=E2=80=99t =
look like pause/resume was contemplated, and as you note this was not =
explicitly called out in the charter whereas credit windowing was. I=E2=80=
=99m wondering what the boundary is around the functionality DLEP is =
expected to provide as a protocol.
>>=20
>> In short, I believe the boundary is simply =E2=80=9Cwhatever the =
users need=E2=80=9D.
>>=20
>> When we re-chartered (a couple of years ago), the WG thought that =
credit windowing would be the focus (there was a document in progress, =
etc.), but that has changed to include this extension, and others.  The =
community working on DLEP is a very close-knit group with related (it =
not significantly overlapping) users =E2=80=94 the focus of the work =
then follows what their users require.
>>=20
>> At some point we should think about generalizing the charter.
>>=20
>> Thanks!
>>=20
>> Alvaro.
>>=20


--Apple-Mail=_2769B660-4FCD-4D69-8DA1-B73E293B02B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
cleared, but it would be good to think about a charter update to capture =
the full scope of the work the group is expecting to do.<div =
class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D"">Alissa<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On May 6, 2019, at 2:26 PM, =
Alvaro Retana &lt;<a href=3D"mailto:aretana.ietf@gmail.com" =
class=3D"">aretana.ietf@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Alissa:</div><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica, Arial; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Hi!</div><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica, Arial; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Do my answers satisfy your DISCUSS question?&nbsp; If =
not, what are your expectations?</div><div style=3D"caret-color: rgb(0, =
0, 0); font-family: Helvetica, Arial; font-size: 13px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Thanks!</div><div style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica, Arial; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br class=3D""></div><div =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D"">Alvaro.</div><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica, Arial; font-size: 13px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><p class=3D"airmail_on" =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica, Arial; =
font-size: 13px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;">On April 11, 2019 at 9:49:39 AM, Alvaro Retana (<a =
href=3D"mailto:aretana.ietf@gmail.com" =
class=3D"">aretana.ietf@gmail.com</a>) wrote:</p><blockquote type=3D"cite"=
 class=3D"clean_bq" style=3D"font-family: Helvetica, Arial; font-size: =
13px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; text-decoration: none;"><span =
class=3D""><div style=3D"word-wrap: break-word;" class=3D""><div =
class=3D""></div><div class=3D""><div style=3D"margin: 0px;" =
class=3D""><font face=3D"Helvetica" class=3D"">On April 11, 2019 at =
9:06:50 AM, Alissa Cooper (<a href=3D"mailto:alissa@cooperw.in" =
class=3D"">alissa@cooperw.in</a>) wrote:</font></div><div style=3D"margin:=
 0px;" class=3D""><font face=3D"Helvetica" class=3D""><br =
class=3D""></font></div><div class=3D""><div class=3D""><blockquote =
type=3D"cite" class=3D"clean_bq" style=3D"font-variant-caps: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px;"><div =
class=3D""><div style=3D"font-variant-caps: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px;" class=3D""><span class=3D""><font=
 face=3D"Helvetica" class=3D"">Is there any scope limitation to the =
functionality that could potentially be characterized as further =
"development of DLEP"? I ask because from a quick read of the base =
specification, it doesn=E2=80=99t look like pause/resume was =
contemplated, and as you note this was not explicitly called out in the =
charter whereas credit windowing was. I=E2=80=99m wondering what the =
boundary is around the functionality DLEP is expected to provide as a =
protocol.</font></span></div></div></blockquote></div><p class=3D""><font =
face=3D"Helvetica" class=3D"">In short, I believe the boundary is simply =
=E2=80=9Cwhatever the users need=E2=80=9D.</font></p><p class=3D""><font =
face=3D"Helvetica" class=3D"">When we re-chartered (a couple of years =
ago), the WG thought that credit windowing would be the focus (there was =
a document in progress, etc.), but that has changed to include this =
extension, and others.&nbsp; The community working on DLEP is a very =
close-knit group with related (it not significantly overlapping) users =
=E2=80=94 the focus of the work then follows what their users =
require.</font></p><p class=3D""><font face=3D"Helvetica" class=3D"">At =
some point we should think about generalizing the charter.</font></p><p =
class=3D""><font face=3D"Helvetica" class=3D"">Thanks!</font></p><p =
class=3D""><font face=3D"Helvetica" =
class=3D"">Alvaro.</font></p></div></div></div></span></blockquote></div><=
/blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_2769B660-4FCD-4D69-8DA1-B73E293B02B8--


From nobody Fri May 10 07:45:51 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: manet@ietf.org
Delivered-To: manet@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0A36120075; Fri, 10 May 2019 07:45:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, sratliff@idirect.net, Stan Ratliff <sratliff@idirect.net>, manet-chairs@ietf.org, manet@ietf.org, draft-ietf-manet-dlep-multi-hop-extension@ietf.org, aretana.ietf@gmail.com, rfc-editor@rfc-editor.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155749953384.3000.10533769730949470471.idtracker@ietfa.amsl.com>
Date: Fri, 10 May 2019 07:45:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/WnPeqaKPeidXfnnN8EtEvq-6tao>
Subject: [manet] Protocol Action: 'Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension' to Proposed Standard (draft-ietf-manet-dlep-multi-hop-extension-07.txt)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2019 14:45:34 -0000

The IESG has approved the following document:
- 'Dynamic Link Exchange Protocol (DLEP) Multi-Hop Forwarding Extension'
  (draft-ietf-manet-dlep-multi-hop-extension-07.txt) as Proposed Standard

This document is the product of the Mobile Ad-hoc Networks Working Group.

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-manet-dlep-multi-hop-extension/





Technical Summary

   This document defines an extension to the DLEP protocol that enables
   the reporting and control of Multi-Hop Forwarding by DLEP capable
   modems.

Working Group Summary

   The Working Group process proceeded without any issues. The 
   authors took most of the points raised on the mailing list and 
   incorporated them into the document. The document reached last 
   call without controversy.

Document Quality

   There are no implementations of the specification, however, vendors 
   plan to implement.

Personnel

   The Document Shepherd is Stan Ratliff. 
   The responsible Area Director is Alvaro Retana.


From nobody Fri May 17 13:39:55 2019
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D90120046; Fri, 17 May 2019 13:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 zEXiUWfJeUF6; Fri, 17 May 2019 13:39:49 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E238120158; Fri, 17 May 2019 13:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=m0SxyHEVP7wpRI1W3Osrvmsn1xbMAzaX9eFQOh3SqgE=; b=4gtSe/ZHHzAGRVndV75b0oWPj MApVmSNvHPgrh+eHKN/eXh0Jvkh5Rcbo1Lsxkymui/9oDLEkqwgBr5lTtu3JK+wnHu1/BGsqjmN+I ktJWnzZF3ThUEzby9Sogb9Ug6sW+doNwB7NXwqMS2q1TROtN24gmszvB+t1j4l7X9PbejPI+MZIJ3 YfJkfSC9psTHIL3rZR1zTscDvn8H69n0aXfDFkN0nDe2LV8plcEYnUa/KYniziT7NegyOLbhYe8Nu rR5RX9iJZvQc+lVkKDNjqcCSAgs9mlKh9EexiLzN6JtsDz89pIxswEbd9WgwzlikGWX0Q9rXcm1De +qQIcK0aQ==;
Received: from [31.185.135.221] (port=60290 helo=[192.168.0.5]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <ietf@bobbriscoe.net>) id 1hRjdp-0001B9-VO; Fri, 17 May 2019 21:39:46 +0100
To: Lou Berger <lberger@labn.net>, tsv-art@ietf.org
Cc: draft-ietf-manet-dlep-multi-hop-extension.all@ietf.org, manet@ietf.org, ietf@ietf.org
References: <155480892243.14232.8537433440288444332@ietfa.amsl.com> <8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <f8cb4053-482e-54b4-07b6-e75e4800fee9@bobbriscoe.net>
Date: Fri, 17 May 2019 21:39:44 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net>
Content-Type: multipart/alternative; boundary="------------29CF8890E9EEAF14027AC68A"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/0cbuCIWyryNmGDBsoYNEQ6iCcpI>
Subject: Re: [manet] Tsvart last call review of draft-ietf-manet-dlep-multi-hop-extension-06
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 20:39:54 -0000

This is a multi-part message in MIME format.
--------------29CF8890E9EEAF14027AC68A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Lou,

On 25/04/2019 16:45, Lou Berger wrote:
> Hi Bob,
> 	Sorry for the late reply. See below for specific responses.
And sry for my longer delay replying...

>
> On 4/9/19 7:22 AM, Bob Briscoe via Datatracker wrote:
>> Reviewer: Bob Briscoe
>> Review result: Ready with Issues
>>
>> This document has been reviewed as part of the transport area review team's
>> ongoing effort to review key IETF documents. These comments were written
>> primarily for the transport area directors, but are copied to the document's
>> authors and WG to allow them to address any issues raised and also to the IETF
>> discussion list for information.
>>
>> When done at the time of IETF Last Call, the authors should consider this
>> review as part of the last-call comments they receive. Please always CC
>> tsv-art@ietf.org if you reply to or forward this review.
>>
>> AFAICT, there's nothing technically wrong, but I believe the authors use of
>> normative text does not convey the meaning they intended, in nearly every case.
>>   It will be seen below that there seems to be a general misunderstanding of the
>> use of, 'SHOULD do X' when there will never be a case when X should not be
>> done. 'SHOULD' and 'MAY' need to be used judiciously, because they make
>> interoperability harder.
>>
>> ==Inappropriate Normative Text==
>>
>> S.2.
>> "The use of the Multi-Hop Forwarding Extension SHOULD be configurable."
>> {I think you mean it SHOULD be possible to enable/disable the extension?
> To me that's what this says.
[BB] It's just ambiguous. "Configurable" usually means "capable of 
having its settings configured". Yes, "the use of" makes it more likely 
that you mean "the ability to use", but it's just not clearly written.
>
>> On a
>> modem. a router or both?
> yes, by any node that supports the extension.
>
>> In what circumstances would it not be configurable (if
>> none, then MUST would be appropriate)?
> We generally don't stop people from building products that meet their
> specific market requirements as long as there's no interop issue, hence
> the SHOULD vs MUST.> What happens if one device uses the
>> extension and another doesn't? This last question also applies for incremental
>> deployment.}
> This is covered in the base DLEP RFC.
>
>> S.3.1.
>> "The Hop Count Data Item SHOULD be carried in the Destination Up, Destination
>> Update, Destination Announce Response, and Link Characteristics Response
>> messages." {I don't think the use of "SHOULD" here achieves what you intend. I
>> think you're trying to say that this data item can only be carried in these 4
>> messages. But what you've said is that all these messages SHOULD contain a Hop
>> Count data item. If any normative text is needed here, I think it would say
>> this data item MUST NOT be carried in messages other than these 4. But maybe
>> just substitute 'SHOULD' with 'can'?}
>>
> I'd be fine with MAY as this is more aligned with RFC8175 statement of
> what DIs to carry in a message.  This siad, I believe the feeling was
> that MAY was too weak for an extension-specific DI.  Unless there is
> strong objection with this, I'm inclined to leave it with how the WG
> approved it.
[BB] I think you've missed my point, which is about ambiguous meaning of 
sentences, not a technical question.

But before we get to that, there was a prerequisite question about this 
sentence in my editorial nits file. The full sentence said:

    The Hop Count Data Item SHOULD be carried in the Destination Up, Destination
    Update, Destination Announce Response, and Link Characteristics Response
    messages when the Hop Count to a destination is greater than one (1).

My nit question about this sentence was:
"{Does this 'when >1' clause apply to all 4 messages, or just Link 
Characteristic Response messages?}"

You've just ignored this and left the sentence as it was. Did you not 
understand my question? if so, you could have asked.

The grammar of the sentence reads as "The Hop Count Data Item SHOULD be 
carried in the first three message types (whatever the hop count), and 
in the fourth message type (when the hop count is >1). I doubt you meant 
that. If not, the sentence ought to be disambiguated as follows:

    When the Hop Count to a destination is greater than one (1), the Hop
    Count Data Item SHOULD be carried in the Destination Up, Destination
    Update, Destination Announce Response, and Link Characteristics Response
    messages.

Next, let's return to the SHOULD. This means that, even when count > 1, 
it doesn't have to be included in these messages. The next para says:

    The absence of the Hop Count Data Item MUST be interpreted by the
    router as a Hop Count value of one (1).

So, when count > 1, you say it doesn't have to be carried in these 
messages,... so the router will assume it is 1, even tho it isn't. Is 
that what you intended to say? If so, surely you need to say under what 
circumstances a hop count >1 would not be carried in these messages.

It all seems very vague to me.

>
>> S.3.2.
>> The Hop Control Data Item MAY be carried in a Session Update Message sent by a
>> router when the control applies to the whole device, or a Link Characteristics
>> Request Message when the control applies to a particular destination. {Again, I
>> think you're trying to say, "If used, the Hop Control Data Item MUST only be
>> carried in" ...one of these two message types.}
[BB] Actually, perhaps you didn't mean to use normative text at all. 
Perhaps you just meant

    The Hop Control Data Item would be carried in...


>>
>> "A modem that receives the Hop Control Data Item in a [XXX] Message SHOULD take
>> whatever actions are needed to make the change indicated by the data item for
>> [YYY]." (two occurrences) {Inappropriate use of SHOULD: a) Surely a modem MUST
>> "take whatever actions are needed." Why would it not? b) Anyway, it's
>> meaningless to normatively require a vaguely defined action}
[BB] You didn't respond to this point.
>>
>> S.3.2.3 Direction Connection
> this should be Direct Connection
>
>> "It indicates that the modem SHOULD attempt to establish a direct connection
>> with the destination identified in the message." {I think you mean 'MUST'. Why
>> would it not even attempt to?}
>>
> local policy, or that it know that a connection is no longer possible.
>
>> "This action SHOULD only be sent for destinations for which the Hop Count is
>> greater than 1 and has the P-Bit set in the previously received Hop Count Data
>> Item." {I think you mean MUST. Why would it be sent otherwise?}
> A must would translate to a dlep error on the receiving side, which
> would translate to a session reset, which is really disruptive.
[BB] I meant "This action MUST only be sent for destinations for which 
... count >1 & P set ...". I don't think that would cause errors, would it?

Again, my point is about use of English, not technical. I'm picking up 
every case where you say "SHOULD" and working out what exceptions your 
English allows. By using "SHOULD only be sent" rather than "MUST only be 
sent", it allows exceptions to 'only' not to 'sent'. So it means 
"although this action will normally solely be sent for destinations with 
count>1 & P set, it could be sent for other destinations..." which, as 
you say yourself, would cause errors.

I don't think you actually need normative text here anyway. I think you 
used 'SHOULD' because you were trying to say something like: "the action 
can only be sent for destinations with count > 1 & P set (but for those 
destinations the action doesn't have to be sent)."

Or perhaps you really do need normative text here for interop in order 
to avoid dlep errors, and you meant to say: "The action MUST NOT be sent 
for destinations that do not have count>1 & P set ..."


This is all becoming rather painful, 'cos you don't seem to be getting 
that I'm just trying to improve the highly ambiguous English around the 
normative text. However, it's hard 'cos I'm not sure what you were 
trying to mean in the first place.

>
>> S.3.2.4. Suppress Forwarding
>> I suggest that you don't gratuitously switch from 'MUST' to 'SHALL' just for
>> this section? Many implementers search the text for 'MUST'.
>>
>> ==Authentication==
>>
>> S.4.
>> RFC8175 says
>>     'For all "networked deployments" ..., the implementation and use of TLS are
>>     STRONGLY RECOMMENDED.'
>>
>> I believe it would be worth identifying which extensions would be unsafe if TLS
>> were not used. Certainly all the Multi-Hop Extensions would be unsafe if not
>> authenticated.
> umm, I think all of DLEP would be unsafe without TLS, or some other
> equivalent, e.g., macsec.
[BB] Again, you're not grocking that I am questioning the use of 
RECOMMENDED, which is equivalent to SHOULD, and therefore weaker than 
MUST, even with STRONGLY added. (BTW, STRONGLY isn't a normative word 
defined in RFC2119).

If you are only saying STRONGLY RECOMMENDED, you are still saying 
implementers don't have to use TLS. If you really don't want to require 
them to, then it is always best to explain why you are not saying MUST 
(e.g. perhaps to allow for deployments in trusted environments).


>
>> ==General Nits==
>> Inappropriate and/or inconsistent capitalization of certain phrases, like 'Data
>> Item' or 'Action' or 'Message'.
>>
>> ==Specific Nits==
>> I've provided suggested corrections in the following xml files:
>> http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.xml
>> http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.txt
>> http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB-DIFF-06.html
On a quick look, I found a couple of nits still:

3.2.4. Suppress Forwarding
s/Impact to destination hop counts are provided to the router by the 
modem as described above./
  /The impact on destination hop counts is provided to the router by the 
modem as described above./
If you didn't mean that, you can't leave the sentence like it is.

Security Considerations:
s/Similar attacks are generally possible base DLEP,/
  /Similar attacks are generally possible in base DLEP,/


> Thanks!
> I've pushed changes to https://github.com/louberger/dlep-extensions and
> will coordinate an update with the AD.
> Lou
Cheers


Bob
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------29CF8890E9EEAF14027AC68A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Lou,<br>
    <br>
    <div class="moz-cite-prefix">On 25/04/2019 16:45, Lou Berger wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">Hi Bob,
	Sorry for the late reply. See below for specific responses.</pre>
    </blockquote>
    And sry for my longer delay replying...<br>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">

On 4/9/19 7:22 AM, Bob Briscoe via Datatracker wrote:
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">Reviewer: Bob Briscoe
Review result: Ready with Issues

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
<a class="moz-txt-link-abbreviated" href="mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or forward this review.

AFAICT, there's nothing technically wrong, but I believe the authors use of
normative text does not convey the meaning they intended, in nearly every case.
 It will be seen below that there seems to be a general misunderstanding of the
use of, 'SHOULD do X' when there will never be a case when X should not be
done. 'SHOULD' and 'MAY' need to be used judiciously, because they make
interoperability harder.

==Inappropriate Normative Text==

S.2.
"The use of the Multi-Hop Forwarding Extension SHOULD be configurable. "
{I think you mean it SHOULD be possible to enable/disable the extension?
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
To me that's what this says.</pre>
    </blockquote>
    [BB] It's just ambiguous. "Configurable" usually means "capable of
    having its settings configured". Yes, "the use of" makes it more
    likely that you mean "the ability to use", but it's just not clearly
    written.<br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">On a
modem. a router or both? 
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">yes, by any node that supports the extension.

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">In what circumstances would it not be configurable (if
none, then MUST would be appropriate)?
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">We generally don't stop people from building products that meet their
specific market requirements as long as there's no interop issue, hence
the SHOULD vs MUST.&gt; What happens if one device uses the
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">extension and another doesn't? This last question also applies for incremental
deployment.}
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">This is covered in the base DLEP RFC.

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">
S.3.1.
"The Hop Count Data Item SHOULD be carried in the Destination Up, Destination
Update, Destination Announce Response, and Link Characteristics Response
messages." {I don't think the use of "SHOULD" here achieves what you intend. I
think you're trying to say that this data item can only be carried in these 4
messages. But what you've said is that all these messages SHOULD contain a Hop
Count data item. If any normative text is needed here, I think it would say
this data item MUST NOT be carried in messages other than these 4. But maybe
just substitute 'SHOULD' with 'can'?}

</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
I'd be fine with MAY as this is more aligned with RFC8175 statement of
what DIs to carry in a message.  This siad, I believe the feeling was
that MAY was too weak for an extension-specific DI.  Unless there is
strong objection with this, I'm inclined to leave it with how the WG
approved it.</pre>
    </blockquote>
    [BB] I think you've missed my point, which is about ambiguous
    meaning of sentences, not a technical question.<br>
    <br>
    But before we get to that, there was a prerequisite question about
    this sentence in my editorial nits file. The full sentence said: <br>
    <blockquote>
      <pre class="moz-quote-pre" wrap="">The Hop Count Data Item SHOULD be carried in the Destination Up, Destination
Update, Destination Announce Response, and Link Characteristics Response
messages when the Hop Count to a destination is greater than one (1).</pre>
    </blockquote>
    My nit question about this sentence was: <br>
    "{Does this 'when &gt;1' clause apply to all 4 messages, or just
    Link Characteristic Response messages?}"<br>
    <br>
    You've just ignored this and left the sentence as it was. Did you
    not understand my question? if so, you could have asked.<br>
    <br>
    The grammar of the sentence reads as "The Hop Count Data Item SHOULD
    be carried in the first three message types (whatever the hop
    count), and in the fourth message type (when the hop count is
    &gt;1). I doubt you meant that. If not, the sentence ought to be
    disambiguated as follows:<br>
    <blockquote>
      <pre class="moz-quote-pre" wrap="">When the Hop Count to a destination is greater than one (1), the Hop 
Count Data Item SHOULD be carried in the Destination Up, Destination
Update, Destination Announce Response, and Link Characteristics Response
messages.</pre>
    </blockquote>
    Next, let's return to the SHOULD. This means that, even when count
    &gt; 1, it doesn't have to be included in these messages. The next
    para says:<br>
    <blockquote><tt>The absence of the Hop Count Data Item MUST be
        interpreted by the router as a Hop Count value of one (1).</tt><br>
    </blockquote>
    So, when count &gt; 1, you say it doesn't have to be carried in
    these messages,... so the router will assume it is 1, even tho it
    isn't. Is that what you intended to say? If so, surely you need to
    say under what circumstances a hop count &gt;1 would not be carried
    in these messages. <br>
    <br>
    It all seems very vague to me. <br>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">S.3.2.
The Hop Control Data Item MAY be carried in a Session Update Message sent by a
router when the control applies to the whole device, or a Link Characteristics
Request Message when the control applies to a particular destination. {Again, I
think you're trying to say, "If used, the Hop Control Data Item MUST only be
carried in" ...one of these two message types.}</pre>
      </blockquote>
    </blockquote>
    [BB] Actually, perhaps you didn't mean to use normative text at all.
    Perhaps you just meant <br>
    <blockquote><tt>The Hop Control Data Item would be carried in...</tt><br>
    </blockquote>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">

"A modem that receives the Hop Control Data Item in a [XXX] Message SHOULD take
whatever actions are needed to make the change indicated by the data item for
[YYY]." (two occurrences) {Inappropriate use of SHOULD: a) Surely a modem MUST
"take whatever actions are needed." Why would it not? b) Anyway, it's
meaningless to normatively require a vaguely defined action}</pre>
      </blockquote>
    </blockquote>
    [BB] You didn't respond to this point.<br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">

S.3.2.3 Direction Connection
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
this should be Direct Connection

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">
"It indicates that the modem SHOULD attempt to establish a direct connection
with the destination identified in the message." {I think you mean 'MUST'. Why
would it not even attempt to?}

</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
local policy, or that it know that a connection is no longer possible.

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">"This action SHOULD only be sent for destinations for which the Hop Count is
greater than 1 and has the P-Bit set in the previously received Hop Count Data
Item." {I think you mean MUST. Why would it be sent otherwise?}
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
A must would translate to a dlep error on the receiving side, which
would translate to a session reset, which is really disruptive.</pre>
    </blockquote>
    [BB] I meant "This action MUST only be sent for destinations for
    which ... count &gt;1 &amp; P set ...". I don't think that would
    cause errors, would it?<br>
    <br>
    Again, my point is about use of English, not technical. I'm picking
    up every case where you say "SHOULD" and working out what exceptions
    your English allows. By using "SHOULD only be sent" rather than
    "MUST only be sent", it allows exceptions to 'only' not to 'sent'.
    So it means "although this action will normally solely be sent for
    destinations with count&gt;1 &amp; P set, it could be sent for other
    destinations..." which, as you say yourself, would cause errors.<br>
    <br>
    I don't think you actually need normative text here anyway. I think
    you used 'SHOULD' because you were trying to say something like:
    "the action can only be sent for destinations with count &gt; 1
    &amp; P set (but for those destinations the action doesn't have to
    be sent)."<br>
    <br>
    Or perhaps you really do need normative text here for interop in
    order to avoid dlep errors, and you meant to say: "The action MUST
    NOT be sent for destinations that do not have count&gt;1 &amp; P set
    ..."<br>
    <br>
    <br>
    This is all becoming rather painful, 'cos you don't seem to be
    getting that I'm just trying to improve the highly ambiguous English
    around the normative text. However, it's hard 'cos I'm not sure what
    you were trying to mean in the first place.<br>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">
S.3.2.4. Suppress Forwarding
I suggest that you don't gratuitously switch from 'MUST' to 'SHALL' just for
this section? Many implementers search the text for 'MUST'.

==Authentication==

S.4.
RFC8175 says
   'For all "networked deployments" ..., the implementation and use of TLS are
   STRONGLY RECOMMENDED.'

I believe it would be worth identifying which extensions would be unsafe if TLS
were not used. Certainly all the Multi-Hop Extensions would be unsafe if not
authenticated.
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
umm, I think all of DLEP would be unsafe without TLS, or some other
equivalent, e.g., macsec.</pre>
    </blockquote>
    [BB] Again, you're not grocking that I am questioning the use of
    RECOMMENDED, which is equivalent to SHOULD, and therefore weaker
    than MUST, even with STRONGLY added. (BTW, STRONGLY isn't a
    normative word defined in RFC2119). <br>
    <br>
    If you are only saying STRONGLY RECOMMENDED, you are still saying
    implementers don't have to use TLS. If you really don't want to
    require them to, then it is always best to explain why you are not
    saying MUST (e.g. perhaps to allow for deployments in trusted
    environments).<br>
    <br>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">

</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">
==General Nits==
Inappropriate and/or inconsistent capitalization of certain phrases, like 'Data
Item' or 'Action' or 'Message'.

==Specific Nits==
I've provided suggested corrections in the following xml files:
<a class="moz-txt-link-freetext" href="http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.xml">http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.xml</a>
<a class="moz-txt-link-freetext" href="http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.txt">http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB.txt</a>
<a class="moz-txt-link-freetext" href="http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB-DIFF-06.html">http://bobbriscoe.net/tmp/draft-ietf-manet-dlep-multi-hop-extension-06_BB-DIFF-06.html</a>
</pre>
      </blockquote>
    </blockquote>
    On a quick look, I found a couple of nits still:<br>
    <br>
    3.2.4. Suppress Forwarding<br>
    s/Impact to destination hop counts are provided to the router by the
    modem as described above./<br>
     /The impact on destination hop counts is provided to the router by
    the modem as described above./<br>
    If you didn't mean that, you can't leave the sentence like it is.<br>
    <br>
    Security Considerations:<br>
    s/Similar attacks are generally possible base DLEP,/<br>
     /Similar attacks are generally possible in base DLEP,/<br>
    <br>
    <br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">
Thanks!
I've pushed changes to <a class="moz-txt-link-freetext" href="https://github.com/louberger/dlep-extensions">https://github.com/louberger/dlep-extensions</a> and
will coordinate an update with the AD.
Lou</pre>
    </blockquote>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <blockquote type="cite"
      cite="mid:8b06996c-a16f-cf33-2c78-8a4733522ac6@labn.net">
      <pre class="moz-quote-pre" wrap="">
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">

_______________________________________________
manet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/manet">https://www.ietf.org/mailman/listinfo/manet</a>

</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------29CF8890E9EEAF14027AC68A--

