Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice

Adam Roach <adam@nostrum.com> Wed, 08 January 2020 18:11 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79567120059 for <art@ietfa.amsl.com>; Wed, 8 Jan 2020 10:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 ZHuEs4mV6i0W for <art@ietfa.amsl.com>; Wed, 8 Jan 2020 10:11:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 4AF39120019 for <art@ietf.org>; Wed, 8 Jan 2020 10:11:30 -0800 (PST)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 008IBFVC017925 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Jan 2020 12:11:16 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1578507078; bh=RK80AGRZNq2ufeZNbqvgAjTwv0aETAn4Oz87fLgj7Ro=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=pu6q/oLCHCGAEH6X/xJGosCusGv8OV7qfiYhhY+GYuh2oooUFLlLnVwTfBl1euDgE fD+4xyUWPqA510GdgQihqyFydRnET1UBR0TnfoE8OqmwTb2Owc4KFobhDxDD39MT2e 5O218/rTsQr5KnsQIy8sa6P6RTqMgFKPAc87EKIE=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: S Moonesamy <sm+ietf@elandsys.com>, Mark Nottingham <mnot@mnot.net>
Cc: art@ietf.org
References: <87E116C31DAF1434C3C3937F@PSB> <a267e8d7-e88f-fe84-a3d4-eb12b88a46ad@nostrum.com> <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <9eda86bf-a31d-a45f-ac8c-98cb7f38e9d1@nostrum.com>
Date: Wed, 08 Jan 2020 12:11:10 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20200107163256.0f2810b8@elandnews.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/9vLaVe7X5siI6FMwDL5VObSQ1K4>
Subject: Re: [art] URNs and Last Call: <draft-nottingham-rfc7320bis-02.txt> (URI Design and Ownership) to Best Current Practice
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2020 18:11:31 -0000

On 1/7/20 7:26 PM, S Moonesamy wrote:
> I was going to comment about the document as there was an announcement 
> about it.  After reading your note I wondered whether it was 
> worthwhile to comment if I have to restrict my comments to what was 
> changed since RFC 7302.


To be clear, what I posted is my personal opinion (as are the following 
two paragraphs), and isn't an official IESG position, much less an IETF 
consensus position. Nothing in the process prevents you from commenting 
on whatever you want.

That said, I think it is a bad idea to slow down or stop improvements to 
a document by asking for unrelated and possibly contentious changes, 
especially at (or, to be honest, somewhat after) the last minute. The 
IETF has a long history of letting "perfect" become the enemy of "good," 
leading to author frustration, participant fatigue, and very long delays 
in publication.

For further clarity: I think it would be completely reasonable to turn 
around and propose yet another bis version of BCP 190 to fix any further 
perceived defects as soon as this version is published, and then work 
towards building consensus that such changes are required. The changes 
in the current bis are needed to address a demonstrable and ongoing 
problem. It seems imprudent to delay needed tactical changes based on 
last-minute musings about what else might be changed.

/a