IETF Logo Mail Archive

Re: AD Sponsorship of draft-moonesamy-recall-rev

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 24 April 2019 23:17 UTC

Return-Path: <jmh@joelhalpern.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 AD0A7120108 for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 16:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] 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 gyjELxh6VwiV for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 16:17:22 -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 6894D1200E3 for <ietf@ietf.org>; Wed, 24 Apr 2019 16:17:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 44qGS22LMgz18Gvt; Wed, 24 Apr 2019 16:17:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1556147842; bh=qncPrF8r8tpksIrassvltNBBoCC8TofPKVkwpvKCcsQ=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Z2rGSdGoL5cpWKVzVCkGXXA0OS9CKsyPXOjweYoSTnUHSj53BhWMQBDVVXYqsh242 CVDPPwj+Ea6MEtHaTbQFUZDuSqi3CTHacEkAKpY6sUSSauSF+iG2P0FJB7FzRJIguq b8GLF/bQIYVmmQvLPQSPJHxr9JCoElKtq/gAPFiY=
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 44qGS15G4sz18GvS; Wed, 24 Apr 2019 16:17:21 -0700 (PDT)
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: "Salz, Rich" <rsalz@akamai.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <033d01d4f52f$c6f2dca0$54d895e0$@olddog.co.uk> <C7274EAB-7DDC-491F-9DD2-0CFFADB13CA9@cooperw.in> <72f00d0b-7ec6-ba6a-b17b-97879d457ae3@comcast.net> <CAKKJt-fOMMdM-mkbJaYpsH6XPCpatUkwZY-d_A+MaNa3nhaNDg@mail.gmail.com> <CABcZeBNdaWU4wwOK_MnWC5hOr7Lu3osmC_6_KKxB5fHuHVHyTw@mail.gmail.com> <23d54797-5c94-aa00-ec55-3f2c4fdfcfae@comcast.net> <6.2.5.6.2.20190424095017.13cdadc8@elandnews.com> <51068F13-E90F-42A2-8AE2-627D5E18B145@akamai.com> <20190424201939.GM3137@localhost> <6.2.5.6.2.20190424134823.0c9faf68@elandnews.com> <20190424211123.GO3137@localhost> <6.2.5.6.2.20190424144539.0cabcde0@elandnews.com> <20F28A58-4D1D-40D7-8513-2DA7A4A8778C@akamai.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <ad42a410-8f6c-b28a-9a7f-bf546ce2fcd7@joelhalpern.com>
Date: Wed, 24 Apr 2019 19:17:20 -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: <20F28A58-4D1D-40D7-8513-2DA7A4A8778C@akamai.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vORgW1ecFsYGsvWpvJBBfOUFSS8>
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: Wed, 24 Apr 2019 23:17:24 -0000

The proposed alternative I thought I saw was to
a) establish a mailing list (because we do not like holding discussions 
of specific documents on the IETF list)
b) hold some explicit virtual sessions to discuss the draft

Given how small and focused the draft is, creating a working group seems 
rather odd.
Making even small process changes in the IETF is hard.  The handling of 
this seems designed to make it even harder.  Note: I do not believe that 
is the actual intent of the responders.  It is however the apparent result.

Yours,
Joel

On 4/24/19 6:53 PM, Salz, Rich wrote:
>>     It doesn't make sense to ask a person who lacks extensive travel
>      resources to fly to Canada to hold a BoF about a short draft.
>    
> I understand the situation, and having been in that place for years, am empathetic.
> 
> But the proposed alternative seems to be "take my draft as-is"
>

v2.23.0 | Report a Bug | By Email