Re: [lisp] The LISP WG has placed draft-farinacci-lisp-decent in state "Call For Adoption By WG Issued"

Joel Halpern <jmh@joelhalpern.com> Mon, 16 October 2023 19:39 UTC

Return-Path: <jmh@joelhalpern.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 45FBAC14CF12; Mon, 16 Oct 2023 12:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZb3hQIkCOeD; Mon, 16 Oct 2023 12:38:58 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F521C14CF0D; Mon, 16 Oct 2023 12:38:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4S8S8x68FBz6G9rq; Mon, 16 Oct 2023 12:38:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1697485137; bh=tYCG8Gky3aSyNBNZ5ykqamjDgaR0vmuI4Nm+bGbgOPQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=YILzlxC0mi7p0gFLUAfbh0BJP2JBjBjP72t7/T++0pGK3HhxuZT8yQ0Wd9VICe57N IIC48Il6RN0Fwhoz12eEmAN0EbrHwVnB21xwhnGU3cFw7kvrTAfVJIfcP21Djwj1FP +i15p2jUV/mUTudpdT13cj6zO9c3Cr8OHKIU8NOo=
X-Quarantine-ID: <kK6rFltDIYDe>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.150] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4S8S8x1N2Mz6G8n4; Mon, 16 Oct 2023 12:38:55 -0700 (PDT)
Message-ID: <ad0457d4-3ebf-58d5-973e-afaee7c8c8bd@joelhalpern.com>
Date: Mon, 16 Oct 2023 15:38:54 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: Dino Farinacci <farinacci@gmail.com>
Cc: draft-farinacci-lisp-decent@ietf.org, lisp@ietf.org
References: <169746361027.17411.9865901417665447137@ietfa.amsl.com> <dbfff200-f976-e89f-925e-97b62e62f0ec@joelhalpern.com> <7D7EBC48-1CFE-4459-96C4-029FA104040B@gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <7D7EBC48-1CFE-4459-96C4-029FA104040B@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/iy65NzVucJ6eNv1LOb_tae9z-Rg>
Subject: Re: [lisp] The LISP WG has placed draft-farinacci-lisp-decent in state "Call For Adoption By WG Issued"
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 16 Oct 2023 19:39:02 -0000

To point to one example of the problem, this draft defines "push based" 
as using multicast.  Decent uses multicast.  But not all push based 
systems use multicast.  The definitions of push-based and pull-based 
should be general.  Decent-pulll and decent-push (or some other terms) 
can be defined as this document uses them.

Yours,

Joel

On 10/16/2023 3:36 PM, Dino Farinacci wrote:
>> Relative to the LISP mapping system, the terms pull-based and push-based long predate this draft.  There was an original push-based mapping system proposed (in which all mappings were pushed to all ITRs).  While we decided not to advance that,
> Right, the LISP-Decent pushed-based uses multicast. The other one, NERD, used management protocols and not a control plane if I recall.
>
>> the term had an understood meaning.  Also, pull-based and push-based have well-defined meaning in many contexts.  This draft
> The pull-based is what all the mapping systems are using. For LISP-Decent we wanted to distinguish the pull-based mechanism based on hashing from the push-base multicast method.
>
>> seems to use those terms in a rather idiosyncratic (not incorrect, but confusing) fashion.  I am not sure whether different terms or additional qualifiers are the better solution.
> Did I make it clearer?
>
> Dino
>
>> Yours,
>>
>> Joel
>>
>> On 10/16/2023 9:40 AM, IETF Secretariat wrote:
>>> The LISP WG has placed draft-farinacci-lisp-decent in state
>>> Call For Adoption By WG Issued (entered by Luigi Iannone)
>>>
>>> The document is available at
>>> https://datatracker.ietf.org/doc/draft-farinacci-lisp-decent/
>>>
>>>
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp