Re: [lisp] AD Review of draft-ietf-lisp-pubsub-09

Dino Farinacci <farinacci@gmail.com> Sun, 06 November 2022 14:39 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 60919C14F73A; Sun, 6 Nov 2022 06:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
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, 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] 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 LpwyF7rJRPkD; Sun, 6 Nov 2022 06:39:17 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 EEFE6C14F72B; Sun, 6 Nov 2022 06:39:16 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id a11-20020a05600c2d4b00b003cf6f5fd9f1so5784007wmg.2; Sun, 06 Nov 2022 06:39:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; 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=eT8/jsjCNfvwEFqkjXUEs+Y+mmoW4N1j2ytbcJjzoV0=; b=IhHFcVDBPY66KvRWxvEk/oR1pr9N12/0qB335i72fjH+1O+6jl6OfffHNkSdebBM7L NUwvwfCjzhyy6ocv2onHI9gRfNBDKqEiXTRqPhtFmS1PsV0eb7844UEOTNKJe4SdbX7h Pw6zRxyzhluB6aszRnQLKLYF97bRtrAF7cvAGqC4Bw98APQ6PsGY/IGc2fWcSrN7RF1E SG3wX5V90DQ205GczYNHpxZgfbQFSMmleGElKDqhpLUDsVOAf9v8MtQru7HrQ9TB/VHL CI58NsKVPdJ/o5vEojfQxtDJxTl2q46z9sYfKjm3y3+JkEf+GaFZ5EL82depS/mkGn1y +Vbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=eT8/jsjCNfvwEFqkjXUEs+Y+mmoW4N1j2ytbcJjzoV0=; b=WU2GNTLCgDGHPJ9pd1OiB4gfI36Di7H+YvxILy3TYMuxLOzYvfVscT5SOhkd6jKb3S TlQ8aaCPjTcRoD3P+KQO73BBhx7m7QbsUvw0aqURxGr9d5+WAtHTzkpHU445QCRnNs9G PjI0R8xxQy9FHcZ1THNNxBJt8zmb8RjZiX19Vz1UeXGhrBDQKi83Z7ZAxQFUzKNOL8zz 4WdeJ+ptb/1H9b6bzCdNWt8kU3ZYupLFLH6Ed4O9y3dvEyvdwelo9C+mhzU+Y3IKou76 FhNMxUKnQq1INaIz8mW7K1pPa5t2LG06kCEZAvN5vsMXx/VUUY4Biwpldk2bq8NVZay+ Lfhw==
X-Gm-Message-State: ACrzQf0mMTQnh+y9mT6pw2e2NAweQr1mv9JI2UsG8tbtWV79eg715vSq 0zvs1MfSJqm40EGIfd41XGw=
X-Google-Smtp-Source: AMsMyM6wUOoWAQ44Kx3be2jhgrEv2G/I/bAq+YWWYD3e6KOY5gJ5mx+U3b+UNpsB6vn2jXF37dMA7g==
X-Received: by 2002:a7b:cc8c:0:b0:3cf:7b8c:d18a with SMTP id p12-20020a7bcc8c000000b003cf7b8cd18amr22035974wma.0.1667745555127; Sun, 06 Nov 2022 06:39:15 -0800 (PST)
Received: from smtpclient.apple ([2001:67c:1232:144:1c38:d33e:5028:2a50]) by smtp.gmail.com with ESMTPSA id n14-20020adfe34e000000b002366ded5864sm4792978wrj.116.2022.11.06.06.39.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Nov 2022 06:39:14 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <BN8PR11MB3588A92BEE89699E39F6503DB63D9@BN8PR11MB3588.namprd11.prod.outlook.com>
Date: Sun, 06 Nov 2022 14:39:11 +0000
Cc: Alvaro Retana <aretana.ietf@gmail.com>, "lisp@ietf.org" <lisp@ietf.org>, Luigi Iannone <ggx@gigix.net>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>, Vina Ermagan <ermagan@gmail.com>, Stefano Secci <stefano.secci@cnam.fr>, Fabio Maino <fmaino@cisco.com>, Sharon Barkai <sharon.barkai@getnexar.com>, Albert Cabellos <acabello@ac.upc.edu>, Johnson Leong <johnsonleong@gmail.com>, JACQUENET Christian INNOV/NET <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <56A80E47-C7E5-4939-B04F-900203103E2D@gmail.com>
References: <CAMMESsyB6WXxZP-CxQ6xzYQ6rRC86TQPT+PDqc3+qvR364qdCw@mail.gmail.com> <BYAPR11MB3591E2378CCEA32D8697F002B62E9@BYAPR11MB3591.namprd11.prod.outlook.com> <BN8PR11MB3588A92BEE89699E39F6503DB63D9@BN8PR11MB3588.namprd11.prod.outlook.com>
To: "Alberto Rodriguez-Natal (natal)" <natal@cisco.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/eP6G241TGiSA7mbKj78kq-Z-BVo>
Subject: Re: [lisp] AD Review of draft-ietf-lisp-pubsub-09
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 14:39:22 -0000

> [AR] As mentioned in the Alvaro/Dino discussion, regular Map-Notifies as per 9301 are sent to the source IP address of the Map-Register that triggered them. Since PubSub extends LISP to specify that Map-Notifies can also be triggered by Map-Requests, we need to specify where these Map-Request-triggered Map-Notifies are sent to.

This isn't making sense to me. Are you talking about a Map-Notify as an ack to the Map-Register or an unsolicited Map-Notify and if the latter, the notification is going to the source address of the LAST subscription request. And if another Map-Request came later with the N-bit set again, with a new/different source IP address, the map-server must cache the last address (and later send Map-Notify to this new address).

Agree?

Dino