Re: [lisp] LISP standardization request from ICAO WG-I

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 08 April 2022 15:14 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9678A3A0A6C; Fri, 8 Apr 2022 08:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 RI4rS-UmfcoX; Fri, 8 Apr 2022 08:14:16 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 580933A0908; Fri, 8 Apr 2022 08:14:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4KZhc72RDCz1pKHf; Fri, 8 Apr 2022 08:14:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1649430855; bh=w4O0SiJWJCiCfTL+1BKuZUp0HUc1xBgc3ZcaOOso9V4=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=rEAwEF0jNieyhmSGb39A8L762nilVtevuiFPa8o5e4n5nV2xjNxF7ywP1QhDeJkTx hLmLqkaiilhPkRUa3O43sEqStmW0HJm36MdXa9Jxjkk+KdxaVz7g78NgcJrkv9RvAW O9zhGcDulB9xvOz7B9CgJ1fBollympWlSTYsfTz4=
X-Quarantine-ID: <GIm-xL29VOan>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4KZhc34Vzjz1pGcy; Fri, 8 Apr 2022 08:14:11 -0700 (PDT)
Message-ID: <dd6d9ef8-e53a-b3dd-2f08-e79f7ff78647@joelhalpern.com>
Date: Fri, 08 Apr 2022 11:14:09 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: "Gulam, Raza Ali" <RGulam@icao.int>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Cc: POPESCU Liviu <Liviu.POPESCU@eurocontrol.int>, HAINDL Bernhard <Bernhard.HAINDL@frequentis.com>, "lisp@ietf.org" <lisp@ietf.org>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "Jonasson, Loftur" <LJonasson@icao.int>, "'danny.bharj@inmarsat.com'" <danny.bharj@inmarsat.com>, "'Noppadol Pringvanich (IATA)'" <pringvanin@iata.org>
References: <c403cf34a7b64bfeb8e8236ab4b29b70@icao.int>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <c403cf34a7b64bfeb8e8236ab4b29b70@icao.int>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/HDXbJka7h3eQ-M-JtnawTZaaMZg>
Subject: Re: [lisp] LISP standardization request from ICAO WG-I
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Apr 2022 15:14:21 -0000

Thank you for your interest in the LISP work.

First, I recommend that anyone interested in IETF work read 
https://www.ietf.org/tao.html as that will give you a better 
understanding of the IETF process.

The IETF is in the process of moving the base LISP specifications from 
experimental to Proposed Standard.  While I can not promise when that 
will happen, we certainly hope it will be completed before 3Q2022.
Note that if the documents are approved, but have not yet been published 
as RFCs, there are ways we can get you the RFC numbers.
But until the approval process is complete we can not commit to anything.

Yours,
Joel

On 4/7/2022 6:02 PM, Gulam, Raza Ali wrote:
> Dear All,
> 
> WG-I is a working group of the ICAO (International Civil Aviation 
> Organization) Communications Panel and is concerned with the 
> standardization of ATNIPS for safety-critical IPv6 communications in 
> aviation.
> 
> The necessary data communication protocols and services are defined in 
> Doc 9896 - Manual on the Aeronautical Network (ATN) using Internet 
> Protocol Suite (IPS) Standards and Protocols.
> 
> For the realization of the mobility and multilink functionality, Doc 
> 9896 Edition 3 proposes a solution that uses LISP as the base 
> technology. Such base technologies must be mature and should be based on 
> IP standards.
> 
> This results in the following standardization request:
> 
> The ICAO WG-I requests the IETF to complete the standardization for the 
> LISP control and data plane draft protocols (draft-ietf-lisp-rfc6830bis 
> and draft-ietf-lisp-rfc6833bis) by the third quarter of 2022
> 
> so that the corresponding RFC standards can be referenced in Edition 3 
> of the ICAO Doc 9896.
> 
> If you need any further information please contact the undersigned.
> 
> Thank you,
> 
> Yours sincerely,
> 
> Raza Gulam
> 
> Secretary, Data Communications Infrastructure
> 
> Specific Working Group of the Communications Panel
> 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp