Re: [manet] I-D Action: draft-ietf-manet-dlep-lid-extension-01.txt

Rick Taylor <rick@tropicalstormsoftware.com> Mon, 05 February 2018 13:14 UTC

Return-Path: <rick@tropicalstormsoftware.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 B15DF126BF3 for <manet@ietfa.amsl.com>; Mon, 5 Feb 2018 05:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 RmRVYkYB_G4U for <manet@ietfa.amsl.com>; Mon, 5 Feb 2018 05:14:32 -0800 (PST)
Received: from mail.tropicalstormsoftware.com (mail.tropicalstormsoftware.com [188.94.42.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4262124B17 for <manet@ietf.org>; Mon, 5 Feb 2018 05:14:31 -0800 (PST)
Received: from tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d]) by tss-server1.home.tropicalstormsoftware.com ([fe80::753b:fa82:5c0:af0d%10]) with mapi; Mon, 5 Feb 2018 13:14:24 +0000
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "hrogge@gmail.com" <hrogge@gmail.com>
CC: "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] I-D Action: draft-ietf-manet-dlep-lid-extension-01.txt
Thread-Index: AQHTmdOgPD5qpa5rD0Sntsrb0M70f6OVnO8AgAAgG4CAAAEtgIAAFJgA
Date: Mon, 05 Feb 2018 13:14:20 +0000
Message-ID: <1517836460.8344.6.camel@tropicalstormsoftware.com>
References: <151732120050.27516.9349844420176741896@ietfa.amsl.com> <CAGnRvuo0dXFdJcjvnbed216+Fu54sV2GYDQOP1hT+xuv3PpZWQ@mail.gmail.com> <1517831785.8344.5.camel@tropicalstormsoftware.com> <CAGnRvupu-79BaAW-2vuNnB5Bs_eCr9HaH-Je_CvLfvYo2WL-VA@mail.gmail.com>
In-Reply-To: <CAGnRvupu-79BaAW-2vuNnB5Bs_eCr9HaH-Je_CvLfvYo2WL-VA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-ID: <803c7493-dc50-4478-8bf5-c8fae5eee654>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/rDIZyU2TYMWf69n5TXxWk-Hj5cs>
Subject: Re: [manet] I-D Action: draft-ietf-manet-dlep-lid-extension-01.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: Mon, 05 Feb 2018 13:14:34 -0000

On Mon, 2018-02-05 at 13:00 +0100, Henning Rogge wrote:
> On Mon, Feb 5, 2018 at 12:56 PM, Rick Taylor
> <rick@tropicalstormsoftware.com> wrote:
> > Hi All,
> > 
> > On Mon, 2018-02-05 at 11:01 +0100, Henning Rogge wrote:
> > > Hi,
> > > 
> > > I think I like the new text two, its easy to read and introduce
> > > the
> > > new concept quickly.
> > 
> > Thank you (and Georg as well) very much!
> > 
> > > 
> > > The only thing I am concerned about is the "empty" flags field...
> > > do
> > > we already have an usecase for this?
> > 
> > I must admit, I copy and pasted the text from elsewhere, and then
> > realized I had no flags.
> > 
> > However, one possible flag could used to distinguish between Links
> > to
> > Destinations with an IP address (addressable destinations/ Layer 3
> > radio net) and Links to  Infrastructure (no IP address, just a
> > subnet).
> >  Although this extension doesn't need to differentiate, it might be
> > useful for the router to know the difference when used with other
> > extensions (hop control perhaps).
> 
> Wouldn't it be easier to look at the prefix length of the IP?
> 
> > > If not, we could remove it and introduce it (if necessary) in an
> > > extension... we could discover the existence of an (optional)
> > > flags
> > > field by comparing the length of the link-id TLV with the (known)
> > > value of the link-id-length TLV.
> > 
> > Yes, if a flags field was needed later, a 'Link Identifiers Flags'
> > extension could introduce it legitimately.
> 
> So what do you think, just drop the flags field?

I'm happy to drop them if no-one can think of a use for them.

Rick