Re: [lisp] Request for WG document - draft-farinacci-lisp-name-encoding

Dino Farinacci <farinacci@gmail.com> Fri, 02 October 2020 18:44 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87D713A1699 for <lisp@ietfa.amsl.com>; Fri, 2 Oct 2020 11:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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] 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 6gfbpn1WwtPE for <lisp@ietfa.amsl.com>; Fri, 2 Oct 2020 11:44:46 -0700 (PDT)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 4AE073A1698 for <lisp@ietf.org>; Fri, 2 Oct 2020 11:44:46 -0700 (PDT)
Received: by mail-pj1-x1036.google.com with SMTP id gm14so1413497pjb.2 for <lisp@ietf.org>; Fri, 02 Oct 2020 11:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=w2MqOovyv+9AL3VhDRTjE4uRjKbt7GZJ9+aiEYA9rBM=; b=Vs4L4WlGx6/C8qHJ0vVe00pUBYGyVE8OXRRr2u74PEybQlKkQ4XOC7oXI11pjknA9w Ty9d5nVebVZn07uZ2WjTz26hrliU4+8KkRrJEYFiLKtuQhAjA0YgrL/K5lxX4xTSEZvx p7/wEnmuh0QO0qfpoRtO0K+6wyW1lNj9aHUPi69Y7vd4pIy+eOApoQCrJ2VuoX9jYRmB K8Py8cLrExWq47/WwV7KjmOYRSXmZuST2u1ZJIyTAu3Asy10srysVKS8j4MSO7oj5bzX Xq5ZHWPsSs//Z1dJgzKhyhTLJ8UsRdrbN/colKIscjSfycxnl4er17xcA4lG16OpZ2PE ua8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=w2MqOovyv+9AL3VhDRTjE4uRjKbt7GZJ9+aiEYA9rBM=; b=axu39rNgRcUmRwdjVagKUglKHTTn/Es45aesGEDg6lW1L4h4ZQTE7XIJK33KD6PHPl I9n1XXoflKDJFioocbTLSPunn5BsADPGqpht5nj7Uv9DrtV86xvOEoI9QxqzBoMPb5Sj tNjON0VmuJ1p+g9vO063t/rubyG6wJl2TlPBQ/PYEYR/E2+V77yy+yucYs3hsnGWatXw 1i9jNx5lSmpFtwShVnY/E8Ycl3dwtEaKJBQMYJmOC+xpXkOKU+AEGAAICc4R9bJdmeRT jeAUZ7AYsLHMEG1Rov14+NIXCdBpqO93r7fVQmTVawXFt7ugMo2SUSs8LX0HQhtRy45K d0NQ==
X-Gm-Message-State: AOAM531CLnIakFgFSRQ1Ms41i7+Squ3suZAY7wsDpjaHtJi8v1M0rMQy r0HU0jsiNvMAwNeW5F8/O2tW755xHf9TRg==
X-Google-Smtp-Source: ABdhPJw8/Zlox70M4bwKUiZWmtSXMe9+VifsnExZKfkc1wurAqKepu1zi+JGzOYzuzmNvoXJqLo9zQ==
X-Received: by 2002:a17:90b:4b8e:: with SMTP id lr14mr4308516pjb.100.1601664285637; Fri, 02 Oct 2020 11:44:45 -0700 (PDT)
Received: from ?IPv6:2601:646:9600:af10:38a8:c2c2:4a71:75aa? ([2601:646:9600:af10:38a8:c2c2:4a71:75aa]) by smtp.gmail.com with ESMTPSA id ie13sm2300033pjb.5.2020.10.02.11.44.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Oct 2020 11:44:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <e7846f3b-dcba-86d9-34d9-9f8cde40fb2e@joelhalpern.com>
Date: Fri, 02 Oct 2020 11:44:43 -0700
Cc: Luigi Iannone <ggx@gigix.net>, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1090FD8-0CBB-49F6-9EAB-9A19A8A20759@gmail.com>
References: <921b82e9-ea40-bab9-eb3e-809375528741@joelhalpern.com> <88FFF16F-1E5F-4B41-B4A1-D3E02750F9BA@gmail.com> <18C66CDF-7714-4258-9D0C-EF4E5CEBC438@gigix.net> <C85A0223-83A1-498B-A3BD-C878E73CB462@gmail.com> <c2bd4ac3-7e14-c127-e563-d6018e54d70d@joelhalpern.com> <115B0A44-F292-49E5-A7EB-B2B6B72FB00D@gmail.com> <0c3ed7ea-be05-805d-7cdd-57f7d0aaeb23@joelhalpern.com> <DCC98356-7341-4FDC-8479-0E0126E4224B@gmail.com> <e7846f3b-dcba-86d9-34d9-9f8cde40fb2e@joelhalpern.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/DP9cdaHbv8nqAFRD0-LaeSxBIvs>
Subject: Re: [lisp] Request for WG document - draft-farinacci-lisp-name-encoding
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2020 18:44:48 -0000

> The design of LISP explicitly separates the Mapping system from the Itr/EtR.  Which means that the "IT Manager configuring xTRs) does not get to define how the mapping system works.

Right, agree, and I didn't say that.

> And if there are undefined variations in how it works for AFI=17, then we have not achieved interoperability.

There isn't. It works exactly like an IPv4 or IPv6 lookup.

> And if there are potential interactions between different uses of AFI=17, then we again have a problem.

There isn't for a given use-case within a given instance-ID. Just like VLANs, VRFs, etc. We are not inventing anything new here. We solely want to encode ascii strings. 

> If you want to define that AFI-17 is always and only used along with instance-ID, then you solve PART of the problem.  But not all 

Its an EID encoding that can or not go inside an Instance-ID LCAF. And when used as an RLOC, there is no instance-ID relationship.

> of it.  If different uses of the AFI clash, then we are creating problems even for a single adminstration using it under a single instance.

IP addresses can clash. We use the same rules for avoiding IP EID clashes as AFI=17 clashes. I mentioned this already in a previous email to you.

> And from where I sit, the LISP working group is not chartered to provide a generic string based key-value store.

Look at it this way. Should the IS-IS working group not create hostnames to map LSPIDs to names? Allowing this makes it infinitely simpler to manage the system. 

This proposal is extremely popular. Ask network operators about IS-IS hostnames. This is the same thing. It really is.

Dino