Re: [arch-d] possible new IAB programme on Internet resilience

S Moonesamy <sm+ietf@elandsys.com> Sun, 29 December 2019 22:08 UTC

Return-Path: <sm@elandsys.com>
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 8B80512008C for <architecture-discuss@ietfa.amsl.com>; Sun, 29 Dec 2019 14:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 UQq0BtOFJDK9 for <architecture-discuss@ietfa.amsl.com>; Sun, 29 Dec 2019 14:08:53 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id BA4C912006F for <architecture-discuss@iab.org>; Sun, 29 Dec 2019 14:08:53 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.26.199]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id xBTM8ahb028633 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Dec 2019 14:08:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1577657332; x=1577743732; i=@elandsys.com; bh=nEu1aGIwOJ0mxcI+sKwApWN/bsDGnUGRGGtg6oAngI4=; h=Date:To:From:Subject:In-Reply-To:References; b=BnqFtNIW5lDr2IoVI4FCHPH1iL8TNiceV4YbUL1meUhrrJHut9stduqC2omwsp3Gj GZPKzhXBshDsYtxRvqjCuv89rlH206kNV8f+BIWdJWxrOX0QyaD3//trZfrNX5mzbb 3IYJsUyMnHcAwVzsSREPteEAmhX0cd115yvBC67I=
Message-Id: <6.2.5.6.2.20191229105554.0ccf0298@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 29 Dec 2019 13:55:57 -0800
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>, Marc Blanchet <marc.blanchet@viagenie.ca>, architecture-discuss@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <1829722692.7358.1577443983540@appsuite-gw1.open-xchange.co m>
References: <f13e1588-35e0-2493-93d2-add3480bb207@cs.tcd.ie> <1127343564.5806.1577112317584@appsuite-gw1.open-xchange.com> <ebcca2be-6839-8f43-d74f-0e863e32cd2d@cs.tcd.ie> <2068147434.6516.1577178675917@appsuite-gw1.open-xchange.com> <LO2P265MB05733E4BD5A72EDEF96D3DE2C2290@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM> <20191227102943.GA14015@nic.fr> <1829722692.7358.1577443983540@appsuite-gw1.open-xchange.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/L3-fHyxpDKfiFlEm9VWBF_EYjXM>
Subject: Re: [arch-d] possible new IAB programme on Internet resilience
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: Sun, 29 Dec 2019 22:08:54 -0000

Hi Vittorio, Marc,
At 02:53 AM 27-12-2019, Vittorio Bertola wrote:
>However, the fact that a proper, effective, global policy-making 
>body for the Internet does not exist will not make the need for it 
>disappear. Simply, what is happening is that, in the absence of 
>global consensus decisions on policy issues, the discussion and the 
>action moves to the only level which is equipped with somewhat 
>effective policy making and enforcement tools: national Parliaments 
>and governments.
>
>This is a consequence of the Internet community failing to establish 
>an effective global policy-making mechanism in parallel to the very 
>effective global technical standardization mechanism, and on top of 
>it, taking decisions and embracing policies that would never reach 
>consensus in the broader circle of non-technical Internet stakeholders.

The attendance number for IGF was 5,000.  The number for the last 
IETF meeting was 1,012.  There were some discussions, from a policy 
perspective, about standardization.  It takes some effort to 
understand the relevance or the pick up the noteworthy details.

Some entities may be of the view that there is a need for a global 
policy-making body.  There are two ways to make that happen.  That's 
not the current trend though.

>Several people here seem to think that they can use their position 
>of technology makers to force unwelcome policies onto about 200 
>countries in the world, but I doubt that in the long term this 
>attempt will bode well for the Internet. I think we will just see more

The 200 figure seems a bit of the high side.

At 11:46 AM 28-12-2019, Marc Blanchet wrote:
>IMHO, we are diverging pretty off the initial proposed charter. Well 
>I can understand your point of view, I think the policy side, as you 
>describe, should be outside the scope of the charter.
>
>Can we come back to technical content?

There is the following sentence in the proposed charter: "For 
example, if one implementation dominates in deployment to the extent 
that bugs or vulnerabilities in that implementation could create 
significant effects, or if only a small number of service providers 
are so widely used that they effectively become "too big to fail", 
even though failures are always possible".  Is the second part of the 
sentence (small number of service providers) a technical matter?

The proposal also states that "resilience is the result of protocol 
design, implementation, and deployment choices".  Are deployment 
choices a technical matter?

Regards,
S. Moonesamy