Re: [ieee-ietf-coord] So, what is actually happening in Bangkok, between the end of IETF 103 and the beginning of IEEE 802? :-)

Lou Berger <lberger@labn.net> Thu, 30 August 2018 13:11 UTC

Return-Path: <lberger@labn.net>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C083D130F55 for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 30 Aug 2018 06:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 pafDIptYKC0r for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 30 Aug 2018 06:11:24 -0700 (PDT)
Received: from gproxy2-pub.mail.unifiedlayer.com (gproxy2-pub.mail.unifiedlayer.com [69.89.18.3]) (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 DBC00130F41 for <ieee-ietf-coord@ietf.org>; Thu, 30 Aug 2018 06:11:24 -0700 (PDT)
Received: from cmgw10.unifiedlayer.com (unknown [10.9.0.10]) by gproxy2.mail.unifiedlayer.com (Postfix) with ESMTP id 6A0251E0AFB for <ieee-ietf-coord@ietf.org>; Thu, 30 Aug 2018 07:11:23 -0600 (MDT)
Received: from box313.bluehost.com ([69.89.31.113]) by cmsmtp with ESMTP id vMfvfeABzuL2QvMhCf8cjQ; Thu, 30 Aug 2018 07:09:39 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: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=NEp4uKFuAj/o2xc6QQ+kmwB49m8zP3kAzTU1EeDYv2o=; b=n44OAhdD3yuX4S5RC3+i078vl/ EborzV/5XEbRlFzWfhyjTbLDW7evOEXR3zv5ajfGptiXns0cwp8Fp8ERScLWebeFZTvQ62MZ80FjF M5YRgtr9uT1nEuqQeJMJhtVqI;
Received: from pool-100-15-106-211.washdc.fios.verizon.net ([100.15.106.211]:59636 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <lberger@labn.net>) id 1fvMfs-000Gxh-5p; Thu, 30 Aug 2018 07:07:50 -0600
To: Russ Housley <housley@vigilsec.com>
Cc: "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
References: <CAKKJt-eHd6ekKJkM9NVn2WFdN0Vd65fY8LamEgyxsT3LT050SQ@mail.gmail.com> <0AACBDAF-CC06-4831-9620-1E8CC802B58D@vigilsec.com>
From: Lou Berger <lberger@labn.net>
Message-ID: <31783320-3934-87c4-5f6d-2c21aab1cf45@labn.net>
Date: Thu, 30 Aug 2018 09:07:42 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <0AACBDAF-CC06-4831-9620-1E8CC802B58D@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
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: 100.15.106.211
X-Source-L: No
X-Exim-ID: 1fvMfs-000Gxh-5p
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-15-106-211.washdc.fios.verizon.net ([IPv6:::1]) [100.15.106.211]:59636
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/ieee-ietf-coord/ydsxEZFO3qikSBZEslU5SnVzL2A>
Subject: Re: [ieee-ietf-coord] So, what is actually happening in Bangkok, between the end of IETF 103 and the beginning of IEEE 802? :-)
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Aug 2018 13:11:36 -0000


On 8/29/2018 5:02 PM, Russ Housley wrote:
> ...
> There will also be a joint DETNET TSN meeting.  It will be the other half of Saturday and it might use part of Sunday too.

Hi Russ,

Jon's mail is correct.  The joint DETNET TSN meeting is only on Sunday.

Lou