IETF Logo Mail Archive

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

Dino Farinacci <farinacci@gmail.com> Mon, 16 October 2023 19:41 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 348EBC14CF0D; Mon, 16 Oct 2023 12:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 (2048-bit key) header.d=gmail.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 nBEFdIrkGQqY; Mon, 16 Oct 2023 12:41:15 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 6714DC14F5E0; Mon, 16 Oct 2023 12:41:15 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id d2e1a72fcca58-6ba172c5f3dso1708248b3a.0; Mon, 16 Oct 2023 12:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697485274; x=1698090074; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=MPW6LckqkER3SiqLEBtYh2m4khEzLFdhin9nmsFWih8=; b=YIxQ5vkztKTdFKwTfgvuvgVOH0q0Zx2qViQpXPcAb53NVq0I3ujuEbJH8+/Rkrk40M gO/mVPCEWswkAA1uHItmS68NWtxfj5TxvghxLwY6i/RgsAYOSm4esfuX6mFfZnnTkeQF ZTsqSlCr2vzihFo9uJDhThuK/YveeaYhVAgI5mIcclc1MhBlJmw++ChdnJMlI9qBWeIg RgMXvTzRo6cE0ajtnNaIwDep+ZM0hbFWUGHihthxorckrdf8O5iQ097sdcALIS2hk8zy exCQbfWvVNlkI9pKF5W3Aloo+kGJ56zS3rYp1o4q7aRRmX83qc83+jJjis871Pbmgw7Z sDCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697485274; x=1698090074; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=MPW6LckqkER3SiqLEBtYh2m4khEzLFdhin9nmsFWih8=; b=cpoBatM3RgsqxbHvMojDnTXB/cjvLVa0T9uqjwVvLJ5Q9/YgN2XlVpT8qdMGvzLHL9 msERBAkS8WiXZu87VmsEmwmepusNKjLOlnlafsKOdrnB7E8YTHMiMna4nk4PBySkY2DD a9wJIEgf8L0G771EN3UMVBMYlVDh8aZ5VhsQx2hKwyMYPhrFyiTgvzqeSCrZlwXV/XZ/ VNk+6tri997eOWwzPOVBtz8xS37KfdsHsVcXG+2xmdBTLO051fMjny3Qzvqd/zcZGlUy 4/MfxgGUyQV08zBtoHcXIqOia3wwvw/VzvJdr2SHDTddCL2eMbLZvWmDoi/iCxdwj0Ar 72Kw==
X-Gm-Message-State: AOJu0YyGcflx4f7zIDJ6kJJf2tpvvkZPg2JxicWpo7AHrykTAEh+IhzG 2lYn5W1RxtP/0cbzi6FdULAwhFvwm/Y=
X-Google-Smtp-Source: AGHT+IF6D+//m7l6hMcalhikWtsheUgb5fZpq52oTxcV6F3wqRSboi1zUfgJUCeA5EUMR73LMtfFYg==
X-Received: by 2002:a05:6a00:1511:b0:68f:f38d:f76c with SMTP id q17-20020a056a00151100b0068ff38df76cmr168820pfu.6.1697485274495; Mon, 16 Oct 2023 12:41:14 -0700 (PDT)
Received: from smtpclient.apple (c-24-5-184-219.hsd1.ca.comcast.net. [24.5.184.219]) by smtp.gmail.com with ESMTPSA id b18-20020aa78ed2000000b006900cb919b8sm288147pfr.53.2023.10.16.12.41.13 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Oct 2023 12:41:13 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <ad0457d4-3ebf-58d5-973e-afaee7c8c8bd@joelhalpern.com>
Date: Mon, 16 Oct 2023 12:41:02 -0700
Cc: draft-farinacci-lisp-decent@ietf.org, lisp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8243282A-FB5B-493F-B05D-515830E1A004@gmail.com>
References: <169746361027.17411.9865901417665447137@ietfa.amsl.com> <dbfff200-f976-e89f-925e-97b62e62f0ec@joelhalpern.com> <7D7EBC48-1CFE-4459-96C4-029FA104040B@gmail.com> <ad0457d4-3ebf-58d5-973e-afaee7c8c8bd@joelhalpern.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/p4BqKzpycGhBeq9b65hGvpRtJPY>
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:41:19 -0000

I can change the spec to be more specific as you suggest. Would that work for you?

Dino

> On Oct 16, 2023, at 12:38 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
> 
> 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

v2.23.0 | Report a Bug | By Email