IETF Logo Mail Archive

RE: Q3 2018 interim planning

"Roni Even (A)" <roni.even@huawei.com> Thu, 31 May 2018 06:05 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1500412EC54 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 23:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 r69JTz3vInPN for <quic@ietfa.amsl.com>; Wed, 30 May 2018 23:05:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 0FF7D12EBEE for <quic@ietf.org>; Wed, 30 May 2018 23:05:36 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9A68CE51D32A9 for <quic@ietf.org>; Thu, 31 May 2018 07:05:32 +0100 (IST)
Received: from DGGEMM424-HUB.china.huawei.com (10.1.198.41) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 31 May 2018 07:05:34 +0100
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.90]) by dggemm424-hub.china.huawei.com ([10.1.198.41]) with mapi id 14.03.0382.000; Thu, 31 May 2018 14:05:31 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Mark Nottingham <mnot@mnot.net>
CC: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Subject: RE: Q3 2018 interim planning
Thread-Topic: Q3 2018 interim planning
Thread-Index: AQHT+I6BB6f69JIiQkKY2HkegPmFYaRJSVAw//+HdACAAIgjQA==
Date: Thu, 31 May 2018 06:05:31 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD891AAE@DGGEMM506-MBS.china.huawei.com>
References: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com> <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
In-Reply-To: <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.203.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/T_WH23q5kNN15tI5dBMnifRTLpg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 06:05:38 -0000

Hi Mark,

> 
> 1. The Jewish holidays are in September so I hope that the meeting 
> will take place after September 20th 2. I may have problem if the meeting will be in a city where hotel prices are expensive (e.g. New York) so expect that the city selection will also consider hotel prices.

We're aware of many potential conflicts and cost sensitivities, and are doing our best to balance them. Please note that this is NOT a request for people to talk about availability / preferred locations.

RE - if you are mentioning someone problem with travel out of the US as a reason for meeting in the US,  you are talking about availability/preferred locations 

> 3. I do not understand what it means "cannot get out of the US due to visa problem"  ; if someone does not have a legal status in the US I do not think that this should affect the meeting location.

We can't go into details without violating people's privacy, but I assure you it is possible.

Thanks,


> 
> Regards
> Roni Even
>

v2.23.0 | Report a Bug | By Email