Re: Opsdir last call review of draft-arkko-trip-registry-update-00

Jari Arkko <jari.arkko@piuha.net> Mon, 03 December 2018 18:04 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBBE5130F82; Mon, 3 Dec 2018 10:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 R9x8mqUahh3O; Mon, 3 Dec 2018 10:04:00 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 46E95130F8E; Mon, 3 Dec 2018 10:04:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5670966028B; Mon, 3 Dec 2018 20:03:59 +0200 (EET)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hN02xixUmUbq; Mon, 3 Dec 2018 20:03:58 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 3BBCC66013A; Mon, 3 Dec 2018 20:03:58 +0200 (EET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Opsdir last call review of draft-arkko-trip-registry-update-00
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <154385988812.4946.9954294611401947565@ietfa.amsl.com>
Date: Mon, 03 Dec 2018 20:03:57 +0200
Cc: ops-dir@ietf.org, draft-arkko-trip-registry-update.all@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9B01DE8-4B07-4CA5-AE5E-027BE5DD4045@piuha.net>
References: <154385988812.4946.9954294611401947565@ietfa.amsl.com>
To: Carlos Pignataro <cpignata@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hH7aa8zr6MX-Lyt84kztfEnAkX0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 18:04:10 -0000

Thanks for your review, Carlos!

I believe this is one issue that should be queued up (also) more generally when we look at RFC8216 revision; the advice there might need to evolve. However, that does not take away the need to make a specific fix to this specific registry.

Jari