Re: [Sidrops] Alexey Melnikov's Discuss on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with DISCUSS)

Sean Turner <sean@sn3rd.com> Thu, 11 April 2019 11:52 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD0A1201B1 for <sidrops@ietfa.amsl.com>; Thu, 11 Apr 2019 04:52:46 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 1li4DROKW7ID for <sidrops@ietfa.amsl.com>; Thu, 11 Apr 2019 04:52:44 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 DF827120099 for <sidrops@ietf.org>; Thu, 11 Apr 2019 04:52:43 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id v20so6606530qtv.12 for <sidrops@ietf.org>; Thu, 11 Apr 2019 04:52:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IiaUZSugxvsfGmOL+qZcueGr1f7sw3mwJf8PVxyElbw=; b=N/eJzXuRFEY7CnRjhMS2PjHO0Zy0XqpkDfeMKqhSA063mHHN0AXjVIUhmylr3x3OxB rqA7GGqKLMlEuUto37c+ftRzwzLJtBMkBnDIg1u3DMmeHjvjMBj4GGL4+A9O3//vKE04 RTd7G/LnLGe3T0A9tUGp25OxLBCyifB454tRk=
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=IiaUZSugxvsfGmOL+qZcueGr1f7sw3mwJf8PVxyElbw=; b=cG9lfhvR0q5yWfVwrC6rSJMBiS4vuT1a5V9RKTKPA4SuoND6MZjnF0fCfbCY536Eb1 w1CfjcpmONRWC22ZkGYsV7P6qF+NjHWxHRTiE2i8kfxbiidkMFYZmhIP2J/y3Z8TERgj 1TziOhQ6rCew01vR0QcNFCENAHxhMInry0bizZnb5uWXVj5o9QPtrIjc0frffJGaadUx +9iSPnZIZ9lHcMPmtYp+El1dlBa7e8jnvt3BREd7KKYmUDH5nmSihl4l9WzvtfOebsTN 2f/yAA7mTN3aovVOHBZ2IPGbun67txwptyk/EwDpk+l1zrNAwXN7v3zXF4d/SVUxh86z I5sw==
X-Gm-Message-State: APjAAAX66vl2sCC0z2oRM/BZ7z7uL7hSb9z4A6Xk22j9LUvgj2MfQXFg 5DTfz0qrtBtwS+E3xXMncoLxCA==
X-Google-Smtp-Source: APXvYqwDDImhU7ne3+Nxb59WrX/cCMdLgo3INF5gsB67ktalhh9EydlkCF85/ByQ/nNFgmIxWcTC7Q==
X-Received: by 2002:ac8:2734:: with SMTP id g49mr40593422qtg.228.1554983563068; Thu, 11 Apr 2019 04:52:43 -0700 (PDT)
Received: from sn3rd.lan ([75.102.131.36]) by smtp.gmail.com with ESMTPSA id h24sm27458252qte.50.2019.04.11.04.52.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Apr 2019 04:52:42 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <554dd3b6-4e1b-4582-8411-cf98425b1d21@www.fastmail.com>
Date: Thu, 11 Apr 2019 07:52:40 -0400
Cc: Benjamin Kaduk <kaduk@mit.edu>, Warren Kumari <warren@kumari.net>, SIDROps Chairs <sidrops-chairs@ietf.org>, draft-ietf-sidrops-bgpsec-algs-rfc8208-bis@ietf.org, SIDR Operations WG <sidrops@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9D741A1-B2AD-4482-AB52-408BCE8CE3AE@sn3rd.com>
References: <155491848705.8904.6102999785203393745.idtracker@ietfa.amsl.com> <CAHw9_iKkxDiB4G1HQbgkDsJN8DpOomwCh1EomAh_co_25KpWEw@mail.gmail.com> <7433410F-E7A3-47B8-87F1-C170C30CE4E5@sn3rd.com> <20190410213026.GH18549@kduck.mit.edu> <554dd3b6-4e1b-4582-8411-cf98425b1d21@www.fastmail.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/uhO8xPrHYP2hZWfY9lSCAwF8Vck>
Subject: Re: [Sidrops] Alexey Melnikov's Discuss on draft-ietf-sidrops-bgpsec-algs-rfc8208-bis-04: (with DISCUSS)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Apr 2019 11:52:46 -0000


> On Apr 11, 2019, at 06:00, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
> 
> On Wed, Apr 10, 2019, at 10:30 PM, Benjamin Kaduk wrote:
>> On Wed, Apr 10, 2019 at 05:27:50PM -0400, Sean Turner wrote:
>>> 
>>> 
>>>> On Apr 10, 2019, at 14:48, Warren Kumari <warren@kumari.net> wrote:
>>>> 
>>>> 
>>>> 
>>>> On Wed, Apr 10, 2019 at 1:48 PM Alexey Melnikov via Datatracker <noreply@ietf.org> wrote:
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>> 
>>>> This is a fine document and sorry for nit-picking, but why is this document
>>>> "Updates: 8208" instead of "Obsolete: 8208"?
>>>> 
>>>> 
>>>> Thanks an excellent question -- I suspect that the answer is simply "Whoops, that was a mistake" -- is that correct?
>>>> W
>>> 
>>> Nope this draft is an updates because it’s just adding some things to 8208 not replacing it entirely.
>> 
>> Er, what is left in 8208 that's not being replaced?
>> The diff seems pretty indicative that all the content is present in the new
>> doc, to me.
> 
> Exactly. This document doesn't just update the IANA registration process, it incorporates the whole RFC 8208 content. After it is published as an RFC, there would never be any need for people to read RFC 8208. This means it is obsolete relationship.

No argument whatsoever from me about whether this is an obsoletes/updates.  am looking forward to the finalized IESG statement on updates vs obsoletes ;).

spt