IETF Logo Mail Archive

Re: [Iasa20] WGLC: draft-ietf-iasa2-rfc4071bis

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 09 January 2019 23:03 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D1212D84C for <iasa20@ietfa.amsl.com>; Wed, 9 Jan 2019 15:03:20 -0800 (PST)
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 bgWHhBWeVy0z for <iasa20@ietfa.amsl.com>; Wed, 9 Jan 2019 15:03:19 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 1374512D7F8 for <iasa20@ietf.org>; Wed, 9 Jan 2019 15:03:19 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id z23so4281498plo.0 for <iasa20@ietf.org>; Wed, 09 Jan 2019 15:03:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=IIUiBKE5Z/qngqlpnTt2fTqgMFwjvOm7rhRhlwMLtDs=; b=B/eC9ZqCuEKhF7zUursE4cSxzZyxc0sKOdQbyKZtFWRke6lOc/4IiFR/b7O1650XT5 J8980IuDl+ozY3eCsnqhWnSm14v41abeEu/oVS+AbXF3uNJbwcEMCg8/6zDtG4MQRPsM jp63xf0k2uHT1Y+VZjlhf0liB+IjNQRAg/u9cpgzVzqUDabOZFCcBC5C5VF1qv2Qu4Qa HM8KBzOnJHlaczdHfmpK7nsDebo2544cFN/M/qXM7mNp4ViHqwYAKFLy77WY9YT33j1v oAeFTS2CqRXRYZwUaUzoW5CCop5AzscjCvNv7V8M6HoaI/GFuE9GUmn2gT2oEmqFO3r1 oO4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=IIUiBKE5Z/qngqlpnTt2fTqgMFwjvOm7rhRhlwMLtDs=; b=el/LzouCCZqG9H50k7WR5CMogOItXWMsiYwD6jFBPQt8gCmkM1H7YjuTKrZ0wbAqV5 z3Bu7ZsufWZCGm8xFXq4VnFk4m1XBX/cN5hAqTKl0p2qxcA5+CtmpyPESB5fq5erln+T aiHGP2jw5hXRE2lgH3faDDmKpZuoe1tT54GPlZzT7TKApCt/NFUlzP7WQJOy1eqQSUz8 +AbMxdzWDoUG9SfJEGletXHXN5R7ajOir2BxV5S5ENFsjVshu2cMHQM5NQ8JjsVLgvCv A6WoiBplOUehhtc92JmW9tx1XkQ8mMwfHszEGm+9xwMPPCdPMuEhkMNMGHozgW7quYnb qIsg==
X-Gm-Message-State: AJcUukfrIrhq1i2duW60tI7OdwvJblrnHGlZq5UOPe32/rhznzIBKN+s LgcakDYmNNKMGMPtzlQF3dTm1uKu
X-Google-Smtp-Source: ALg8bN6x7qfx4wyA7WCdFKtASdUp16Fo3+BSstRYal9vD6SxiInzrILKQJ/bUee4wwLVfYPZjrGEsw==
X-Received: by 2002:a17:902:a60f:: with SMTP id u15mr7536411plq.275.1547074998206; Wed, 09 Jan 2019 15:03:18 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id w184sm84305495pgd.34.2019.01.09.15.03.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Jan 2019 15:03:17 -0800 (PST)
To: Joseph Lorenzo Hall <joe@cdt.org>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, "iasa20@ietf.org" <iasa20@ietf.org>
References: <605F45EE-1FAA-4859-B047-DBA769F14289@cable.comcast.com> <26c0b1fd-3e69-89ea-42c9-977db9aee53a@gmail.com> <CABtrr-VQ8bg4K97be0f9U1H9KveGfzaYEtXZ3mi+tnS8oLgHWQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7fbd7537-c11d-2297-c404-d2424f4f92eb@gmail.com>
Date: Thu, 10 Jan 2019 12:03:12 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <CABtrr-VQ8bg4K97be0f9U1H9KveGfzaYEtXZ3mi+tnS8oLgHWQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/T6VrCZFvfMvF8wLG84itUI4D5Mo>
Subject: Re: [Iasa20] WGLC: draft-ietf-iasa2-rfc4071bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2019 23:03:20 -0000

On 2019-01-10 11:17, Joseph Lorenzo Hall wrote:
> On Fri, Dec 21, 2018 at 9:49 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> Maybe I missed some discussion, but this:
>>
>>> This document obsoletes [RFC4071] (BCP101), [RFC4333], and [RFC7691].
>>
>> is very unusual by including "(BCP101)".
>>
>> BCP101 is currently a set of three RFCs: RFC4071, RFC4371, and RFC7691.
>> This draft obsoletes only two of those. So it cannot claim to obsolete
>> BCP101 as a whole.
>>
>> As already noted, draft-ietf-iasa2-trust-update-02 claims to update
>> RFC4071 (which makes no sense since 4071bis obsoletes it) and RFC4371
>> (without obsoleting it).
>>
>> The fix for this is fiddly but trivial:
>>
>> 1. 4071bis should not claim to obsolete BCP101.
>> 2. trust-update should not claim to update RFC4071.
>> 3. trust-update should include a short text extract from RFC4371**.
>> 4. trust-update should obsolete RFC4371.
>> 5. 4071bis will be designated as BCP101 when published.
>>
> 
> Brian, if you know the answer or have an opinion: Should we put something
> in the document to the RFC Editor to specify this?

My *belief* is that this will happen automatically, but to be on the safe
side the AD can attach a note to the RFC Editor when the IESG approval
is sent out.

>> 6. trust-update will be designated as BCPxxx when published.

Same there - a note clarifying that this is now a separate BCP from 101
might be in order, if people agree with that.

   Brian

>>
>> ** See
>> https://mailarchive.ietf.org/arch/msg/iasa20/uQZsZiarA8u1lVWyOCQr-L6Pvfo
>>
>> Regards
>>    Brian Carpenter
>>
>> _______________________________________________
>> iasa20 mailing list
>> iasa20@ietf.org
>> https://www.ietf.org/mailman/listinfo/iasa20
>>
> 
>

v2.8.7 | Report a Bug | By Email