Re: IETF 107 Standard Registration and Internet Draft Deadline Approaching

Lou Berger <lberger@labn.net> Fri, 06 March 2020 12:13 UTC

Return-Path: <lberger@labn.net>
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 0FD693A0DFB for <ietf@ietfa.amsl.com>; Fri, 6 Mar 2020 04:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.net
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 9YgSH3jLPGv6 for <ietf@ietfa.amsl.com>; Fri, 6 Mar 2020 04:13:09 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) (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 DD0153A0DF5 for <ietf@ietf.org>; Fri, 6 Mar 2020 04:13:08 -0800 (PST)
Received: from cmgw10.unifiedlayer.com (unknown [10.9.0.10]) by gproxy9.mail.unifiedlayer.com (Postfix) with ESMTP id 469B81E08EE for <ietf@ietf.org>; Fri, 6 Mar 2020 05:12:58 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id ABqcjuf2URlnNABqcjzxS3; Fri, 06 Mar 2020 05:12:58 -0700
X-Authority-Reason: nr=8
X-Authority-Analysis: v=2.3 cv=PvO9kTE3 c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=dLZJa+xiwSxG16/P+YVxDGlgEgI=:19 a=SS2py6AdgQ4A:10:nop_rcvd_month_year a=Vy_oeq2dmq0A:10:endurance_base64_authed_username_1 a=r77TgQKjGQsHNAKrUKIA:9 a=48vgC7mUAAAA:8 a=wU2YTnxGAAAA:8 a=gKmFwSsBAAAA:8 a=AHLsfpCemTfWOUn8EqcA:9 a=xpCOIoiNDmxyUA0A:21 a=2SQA2h8FpEJg1TUm:21 a=QEXdDO2ut3YA:10:nop_charset_2 a=rFTyi0wc2-xCzAz7owEA:9 a=riiiziiJvZg15LGd:21 a=25G5qyY-dUob8LFo:21 a=ShKMhXEyg09nRiRN:21 a=_W_S_7VecoQA:10:nop_html a=w1C3t2QeGrPiZgrLijVG:22 a=Yz9wTY_ffGCQnEDHKrcv:22 a=nnPW6aIcBuj1ljLj_o6Q:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Type:MIME-Version:Subject:References:In-Reply-To: Message-ID:Date:CC:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=duI7hmtTl1l3MvaN27jKDcRQ6G6ERW/MPDS7ngw3vkA=; b=aET5WYBtdt/N5ko6TqXvpfCAke 9bRlDdbHHixqGS1Q/SBJ1XinXv3o6iRdUs7CGB9+QU3opnEZ3O5gxqW+9mLRYEfIrdWO3CZiM6hcA y3j7hMjh6f/MXqyRANGZ62Wsp;
Received: from pool-72-66-11-201.washdc.fios.verizon.net ([72.66.11.201]:52162 helo=[11.5.0.140]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <lberger@labn.net>) id 1jABqb-000LJ5-QW; Fri, 06 Mar 2020 05:12:57 -0700
From: Lou Berger <lberger@labn.net>
To: Jay Daley <jay@ietf.org>
CC: Carsten Bormann <cabo@tzi.org>, IETF discussion list <ietf@ietf.org>, 107all@ietf.org
Date: Fri, 06 Mar 2020 07:12:55 -0500
Message-ID: <170afc34558.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <DCDA91A2-8CE1-4655-B6CD-B1C3CE3A2D59@ietf.org>
References: <170ad4f0938.277b.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <DCDA91A2-8CE1-4655-B6CD-B1C3CE3A2D59@ietf.org>
User-Agent: AquaMail/1.22.0-1511 (build: 102200004)
Subject: Re: IETF 107 Standard Registration and Internet Draft Deadline Approaching
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----------170afc348775683277b89c46c7"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 72.66.11.201
X-Source-L: No
X-Exim-ID: 1jABqb-000LJ5-QW
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-72-66-11-201.washdc.fios.verizon.net ([11.5.0.140]) [72.66.11.201]:52162
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3NMItdf08whSOyD0ORawv4JgsLA>
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: Fri, 06 Mar 2020 12:13:13 -0000

Jay,

Thanks for link, although it doesn't look like it is transparent on the 
full policy.  I'm not a big fan of arrangements where those who know a 
secret handshake get different treatment...

Lou


----------
On March 5, 2020 8:11:05 PM Jay Daley <jay@ietf.org> wrote:

> Lou
>
>> On 6/03/2020, at 1:46 PM, Lou Berger <lberger@labn.net> wrote:
>> 
>> 
>> Jay
>> 
>> ----------
>> On March 5, 2020 7:40:22 PM Jay Daley <jay@ietf.org> wrote:
>> 
>> > Lou
>> >
>> >
>> >> On 6/03/2020, at 1:33 PM, Lou Berger <lberger@labn.net> wrote:
>> >>
>> >> 
>> >> Jay,
>> >>
>> >> two very different points here:
>> >>
>> >> 1) Everyone's situation is different / unique and often more complicated 
>> than simply who is canceling. I  strongly urge you, the LLC and the iesg to 
>> have a single consistent, and public, refund policy for all.  (Either full 
>> refund for all or service charge for all).
>> >>
>> > I’m comfortable that our current policy strikes the right balance between 
>> an individual policy for each individual circumstance and a 
>> one-size-fits-all policy.
>> >
>> 
>> Can formally State / post what the policy is?. I think I heard if canceling 
>> due to the corporate policy, no refund. if individual is canceling and 
>> paying out of pocket or due to CA government action, full refund.
>> 
>> what about cancellation due to health issues?
>> 
> The special registration provisions are here 
> https://www.ietf.org/how/meetings/107/ietf107-special-registration-provisions/
>
> If anyone has a special circumstance which is not covered but they believe 
> it should be then they should let us know at ietf-registrar@ietf.org. If 
> your next question is why don’t we publish that, then the answer is because 
> people who are actually in that position do get in touch.
>
> Jay
>
> -- 
> Jay Daley
> IETF Executive Director
>
>> 
>> >> 2) have you checked on the legal exposure to the organization of 
>> continuing to hold the meeting in the face of so many public cancellations 
>> -  which are taking place at the organizational level (e.g., f8), the 
>> association level (IEEE, apc) and at the national level (CN and IS)?
>> >>
>> > Yes.
>> 
>> Very happy to hear that.
>> 
>> Thank you
>> Lou
>> 
>> 
>> >
>> > Jay
>> > --
>> > Jay Daley
>> > IETF Executive Director
>> >
>> >> Thanks,
>> >> Lou
>> >>
>> >>> On March 5, 2020 6:58:28 PM Jay Daley <jay@ietf.org> wrote:
>> >>>
>> >>>
>> >>>
>> >>>> On 6/03/2020, at 12:50 PM, Carsten Bormann <cabo@tzi.org> wrote:
>> >>>>
>> >>>> The difference should not be between corporate and government travel 
>> restrictions but between self-inflicted (company halts travel, company 
>> pays) and externally imposed (individual pays, employer still forbids 
>> travel; company pays, government forbids travel).
>> >>>
>> >>> I agree.
>> >>>
>> >>> Jay
>> >>>
>> >>>>
>> >>>> Grüße, Carsten
>> >>>>
>> >>>
>> >>> --
>> >>> Jay Daley
>> >>> IETF Executive Director
>> >>> jay@ietf.org
>> >>> +64 21 678840
>> >>>