Re: [arch-d] ETSI launches new group on Non-IP Networking addressing 5G new services

Toerless Eckert <tte@cs.fau.de> Thu, 09 April 2020 22:08 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 7A26D3A101A for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 15:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level:
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 MrIDpwCB4hSj for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 15:07:59 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 0E0C33A100D for <architecture-discuss@ietf.org>; Thu, 9 Apr 2020 15:07:53 -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 48675548015; Fri, 10 Apr 2020 00:07:49 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 40629440040; Fri, 10 Apr 2020 00:07:49 +0200 (CEST)
Date: Fri, 10 Apr 2020 00:07:49 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: tony.li@tony.li
Cc: Dino Farinacci <farinacci@gmail.com>, architecture-discuss@ietf.org
Message-ID: <20200409220749.GB44502@faui48f.informatik.uni-erlangen.de>
References: <4200C5F8-9F56-4FFF-90F4-7AD76A9F4FC8@eggert.org> <20200409121941.GZ28965@faui48f.informatik.uni-erlangen.de> <C758BDF2-8CD6-4C22-90CA-6ED98DACD740@eggert.org> <20200409175431.GF28965@faui48f.informatik.uni-erlangen.de> <1e89795e-6bd9-2318-aa81-27f8327e1226@gmail.com> <229AAF4A-C43F-46E9-97C6-99CC124E9B48@gmail.com> <20200409212841.GK28965@faui48f.informatik.uni-erlangen.de> <0A15B52E-2A67-4D6A-AACF-8A92FB67ADEC@gmail.com> <20200409214205.GL28965@faui48f.informatik.uni-erlangen.de> <FCAB9CB5-32C6-4B03-A36B-29E83C4E8774@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <FCAB9CB5-32C6-4B03-A36B-29E83C4E8774@tony.li>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/YYRnRb3Rrsk3ouGchYMXOCby6AI>
Subject: Re: [arch-d] ETSI launches new group on Non-IP Networking addressing 5G new services
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: Thu, 09 Apr 2020 22:08:01 -0000

On Thu, Apr 09, 2020 at 03:00:40PM -0700, tony.li@tony.li wrote:
> SPs are somewhat sheltered from hardware limitations.  They simply ask for scale numbers.
> 
> I don???t think that the bandwidth implications of SRv6 are well understood yet. IMHO, those are actually more of a concern.

Indeed. I remember some rude platform awakening in IP multicast when
throughput was designed for video with > 1K avg packet size and the
customers where finance market data with < 200 byte payload.

Its really hard to predict if environmental telemetry in metropolitan
networks will become an actual problem in this respect, but from what i
understand, the amount of telemetry collected in DCs already is often
surprisingly more traffic volume than one would guess.

Toerless