Re: Sergeant-at-Armss and New proposal/New SOW comment period

Bob Hinden <bob.hinden@gmail.com> Sat, 31 August 2019 15:18 UTC

Return-Path: <bob.hinden@gmail.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 23471120096 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2019 08:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 exdhIZgqs4k2 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2019 08:18:06 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60EE91200C4 for <ietf@ietf.org>; Sat, 31 Aug 2019 08:18:06 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id l11so940349wrx.5 for <ietf@ietf.org>; Sat, 31 Aug 2019 08:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nCqTRZEpalsrz2EWKIrlLkir1VhZbErC26nTr0rkkP0=; b=CM3wOu6NUoN3lghBjV92tphwnnbTNYUMahA8Zr96NlLNyHKLCIXPkj20ETiPSN/vh+ 61aR2aBW1RXQT7kzq4ZyyqQy6v//uHLZwAY3xnTz36OXi1ExmQPjLyoAsNSylG4LiCrB 8WN60OeOpaJXwj2b4xqCJx7D1OiNsd+0hB5/nMHPKnbsq29y6fD8Ws5nCOGhDHFCZgwz nAnCZyVILcRbDoVKGrxs3OT1d+K7LQrmLHjjl5xExOhhpBy+1h3/FJRiTUval6eEMeQb i+rnvv7u/wE9Suueru5GuZMdZ9JsMIzc1ZC8jhvdGmn1nISnmdksFG6+BaLskPuxm1nB 424Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nCqTRZEpalsrz2EWKIrlLkir1VhZbErC26nTr0rkkP0=; b=KJ9pqJmbEYNTN3ROjpd4Uh/BsFOmfv0G6e0u4tRhMo370DxP4SBUeoAC2cnv66ue4O 1VZlxZDcAz3ZM/lKxa/2E6g4Htm+8NgoqyDsZXLHr2UKiVX3VfjmvTDXmF8B8pGIs0By isuQ/xPHgI9z2PEQwfv01vJJjC73JaJWjA5rowVUD/9n4as03WVC2S4ua5lEKmig1VjA 1KslG3K3DcSQD7NiQkk4pVgYhWplckc2HJKOIMAC+W+2zcn+48jGdDdXP7XIq5lCn+Hh auf7w4SAu1ao5Yu+F84LHfA1eFXSSvbslfK0NYFUevpLj1I/xZq5oU9STYQwgvlmg9qi sHEw==
X-Gm-Message-State: APjAAAXb9wiDsXMdRIrJmjJFv57OM+2yaILPBGHsZV0nVtU+SN8m4khc KGnCIvQkFnaknGBnwtJMuxidd2w7
X-Google-Smtp-Source: APXvYqy0+El9qd2LSft4Mxx9f+QF4+q90XviL5L/dSrFZ2RaUf2hFToBrDUApXPRExVZ1f19/Um0uA==
X-Received: by 2002:adf:de8a:: with SMTP id w10mr14100426wrl.276.1567264684669; Sat, 31 Aug 2019 08:18:04 -0700 (PDT)
Received: from [10.0.0.199] (c-24-5-53-184.hsd1.ca.comcast.net. [24.5.53.184]) by smtp.gmail.com with ESMTPSA id e15sm9665579wrj.74.2019.08.31.08.18.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Aug 2019 08:18:04 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <A77DE8CF-3984-417C-A8AA-72AC86046A50@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_DE679C65-2284-4CE9-B13F-8E4C81621C49"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Sergeant-at-Armss and New proposal/New SOW comment period
Date: Sat, 31 Aug 2019 08:18:00 -0700
In-Reply-To: <6FA9D85E1B425914CA994AFD@PSB>
Cc: Bob Hinden <bob.hinden@gmail.com>, Eliot Lear <lear@cisco.com>, "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>, John C Klensin <john-ietf@jck.com>
To: IETF <ietf@ietf.org>
References: <061D2F46-71C3-4260-B203-73B07EB59418@encrypted.net> <5B276430-96A9-44EA-929B-B9C2325AFCA5@encrypted.net> <863c6fa8-2735-b2c6-5542-d5d100485a6e@outer-planes.net> <10843FAF-66D2-483D-96AB-2F993803AAC6@cisco.com> <6FA9D85E1B425914CA994AFD@PSB>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mi_YvsDmUbO_BImi8kaZzE3WDhM>
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: Sat, 31 Aug 2019 15:18:09 -0000

Hi,

> On Aug 31, 2019, at 5:54 AM, John C Klensin <john-ietf@jck.com> wrote:
> 
> (changing the subject line to try to avoid a nasty S/N problem)
> 
> --On Saturday, August 31, 2019 10:20 +0200 Eliot Lear
> <lear@cisco.com> wrote:
> 
>> Can the Sergeant-at-Arms please not be this trigger happy?
>> 
>> This was the focus of the discussion at the administrative
>> plenary, and deserves wide attention, in part because the
>> matter is urgent to close, given the limited period of time,
>> and quite frankly what Sarah is asking for amounts to last
>> call comments.  The IETF list has always welcomed those.  Do
>> we really need to reopen 3005 to make that point clearer?
> 
> Matthew,
> 
> I wouldn't have chosen "trigger happy" as a description, but I
> agree with Eliot and would go a bit further.  First, as he
> points out, this topic was of broad enough concern in Montreal,
> and drew enough list discussion in the prior weeks, to have
> dominated the administrative plenary. It is clearly of broad
> concern to the community and I appreciate Eliot's comparison to
> a Last Call.
> 
> There is, however, another issue: the rfc-interest list has
> traditionally focused on substantive issues with RFCs and the
> RFC Series, not personnel and administrative policies.  Pushing
> this discussion there is inconsistent with "Discussions that
> fall within the area of any working group or well established
> list" because this is not clearly within the area of that list.
> More important RFC 3005 clearly calls out "Discussion of IETF
> administrative policies" as an appropriate posting topic and
> this discussion is very much about administrative policies.
> 
> So, please reconsider your comment and back it out.  Where I
> disagree with Eliot is that, if you don't consider withdrawing
> your instruction appropriate, I think the appropriate action, at
> least in the short term, would not be to open 3005 but to appeal
> your decision.

I agree with Elliot, S. Moonesamy, and John.   The Sergeant-at-Arms email was ill considered and should be withdrawn.

Bob


> 
> thanks,
> 
>   john
> 
> 
>> On 31 Aug 2019, at 01:09, Matthew A. Miller
> <linuxwolf+ietf@outer-planes.net> wrote:
>> 
>> Please note that discussion on the Temporary RFC Series
> Project Manager
>> SOW should occur at < rfc-interest@rfc-editor.org >.  As per
> RFC 3005,
>> the general list is appropriate unless there is a more
> specific venue.
>> 
>> Information about the list, including how to subscribe, can be
> found at
>> < https://www.rfc-editor.org/mailman/listinfo/rfc-interest >.
>> 
>> 
>> Thank you,
>> 
>> - Matthew A. Miller
>> Sergeant-at-Arms
> 
> 
> 
>