Re: [lisp] Alvaro Retana's No Objection on draft-ietf-lisp-rfc6830bis-16: (with COMMENT)

Dino Farinacci <farinacci@gmail.com> Tue, 11 September 2018 20:52 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 D4828130DE4 for <lisp@ietfa.amsl.com>; Tue, 11 Sep 2018 13:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 R1tXKLvZzC9p for <lisp@ietfa.amsl.com>; Tue, 11 Sep 2018 13:51:57 -0700 (PDT)
Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (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 727B8130DE5 for <lisp@ietf.org>; Tue, 11 Sep 2018 13:51:57 -0700 (PDT)
Received: by mail-oi0-x243.google.com with SMTP id m11-v6so50003437oic.2 for <lisp@ietf.org>; Tue, 11 Sep 2018 13:51:57 -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=7YgSX8SoM6FDfuUG3FaSfNZOZjYL14O3cUBWGzO93dc=; b=TThq8ynYIs5YagmgvxKZhal0fPcpihAp0L1tNP8XiwjrEyFsDU5AP95EMuVBMAgP5p 9HTxFYNH01GbHRhNCAgbZ0p+wB8dNey1XtpBbOZU3PFmiuWVU5TB2JQ97zCNX7FmKwIC IxVjDrzwUSr/PcEy/nkp7jGoDSlNvXsA+nM7CqNFvsxq2r+6xPJHjTIKp4dSASr5rSBC VF5B0/PGoxJQHKXuGDFCVI+Ufatb4GOo/Hu1UhbnRXcNcshQifha9Ee/CHSrlwwMHNS8 aUGbxdB/J0IoTfEHaW6ICuXN7r0qULcJbqlYa/LFdr6Mhr7Bc1YsWKlu36giY3+48qK8 fc5Q==
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=7YgSX8SoM6FDfuUG3FaSfNZOZjYL14O3cUBWGzO93dc=; b=GE0ROKQSDWTwIUAZY6gNxXXyqnGTkkAcP/2HxkdV97lzdMMe+RoMreRc2YYgjL26+5 Ay+kdvF1Sv33PXeEWhmAlDztClvVxVmuZc+kbHbMiSWoYzacEI0RBjStHTHuGNP9IbIA 7K53eEAOIF/ChesbkT836YKrizm8Ui4RWlzjp0ZVipcFkvLTE5du+snYQLV0vAsiKbp3 0cjALqT9Gj7KZFJj5v32/y77K8xlpbnbP4G8rd0PCGjv8Zp52lu7tnsVZNRK3nopX3A7 Ol/UZg9as4Lzyi1wgiBnAKy3IGye1nEdFTeEPNvADTeJ09AnSPhs9S7pwuVV8ZE/6DMz U2Bw==
X-Gm-Message-State: APzg51CnhiSvP8/s43qpe2GyE91MwrbhyWbAEUOI8+fndvNs+LWs8CeM RQy/5Cc4OdGkL8CvUiFlPis=
X-Google-Smtp-Source: ANB0VdZfGOE7xZISVZXiUeXXgEC4RMl7qUtRXQTtSw5dHQVsI5v6E0tWAsbuCObXKjjHcSgAKVCQoQ==
X-Received: by 2002:aca:4dca:: with SMTP id a193-v6mr27527817oib.343.1536699116818; Tue, 11 Sep 2018 13:51:56 -0700 (PDT)
Received: from dino-macbook.attlocal.net (adsl-108-94-2-123.dsl.pltn13.sbcglobal.net. [108.94.2.123]) by smtp.gmail.com with ESMTPSA id o9-v6sm16437258oia.21.2018.09.11.13.51.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Sep 2018 13:51:56 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAGE_Qexi9hkxEVfkLwy85N94mLbF8xLJ9ycgLgTctN2=ZC5M5A@mail.gmail.com>
Date: Tue, 11 Sep 2018 13:51:54 -0700
Cc: aretana.ietf@gmail.com, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <446E0FA7-359C-44EF-8855-01AA87C2CAFD@gmail.com>
References: <153661454107.16021.14181238567935017697.idtracker@ietfa.amsl.com> <82C0DF7A-E661-48DF-ABCE-7C830E875E70@gmail.com> <f51f97af-5b4c-ac7f-b239-bc39088a263a@joelhalpern.com> <CAMMESsxdBxCCdAVL5LR-QcknucoKayNFV7mp=jGX+txxVz4fog@mail.gmail.com> <8A78EF35-B0E4-43EC-A6B7-EB7DED60210F@gmail.com> <CAGE_Qexi9hkxEVfkLwy85N94mLbF8xLJ9ycgLgTctN2=ZC5M5A@mail.gmail.com>
To: Albert Cabellos <albert.cabellos@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/poxDRqiir1EElNdWEmo_W2HmhFg>
Subject: Re: [lisp] Alvaro Retana's No Objection on draft-ietf-lisp-rfc6830bis-16: (with COMMENT)
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: Tue, 11 Sep 2018 20:52:01 -0000

The bottleneck is lisp-sec. So no matter what happens to 6830bis or 6833bis, it may not change that. Yes, we should do the right thing.

Dino

> On Sep 11, 2018, at 1:03 PM, Albert Cabellos <albert.cabellos@gmail.com> wrote:
> 
> Hi
> 
> I am not familiar with all the IETF procedures, but lisp-intro has been waiting for a missing reference for 1000+ days and the day it will become RFC it will be referencing an obsolete document.
> 
> I think that we should make it right, if someone can shepherd me on what to do I´ll be happy to work on it.
> 
> Albert
> 
> On Tue, Sep 11, 2018 at 6:37 PM Dino Farinacci <farinacci@gmail.com> wrote:
> Right now there is no circular dependency. To summarize:
> 
> (1) RFC6830 does not point to 6830bis or lisp-intro.
> (2) lisp-intro points to RFC6830.
> (3) 6860bis needs to point to RFC6830.
> 
> Let’s please don’t change any this. Let’s not make this more complciated then it needs to be and let’s not confuse people, especially the authors. ;-)
> 
> Dino
> 
> 
> > On Sep 11, 2018, at 9:29 AM, Alvaro Retana <aretana.ietf@gmail.com> wrote:
> > 
> > On September 11, 2018 at 9:50:29 AM, Joel M. Halpern (jmh@joelhalpern.com) wrote:
> > 
> > Hi!
> > 
> >> Any change to lisp-intro should be done by discussion with the RFC 
> >> Editor, as it is in the RFC Editor queue (pending reference completion).
> >> If the working group considers it acceptable, we could easily ask them 
> >> to change the references to 6830 and 6833 to the bis documents (after 
> >> all, it is alreay blocked by documents which depend upon those.)
> > The reference would still be circular: rfc6830bis would point at lisp-introduction for architecture details, and that would point back here.
> > 
> > If lisp-introduction was just that (an introduction) and the details were in rfc6830 to start with…. Maybe the easy fix is to just not point to lisp-introduction from rfc6830bis, because the details should be here (and rfc6833bis) already.
> > 
> > s/Finally, [I-D.ietf-lisp-introduction] describes the LISP architecture.//
> > 
> > Alvaro.
> > 
> > 
> > 
> >> 
> >> 
> >> Yours,
> >> Joel
> >> 
> >> On 9/10/18 11:27 PM, Dino Farinacci wrote:
> >> > If you guys have source for the intro doc, I could point it to bis 
> >> > documents?
> >> > 
> >> > Dino
> >> > 
> >> > 
> >> > Begin forwarded message:
> >> > 
> >> >> *Resent-From:* <alias-bounces@ietf.org <mailto:alias-bounces@ietf.org>>
> >> >> *From:* Alvaro Retana <aretana.ietf@gmail.com 
> >> >> <mailto:aretana.ietf@gmail.com>>
> >> >> *Date:* September 10, 2018 at 2:22:21 PM PDT
> >> >> *Resent-To:* farinacci@gmail.com <mailto:farinacci@gmail.com>, 
> >> >> vince.fuller@gmail.com <mailto:vince.fuller@gmail.com>, dmm@1-4-5.net 
> >> >> <mailto:dmm@1-4-5.net>, darlewis@cisco.com 
> >> >> <mailto:darlewis@cisco.com>, acabello@ac.upc.edu 
> >> >> <mailto:acabello@ac.upc.edu>
> >> >> *To:* "The IESG" <iesg@ietf.org <mailto:iesg@ietf.org>>
> >> >> *Cc:* draft-ietf-lisp-rfc6830bis@ietf.org 
> >> >> <mailto:draft-ietf-lisp-rfc6830bis@ietf.org>, Luigi Iannone 
> >> >> <ggx@gigix.net <mailto:ggx@gigix.net>>, lisp-chairs@ietf.org 
> >> >> <mailto:lisp-chairs@ietf.org>, lisp@ietf.org <mailto:lisp@ietf.org>
> >> >> *Subject:* *Alvaro Retana's No Objection on 
> >> >> draft-ietf-lisp-rfc6830bis-16: (with COMMENT)*
> >> >>
> >> >> Alvaro Retana has entered the following ballot position for
> >> >> draft-ietf-lisp-rfc6830bis-16: 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.)
> >> >>
> >> >>
> >> >> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> >> >> for more information about IESG DISCUSS and COMMENT positions.
> >> >>
> >> >>
> >> >> The document, along with other ballot positions, can be found here:
> >> >> https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/
> >> >>
> >> >>
> >> >>
> >> >> ----------------------------------------------------------------------
> >> >> COMMENT:
> >> >> ----------------------------------------------------------------------
> >> >>
> >> >> Thanks for the work on this document!
> >> >>
> >> >> I have some relatively minor comments/nits:
> >> >>
> >> >> (1) §18: s/RFC8060/RFC8061
> >> >>
> >> >> (2) §1: "Finally, [I-D.ietf-lisp-introduction] describes the LISP
> >> >> architecture."  First of all, it would seem to me that the 
> >> >> Architecture should
> >> >> be a Normative reference...but I-D.ietf-lisp-introduction says that it 
> >> >> "is used
> >> >> for introductory purposes, more details can be found in RFC6830, the 
> >> >> protocol
> >> >> specification."  This document obsoletes rfc6830...so it seems to me 
> >> >> that there
> >> >> is a failed circular dependency.
> >> >>
> >> >> (3) References to rfc2119/rfc8174 and rfc8126 should be Normative.
> >> >>
> >> >>
> >> 
> >> _______________________________________________
> >> lisp mailing list
> >> lisp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp