Re: [manet] DLEP LID lengths

Rick Taylor <rick@tropicalstormsoftware.com> Mon, 19 June 2017 15:53 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 EE803131546 for <manet@ietfa.amsl.com>; Mon, 19 Jun 2017 08:53:50 -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, RP_MATCHES_RCVD=-0.001, 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 Np9LuLKDYAgf for <manet@ietfa.amsl.com>; Mon, 19 Jun 2017 08:53:49 -0700 (PDT)
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 672F1131548 for <manet@ietf.org>; Mon, 19 Jun 2017 08:53:39 -0700 (PDT)
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, 19 Jun 2017 16:53:14 +0100
From: Rick Taylor <rick@tropicalstormsoftware.com>
To: "ratliffstan@gmail.com" <ratliffstan@gmail.com>
CC: "kmorga07@harris.com" <kmorga07@harris.com>, "manet@ietf.org" <manet@ietf.org>
Thread-Topic: [manet] DLEP LID lengths
Thread-Index: AQHS6Qc8XDbHi2PNfkeVCwyLbnKMmqIsL14AgAAWIQA=
Date: Mon, 19 Jun 2017 15:53:14 +0000
Message-ID: <1497887594.2674.56.camel@tropicalstormsoftware.com>
References: <63448cdd41fa4c94a44a390dd10848a1@MLBXCH18.cs.myharris.net> <1496242619.3129.19.camel@tropicalstormsoftware.com> <61e159c5594246d8afa42b5ee5cda557@MLBXCH18.cs.myharris.net> <CALtoyonckmMUzLJtR=R5tw5TJNCi=2DXxXmvb+hugARmkOeQ9g@mail.gmail.com> <1496664069.3788.31.camel@tropicalstormsoftware.com> <CALtoyokHwgnoR19Zw_BKDbhaRpx2bzguwZawwngzro4Qf6=3=Q@mail.gmail.com> <1496676769.3788.60.camel@tropicalstormsoftware.com> <CALtoyokRc0EWLP7D3RyfcZ57WTbTvsGXUPiSnrYMgBaYTTVvFA@mail.gmail.com> <1497882042.2674.34.camel@tropicalstormsoftware.com> <CALtoyomskw-WUEuRE-Zy+9tKvChbJaf--M4hhyHY_fdjWLp+mQ@mail.gmail.com>
In-Reply-To: <CALtoyomskw-WUEuRE-Zy+9tKvChbJaf--M4hhyHY_fdjWLp+mQ@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: <3482f2d3-d706-4741-9fdd-15d56b2d5b8c>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/manet/vQ12IIjf760LFpI6sZw8xeE4GWQ>
Subject: Re: [manet] DLEP LID lengths
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, 19 Jun 2017 15:53:51 -0000

Comments inline...

On Mon, 2017-06-19 at 10:34 -0400, Stan Ratliff wrote:
> 
> 
> On Mon, Jun 19, 2017 at 10:20 AM, Rick Taylor <rick@tropicalstormsoft
> ware.com> wrote:
> > All,
> > 
> > I've been mulling this over.
> > 
> > How about the LID length MUST be the same as the MAC, so it's up to
> > the
> > advertiser of the LID to bit pack?
> Does that mean that if a modem is using EUI-64 MACs, then the LIDs
> are 64 bits as well? I'm OK with that, I just think we need to state
> it. 

Yes, that's the idea.  A draft-01 will be forthcoming...


> Also, I think there should be a sentence about LIDs not being
> duplicated (and, in fact, that a LID MUST NOT duplicate an existing
> MAC, or vice-versa). I'd think that a duplicate LID on Destination Up
> would be rejected, and the Destination would not be seen as Up
> (Destination-level error, NOT a peer session level error).

I'm not sure about this.  I can see why it seems helpful:
an implementation can keep one data structure for all destinations,
physical/logical/LID.  But, I can't see a simple way for a dual-mode
modem implementation to ensure no clashes.

Part of the reasons behind LIDs was to produce a separate namespace.
Forcing and implementation to maintain 2 datastructures (of the same
type) for the two namespaces seems little extra effort (again, ignoring
ADA implementations).

>  
> > 
> > This seems to work with existing use cases, and avoids the need for
> > LID
> > length negotiation.  The only down-side I can see is that 2^48 LIDs
> > is
> > a common maximum, but that seems plenty currently.
> Yeah, I'm thinking that 1 modem supporting 2^48 links will cause
> insanity well before DLEP has a problem... ;-)

As was pointed out to me: 640Kbytes has traditionally been plenty, 2^48
looks like carelessness! :-)

Cheers,

Rick