Re: [Idr] [EXTERNAL] Re: [Int-area] New Version Notification for draft-lhan-problems-requirements-satellite-net-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 10 July 2021 03:52 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEA33A191D; Fri, 9 Jul 2021 20:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.436
X-Spam-Level:
X-Spam-Status: No, score=-1.436 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, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.338, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 2GiWdtVNnRjJ; Fri, 9 Jul 2021 20:52:05 -0700 (PDT)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 8C48D3A191E; Fri, 9 Jul 2021 20:52:04 -0700 (PDT)
Received: by mail-pl1-x636.google.com with SMTP id p17so5518248plf.12; Fri, 09 Jul 2021 20:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=n7s0LWFdNhFwelOtbRFOM+XfmbPZs62qvamIWkNaDoM=; b=mDv0be2RLtLtFaXjcnsbT6rcRwJ3I2LSe1h3C9Hjdkvrq0VBCOMGGZYMaymfm2Wcl3 Eurv+XHL3Rt0wqvaQ8Q3gUM3gJdWMHF3P3FYr7ysyHjKycCqQMbYNyb6R3Uqa5Ezbm0Z kmfDTXICqCiy4/BCaG4YmLPcboAvJFBxSFheWpGd9xveBe9qejCNyuhqPn1daBF0OBCW GGetX6ocmsUhtp+CtKGdtKVqGWpn2a1wmDncHxbYR4Rdskum0oUkQ4hORpFgiSayK9t4 N38UHDCKho7Ec+5AsBaP/XX89cvwnEUv89dhC9cPrI4/r9sW2CyrCLlJbH88O+EBeJZW 5caA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=n7s0LWFdNhFwelOtbRFOM+XfmbPZs62qvamIWkNaDoM=; b=QfO05iGByjRYZJVJ9dAJvaajWvXgJ36L0Df+AeFoXZw2Jqfj3CFUx7UMiZYMpQcLoe UY4C8NUEremxl1joB8e9OkMfqsv2QC78x4IrANO2zdZAIYVDZnWbS3zUmfVTsedvCMsR VjYlkO15Bx+NEVzmUVXsi8pR5ycPhrDoyEziCJzzVzf4hvFYoTBvaf6dY0IEbcKQrbdg dNYge3+QJUlxx7nuJAq7Nqk/4CDcCuPyOSrnwIaU0jV8btFoOmfVTdcE0SodDyAiKhy/ W49M+T+olfjgIFohPolIGbIcwWrYCfyd0Zvbs1sD5dJJ+7/tt0clomBbMtZhuTOq23+p iFBg==
X-Gm-Message-State: AOAM530zT4zyXS2VS4UoQXFaFKKhTt+fVKqehsqEZ8WF6dSaSI17kEP7 L8OOAi3OzH0TkGdUoiUpWDzB51ocvHON7g==
X-Google-Smtp-Source: ABdhPJxyXDjzm1SSkWYvMOYK2hGeHF+UXe0cd9fx1+nKm1JD3hTbGvD7oou6qKDUZ2g4UFjPLzhung==
X-Received: by 2002:a17:90b:33c8:: with SMTP id lk8mr1585315pjb.0.1625889122905; Fri, 09 Jul 2021 20:52:02 -0700 (PDT)
Received: from ?IPv6:2406:e003:1188:5b01:80b2:5c79:2266:e431? ([2406:e003:1188:5b01:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id x6sm9669990pgq.67.2021.07.09.20.51.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Jul 2021 20:52:02 -0700 (PDT)
To: Alexander Vainshtein <Alexander.Vainshtein@rbbn.com>, Stewart Bryant <stewart.bryant@gmail.com>
Cc: Lin Han <lin.han@futurewei.com>, "idr@ietf.org" <idr@ietf.org>, INT Area <int-area@ietf.org>, "SARAH@jiscmail.ac.uk" <SARAH@jiscmail.ac.uk>, "UTTARO, JAMES" <ju1738@att.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
References: <BY5PR13MB3144786C6AB5D1008F34231AE9199@BY5PR13MB3144.namprd13.prod.outlook.com> <E30CBF32-962B-4FE1-B1D4-C2B0664EFC20@gmail.com> <CANMZLAaDSv+P96HMb4_VaaFxqASh8BxGcJyZUnfv_oyiA9Cv1w@mail.gmail.com> <MW4PR03MB63955CD017E1DEA84376C942F6189@MW4PR03MB6395.namprd03.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <c465f14b-10f8-b001-f606-f5b23ef7bc81@gmail.com>
Date: Sat, 10 Jul 2021 15:51:55 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <MW4PR03MB63955CD017E1DEA84376C942F6189@MW4PR03MB6395.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/xYKME9nbqyBLVDg7SJDuoOddMzM>
Subject: Re: [Idr] [EXTERNAL] Re: [Int-area] New Version Notification for draft-lhan-problems-requirements-satellite-net-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jul 2021 03:52:10 -0000

Alexander,

As the tracker shows, that RFC was published in the Independent Submission stream, not the IETF stream. There are indeed many cases of non-IETF protocols being published as Informational RFCs, but today that would always be in the Independent stream. The "status of this memo" section is then 
quite explicit, e.g.:
https://www.rfc-editor.org/rfc/rfc8799.html#name-status-of-this-memo

That is of course a precedent. 

Regards
   Brian Carpenter

On 10-Jul-21 03:02, Alexander Vainshtein wrote:
> Brian, Stewart and all,
> RFC 2804  notwithstanding, IETF has published RFC 3924 <https://datatracker.ietf.org/doc/html/rfc3924>  on Cisco LI Architecture.
> This is not a formal contradiction, since 3924 has been published as Informational.
> Can this be used as a precedent?
> 
> 
> 
> 
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> *From:* rtgwg <rtgwg-bounces@ietf.org> on behalf of Brian Carpenter <brian.e.carpenter@gmail.com>
> *Sent:* Friday, July 9, 2021, 10:25
> *To:* Stewart Bryant
> *Cc:* Lin Han; idr@ietf.org; INT Area; SARAH@jiscmail.ac.uk; UTTARO, JAMES; rtgwg@ietf.org
> *Subject:* [EXTERNAL] Re: [Int-area] New Version Notification for draft-lhan-problems-requirements-satellite-net-00.txt
> 
>     The IETF position on LI is not exactly that it's anathema, but that 
we will not standardise *any* intercept techniques, legal or otherwise. RFC 2804.
> 
> 
>     Regards,
>         Brian Carpenter
>         (via tiny screen & keyboard)
> 
>     On Fri, 9 Jul 2021, 18:33 Stewart Bryant, <stewart.bryant@gmail.com 
<mailto:stewart.bryant@gmail.com>> wrote:
> 
>         Unfortunately LI is not our call.
> 
>         I know the IETF finds it an anathema but it is an unspoken (in IETF) reality of the telecommunications industry.
> 
>         The concept of a huge number of highly portable, highly directional, microwave links that are then relayed opaquely to a foreign country 
is going to delight some agencies and give heartburn to their colleagues in other parts of the same agency cluster.
> 
>         I think that we can all postulate how this would (will) be solved in a mega-cluster owned by a large ITU region 2 country, or a particularly large Asian country but I assume we want to design a global / universal system rather than one that will otherwise inevitably be partitioned due to geo-political security concerns.
> 
>         Stewart
> 
>         Sent from my iPad
> 
> 
> 
> 
> Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.
> 
> 
> Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.