[Dlt-networking] New Non-WG Mailing List: Dlt-networking

IETF Secretariat <ietf-secretariat@ietf.org> Fri, 01 April 2022 16:54 UTC

Return-Path: <ietf-secretariat@ietf.org>
X-Original-To: dlt-networking@ietf.org
Delivered-To: dlt-networking@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D9C3A006A; Fri, 1 Apr 2022 09:54:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: mmcbride7@gmail.com, farinacci@gmail.com, dlt-networking@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <164883206521.18978.823035018889389214@ietfa.amsl.com>
Date: Fri, 01 Apr 2022 09:54:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dlt-networking/1-qdTFM26XWZIiUH5m7_a0ZL7p4>
Subject: [Dlt-networking] New Non-WG Mailing List: Dlt-networking
X-BeenThere: dlt-networking@ietf.org
X-Mailman-Version: 2.1.29
List-Id: DLT Networking <dlt-networking.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dlt-networking>, <mailto:dlt-networking-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dlt-networking/>
List-Post: <mailto:dlt-networking@ietf.org>
List-Help: <mailto:dlt-networking-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dlt-networking>, <mailto:dlt-networking-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2022 16:54:26 -0000

A new IETF non-working group email list has been created.

List address: dlt-networking@ietf.org
Archive: https://mailarchive.ietf.org/arch/browse/dlt-networking/
To subscribe: https://www.ietf.org/mailman/listinfo/dlt-networking

Crypto currencies (such as Bitcoin) and their DLT networks (such as Blockchain) 
don’t concern themselves with the underlying TCP/IP network. They have a P2P network,
with a pool of transport layer (TCP, UDP) connections, and they have done a good job 
securing their application and hope the TCP/IP network performs as needed. 
What is the impact of choices made by the application design on the network, e.g., 
in terms of costs, traffic generated etc.? This list help share work to understand the 
impact of DLTs on provider networks and the possible opportunities to improve on
those impacts. And there are a variety of opportunities to understand including DLTs
potentially providing better trust with packet capture data,

moving network management to a decentralized smart contract-based system, signing
routing advertisements and proof of transit, possibly including RPKI ROA’s in a blockchain,
and how overlays, such as LISP, could provide intimacy between the application layer and 
network layer. A DLT in Networking side meeting occurred at IETF 113 and this list will 
provide an opportunity for the participants to further discuss this topic.

This list belongs IETF area: Routing