IETF Logo Mail Archive

Re: Visas for IETF 103 in Thailand

Jared Mauch <jared@puck.nether.net> Wed, 15 August 2018 12:25 UTC

Return-Path: <jared@puck.nether.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 8B3E6130DBE; Wed, 15 Aug 2018 05:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 ZaoO1cJFi5By; Wed, 15 Aug 2018 05:25:57 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E23EC127148; Wed, 15 Aug 2018 05:25:56 -0700 (PDT)
Received: from [10.0.0.135] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 9DBA6540E91; Wed, 15 Aug 2018 08:25:53 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: Visas for IETF 103 in Thailand
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <C0533504-4EE0-44CB-AD42-7C5F1051AC2A@tzi.org>
Date: Wed, 15 Aug 2018 08:25:39 -0400
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, 103all@ietf.org, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <66B8DE05-EAFE-4655-A4C8-03B6EB00C92F@puck.nether.net>
References: <153426794535.27168.17582506604424633822.idtracker@ietfa.amsl.com> <CAA=duU0ijWy8hxRdDE0arC1MhBZwSt=YQSkC-bfZX8ySH5BqSw@mail.gmail.com> <20180814194722.GA16126@mx4.yitter.info> <C0533504-4EE0-44CB-AD42-7C5F1051AC2A@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y3dPv_TUXR-MfdjyN3h84uxHU6w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.27
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, 15 Aug 2018 12:25:59 -0000

When we went to Argentina things did change if you held a US passport. I had already paid my fee and then in the days up to the meeting things changed. 

Talk to your travel agent or use a visa service if necessary. Your unique situation may be different than me or someone else. International travel carries risks and you should know what those are before you leave home. 

I have been advised by CBSA agents that speaking at a conference in Canada would/should require a visa for example. Does this count as presenting at a WG meeting? IANAL, but you need to adjust your behaviors according to the laws of where you are. 

Importantly: you can always participate remotely. The tools are quite good

Jared Mauch

> On Aug 15, 2018, at 4:03 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> Yes, it would need to be qualified as “not legal advice”, “subject to change”, “void where prohibited”, etc.
> It would help if it contains pointers to authoritative information I can look up myself.

v2.23.0 | Report a Bug | By Email