Re: [Iasa20] Ballot positions on draft-ietf-iasa2-rfc7437bis

John C Klensin <> Fri, 05 July 2019 21:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 31346120122; Fri, 5 Jul 2019 14:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F6OXDL-Ed2V5; Fri, 5 Jul 2019 14:06:52 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 296D1120119; Fri, 5 Jul 2019 14:06:52 -0700 (PDT)
Received: from [] (helo=PSB) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1hjVPs-000JTg-Rt; Fri, 05 Jul 2019 17:06:48 -0400
Date: Fri, 05 Jul 2019 17:06:43 -0400
From: John C Klensin <>
To: Brian E Carpenter <>, Alissa Cooper <>, IESG <>
cc: IASA 2 WG <>
Message-ID: <8D3B2BFF27A5BADBA97ED23F@PSB>
In-Reply-To: <>
References: <> <>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Subject: Re: [Iasa20] Ballot positions on draft-ietf-iasa2-rfc7437bis
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?= <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 05 Jul 2019 21:06:55 -0000

FWIW, as someone who argued for making more extensive changes in
order to clean up problems we knew about _and_ who argued for
more focus on the approach of draft-ietf-iasa2-consolidated-upd
in order to avoid issuing replacement ("X obsoletes Y")
documents when we knew there were outstanding issues with them,
I agree with Brian and Alissa.  

The time to raise the question of whether IASA2 should do a
general cleanup was back when the IASA2 WG was chartered and has
long passed.  If we are ready to reopen basic procedures or
models that are not involved with the IASA transition, something
in the POISED, POISED95 or POISSON chain, or perhaps the NEWTRK
one, might be appropriate but pretending that IASA2 is properly
organized to do that -- even with a recharter -- would, IMO, be
a considerable disservice to the community.

In a more perfect world, I strongly prefer that we not replace
documents unless we sort out all known issues with them.  For
technical specifications, the language of RFC 2026 just about
requires that.  But that isn't what the IESG (and, at least to
some extent, the community) decided to with IANA2.  Trying to
change that retroactively would be even worse.

In the interim, if clarifications that are not in scope for
IASA2 are needed, there is a relatively lightweight mechanism
that would probably be considered the only appropriate one if
these suggestions were not emerging from the IESG.   Generate an
I-D that updates whatever comes out of IASA2, get some AD to
sponsor it, push it through IETF LC, and move on.


--On Saturday, July 6, 2019 08:10 +1200 Brian E Carpenter
<> wrote:

> I'm with Alissa on this. There are quite a lot of reasons why
> we might need RFC7437bisbis, some of which are much more
> serious than the various points raised by several ADs, but I
> believe we should first wrap up the changes required by the
> creation of IETF LLC.
> I don't think rechartering IASA2 for this purpose would be
> appropriate at all. Starting a process that might lead to a new
> version of the POISED, POISED95 or POISSON WG would seem more
> suitable. See
> for example.
> Regards
>    Brian Carpenter
> On 06-Jul-19 06:41, Alissa Cooper wrote:
>> Dear IESG,
>> I wanted to draw your special attention to this text in
>> draft-ietf-iasa2-rfc7437bis:
>> "This revision addresses only the changes required for IASA
>> 2.0; should the community agree on other changes, they will
>>    be addressed in future documents."
>> As well as this text in the IASA2 WG charter:
>> "This working group is chartered to document the normative
>> changes to IETF administrative structures and processes
>> necessary to effectuate [the change to IASA 2.0]."
>> If the IESG is not going to allow draft-ietf-iasa2-rfc7437bis
>> or other IASA2 documents to progress unless changes unrelated
>> to IASA 2.0 are made, I think the WG needs to be rechartered.
>> The authors and the WG purposefully did not make any other
>> changes to the base documents, so making other changes as a
>> result of IESG evaluation does not seem appropriate. I think
>> the appropriate thing to do would be for ADs who want to see
>> that happen to start a thread about re-chartering on the
>> iasa20 list. (Note: this is not my preference since I suspect
>> it will delay the minimal changes related to IASA 2.0 from
>> being published for a long time, but if that's what the
>> community wants I'll support it.)
>> Thanks,
>> Alissa
>> _______________________________________________
>> iasa20 mailing list
> _______________________________________________
> iasa20 mailing list