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

Alvaro Retana <aretana.ietf@gmail.com> Fri, 08 April 2022 15:23 UTC

Return-Path: <aretana.ietf@gmail.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 C633E3A0E3E for <lisp@ietfa.amsl.com>; Fri, 8 Apr 2022 08:23:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sXCpm4ypLRq2 for <lisp@ietfa.amsl.com>; Fri, 8 Apr 2022 08:23:48 -0700 (PDT)
Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FE9D3A0E1D for <lisp@ietf.org>; Fri, 8 Apr 2022 08:23:48 -0700 (PDT)
Received: by mail-wr1-x42a.google.com with SMTP id m30so13466242wrb.1 for <lisp@ietf.org>; Fri, 08 Apr 2022 08:23:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=+cCxzaXaCHBxbNYIpKM8sIv7p/jOAxYO88HzFBzAtG0=; b=FKEakCToHFNqXNu+2clyYOv54RQw0qAl/ax08CQL4I9E2yINdJ67LCPAbcnQXtcr2I LjmeoB2nW4IbF06WPz+vzYaM5cuHHzmcPBiSbpBDyRQd4L+DVKA2nbAganG7g6kU3ITV Je/Kes6pf3Hh6r7qc9Sa9FUj4td+Cax0fQORZOwb64V4u+Or6UbqL3jZ1VJHrp4FHe2B +jYQsq2X4gaRJ+mgKp8H3DpRcrZrSmsaw0xqrpG2Z7sR6lodPWtXY9ul19ExuTqypTTj QVgHENpkTt0VlwUYW/rnkW4U5RdFVrakzi3qieMbc3mI7zxe9JVaiTibXdQRjhFVa9wJ KiZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=+cCxzaXaCHBxbNYIpKM8sIv7p/jOAxYO88HzFBzAtG0=; b=6xutCLQ3rJCo7/52umHvanE/tmmZN6GH83Q3qYIHh+/J9oLChEgZlIY3i1Tyq0zp9D FEOYesTbA/3WEC4U5LurlcbJVyEHxbPZnhjJ0M1TVY1xl9S0dz/sQnh3pMiMSeL+TrL2 BTDdsB9rpD9SFdWf4ShjZ4StYaVsk2BTeOCbqLYIM+RfVm2zq/vYe4s/1IZ8N2/4vRYp jFPqWUs2jmTaKjD7r/RoR4ETgxYmSiBJqpMLlGUcfjNRfGXrjIydnJD6AU7CqCkDJ6fS 5oaRDDkeRg9cYfswobSDFWk9l2m7GqCSUfYnm1KyAxBE0Q8RzxS50azik5vDGSiH9DtB tm+w==
X-Gm-Message-State: AOAM533OEbqmyWl11zrkx+MF4U28eUWUCIprvmCxQYL12cznRxFc5we9 8v7aEi0Oj7cIfzPsg/3KTVicUfERROub0nm+AA4=
X-Google-Smtp-Source: ABdhPJx5kAFZQyfCCT0ZAhtclNL+xLxDy85tHtofTVlJpaLIlZKxNOJu8VsOvQSkxBkC3kJFFSudRWcjfK7KPU+tJbA=
X-Received: by 2002:a5d:52d2:0:b0:207:97df:d166 with SMTP id r18-20020a5d52d2000000b0020797dfd166mr2601607wrv.356.1649431426638; Fri, 08 Apr 2022 08:23:46 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 8 Apr 2022 08:23:45 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <dd6d9ef8-e53a-b3dd-2f08-e79f7ff78647@joelhalpern.com>
References: <c403cf34a7b64bfeb8e8236ab4b29b70@icao.int> <dd6d9ef8-e53a-b3dd-2f08-e79f7ff78647@joelhalpern.com>
MIME-Version: 1.0
Date: Fri, 08 Apr 2022 08:23:45 -0700
Message-ID: <CAMMESsxJpUhu8-gnG-pAQH2ctj9QyJYWRKXNciYY-9dnrydimw@mail.gmail.com>
To: "Gulam, Raza Ali" <rgulam@icao.int>
Cc: HAINDL Bernhard <bernhard.haindl@frequentis.com>, POPESCU Liviu <liviu.popescu@eurocontrol.int>, "danny.bharj@inmarsat.com" <danny.bharj@inmarsat.com>, "Jonasson, Loftur" <ljonasson@icao.int>, "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "Noppadol Pringvanich (IATA)" <pringvanin@iata.org>, lisp-chairs@ietf.org
Content-Type: multipart/alternative; boundary="00000000000044261e05dc262efe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/9qXOSMqlYhK-_L6lfgjknXKomc8>
X-Mailman-Approved-At: Sat, 09 Apr 2022 13:43:33 -0700
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:23:54 -0000

[Thank you Joel!]

Dear Mr. Gulam:

As Joel explains, the IETF process is not deterministic.

To help me better understand ICAO’s requirements, I have a couple of
questions.  We may be able to have an RFC number for you sooner than a
published document — would that be enough?  The expectation would be to
have a published document soon after. Also, do you need the number by the
start of Q3 (July), or is there some flexibility.

Thank you!

Alvaro.
(Routing Area Director — responsible for the lisp WG)

On April 8, 2022 at 11:14:21 AM, Joel M. Halpern (jmh@joelhalpern.com)
wrote:

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