Re: [Int-area] Continuing the addressing discussion: what is an address anyway?

Dino Farinacci <> Mon, 07 March 2022 23:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6B5DF3A118D for <>; Mon, 7 Mar 2022 15:09:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Nj9Z0TIFNlUK for <>; Mon, 7 Mar 2022 15:09:10 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0DD053A1446 for <>; Mon, 7 Mar 2022 15:08:48 -0800 (PST)
Received: by with SMTP id z11so15399895pla.7 for <>; Mon, 07 Mar 2022 15:08:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fkGSr+VFNmlo8eS5UbSrcI64hyHAhvCViQhy6GTR8jI=; b=fHgYAuX9bVmC7bYBT+MOvqr8Am2WsekOMfHqbQe80Sap9qQXR3v1Fy8azfChPLEbc5 m26E+S44vj7CWZZQ6Fg7zTcKG9dY7bLhfPlxGQ250jTZ5yVTmPz4WshkAYkYpDDfgIZA 0Z9SPYsUYEG3e0j/3TcawJPkMQ5AjQXgP8oPBXL9nb391ncSFquqkkHj0Xi1I1nd2Yha 1a+QPGOk5Db+8U8O5GeNtMQDmBE1+hzC6VDTwhGfClU/tTV/h/kDwh40PWnB08tcun7L L1Ig8XDlrIYGcKxQzABP/tAvYmamjvIGNA33Ya5dG8vf3Nyttbk2mzIMYZpmX0fPI6rI qPow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=fkGSr+VFNmlo8eS5UbSrcI64hyHAhvCViQhy6GTR8jI=; b=xBtccXhuCVKK5rcFQ9sQgmahTI0GvKra3F140WnYQH6csoti0D3nEfoq4Gl/SJxlWr zm1j7b58gkG1G6BKCGBcvDrCN9AVy6XiaPEycXelfdkeRLS+FctYvonDlNARkLGtpWHJ vxtpRX4vdurCsZVe5BATincfgW3Mq6zT4D5gFWzhPqJL+1bxR6uIS7xZ9vdv7DduPb3x pLNfvlrP1f8qm0fNIOg5Y3urRHsjwceIg4kltCZoHM3lyD3w7kdEauW4j0+RkplMuAo1 nvaiWiz+EBpfcs1YVKEXF9Ol/+ByliTMWYtqfMH7FBeP+Lns3pw09SA0ky+jJ/2DKvDh NNSQ==
X-Gm-Message-State: AOAM530XLXg/CuNdu+fnOSH7CkuioNeQ/MSFVWw9enF+6dwsBf4DoQck EwdEKYAjLloOyvMp6TSpbmI=
X-Google-Smtp-Source: ABdhPJxVsAp2BOKXwDscAbHfSkPt/7pO1kZ2sWYGGz9iJWjxo1aAQHMVosFQYCWLzhP8UlKFMoPVMA==
X-Received: by 2002:a17:902:be14:b0:14f:ce67:d0a1 with SMTP id r20-20020a170902be1400b0014fce67d0a1mr14347227pls.29.1646694527238; Mon, 07 Mar 2022 15:08:47 -0800 (PST)
Received: from ( []) by with ESMTPSA id 124-20020a620582000000b004dee0e77128sm16295557pff.166.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Mar 2022 15:08:46 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
From: Dino Farinacci <>
In-Reply-To: <>
Date: Mon, 07 Mar 2022 15:08:45 -0800
Cc: Antoine FRESSANCOURT <>, Toerless Eckert <>, "" <>, Dirk Trossen <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <Yh5M18z2/> <> <> <> <> <> <> <> <>
To: Jens Finkhaeuser <>
X-Mailer: Apple Mail (2.3693.
Archived-At: <>
Subject: Re: [Int-area] Continuing the addressing discussion: what is an address anyway?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 Mar 2022 23:09:16 -0000

> On Mar 7, 2022, at 4:18 AM, Jens Finkhaeuser <> wrote:
> Different sections of the draft claim different things; some claim EIDs never change, others talk about multiple EIDs used in different scenarios. I find section 5.1 interesting: "It is anticipated that these EIDs will change infrequently if at all, since the assignment of a LISP-MN's EID is envisioned to be a subscription time event."
> Subscription is an undefined term that also appears in LISP+ALT. In the context of drones (not to bombard you with terminology from that area), one could imagine that subscription occurs when loading a mission plan onto a drone prior to departure. But by definition, this then only entails anticipated scenarios, not emergency response situations.

"Subscription time" means the mobile-node manufacture assigns an EID like it would a IMEI. Then it never changes.

> A completely static drone identifier is one thing; EIDs changing rarely is another. Drones may require communications with isolated, private networks, which are outside the scope of LISP+ALT - how subscription should be interpreted here is an interesting topic!

EIDs need to be unique *within* a mapping system. So you can have multiple mapping systems that use, say (for IPv4 EIDs), for static assignment, where the low-order 3 bytes is a random number generated and verify from the mapping system the node uses to be unique.