[ipwave] ITU-R liaison statement 1686

housley@vigilsec.com Fri, 16 October 2020 19:05 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3EB53A0898 for <its@ietfa.amsl.com>; Fri, 16 Oct 2020 12:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 p2ENCZ5jBbSn for <its@ietfa.amsl.com>; Fri, 16 Oct 2020 12:05:09 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ED353A0876 for <its@ietf.org>; Fri, 16 Oct 2020 12:05:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 008F5300B7E for <its@ietf.org>; Fri, 16 Oct 2020 15:05:06 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dL6pY4iExc53 for <its@ietf.org>; Fri, 16 Oct 2020 15:05:05 -0400 (EDT)
Received: from mail.smeinc.net (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTPSA id D283F300A91; Fri, 16 Oct 2020 15:05:05 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 16 Oct 2020 15:05:05 -0400
From: housley@vigilsec.com
To: its@ietf.org
Cc: scott.mansfield@ericsson.com
In-Reply-To: <4725B596-F5FA-49F9-A312-BC40CD053F23@kuehlewind.net>
References: <4725B596-F5FA-49F9-A312-BC40CD053F23@kuehlewind.net>
Message-ID: <9af15ae85892d25b98fc6dda98a8851c@vigilsec.com>
X-Sender: housley@vigilsec.com
User-Agent: Roundcube Webmail
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/Yx-12cm6A7IqJg3PBTlGC4vzJMA>
Subject: [ipwave] ITU-R liaison statement 1686
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 19:05:11 -0000

The ITU-R sent a liaison: https://datatracker.ietf.org/liaison/1686/

Does anyone think that the IPWAVE WG should reply?

Russ