Re: [lisp] Request for WG document - draft-farinacci-lisp-name-encoding

Dino Farinacci <farinacci@gmail.com> Fri, 02 October 2020 15:08 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 327263A1680 for <lisp@ietfa.amsl.com>; Fri, 2 Oct 2020 08:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y0tHHkYHgzPF for <lisp@ietfa.amsl.com>; Fri, 2 Oct 2020 08:08:26 -0700 (PDT)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD7763A1690 for <lisp@ietf.org>; Fri, 2 Oct 2020 08:08:26 -0700 (PDT)
Received: by mail-pj1-x1035.google.com with SMTP id a17so277675pju.1 for <lisp@ietf.org>; Fri, 02 Oct 2020 08:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VlS/zTB4sspo92bKX4SG3v8J3raAXGBy/F2uVJOua0k=; b=M0eJ8sIP4QrSUHz+rN2+PfV17j3Y8xCqkgGazn59VQr9iNJ4Blc3B+EU3lQmzFdQh1 HNkJIdGAveZwNoyVyJuoNoz2E4MOKvsvV2G/17k/2wQu5pZbrY3JnJLE/kPB7FVpYNTv b0Wa9k0CQT0XbZxMPLCjnhCs3ywQXlX3wGgiYZ3Kfh3pkwtUq9FaxAOzbnTuI7/0C6Sg kebpMzbM7tURqo7i44FeS8G/Qb5oF6+n4dyt5GSEXss+r2ChdbuoMLu9Prxk03mwq+u6 H1icNcmph1FQzi6NE9xvGd+HEcyErDAuOKU1OXs88whMkq/JV3ruvZxaTKJlrvRDyGbM ahQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VlS/zTB4sspo92bKX4SG3v8J3raAXGBy/F2uVJOua0k=; b=aE5jtirtiTZjVmcMC18uhzJ6AQwSWrZu6wzm8VLasaB6R7+gtvJ9nORyyw76z0cYAI beiKMPkxHMwzsAsmutZuKFkKFCIP9fygTJVASAidKS4/mKa/JiB00Y6yxJnrYrzk7wsi BJlQOGJOiu07twGcCP8I9OxITrHmG5D5gfi22vjMBSIsbrGrbbrbFyGkkdrcqU/9SmAL tS/5Dqo7G9U/O02iT+CUcDUBkZLio/xdjPhBZ0MCP2AjnFxOyFY0e1S1/laCzuSQMSSw VNXBZI9Sc8RDJPe607L/wrSFcz1BZpyjYZ4+ee/LKAxb1FGmnPTQPlMisnv6Z9tTWyg9 W41A==
X-Gm-Message-State: AOAM5331TQKzM3yk3oyb8ijO4E4YcyE8bPEP6DUl3l4EDFDklQqDNIMz iMUHWt1hpOJ5pIHO1pzLji8=
X-Google-Smtp-Source: ABdhPJyJxGyjwqbWgdhJ/6LAqpwIPLRozb4AeAAhN+6nyVMSTZ4saO7FGsK4EiwUn3BKhs2Hvy1EuQ==
X-Received: by 2002:a17:90a:b314:: with SMTP id d20mr3133452pjr.7.1601651306060; Fri, 02 Oct 2020 08:08:26 -0700 (PDT)
Received: from ?IPv6:2601:646:9600:af10:38a8:c2c2:4a71:75aa? ([2601:646:9600:af10:38a8:c2c2:4a71:75aa]) by smtp.gmail.com with ESMTPSA id w14sm2221654pfu.87.2020.10.02.08.08.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Oct 2020 08:08:22 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <61AF04E6-BC8F-43E3-9719-9DDB8AA4081A@gigix.net>
Date: Fri, 02 Oct 2020 08:08:19 -0700
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "lisp@ietf.org list" <lisp@ietf.org>, Dino Farinacci <farinacci@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <22359932-CAC4-489D-8777-8B89B781FB7C@gmail.com>
References: <88FFF16F-1E5F-4B41-B4A1-D3E02750F9BA@gmail.com> <D8703342-8336-49E8-997E-9A5BE08C8602@gmail.com> <61AF04E6-BC8F-43E3-9719-9DDB8AA4081A@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/RUQO_VcPTbISd9J7OZKdqdxFFRw>
Subject: Re: [lisp] Request for WG document - draft-farinacci-lisp-name-encoding
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 02 Oct 2020 15:08:35 -0000

> This document has been sitting around for 4 years indeed, but it has been presented to the WG for discussion only during IETF 96 (Summer 2016).
> https://www.ietf.org/proceedings/96/lisp.html
> The presentation was only 2 slides long and had no comments (you can check the minutes).

Because it is that simple and nothing has changed in the document.

> No discussions have being going on ever since, neither in the mailing list nor during face to face meetings.

Because people support it. You saw that on the mailing list. Joel just had recent comments, and they surfaced because of my initial email. He wanted clarity in the document. So I will make another revision.

> You have all rights to ask for adoption, but not to formally open the call for adoption.

I don't have authority to formally do anything. I sent an email *requesting* adoption. I cannot mandate it as an individual. You chairs know that.

> IETF procedures want that is up to the chairs to open the adoption call.
> Even so, your _informal_ call for adoption has raised 2 supports and 1 objection.

There were more than 2 supports emails. And you said "formal" above and now you said "informal". So the labels are not helpful.

> At this stage there are no sufficient elements that allow the chairs to declare consensus for adoption.

Well I will let the working group speak. So I would request the group to post on this list and show even more support.

> What I would suggest is:
> - to continue the technical discussion on the mailing list 
> 	- the more the better

Agree. But how much is enough is the question.

> -  present the document during one of the next meetings

Sure.

> 	- Please focus on why this is needed from a technical standpoint. Just stating I use it in another document is not a technical reason.

The drafts that reference it provide technical material.

>         - If at that point there is interest from the WG, we will make the call for adoption.

There is interest. I don't know what more you want.

> I encourage you all to continue the discussion.

And I encourage you chairs to be open minded. And allow the working group to be creative and productive.

Dino