Re: [118attendees] Request for inclusion of IPv6 examples in presentations

Toerless Eckert <tte@cs.fau.de> Wed, 08 November 2023 09:24 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: 118attendees@ietfa.amsl.com
Delivered-To: 118attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D46C15106C for <118attendees@ietfa.amsl.com>; Wed, 8 Nov 2023 01:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.66
X-Spam-Level:
X-Spam-Status: No, score=-6.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 Pm0WQNHzLgd1 for <118attendees@ietfa.amsl.com>; Wed, 8 Nov 2023 01:24:10 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB9C4C1C5F50 for <118attendees@ietf.org>; Wed, 8 Nov 2023 01:24:08 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4SQKQr03N5znkmJ; Wed, 8 Nov 2023 10:24:04 +0100 (CET)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4SQKQq6DR9zklwB; Wed, 8 Nov 2023 10:24:03 +0100 (CET)
Date: Wed, 08 Nov 2023 10:24:03 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Christian Amsüss <christian@amsuess.com>
Cc: "Marco Davids (SIDN)" <marco.davids=40sidn.nl@dmarc.ietf.org>, "118attendees@ietf.org" <118attendees@ietf.org>
Message-ID: <ZUtTsw8MfKwY31c1@faui48e.informatik.uni-erlangen.de>
References: <5ff23ea7-e71c-4fa8-9f10-832385dfc239@sidn.nl> <ZUtP6uYfBz9OEqYJ@faui48e.informatik.uni-erlangen.de> <ZUtRi-KZLk8clszM@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <ZUtRi-KZLk8clszM@hephaistos.amsuess.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/118attendees/jZzWLt4-7atNGoEHfIPZckVOnTQ>
Subject: Re: [118attendees] Request for inclusion of IPv6 examples in presentations
X-BeenThere: 118attendees@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mailing list for IETF 118 attendees <118attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/118attendees>, <mailto:118attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/118attendees/>
List-Post: <mailto:118attendees@ietf.org>
List-Help: <mailto:118attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/118attendees>, <mailto:118attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Nov 2023 09:24:12 -0000

On Wed, Nov 08, 2023 at 10:14:51AM +0100, Christian Amsüss wrote:
> > Alas, IPv6 addresses may not always be abbrebiaviated, [...]
> 
> Many examples constructed from that are derived to have compact forms
> even for several organizations, resulting in 2001:db8:a::1,
> 2001:db8:a::2 for example.com, 2001:db8:b::1 for example.net.

Right, but when i encode in systems such as DNS, the format itself can often
not be abbreviated, so if i would just use 2001:db8:a::2, that could derail
implementations which would need to encode e.g.: 2001db8000a00000000000000000002
or 2001:db80:00a0:0000:0000:0000:0000:0002 - depending on encoding desired
by where you put the IPv6 address. CVery unwieldy.

Just pondering what to do about this in my draft (which is of course using
IPv6, not IPv4 addresses).

Cheers
    Toerless