Re: [manet] I-D Action: draft-ietf-manet-dlep-multi-hop-extension-04.txt

"Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu> Fri, 16 February 2018 21:34 UTC

Return-Path: <prvs=55852a50d5=david.wiggins@ll.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 09DD112D7F8; Fri, 16 Feb 2018 13:34:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 rXJ5g1DuLemP; Fri, 16 Feb 2018 13:34:50 -0800 (PST)
Received: from llmx2.ll.mit.edu (LLMX2.LL.MIT.EDU [129.55.12.48]) by ietfa.amsl.com (Postfix) with ESMTP id EB5D3124207; Fri, 16 Feb 2018 13:34:49 -0800 (PST)
Received: from LLE2K10-HUB01.mitll.ad.local (LLE2K10-HUB01.mitll.ad.local) by llmx2.ll.mit.edu (unknown) with ESMTP id w1GLYmRj003404; Fri, 16 Feb 2018 16:34:48 -0500
From: "Wiggins, David - 0665 - MITLL" <David.Wiggins@ll.mit.edu>
To: Lou Berger <lberger@labn.net>, "manet-chairs@ietf.org" <manet-chairs@ietf.org>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-dlep-multi-hop-extension-04.txt
Thread-Index: AQHTpzhBBHDz7z21eUSkqZjVoXqb3KOndxGAgAAD8ICAAGOqgP//rtOA
Date: Fri, 16 Feb 2018 21:34:47 +0000
Message-ID: <8B2FB185-4DEC-4C28-81D9-DB05A5139B81@ll.mit.edu>
References: <151879377285.5017.233118525184173608@ietfa.amsl.com> <15cbeb3f-aaab-1d40-4ace-75f1326ff63a@labn.net> <088A520C-39BC-4463-9C43-88B71F7A1DF7@ll.mit.edu> <e48b6fd6-cac6-cf00-c444-e5d11c498db1@labn.net>
In-Reply-To: <e48b6fd6-cac6-cf00-c444-e5d11c498db1@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [172.25.59.118]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3601643687_772145824"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-02-16_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1802160252
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/r9TV1Rd5XKbxx7QNr-j8F74xNqM>
Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-multi-hop-extension-04.txt
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.22
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, 16 Feb 2018 21:34:53 -0000

Yes, that's clearer to me.  Thanks!

David

On 2/16/18, 4:26 PM, "Lou Berger" <lberger@labn.net> wrote:

    Hi David,
    
    On 2/16/2018 3:28 PM, Wiggins, David - 0665 - MITLL wrote:
    > Thanks for updating this, Lou.
    >
    > I had a bit of trouble parsing this:
    > "Note that neither Destination Down or Update Message SHOULD NOT
    > be sent for the destination MAC address contained in the Link Characteristics
    > Response Message."
    Fair enough - it is hard to parse.
    How about
    OLD:
       ....  Note that other destinations can be
       impacted as a result of the change and such changes are reported in
       Destination Down and Destination Update Messages.  The modem MUST
       notify the router of each destination that is no longer reachable via
       a Destination Down Message. The modem MUST notify the router of any
       changes in Hop Counts via Destination Update Messages.  Note that
       neither Destination Down or Update Message SHOULD NOT be sent for the
       destination MAC address contained in the Link Characteristics
       Response Message.
    
    NEW:
       ...Note that other destinations can be
       impacted as a result of the change and such changes are reported in
       Destination Down and Destination Update Messages.  The modem MUST
       notify the router of each destination that is *not identified in the
       Link Characteristics Response Message and* is no longer reachable via a
       Destination Down Message.  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*.
    
    Changes are flagged with asterisks.
    
    Does this work?
    Lou
    
    
    > The double negative threw me... maybe just omit "neither"?
    >
    > Otherwise, looks good!
    >
    > David
    >
    > On 2/16/18, 10:15 AM, "manet on behalf of Lou Berger" <manet-bounces@ietf.org on behalf of lberger@labn.net> wrote:
    >
    >      Hi,
    >      
    >           I thought it would be good to publish this version which captures
    >      all LC comments and discussion to date.  Please review (diffs) and let
    >      us know if we missed anything or if you still would like to see any
    >      additional language changes?
    >      
    >      Chairs,
    >      
    >           What's the next step?  Is LC now closed?  What else would you like
    >      to see happen before publication request?
    >      
    >      Thanks,
    >      
    >      Lou
    >      
    >      
    >      On 2/16/2018 10:09 AM, internet-drafts@ietf.org wrote:
    >      > 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 Multi-Hop Forwarding Extension
    >      >          Authors         : Bow-Nan Cheng
    >      >                            Lou Berger
    >      > 	Filename        : draft-ietf-manet-dlep-multi-hop-extension-04.txt
    >      > 	Pages           : 10
    >      > 	Date            : 2018-02-16
    >      >
    >      > Abstract:
    >      >     This document defines an extension to the DLEP protocol 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-04
    >      > https://datatracker.ietf.org/doc/html/draft-ietf-manet-dlep-multi-hop-extension-04
    >      >
    >      > A diff from the previous version is available at:
    >      > https://www.ietf.org/rfcdiff?url2=draft-ietf-manet-dlep-multi-hop-extension-04
    >      >
    >      >
    >      > 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/
    >      >
    >      > _______________________________________________
    >      > manet mailing list
    >      > manet@ietf.org
    >      > https://www.ietf.org/mailman/listinfo/manet
    >      >
    >      
    >      _______________________________________________
    >      manet mailing list
    >      manet@ietf.org
    >      https://www.ietf.org/mailman/listinfo/manet
    >