IETF Logo Mail Archive

fundamental brokenness of iasa2 updates (was Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt)

Scott Bradner <sob@sobco.com> Mon, 22 October 2018 21:08 UTC

Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA1412DD85; Mon, 22 Oct 2018 14:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 Nh7IsauzCA0T; Mon, 22 Oct 2018 14:08:54 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 635CD12D4EA; Mon, 22 Oct 2018 14:08:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id DE8DD7658CF2; Mon, 22 Oct 2018 17:08:50 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YFNWZKXn8e3l; Mon, 22 Oct 2018 17:08:43 -0400 (EDT)
Received: from [10.10.10.1] (g2.sobco.com [136.248.127.171]) by sobco.sobco.com (Postfix) with ESMTPSA id 184D77658CE2; Mon, 22 Oct 2018 17:08:42 -0400 (EDT)
From: Scott Bradner <sob@sobco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
Subject: fundamental brokenness of iasa2 updates (was Re: [Iasa20] draft-ietf-iasa2-rfc2418bis-01.txt)
Date: Mon, 22 Oct 2018 17:08:36 -0400
References: <4915CD062D28D607D3D4AD44@PSB> <8906b727-f9c3-e7e1-164b-f7b88e48e74b@gmail.com> <1C77C07809EFB402E3E10907@PSB> <DE6E9C0D-C46B-4010-9E6D-8438DE687275@sobco.com> <2A42A5D2-9785-4350-92A5-0FDFD54AD17F@cable.comcast.com> <9A5B610BA33D4336A91409DA@PSB> <CABtrr-UdUaZpoy8JroUL8oNkibc=F8hJ1ksnmvar0a1x3VCNrQ@mail.gmail.com> <541E68A8540C1AB8D39A96E4@PSB>
To: IETF Discussion Mailing List <ietf@ietf.org>, IASA 2 WG <iasa20@ietf.org>
In-Reply-To: <541E68A8540C1AB8D39A96E4@PSB>
Message-Id: <313EA233-92B1-4D61-AECA-099ADEECD063@sobco.com>
X-Mailer: Apple Mail (2.3445.100.39)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gJ6PHsMd7-XoSaRB0KWLEhlm3BM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 21:08:56 -0000

this is a separate issue about the iasa2 proposed updates

come on - you update an RFC without including a section that says what changes you are making???

are you purposely trying to make it harder for IETF participants to understand what’s going on?

every RFC that updates another RFC needs (MUST?) have a section that tells the reader what has
changed - this is vital for any technical speck so the implementor knows what they have to change in
their implementation but its also very important in process documents so participants can understand 
if they need to change how they do things

so, be nice to the participants and admit (in writing) what changes you are proposing

Scott

v2.23.0 | Report a Bug | By Email