Re: [lisp] Mirja Kühlewind's Discuss on draft-ietf-lisp-rfc6830bis-16: (with DISCUSS and COMMENT)

Dino Farinacci <farinacci@gmail.com> Mon, 24 September 2018 17:34 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 0E933130E3F; Mon, 24 Sep 2018 10:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 G_GiCUvyEPdM; Mon, 24 Sep 2018 10:34:18 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 87BF5126CB6; Mon, 24 Sep 2018 10:34:11 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id a18-v6so2514636pfo.4; Mon, 24 Sep 2018 10:34:11 -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=nmfwWX6Yz/2PlRpyQ5UWO8HZspDx+p7dS4VGMkoOEbA=; b=OWLjaTxr/JTotLzle7+ZVKZFAegSrbwiMevAnn+v4zSPcqujN0f61j+HwTcwyx9Qd6 tXLlJujCZ0NfWfu4bFIisGnPz/ZVNPPK0wsZ4f4GdYVdwjBhYCTzjKybtfjA7uYyx3HJ 5tAbBmxfPPUoZ5oj68wkU6MXs47r901Yjde4IRV32BqABVRrtLvYBhsxXOucgw5vuSnr MSKJU5b+PMHjsvZRkhbGeM7r/iHNZ5SXr9N1isqBy6EleNN8ZbvOl387Mpmh8TIROKjj tTJ4pX0KIYNvB+Of9aHea7xsnPuIw3r5ohoqH6stjLuwMwCdd8Hx8SaKjBeQfJqvR1qC pG3g==
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=nmfwWX6Yz/2PlRpyQ5UWO8HZspDx+p7dS4VGMkoOEbA=; b=DcjwFc1dDLH2QO/KMx3c4IJq+myJAZvR885CKArbgxFf1o7Vh7Gh9xrnNa7eVwSVbm AHTV4kGHfFH8h9v4ACVL1IjZe2TjhO8VnR4yTOYTXkQbyHd8IMWDfBYlbcBY/duyE0e0 8yGJ1VWEg0eo3DZ9W1dv+qtmEq8iM3zZfQuKcRn0XrYrZEYKQawhddUAaZDKXmdsnW/t teo55KEuL/6ePT8kpU607W1+/hN1p1iz+iPUzZW2IFakfv1AXBjH0REM9uxXo7OBmn7O RIbkJoCsES35YrJx4NifoT6qecTSDhS2hqQ112DMHIezXBdbQcZCiY9O1RcxXeQxcT8Q tx+g==
X-Gm-Message-State: ABuFfohnHSlbDokcBErU2TrltFTYoMn5QYvHrKCTh1r5lbHhWw/pmRy6 6eDQ1r8xksbyk3S2ms3Y0i2npRNX
X-Google-Smtp-Source: ACcGV635xqshREQvPX/EwE6l0WJNcVfKNkuV/7QBRMxy5ICeJJc5M6dm1bWrWJ4L/jupiHGD8Ecj5w==
X-Received: by 2002:a63:69c3:: with SMTP id e186-v6mr10323493pgc.431.1537810451029; Mon, 24 Sep 2018 10:34:11 -0700 (PDT)
Received: from [10.31.79.57] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id g5-v6sm51259193pgn.73.2018.09.24.10.34.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Sep 2018 10:34:10 -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: <11FBAC13-2859-4778-84CA-B546EB669727@kuehlewind.net>
Date: Mon, 24 Sep 2018 10:34:09 -0700
Cc: Luigi Iannone <ggx@gigix.net>, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>, draft-ietf-lisp-rfc6830bis@ietf.org, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB03EA1D-6C18-4039-A228-224774D991B5@gmail.com>
References: <153667905625.16761.12157659372502604927.idtracker@ietfa.amsl.com> <7DEBCA24-9D55-4325-85AA-48AB3FAAB91D@gmail.com> <0201F06C-DA9E-445A-A995-54BA805B595C@kuehlewind.net> <DDA9C261-44DD-4389-9463-3A84E4C176BB@gmail.com> <5EC21C57-D217-48A9-AFD0-24710299CF7F@kuehlewind.net> <5A3C4B1F-EA31-4698-96F4-915A77400A56@gmail.com> <2CAF25CC-01EE-49D4-B970-F8EFB24940A8@kuehlewind.net> <5F9D8F39-871D-4A96-9C0A-7BACD2ABB1F7@gmail.com> <AC0C4ACA-0E15-441E-B05A-64F034CBF2F1@kuehlewind.net> <CDF10486-2CD1-43C2-BF1B-BA8CA8C29444@gmail.com> <2DC6D38E-C46B-4D38-B093-B88720BCD550@kuehlewind.net> <0BE5C929-D2FA-4786-9F5E-0A93E7700880@gmail.com> <11FBAC13-2859-4778-84CA-B546EB669727@kuehlewind.net>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/gvPPL8gAmAXfDzQLFzcjW2SHF1o>
Subject: Re: [lisp] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf-?= =?utf-8?q?lisp-rfc6830bis-16=3A_=28with_DISCUSS_and_COMMENT=29?=
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: Mon, 24 Sep 2018 17:34:20 -0000

Well, the implementations are out and working. And we said in the latest updates to consider using RFC6040. So not sure we can do much more than that.

Dino

> On Sep 24, 2018, at 5:52 AM, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote:
> 
> Because they don’t follow RFC6040 and therefore we do something different in some corner cases.
> 
> 
> 
>> Am 22.09.2018 um 06:52 schrieb Dino Farinacci <farinacci@gmail.com>om>:
>> 
>>> However, I totally disagree with your comment on providing details that are not implemented. If they are not implemented correctly, it might even be more important to spell them out in this document, so implementors have chance to update their (future) implementation to do the correct thing. Having deployed implementations that are non standard-conform always happens and in this case it is probably not specifically problematic as it doesn’t impact interoperability. However, it is important though that the spec is correct.
>> 
>> And why do you think they are implemented incorrectly? 
>> 
>> Dino
>> 
>