Re: [Rum] Meetings at IETF104

James Hamlin <james.hamlin@purple.us> Mon, 25 March 2019 13:23 UTC

Return-Path: <james.hamlin@purple.us>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C8E1203E7 for <rum@ietfa.amsl.com>; Mon, 25 Mar 2019 06:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 FEqJOPQVPSc0 for <rum@ietfa.amsl.com>; Mon, 25 Mar 2019 06:23:36 -0700 (PDT)
Received: from 1pmail.ess.barracuda.com (1pmail.ess.barracuda.com [209.222.82.13]) (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 E7D101203F5 for <rum@ietf.org>; Mon, 25 Mar 2019 06:23:35 -0700 (PDT)
Received: from smtp.purple.us (unknown [208.17.91.143]) by mx12.us-east-2a.ess.aws.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NO); Mon, 25 Mar 2019 13:23:33 +0000
Received: from 1-WP-402-EXCH.purplenetwork.net (10.0.10.144) by 1-wp-401-exch.purplenetwork.net (10.0.10.143) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Mon, 25 Mar 2019 06:23:18 -0700
Received: from 1-WP-402-EXCH.purplenetwork.net ([fe80::a968:f529:2be7:c099]) by 1-wp-402-exch.purplenetwork.net ([fe80::a968:f529:2be7:c099%27]) with mapi id 15.00.1263.000; Mon, 25 Mar 2019 06:23:18 -0700
From: James Hamlin <james.hamlin@purple.us>
To: "rum@ietf.org" <rum@ietf.org>
Thread-Topic: [Rum] Meetings at IETF104
Thread-Index: AQHU4wyLTWP94wHN/kCw/NwPiUBHcg==
Date: Mon, 25 Mar 2019 13:23:17 +0000
Message-ID: <1553520197778.78802@purple.us>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.0.10.15]
Content-Type: multipart/alternative; boundary="_000_155352019777878802purpleus_"
MIME-Version: 1.0
X-BESS-ID: 1553520198-893022-7833-64452-1
X-BESS-VER: 2019.1_20190322.2057
X-BESS-Apparent-Source-IP: 208.17.91.143
X-BESS-Outbound-Spam-Score: 0.00
X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.211017 [from cloudscan23.us-east-2b.ess.aws.cudaops.com] Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message 0.00 BSF_BESS_OUTBOUND META: BESS Outbound
X-BESS-Outbound-Spam-Status: SCORE=0.00 using global scores of KILL_LEVEL=7.0 tests=HTML_MESSAGE, BSF_BESS_OUTBOUND
X-BESS-BRTS-Status: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/qF4JHtlKBP3vJ3V3SNaEY9X2Cao>
Subject: Re: [Rum] Meetings at IETF104
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Mar 2019 13:28:32 -0000

Brian


As this meeting has been announced at very short notice, it has not been possible for VRS relay providers to attend. VRS relay providers have a considerable interest in this work, and so remote access would be in the interests of inclusive discussion.

Would it be possible for remote access to be arranged at this stage? Also, is there any more agenda information? I see a one hour slot (10-11 CET) described "

Rum organizational, cont from DISPATCH".


Best regards


James


----

We have a slot in DISPATCH agenda on Monday morning.  We also have the Paris meeting room reserved at 10 AM.  There is no Meetecho or other remote service available for the Wednesday meeting, sorry.

Brian