Re: [GROW] IESG requested changes on draft-ietf-grow-wkc-behavior

David Farmer <farmer@umn.edu> Thu, 13 June 2019 16:58 UTC

Return-Path: <farmer@umn.edu>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B9D2120156 for <grow@ietfa.amsl.com>; Thu, 13 Jun 2019 09:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
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 QCTmnjd4nsZ5 for <grow@ietfa.amsl.com>; Thu, 13 Jun 2019 09:58:44 -0700 (PDT)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3973B12012D for <grow@ietf.org>; Thu, 13 Jun 2019 09:58:44 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id A5E57B9D for <grow@ietf.org>; Thu, 13 Jun 2019 16:58:43 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2yWTiZw3-b6 for <grow@ietf.org>; Thu, 13 Jun 2019 11:58:43 -0500 (CDT)
Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 6B8A9715 for <grow@ietf.org>; Thu, 13 Jun 2019 11:58:43 -0500 (CDT)
Received: by mail-ua1-f69.google.com with SMTP id v20so1963379uao.2 for <grow@ietf.org>; Thu, 13 Jun 2019 09:58:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5wbE63SBmQH7+MfPvjNfxqiqLMjc+yNTBJwJFfMYaJw=; b=okLjZaZDhc7zUVNCb7Q7smLnM62f1Zl1eXW4porym5CafGPIPYDEqtCjyHMGEeqimO iPvZuhWUwFnOf3sYMP1nTUJWeGecdxkn3HaWM7E7qwTZQNtfoXoyLEYaapTgCeZigrM+ MTIRsMmIR3/tyLOlIWxJxAXWZWLovmnY9jviinFvDDq+azOdRMg6iTifARoDABAyalc+ 21QL7gGeSkEnIQXF7DelYxkH7EdnZN7Rn4emcnmQeJ+lnOIQOdd3pQ73uAzeNUU5o8qW uyyngTlrcz6OjutefVBynnqHqEtIPFrK1s5Phvu5JS8Z3TcaeaNvKwfsV4lWzn86p+4c HL9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5wbE63SBmQH7+MfPvjNfxqiqLMjc+yNTBJwJFfMYaJw=; b=FD4otKtlPnxtAVVRUjf16m5mVhIHzNyiuggMpQH3NFLGONAi32cR0Bp+B2U78VOdaV Qw50YjbLO3FzxcuEtJhCjLahU4l4EiaAxHDd18jv+I0f1fRQvXCrbETTYtcbOh0/NANH kyG4k2VkAiRBMn03Vp335t/+b17T5+1jFctl1NQa+jXuBe4Xu+UJU5bJs7AG+e8sft+R Dq4kHf+pTzuxJB+tmCl4V1yKl1IHUkncUwG332I7NdvYcEgMIUB45p95fGBTVgrWi+DL vUvsiavq/cnA1VSpKLgNqIZbKVzIl/U3rtst9tpwnKaXyBemhcIy6pTw5PGfg3rFlcyf cj4g==
X-Gm-Message-State: APjAAAVxKwFs6xH+1SUq+hL6xWw5OCNmiQBVPBh+PNrBjNscLSXSozjT mFzZ+CAT5GUlnaio1vAx4ZKhYAbmwDzdaeDoujs5KYaLMvZ7Q8s5jQZM9M/RF2RvrDXOjmnxbsT z12EqQ2Q/rj2OzSQYHPe3nytS
X-Received: by 2002:a05:6102:85:: with SMTP id t5mr18802453vsp.221.1560445122178; Thu, 13 Jun 2019 09:58:42 -0700 (PDT)
X-Google-Smtp-Source: APXvYqygWYDKiAA5e/I5WVf+DgncuTcW/EY9aEHF1VRgKoKV9CkUaLhd/mbEC6N4fCxG2HzgYYese4YHdhGO0hfgkj8=
X-Received: by 2002:a05:6102:85:: with SMTP id t5mr18802406vsp.221.1560445121827; Thu, 13 Jun 2019 09:58:41 -0700 (PDT)
MIME-Version: 1.0
References: <CAHw9_iJnVf=yiQLWgnzdWTXrm6A6jWDSCsrQr9pfAwWuMJhOww@mail.gmail.com>
In-Reply-To: <CAHw9_iJnVf=yiQLWgnzdWTXrm6A6jWDSCsrQr9pfAwWuMJhOww@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 13 Jun 2019 11:58:28 -0500
Message-ID: <CAN-Dau3PZHjDUiENAqhkWwRspczczcntVhiPnG_hZPTH0VuPOQ@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
Cc: "grow@ietf.org grow@ietf.org" <grow@ietf.org>, draft-ietf-grow-wkc-behavior@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002daa32058b37718c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/xKbwYIbeM-Usw5HTowTcgHf2Q4Y>
Subject: Re: [GROW] IESG requested changes on draft-ietf-grow-wkc-behavior
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2019 16:58:47 -0000

On Thu, Jun 13, 2019 at 9:56 AM Warren Kumari <warren@kumari.net> wrote:

> Hi there all,
>
> The IESG felt that (esp because this is listed as Standards Track)
> that we should replace:
> "Vendors SHOULD clearly document the behavior of "set" directive in
> their implementations."
> with:
> "Vendors MUST clearly document the behavior of "set" directive in
> their implementations."
> (s/SHOULD/MUST/).
>
> The document had sufficient support to be approved as is, but I think
> that this is a useful improvement, and so agreed that we would make
> that change (and the document is approved). I was initially
> uncomfortable with the IETF telling vendors what they "MUST" do, but
> then realized that we implicitly do this all throughout the IETF
> series. Please let me know by  2019-06-19 if you *strongly* object to
> this change.
>
> Thank you all,
> W
>
>
This change doesn't my support for the document, I still support it.

I brought this up previously, so feel free to ignore it.

In RFC1997 the three Well-known Communities are defined using MUST NOT,
that seems at odds with the idea that the communities can be removed,
SHOULD NOT seems compatible with the ability to remove them and effectively
ignore them.

Thanks.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================