Re: [Raw] Alvaro Retana's Discuss on draft-ietf-raw-ldacs-10: (with DISCUSS)
Alvaro Retana <aretana.ietf@gmail.com> Tue, 19 April 2022 16:09 UTC
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: raw@ietfa.amsl.com
Delivered-To: raw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8063A0C1E; Tue, 19 Apr 2022 09:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, RCVD_IN_DNSWL_HI=-5, 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 oHWwT_qYSiku; Tue, 19 Apr 2022 09:09:40 -0700 (PDT)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 8CD833A0C33; Tue, 19 Apr 2022 09:09:40 -0700 (PDT)
Received: by mail-wm1-x336.google.com with SMTP id r187-20020a1c44c4000000b0038ccb70e239so1893603wma.3; Tue, 19 Apr 2022 09:09:40 -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:content-transfer-encoding; bh=KFcOEVbz8JEOSeMNMgt2sQc9egdGKoC1olxcb1wcaXg=; b=E8/MRfLuIAixqnrkIThQlMdDQq5GiN8giI7aMFIFTdJNwTdewqcoGfNvxRFVNFTdYL fw3bvp8dkvR7BI4M7unSNy4qpzElSuw9zWPbwMlfgR01L/ZtoXQ7e0BBFokNT2MpKhBD ftzy7i6ryFouN49i/sbXEeiZsRhE9tKL42kUGhbJhjTYqxd1Dr/y/NhoAM6Pq3oe02Ge u+PsJW+EV7U7D2QJ+Oi2tsmZF3Gl5yItlB6q7XrpLRWymqbzxWI+IMxYpk+FOqifLTHm fbee4738aXOvX5NH95p5vJfusHEGwgdxC1D6wjkYzXhAlB+jJwSuvxbCmVcXt610NfzX qypA==
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:content-transfer-encoding; bh=KFcOEVbz8JEOSeMNMgt2sQc9egdGKoC1olxcb1wcaXg=; b=iV5H3r4iU2DjECPLsc37KS25Xs/zNfCjtP8qdxmI1xPhiEk+Ch3+JeVrOFjLmpjrkl ZckKzr3Jv5RUDDKuprufFDNIjskDr59ZuOMiIA/gAHQdceBSA7O3tNVjvXdaaA5zWvF6 nCkPKcfahCT9Dcg1DO+VWjAru200FARnx4aQZ6Ykfz+21HRXoYto9l3q4sCsW86gsQ9h 7pFSOlPloqx2MDMHswvD6SNT0A7VHjCMWCIZFuJKTuTiWdOKr0J9sf816ns/ZxsuRLIZ wylhCVpfebF46XS3AOvMkmoariHfFAmxxUhFBiGk0DYDTXRUVBJYIwjcPXB6abb2nV5p jveQ==
X-Gm-Message-State: AOAM532Icrem1nKzMCBcsIM19QVGO+seFf6ucA67eljT++l4dqJaPds1 rauaHvaAcIyPRKDEgbmgrtVgLA0RDLSSajlIsgg=
X-Google-Smtp-Source: ABdhPJx2BejecaiSsSgO1W/Xxus2g2RvESgMcRL6isHV6GXK9lfDjHuJA0/sfSTDHE6afjgznq3ch3JEAEZ5AGWpPC4=
X-Received: by 2002:a05:600c:3b28:b0:38e:bb86:d68d with SMTP id m40-20020a05600c3b2800b0038ebb86d68dmr16674285wms.135.1650384578257; Tue, 19 Apr 2022 09:09:38 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 19 Apr 2022 18:09:37 +0200
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <10B10647-9FD2-48C1-B574-F907004445EE@juniper.net>
References: <165029599971.2585.13528595173373019708@ietfa.amsl.com> <10B10647-9FD2-48C1-B574-F907004445EE@juniper.net>
MIME-Version: 1.0
Date: Tue, 19 Apr 2022 18:09:37 +0200
Message-ID: <CAMMESsxLaxR+RYxhvrbTmZ2Juj-37yFvQHGDsoZFZaNBWUjH_w@mail.gmail.com>
To: John Scudder <jgs@juniper.net>
Cc: "draft-ietf-raw-ldacs@ietf.org" <draft-ietf-raw-ldacs@ietf.org>, "pthubert@cisco.com" <pthubert@cisco.com>, "raw-chairs@ietf.org" <raw-chairs@ietf.org>, The IESG <iesg@ietf.org>, "raw@ietf.org" <raw@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/raw/6JwTkS3s7InkqbDabPVt10MVa-0>
Subject: Re: [Raw] Alvaro Retana's Discuss on draft-ietf-raw-ldacs-10: (with DISCUSS)
X-BeenThere: raw@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: reliable and available wireless <raw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/raw>, <mailto:raw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/raw/>
List-Post: <mailto:raw@ietf.org>
List-Help: <mailto:raw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/raw>, <mailto:raw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2022 16:09:43 -0000
On April 18, 2022 at 5:37:06 PM, John Scudder wrote: John: Hi! > I’m a little unclear as to your reasoning, let me see if I have it right: > > 1. You’re making the assertion that it’s not possible for the IETF to “reach > rough consensus on a document that describes someone else's technology”. As I > understand it, you’re not citing an authority for this — you just think it’s > self-evident, like the statement “rain doesn’t fall up”. When I read rfc2418, the discussions around consensus are related to addressing disagreements about the topic the WG was chartered for. In general, that topic is technology development, so disagreements are usually about design choices, deployment options, etc. In the case of LDACS, the WG is not chartered nor is working on developing it. While people may express concerns about the technical choices made, any resolution would happen outside the IETF. Also compelling to me is this question that I found as one of the issues to consider when creating a WG (§2.1/rfc2418): - Does the IETF have a reasonable role to play in the determination of the technology? There are many Internet-related technologies that may be interesting to IETF members but in some cases the IETF may not be in a position to effect the course of the technology in the "real world". This can happen, for example, if the technology is being developed by another standards body or an industry consortium. I believe this point is significant because it clarifies that the IETF should not be working on technology developed elsewhere. To quote one of the authors: the "LDACS specification is written within the framework of the Single European Sky ATM Research (SESAR) project" [1]. [1] https://mailarchive.ietf.org/arch/msg/raw/iyext4Ub8MgUjNYYPE7XOPpq1Y0/ ... > In any case we agree that the document should be published in some stream. Yes, I believe the Independent Stream would be appropriate. Alvaro.
- [Raw] Alvaro Retana's Discuss on draft-ietf-raw-l… Alvaro Retana via Datatracker
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… John Scudder
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Erik Kline
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Eric Vyncke (evyncke)
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Rob Wilton (rwilton)
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Alvaro Retana
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Pascal Thubert (pthubert)
- Re: [Raw] Alvaro Retana's Discuss on draft-ietf-r… Rick Taylor