IETF Logo Mail Archive

Re: [arch-d] Possible IAB Adoption of draft-nottingham-avoiding-internet-centralization

Dominique Lazanski <dml@lastpresslabel.com> Thu, 25 August 2022 06:35 UTC

Return-Path: <dml@lastpresslabel.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 067E4C15790C for <architecture-discuss@ietfa.amsl.com>; Wed, 24 Aug 2022 23:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lastpresslabel-com.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LzdSVZcjbmxq for <architecture-discuss@ietfa.amsl.com>; Wed, 24 Aug 2022 23:35:30 -0700 (PDT)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4EDEC1524D7 for <architecture-discuss@ietf.org>; Wed, 24 Aug 2022 23:35:30 -0700 (PDT)
Received: by mail-ed1-x52b.google.com with SMTP id s11so24772424edd.13 for <architecture-discuss@ietf.org>; Wed, 24 Aug 2022 23:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lastpresslabel-com.20210112.gappssmtp.com; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc; bh=SCKTAxQyIVcVTqF3wvJL0WMulK2h4nUkBU7zEFPGBv8=; b=G8qOUAzhnKsCZjTwgvltoX6/8MJOhh0H66THX0uxYJFNpKmDeJeS//jQ7ght7QT081 qfmR8HGnEhwmpE6FWcSP3laXhtgunmUVgGWsEpdVWjLd4WdGNkUiQQxud20Q3EKCmBRI U/6U4JX+VpJ5kHWXAYA4thSLAN3U225TG2Hae+sdLw/Q8FQe9+RhBbxgvD61hvjuKt3l Cpx63M5fvSZEgZIIrFk5BX44dRB/MlZj68+aSbgLhG5YijfGSlX+F6ZW/odFe284VI1A 8Q/Saffsx+dwjfk+v0WFYzuSzYpBETYnXEj2Tewz0aBdNvLGgHeLUL3bfGq3HE5uswC6 2uBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc; bh=SCKTAxQyIVcVTqF3wvJL0WMulK2h4nUkBU7zEFPGBv8=; b=ZazNLqhVbSRpO4Wfg7DxvBLGrS0iKMq/ufcWCMbwWoHqgAr+PNBakWms1hU7Gn+CDR SFcDqfqxkROZXuXX1UZKs9efS95wGanhRr1n5WyCiMpreadV3Q8maX779kSTOUuy0V1v 85r5mFtM/uaxBQ0MUV60P+KrpbP4yrkOa5dbGZFT/Utc2YG7WhRGzMcNqJxwLmX6k/Bl J9w6bAylo5Tjdw8WbXnE+zYEC3TVsI5ADdkpQz7SkA4K+vNDcMZlhR1Gh45Twfgl6vJD Ak2jUabWlgDzjB6aN0FVKF8xkA6e2xn8UNybZb4xZ+VUbvBs4CfMOE1RGHBbnc0LHBPs +fmg==
X-Gm-Message-State: ACgBeo0o0HLQbN3cAvGmJnuj+5K+hNvtKYCBnEF/JnsEMeW3ag/yzMwA KfhkD6Kr0ZfK93XfFCE1/fZM8ht72dzQFwlF3WM=
X-Google-Smtp-Source: AA6agR5ucN30ynuICL3R6ib9oTMaLzHVMJ8R8iE1F4srw9+bJweJVZzSZ7aQGo6IezZYptTMxjCS5A==
X-Received: by 2002:aa7:c3c2:0:b0:447:7d68:7187 with SMTP id l2-20020aa7c3c2000000b004477d687187mr1883829edr.400.1661409329094; Wed, 24 Aug 2022 23:35:29 -0700 (PDT)
Received: from smtpclient.apple ([2a00:7580:60:1224:54cb:d57:ff9:99e3]) by smtp.gmail.com with ESMTPSA id y21-20020a170906559500b0073d685a2985sm2013824ejp.108.2022.08.24.23.35.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Aug 2022 23:35:28 -0700 (PDT)
From: Dominique Lazanski <dml@lastpresslabel.com>
Message-Id: <4768AC46-C5AF-4756-AF96-1481EF45CFCB@lastpresslabel.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_04157A86-7C45-452A-8F54-586292A43AAB"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 25 Aug 2022 08:35:28 +0200
In-Reply-To: <166119246622.15164.113740897507466451@ietfa.amsl.com>
Cc: iab@iab.org
To: architecture-discuss@ietf.org
References: <166119246622.15164.113740897507466451@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/-KjR4RkmXbbTqg-ITVmYJEzRwms>
Subject: Re: [arch-d] Possible IAB Adoption of draft-nottingham-avoiding-internet-centralization
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 25 Aug 2022 06:35:35 -0000

Thanks to the IAB and Mark for all the work on this. I was wondering what the justification for adopting this (Nottingham) draft and not also adopting the following draft on the same subject:

https://datatracker.ietf.org/doc/draft-lazanski-consolidation/ <https://datatracker.ietf.org/doc/draft-lazanski-consolidation/>

Or, indeed combining these two drafts with https://github.com/intarchboard/draft-three-protocols <https://github.com/intarchboard/draft-three-protocols> and coming up with a draft? I’d be happy to do the legwork on that. Also the output of the DINRG workshop should be taken into consideration and more discussion on this could lead to some other RFCs. 

I’m not suggesting that this will be the one and only RFC on consolidation, but I’m just curious why other drafts and discussions are not being considered as well?

Thanks!
Dominique

Dominique Lazanski
lastpresslabel.com 
+44 7783 431 555

> On 22 Aug 2022, at 20:21, IAB Executive Administrative Manager <execd@iab.org> wrote:
> 
> The IAB will discuss adoption of draft-nottingham-avoiding-internet-centralization (Centralization, Decentralization, and Internet Standards) on the IAB stream at its meeting on 2022-09-07.
> 
> The draft can be found here: https://datatracker.ietf.org/doc/draft-nottingham-avoiding-internet-centralization/
> 
> The agenda for the meeting will be posted 48 hours ahead of the meeting here: https://www.iab.org/wiki/index.php/Agenda
> 
> Feedback about this draft can be sent in response to this mail on architecture-discuss@ietf.org, or to the IAB directly at iab@iab.org.
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss

v2.23.0 | Report a Bug | By Email