Re: [Gen-art] Genart last call review of draft-ietf-roll-useofrplinfo-25

Alissa Cooper <alissa@cooperw.in> Tue, 30 April 2019 18:53 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771FA12032C; Tue, 30 Apr 2019 11:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=PF73kDqh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=WGGAtLjb
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 TmcZAfYKAGc5; Tue, 30 Apr 2019 11:53:13 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A06E912032A; Tue, 30 Apr 2019 11:53:13 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 914DA2228D; Tue, 30 Apr 2019 14:53:12 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 30 Apr 2019 14:53:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=h 6O3+hJjtEaQ6tdj7vLb1rmgsClQ4rQkNdCWcGBA1kc=; b=PF73kDqhV1tu7Z7wR wpDtolX4ojsChr2mIA0iM2zQpQiYwKyW7kMvCbW6VU3cKWsdB0kngGgDFFLnjogr DVYVdZntXcKOQfqQBpS0wvi1p8pdt/ITapll2kqJ49xdIh1AsB7GQibhM8RANbkj 6Jb8y15/3ylK5xBXF6kagZFkrafFe5f9VEHLTbOr6PG2X+KM/FewDV1VD8qNCFNW HH3W9puxkA6mgljSR6lfqRGouce7CByKbR4IV9kwbqqv0KlUjUA8ItBW9rGB1G62 H+S+QURquuOBwepd9hzkcmG0fMaa1FU8HiQPWxKbUZ9ZdSDvurUs17dyrW5iqeFR EG7qg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=h6O3+hJjtEaQ6tdj7vLb1rmgsClQ4rQkNdCWcGBA1 kc=; b=WGGAtLjbxq0uK5ZRv3+uYIufa+bJ3oVL7O4mvH3JmwLOFVN6/Yo/HjPQT Jhm+hpmUBjB0MYOlUFAq/LK3+DpwwAsU4HVIipeIEmUzwRDStgs9Jrz0CBdWOFpX aQ2/rMJfSw19pnFYJUJt36HdQwlRaYAPXA5CyTkz0jJ+0AoU4VtjlbcLBjuIDK23 TJKlT4ys4RWSsoSNzWCS3rsYxNmWv6TrdwIaX9OC7tQREadPLW5T/nOqzRErawBh RzF/jUZIMEJd4FLgKZN882Mc4Yvy1HEs7fwDNN77KrXEnmoBMB2XtTS3Rl1ir9+9 Pyv6XenU2aYraQCMfuC1A3owlP5sg==
X-ME-Sender: <xms:l5nIXCC-QwKDUZABhj0sczPlGI-YiWU6cMbsUUXLzLK4O_Y6nSHhlA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieehgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrdejheenucfrrghrrghm pehmrghilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinhenucevlhhushhtvg hrufhiiigvpedt
X-ME-Proxy: <xmx:l5nIXNSCnj_Ng_SIJTuBqiLiW7gEvmQ1MOEcmdYD6KtIAYn1L0FzMg> <xmx:l5nIXBtLqILDu_F2lmz9x5Z-QiqDSnfUVbBck1lBm0UQZjdYzDwzZg> <xmx:l5nIXB2zDopCzt2DfgbYBGSrZw3QY480_TF-CViaCote9fhZS8nE-A> <xmx:mJnIXA2D5Nudp4mkxvHMGLHGijHmcUMLpWLTjrRkzvL6RPYKlqA4yw>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.75]) by mail.messagingengine.com (Postfix) with ESMTPA id 36CFAE47C4; Tue, 30 Apr 2019 14:53:11 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <23139.1554939802@dooku.sandelman.ca>
Date: Tue, 30 Apr 2019 14:53:09 -0400
Cc: draft-ietf-roll-useofrplinfo.all@ietf.org, General Area Review Team <gen-art@ietf.org>, roll@ietf.org, "<ietf@ietf.org>" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1318682-9A79-4777-B431-F14CE2E03CCE@cooperw.in>
References: <155431284696.22772.5756397598445681320@ietfa.amsl.com> <23139.1554939802@dooku.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/c0YbdP8-tZM-M1wMC24B7sbCLHQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-roll-useofrplinfo-25
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Apr 2019 18:53:17 -0000

Russ, thank you for your review. Michael, thank you for your response. I entered a No Objection ballot.

Alissa


> On Apr 10, 2019, at 7:43 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Russ Housley via Datatracker <noreply@ietf.org> wrote:
>> Section 1 says:
> 
>>   ... This document clarifies examples that intend to illustrate the
>> result of the normative language in RFC8200 and RFC6553.  In other
>> words, the examples are intended to be normative explanation of the
>> results of executing that language.
> 
>> This set the wrong expectation for me.  What the document seems to be
>> doing is aligning with the recent normative change in RFC8200.  The
>> alignment could lead to a flag day, and this document suggests a way to
>> avoid a flag day.  It goes through a whole bunch of use cases to
>> illustrate the updates.
> 
> So, the actual order of operations was more like:
>    - we aren't following 2460, so let's write down the right rules
>    - oh, look, 2460bis is happening, can we get the rules changed?
>    - cool, it happened, now what does that mean.
> 
> So I'll try to fix the text to match what a reader would now expect.
> Can you help with that paragraph? How about:
> 
>    } This document provides a series of examples that align RFC6553
>    } with the recent changes in processing described in RFC8200.  In other
>    } words, the examples are intended to be normative explanation of the
>    } results of executing that language.
>    } Existing deployed networks may experience a flag day as a result of
>    } some of the suggested changes, and this document provides a way
>    } to mitigate such an occurance.
> 
> 
>> Nits:
> 
>> In Table 6, please move some of the whitespace on the right to the
>> first column to avoid so many words being split across lines.
> 
> I don't think we control the table formatting, xml2rfc does.
> I'll see if I can do something about that.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art