IETF Logo Mail Archive

Re: [Ietf108planning] Registration open for IETF 108

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 11 June 2020 19:28 UTC

Return-Path: <hallam@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 D097A3A07BF for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 12:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.396
X-Spam-Level:
X-Spam-Status: No, score=-1.396 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 aetv1qdePiPJ for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 12:28:03 -0700 (PDT)
Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) (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 1C60F3A07BE for <ietf@ietf.org>; Thu, 11 Jun 2020 12:28:03 -0700 (PDT)
Received: by mail-ot1-f52.google.com with SMTP id n70so5466828ota.5 for <ietf@ietf.org>; Thu, 11 Jun 2020 12:28:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SQfnzwUB6cjbnZ0GywaMcHTzuxkSYD00Wwb5bO6mmiM=; b=ucOn8we+EOXJKcj9fFnXVJ/mBqRwZthDnWj5oOvlIatNXhnSEMmgJfl6rWdt/pYRcu vWT6dVoNNi5Soh6yqYAgIAG9sJT1luRDthLozxmgv9s3oHBCKSnqfYTR2Nctj8ZdiqbE SfpMlqRsqBPZiV6NLGtqP22ZoSNtJd2/BBxAsln4zUtI5TVirEVrCOVlSkMgibUFLk0a i1cEewGd/JGmnjMBO9UMtNwnN800OCpU3cflC1pp7TWX4gNQg9KvZ9wgGwlufFyfAYHS KMNyN3mhsAvmoxG9A9UnxLvxI1XJGVTUl0wl+GhJItb4AIHQPqMXTyf+eav2joW+6Aqh pzSw==
X-Gm-Message-State: AOAM5330FuQAD/xqcevbU+siwDG03Ntw3k66pCZvzTii6C0ZSdLuGXOg yKwKJA4jiOwxP9wa3xt9mubJj5BXxAbizIZJ3Po=
X-Google-Smtp-Source: ABdhPJxEXlQl2+HrMhmepWWgHgHH3iojH3QvQ0i5IxeswaGSk71ruRAyGU7vQ3PNysw8cvr+b8TxsPtuF9hzARm4V74=
X-Received: by 2002:a9d:7e8d:: with SMTP id m13mr7772331otp.64.1591903682390; Thu, 11 Jun 2020 12:28:02 -0700 (PDT)
MIME-Version: 1.0
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <CAFgnS4WOjmNOf_MRfms1RD0e15xYP-xcfNiyqS7p5ofYBEQPdw@mail.gmail.com> <d65a8aeffc61b6d069afa87f3c91b10496c4d5b2.camel@lsl.digital> <5FCC8656386268B41681E1DE@PSB> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <46159495-3bef-be6d-31f7-1b83737359ad@gmail.com> <B6DFDB6D-7A97-4EE3-8554-6AF005C73EC3@ietf.org> <2a36750841d34cb99695077d60760ceb@att.com> <3949E994-C3BA-4392-BB1A-0D66EDE84065@vigilsec.com> <71021dea-5bf0-ac05-f9d7-cc7396540767@mtcc.com>
In-Reply-To: <71021dea-5bf0-ac05-f9d7-cc7396540767@mtcc.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 11 Jun 2020 15:27:51 -0400
Message-ID: <CAMm+LwjYh_y8ovKQ069zdSaEsun0q9FkNm7hLAv=KywcpkoRgQ@mail.gmail.com>
Subject: Re: [Ietf108planning] Registration open for IETF 108
To: Michael Thomas <mike@mtcc.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000081707205a7d3f5ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4A4h5KeXfACscYvhAFxnDVmZWjE>
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: Thu, 11 Jun 2020 19:28:05 -0000

On Thu, Jun 11, 2020 at 3:13 PM Michael Thomas <mike@mtcc.com> wrote:

>
> On 6/11/20 12:07 PM, Russ Housley wrote:
> >
> >> On Jun 11, 2020, at 2:42 PM, STARK, BARBARA H <bs7652@att.com> wrote:
> >> IETF likes to experiment. So we should experiment with a trust model.
> Trust that only those who need the waiver will request it, and see what
> happens.
> >> Barbara
> >
> > I really like this idea.
> >
> Not to be a wet blanket but what happens if corpro bean counters find
> out that they can game the system for the cost of a checkbox?
>

And what do the same bean counters say when it comes to sponsoring a coffee
break?

I really doubt that the issue is going to be 'bean counting'. A much bigger
issue for me has been everything I would ask for was an
extraordinary request. There is an overhead in terms of time and effort for
establishing a slot for a type of request.

When I was a student I found that it was often easier to get $50,000 than
$500.

v2.23.0 | Report a Bug | By Email