Re: [lisp] LISP PubSub to Proposed Standard?

Dino Farinacci <farinacci@gmail.com> Sun, 06 November 2022 12:57 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 4B093C14CF1D for <lisp@ietfa.amsl.com>; Sun, 6 Nov 2022 04:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 CPkwARO4Yklp for <lisp@ietfa.amsl.com>; Sun, 6 Nov 2022 04:57:53 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 D85C5C14F746 for <lisp@ietf.org>; Sun, 6 Nov 2022 04:57:53 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id i9so5805468qki.10 for <lisp@ietf.org>; Sun, 06 Nov 2022 04:57:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=vfYU3Ohs2WN9MTkcLmZg9oeGImRHNQiLTl56afC44QE=; b=lJSL79yISWi9vV16CwGx5TtOD39wsA+We5MozCMj/9qa2m9O3CsXYyvpLuUfEk/G97 UBCgOJewRkKNaNE7+WpNOlPK5gMIC28jJ4TFJN/jpXDfRIURgY2VG8tZ39Jc2mLFeUY1 olAKdmuNrEJM52gFtAUedm/FDwtlhJtW2OsQJsZzwN6flYJmVnTU74NNDjzNJ0lBGb45 ollQyeY+nM5itnpibbMRPJX4fZoVGoiYf8bvSC7BgpKtq7fmFVUWgX4lOFPfTFhy0Bpm SCjAw79fs9p3nXXoeGPtixXUsULY1X98nXETYNGkubv6drqk0N9T68R6fVHn9NHUdlmh FV/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=vfYU3Ohs2WN9MTkcLmZg9oeGImRHNQiLTl56afC44QE=; b=0plcVCKw9Q48CiwYJcDl90WSiajBygs7NyM4pU2st/2L8bOQzprwHJ89VFq5oq6iNe zYJbWGE1Gkjp1kp3csmEwN72UrHFepEKv1siOy2J8j9lXBPQjBgzifz2y2siN7/RrY0d oA6MPJD7suZ07zdLU+qfXhI9/kEg3OasKHDX94/5Fi6vwe4FDqD1LpFsXVFpdb2htZJr /iTK9yV6S5eyXXrjSi9Jr2382rlhBM2MtNKAVPEVgU0SY5XlIsesS1d0DOd1kCv+M7Q7 CLvUris8lT4EKNidkZtN5LfLkRKS0atOpkBX4IIDbC3XiY4kxcYnI/Tl+Nt3ruFV2BuX ZuQg==
X-Gm-Message-State: ACrzQf0OzzEeqlbZ1nwQ7j2Ve9pVc9m/SE7hFFwGnGLBM9exuwLnjcR6 0HM7HoMRdm8mDEcYL8MUvhLVZsCwgU4=
X-Google-Smtp-Source: AMsMyM5H6QSvkcGi/ymORYfVQyyh0rh3aeDO/6nNWy6OIjeN3Q/SnVTlb9JkjyMcqYDa5EA2ljGJcQ==
X-Received: by 2002:a37:5803:0:b0:6ee:834c:b605 with SMTP id m3-20020a375803000000b006ee834cb605mr31902858qkb.643.1667739472615; Sun, 06 Nov 2022 04:57:52 -0800 (PST)
Received: from smtpclient.apple ([2600:381:491e:4bf4:796d:3456:75fc:1557]) by smtp.gmail.com with ESMTPSA id bk42-20020a05620a1a2a00b006fa4b111c76sm4399097qkb.36.2022.11.06.04.57.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 06 Nov 2022 04:57:52 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Dino Farinacci <farinacci@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 06 Nov 2022 12:57:36 +0000
Message-Id: <B42CB591-2F39-41E6-82BE-A29E13CD1053@gmail.com>
References: <BN8PR11MB3588AFF6D1B8F86A1909FD94B63D9@BN8PR11MB3588.namprd11.prod.outlook.com>
Cc: lisp@ietf.org
In-Reply-To: <BN8PR11MB3588AFF6D1B8F86A1909FD94B63D9@BN8PR11MB3588.namprd11.prod.outlook.com>
To: "Alberto Rodriguez-Natal (natal)" <natal=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (20A380)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/4mzMB2eyNjJ4iPtk4-mhNdLX6tg>
Subject: Re: [lisp] LISP PubSub to Proposed Standard?
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: Sun, 06 Nov 2022 12:57:54 -0000


> On Nov 6, 2022, at 12:27 PM, Alberto Rodriguez-Natal (natal) <natal=40cisco.com@dmarc.ietf.org> wrote:
> 
> On the meantime, what is the view of the WG on moving the document to Proposed Standard?

I think it is critical to carry this fundamental solution as Proposed Standard. We have struggled for years keeping mappings up to date on proxy-ITRs. 

Pubsub provides an event triggered solution which I believe is fundamental functionality the architecture needs. 

Dino