IETF Logo Mail Archive

Re: [v6ops] Our IPv6-only home network and future experiments

Gert Doering <gert@space.net> Mon, 15 April 2024 08:17 UTC

Return-Path: <gert@space.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBCCFC14EB17 for <v6ops@ietfa.amsl.com>; Mon, 15 Apr 2024 01:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=space.net
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 lE2L_nRwccag for <v6ops@ietfa.amsl.com>; Mon, 15 Apr 2024 01:17:14 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E88DC14F708 for <v6ops@ietf.org>; Mon, 15 Apr 2024 01:17:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1713169034; x=1744705034; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=GF4IH2g9I/oXDG+BJKkwAXEkcW8MsyWWN/50xp2K4E8=; b=U31cdEYnxpDV82izNHvawTFb20hggc7Wa5rg5E52BgTKBie6Cvku/u/R ypyzFN+MDWZYR8vhPX+2f+6NfZ+QBbQfZSGl/548hNWMlsjGAKBhEvAuW IP+jg/UZCldbKpkvvkecJ+hkgJgYuuGGDxkIkii0DVjsGuE74MQ6H2aWm L4yEh5pBilYZrmRLzlzjYxcukV83jCLQW7V2uvS1M/U+UAZya7C/KXhGz 2s2UI7rKMpO+HZ1JigGLpR+SPVLi6hZhPuxdWyx32rY0BFsMoSsZM2O6T HMAjmZLpMy3F0J9f/CI8qsRiilPJnEf6VLyah8XTwJ+0Q7hLAwUrmeBpw A==;
X-CSE-ConnectionGUID: /y08UEsRSMuDP6Of85kcWA==
X-CSE-MsgGUID: J2VOYfU2SJ+jy2FeVetiXg==
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Apr 2024 10:17:10 +0200
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 8284C4246D for <v6ops@ietf.org>; Mon, 15 Apr 2024 10:17:09 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 67ED941B6B; Mon, 15 Apr 2024 10:17:09 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 60BA92EEEF; Mon, 15 Apr 2024 10:17:09 +0200 (CEST)
Date: Mon, 15 Apr 2024 10:17:09 +0200
From: Gert Doering <gert@space.net>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
Cc: Gert Doering <gert@space.net>, "Soni \"They/Them\" L." <fakedme+ipv6@gmail.com>, IPv6 Operations <v6ops@ietf.org>
Message-ID: <ZhzihWihmgpwWt7V@Space.Net>
References: <91ee2782-c98a-4ccf-ae8f-71be571420b6@gmail.com> <7b89e8bd81674a61b364e1fec4176006@huawei.com> <ZhzSD0g_xmVfeiM1@Space.Net> <0685641f158c4c9885a4b53964548abd@huawei.com> <Zhzcs9PU3HbYtwYp@Space.Net> <a1dea94cb05548328e0de9f1b7c3aa16@huawei.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="eb1GRpx+FS3Ex4el"
Content-Disposition: inline
In-Reply-To: <a1dea94cb05548328e0de9f1b7c3aa16@huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nR38M8X5ySsWCOak2vmdtXVisiQ>
Subject: Re: [v6ops] Our IPv6-only home network and future experiments
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Apr 2024 08:17:18 -0000

Hi,

On Mon, Apr 15, 2024 at 08:01:47AM +0000, Vasilenko Eduard wrote:
> OK. The majority of applications is compiled without any special keys, hence, libc is linked dynamically.
> And we do not care about unlucky loosers who compiled libc into the code - their application would break. Right?

On a normal system, you can't really link libc statically these days,
for a variety of reasons.

> > nothing new needs to be added, API-wise
> I doubt that it would be possible to persuade the community to radically modify the behavior of basic functions.

This is an unfounded assumption.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard,
                                           Ingo Lalla, Karin Schuler
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email