Re: [lisp] Martin Duke's No Objection on charter-ietf-lisp-04-01: (with COMMENT)
Luigi Iannone <ggx@gigix.net> Tue, 28 November 2023 12:48 UTC
Return-Path: <ggx@gigix.net>
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 31180C151064 for <lisp@ietfa.amsl.com>; Tue, 28 Nov 2023 04:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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_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 (2048-bit key) header.d=gigix-net.20230601.gappssmtp.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 hFaQTpqLkEAY for <lisp@ietfa.amsl.com>; Tue, 28 Nov 2023 04:48:48 -0800 (PST)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 5E498C151065 for <lisp@ietf.org>; Tue, 28 Nov 2023 04:48:46 -0800 (PST)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a00cbb83c82so773651266b.2 for <lisp@ietf.org>; Tue, 28 Nov 2023 04:48:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20230601.gappssmtp.com; s=20230601; t=1701175724; x=1701780524; 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=PxrzKWLRBJXbi3+DICQL7PUcH0nCjQvQc8KVBp/vnPM=; b=E21m0VV2c3knHca8HqN4llacrAi545efMt1bVZ6Hy/XZTpc+IXrfkvJyH1/wrRc3Gj mw+h4+rmCvxYBTUgv8pw3rg5XNExYzsYBzgXIYmAnHXKp/FvhdsiSH3EsQ6M3GL230Cg jEu4BV5x99bJSs32rzMePvoBhIZzjrMmYchuPYgW88bfFzu5Yo0kr3j0cU84+6Kk2hDD 2Beb2dpPmw5FsezJvy1pkmMFbQ37eLjjZtj+H2tNJtsleRlzzy95OCbbZiOBb7EFx3Q6 VUYbK+Vvdo8nkDy137ptF3LsaX0AHlfMvTG17OvHvjYS94Lm75+sq+RqXIG0M8poS/4d v5ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701175724; x=1701780524; 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=PxrzKWLRBJXbi3+DICQL7PUcH0nCjQvQc8KVBp/vnPM=; b=saJ92nKna9Emrw8rz27BXcNEO71c61g/w27Ap+F3fBYHYPZxg1ImkiiuyeI3yp2vhv G5EXmG8iVgWjCWhuyLTJpiaJIw/Jo5ORxeDkTF+Eo0PzDezF85S+ZXuqw4dq9AcVVKt9 beJS6JAB7XWhuXTFI/JtZuasSORkdILuL35+EaoMPCZh7Jft6+nNTT/RZHzB+pO/3QNn LvEJx8lZti56iNVqpZTiAefU2dSSElgAPTvq/ODe28hqYdj+Dy0ds4bUW4F38SK4jKtP K8eLHH5Q14IWbLb1hlccn/KTcpGnvi3xQeyxeKnX9/PsgpG6JtJmFJaUCLr8/E0E9dTk APzg==
X-Gm-Message-State: AOJu0YySO02Vy6tu8NhR5Q9HkCnRyPLSx4TzV7tSrp3gIDF2avNYuR/d LKx3j33qA8msZOYsVrj62Q4MnA==
X-Google-Smtp-Source: AGHT+IFyQ49+QfWrV03biVrALu7zkgsRXiGTXe+f6fZOm2ebjzsL22p0tZkIh6Yg59xDwuSO2usOUQ==
X-Received: by 2002:a17:907:11c2:b0:a0f:78bc:649a with SMTP id va2-20020a17090711c200b00a0f78bc649amr4944333ejb.74.1701175724408; Tue, 28 Nov 2023 04:48:44 -0800 (PST)
Received: from smtpclient.apple (91-167-176-17.subs.proxad.net. [91.167.176.17]) by smtp.gmail.com with ESMTPSA id p18-20020a1709061b5200b009b9a1714524sm6874548ejg.12.2023.11.28.04.48.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Nov 2023 04:48:43 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <170110985397.45307.7808620903152056899@ietfa.amsl.com>
Date: Tue, 28 Nov 2023 13:48:32 +0100
Cc: The IESG <iesg@ietf.org>, lisp-chairs@ietf.org, lisp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3AF32302-3773-4063-94DB-6D121FBB8EA9@gigix.net>
References: <170110985397.45307.7808620903152056899@ietfa.amsl.com>
To: Martin Duke <martin.h.duke@gmail.com>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/I2eKjJ1wCpBZZL-Ywxt7AUv86ng>
Subject: Re: [lisp] Martin Duke's No Objection on charter-ietf-lisp-04-01: (with COMMENT)
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: Tue, 28 Nov 2023 12:48:52 -0000
Hi Martin, Thanks for the catch the sentence is indeed unclear. What about: LISP technology has a wide span of potential applications beyond the simple routing aspects. Better? L. > On Nov 27, 2023, at 19:30, Martin Duke via Datatracker <noreply@ietf.org> wrote: > > Martin Duke has entered the following ballot position for > charter-ietf-lisp-04-01: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/charter-ietf-lisp/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > What does this sentence mean? > > "The scope of the LISP technology is potentially applicable to have a large span" > > Does it mean > "LISP technology has a wide span of potential applications?" > > and if so, is that a useful statement in a charter without more specifics? > > >
- [lisp] Martin Duke's No Objection on charter-ietf… Martin Duke via Datatracker
- Re: [lisp] Martin Duke's No Objection on charter-… Luigi Iannone
- Re: [lisp] Martin Duke's No Objection on charter-… Martin Duke
- Re: [lisp] Martin Duke's No Objection on charter-… James Guichard