Re: [lisp] Supporting lisp-geo [Was: Re: lisp - Requested session has been scheduled for IETF 115]

Sharon Barkai <sharon.barkai@getnexar.com> Thu, 03 November 2022 10:18 UTC

Return-Path: <sharon.barkai@getnexar.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 8F57FC1524C7 for <lisp@ietfa.amsl.com>; Thu, 3 Nov 2022 03:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=getnexar.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 q2vhr7x7MJNl for <lisp@ietfa.amsl.com>; Thu, 3 Nov 2022 03:18:37 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (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 A098BC14F73B for <lisp@ietf.org>; Thu, 3 Nov 2022 03:18:37 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id j15so2040181wrq.3 for <lisp@ietf.org>; Thu, 03 Nov 2022 03:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getnexar.com; s=google; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=30u4a6xN0p7BrIiDUODPz/M3W9PRfP0hEBG5l2fb58A=; b=X0+TYGb8VzGVGK34kqyV6hV/Ij/E2YmbyH6qk5twocjiz81c7hQRgcUkj+ikWordDL OzZojkbZX/ijp90EGfZX1B0gfwKTAyZOb9t6ll4adOW0fQkC2v9fyXn8c2p3Ap1Tjeyz 1lkkZogYy8kPWpk7bsidx4aYhDG9iX8JRUy0c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=30u4a6xN0p7BrIiDUODPz/M3W9PRfP0hEBG5l2fb58A=; b=RctfM6nWTI0w+gUXDw+J4hY2zHzOBQWqAGBEm7qr4oL/yXRKN6mB2Oilr3kuogxDdx D5PFzzGO2/qrWkSl3YnvVr2+au46DJVwvK9JcCVp/bv1EfUVliZ6U8xG3HaAGevjW7dr r9CjHyLl0FxrZ+gUrzVU4CA6ZDmPcgJKWneeB482Hsuk8GngGuqv7XXjkfnVmTtzDBcp rPzOlLZfkXtXTT15Y4J1ujbA1XBiGuxZUvktmuvIjX/cPLMy4OoCpSjkhIVW5hAFFEk6 obH6yykbXi+D2wKy3PANEwT0dqLd5/RMYX0WD4x80SbC1pNeaNiu8SOemZRY5gMHmtI7 zJWg==
X-Gm-Message-State: ACrzQf1uJaCHwcfMPnoSMbIemgpLdvW+LQHKLU/ZluvjAE2cB5ytvIM5 W222RLwaS5TsTWdiq6oeBG5KLQ==
X-Google-Smtp-Source: AMsMyM6jJlVEb99c4V4PmhnoL0W7Z4nivae8Pm4A5vV2cwH79g8XoN/dE7Y/4MheQKzIIEfU6sC6WA==
X-Received: by 2002:adf:f989:0:b0:236:5730:62f1 with SMTP id f9-20020adff989000000b00236573062f1mr18020649wrr.98.1667470715997; Thu, 03 Nov 2022 03:18:35 -0700 (PDT)
Received: from smtpclient.apple ([46.120.74.177]) by smtp.gmail.com with ESMTPSA id k16-20020a5d6e90000000b002366d1cc198sm445963wrz.41.2022.11.03.03.18.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 03 Nov 2022 03:18:35 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Sharon Barkai <sharon.barkai@getnexar.com>
In-Reply-To: <5B4B1037-5DFE-4944-81F1-6F8AC0624D8C@cisco.com>
Date: Thu, 03 Nov 2022 12:18:33 +0200
Cc: Dino Farinacci <farinacci@gmail.com>, lisp-chairs@ietf.org, lisp@ietf.org
Message-Id: <0AA53AAC-419F-456B-8D88-AD81A1910FD6@getnexar.com>
References: <5B4B1037-5DFE-4944-81F1-6F8AC0624D8C@cisco.com>
To: "Fabio Maino (fmaino)" <fmaino=40cisco.com@dmarc.ietf.org>
X-Mailer: iPhone Mail (20A380)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/hPOl8GpJ-NWzH0TWeGEMS9mTNMs>
Subject: Re: [lisp] Supporting lisp-geo [Was: Re: lisp - Requested session has been scheduled for IETF 115]
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: Thu, 03 Nov 2022 10:18:41 -0000

I agree Fabio, it is well written!

However, if it will become at some point acceptable to submit drafts in bullets, along with masks and headers, and flow diagrams (still pure currier) ,  it will make life a lot easier for non native english speakers :)

--szb
Cell: +972.53.2470068
WhatsApp: +1.650.492.0794

> On Nov 3, 2022, at 00:45, Fabio Maino (fmaino) <fmaino=40cisco.com@dmarc.ietf.org> wrote:
> 
> Chairs, 
> I would like to support Dino's request for WG adoption of https://datatracker.ietf.org/doc/draft-farinacci-lisp-geo/. 
> 
> It's a well written document that defines the Geo-coordinate LCAF type. The draft brings up a couple of good use cases that illustrates how the LCAF type would be used. 
> 
> It's a fairly simple document, and I can't think of anything that I would do differently. I'm also supportive of getting this to last call as soon as IETF procedure allows. 
> 
> Thanks,
> Fabio 
> 
> On 10/15/22, 10:37 AM, "lisp on behalf of Dino Farinacci" <lisp-bounces@ietf.org on behalf of farinacci@gmail.com> wrote:
> 
>    And I would like to request WG document for draft-farinacci-lisp-geo again. It has been around for a long time and has an LCAF encoding code point in RFC 8060. I can present this draft too in London. 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp