Re: [Iasa20] 6635bis

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 29 April 2019 17:51 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD901204A8 for <iasa20@ietfa.amsl.com>; Mon, 29 Apr 2019 10:51:09 -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 (1024-bit key) header.d=joelhalpern.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 1luKLIQxh8tY for <iasa20@ietfa.amsl.com>; Mon, 29 Apr 2019 10:51:06 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 71EA11200CD for <iasa20@ietf.org>; Mon, 29 Apr 2019 10:51:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 44tBzG2HpMzyfqn; Mon, 29 Apr 2019 10:51:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1556560266; bh=pJD9g41OVJ+VjnJeegMYXbz/njYdN+ldIE5fcVJysJk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=MT3v8V14UV+YcSw14kSlKP2m39NNOT/Gg8ufhiO8TOJgWyJPw8D7mRR58DvChRMvW lIu5hGeDx8PSZHh+Bb4Cb23gKYieQRMNgEtjgQmmpLeOFi6hXB5fUrX02Jl6j2Ah0C l7SLqOWG63kXA/DJxeYTRFh1s/IzjQwj1542FH8w=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 44tBzF5h6jzyfqh; Mon, 29 Apr 2019 10:51:05 -0700 (PDT)
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IASA 2 WG <iasa20@ietf.org>
References: <20190426211900.555852012FE081@ary.qy> <22f00e3c-faa1-2eb3-ad38-97f6fb743aac@joelhalpern.com> <alpine.OSX.2.21.1904261835490.29589@ary.qy> <c2a25515-b5cc-13f9-cdf9-058170194d1f@joelhalpern.com> <A0C444C3-8184-4117-B3D4-9F58584292FD@cooperw.in> <daf8ee48-91fa-4a29-9ca8-8e348ed8e0cd@joelhalpern.com> <AD0195AF-98EA-4753-8CDE-B31A6D8FFF67@cooperw.in> <CA+9kkMB2bXoWLLjA_UGot8t5WY4yR7XJjB19XSoLq-bp+VQ0vg@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <ecc3222c-361f-c881-70c0-96e805d8874a@joelhalpern.com>
Date: Mon, 29 Apr 2019 13:51:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <CA+9kkMB2bXoWLLjA_UGot8t5WY4yR7XJjB19XSoLq-bp+VQ0vg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/3SydK4Jl9vEsgiAPPLD0gx3RgUI>
Subject: Re: [Iasa20] 6635bis
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 17:51:09 -0000

Your comment at the end about further discussion goes directly to the 
issue of scope.
People have joined this list for specific purposes.  That purp[ose does 
not include policy changes.  Much less policy changes regarding the RSE.

So no, I do not see how discussion on this list takes care of the need 
for discussion elsewhere after we know what the IAB actually wants to do.

It was specifically brought forward, and has been defended by some 
participants on this list, as being a minor procedural matter.  While 
small, it does have significant implications.  As such, it is not a 
procedural matter.

----

If this is the correct place for discussion, then I would have expected 
to see meaningful answers to the substantive concerns about this proposal.

Yours,
Joel

On 4/29/19 12:27 PM, Ted Hardie wrote:
> Howdy,
> 
> (much snipped)
> 
> On Mon, Apr 29, 2019 at 7:30 AM Alissa Cooper <alissa@cooperw.in 
> <mailto:alissa@cooperw.in>> wrote:
> 
> 
>     My point is that while there will not be a WG consensus call on this
>     document, I think it is helpful to have this group discuss the
>     document since the expertise is here and the document’s whole reason
>     for being is the same as this WG’s reason for being.
> 
>     As I noted in my prior mail, I thought the plan for this doc and the
>     other IAB stream bis documents was to discuss them here prior to the
>     IAB running its usual call for community comment for IAB stream
>     documents. This is my understanding from talking to Ted.
> 
> 
> This is also my understanding.  Any discussion that happens here is 
> useful in getting community issues in focus early, so that those are 
> clear when the IAB does its review and interprets comments that come in 
> during the community review period.
> 
> As an individual, I appreciated Sean bringing the issue up here, because 
> it seemed useful to have the discussion in a larger setting before the 
> IAB review.   I believe we will not need to repeat this discussion again 
> when the community review occurs, as the document should reflect the 
> results of the discussion by the time it goes to the IAB.
> 
> regards
> 
> Ted
> 
> 
> 
> 
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>