[arch-d] FYI: "ISOC" "New IP" "discussion" "paper"
Toerless Eckert <tte@cs.fau.de> Tue, 28 April 2020 19:07 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC733A0C69 for <architecture-discuss@ietfa.amsl.com>; Tue, 28 Apr 2020 12:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 CrOcJzRnSnUp for <architecture-discuss@ietfa.amsl.com>; Tue, 28 Apr 2020 12:07:17 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 186F93A116E for <architecture-discuss@ietf.org>; Tue, 28 Apr 2020 12:06:14 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 1B1FD548049; Tue, 28 Apr 2020 21:06:08 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 138F3440041; Tue, 28 Apr 2020 21:06:08 +0200 (CEST)
Date: Tue, 28 Apr 2020 21:06:08 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: architecture-discuss@ietf.org
Message-ID: <20200428190608.GN62020@faui48f.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/NdNoxMpGbOsh7bBzOkDSRkp2QH8>
Subject: [arch-d] FYI: "ISOC" "New IP" "discussion" "paper"
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2020 19:07:25 -0000
Dear architecture-discuss, Olaf I hope this forward is beneficial to the IETF architecture-discussion mailing list. - Even though the the appended email claims that this was widely cross-posted, i did NOT see it in any of the many IETF mailing lists i am subscribed to. - I could not find any actual public place (mailing list) for an open discussion about he topic of the paper: - internetpolicy@elists.isoc.org does not allow Global ISOC members to join by themselves, nor do i know if it would welcome discussion. In fact it is not even listed on the set of pubic ISOC mailing lists. So the nature of this mailing list seems to be secret to me. - NewIP-Discussion-Paper@isoc.org does seem to be just an alias for the authors. Unfortunately, the set of recipient seems to be secret, so i would not know the extend of people who will receive my emails, no would i be able to know about any other feedback (no public archive of the alias). If there was for example any US EAR entity listed recipient on that private mailing list alias, i could be violating US export regulations by sending technical detail explanations to such a non-public alias. >From these few data points, i find the proposed communication mechanisms about that paper somewhat confusing, if not concerning, but maybe i do misunderstand how ISOC is or is not an open communtiy like i have experienced IETF to be. Cheers Toerless https://www.internetsociety.org/resources/doc/2020/discussion-paper-an-analysis-of-the-new-ip-proposal-to-the-itu-t/ > On April 28, 2020 at 2:33:06 AM, Olaf Kolkman via InternetPolicy (internetpolicy@elists.isoc.org) wrote: > > Dear Colleagues, > > With the usual cross-post apologies[*]. > > In the run up to the ITU World Telecommunication Standardization Assembly (WTSA-20) later this year there has been some discussion about a proposal called the âNew IPâ. It is positioned as a top-down architecture to solve a number of use cases that are currently been developed in the ITU-Tâs Future Network 2030 Focus Group. > > The Internet Society is carefully following the developments in the run-up to WTSA-20. We are trying to understand if and how the New IP works with the Internet as we know it, if it actually solves problems that cannot be solved in the Internet, and, if the ITU-T is developing standards, where other standards development organizations (SDOs) have change control. > > In order to get a sense of the environment we commissioned a discussion paper, âAn analysis of the âNew IPâ proposal to the ITU-T.â The paper helps inform us and the broader community whilst the public debate around these proposals shapes up. It also aims to inform and shape the discussion from the Internetâs Societyâs perspective. Eventually the debate around it will inform our position and the potential further evolution of the discussion paper itself. Note that the paper documents the Internet Societyâs emerging opinion, but does not represent a final Internet Society position. Instead, we intend it as a means to gather information and insight from our community on the topic. > > We welcome any feedback on âAn analysis of the âNew IPâ via the email address NewIP-Discussion-Paper@isoc.org > > âOlaf Kolkman > > [*] This mail has been sent to various relevant mailing lists and featured as a blog on the Internet Society website. > > Olaf M. Kolkman > Principal - Internet Technology, Policy, and Advocacy > Internet Society Tweets as: @kolkman > _______________________________________________ > To manage your Internet Society subscriptions > or unsubscribe, log into the Member Portal at > https://admin.internetsociety.org/622619/User/Login > and go to the Preferences tab within your profile. > - > View the Internet Society Code of Conduct: https://www.internetsociety.org/become-a-member/code-of-conduct/
- [arch-d] FYI: "ISOC" "New IP" "discussion" "paper" Toerless Eckert
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Brian E Carpenter
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Toerless Eckert
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Ian Peter
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Toerless Eckert
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… John Levine
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Olaf Kolkman
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Olaf Kolkman
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Andrew Campling
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Toerless Eckert
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Brian E Carpenter
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… John Grant
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Andrew Campling
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Stephen Farrell
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… John Grant
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Brian E Carpenter
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Guntur Wiseno Putra
- Re: [arch-d] FYI: "ISOC" "New IP" "discussion" "p… Andrew Sullivan