Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression

Ted Hardie <ted.ietf@gmail.com> Fri, 15 October 2021 10:40 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57C043A190F; Fri, 15 Oct 2021 03:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 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, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 d_m1xnmNaU-J; Fri, 15 Oct 2021 03:40:22 -0700 (PDT)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ECA53A115D; Fri, 15 Oct 2021 03:40:22 -0700 (PDT)
Received: by mail-ot1-x32f.google.com with SMTP id w12-20020a056830410c00b0054e7ceecd88so12291236ott.2; Fri, 15 Oct 2021 03:40:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EXYG2g1NZNwHHJLK6hCAmUcr766MA+Rs9bB4I5h4T8A=; b=oIgQbp1ozV/e3lcyjgQY6qRAuz86MxsISYZp413/lI67ScGLVCZdhCZN0TDCkrSJVG Zhb7ZcVmXAxClxVYiOIy8erdC+zLS3e5Yzj5xiVeuh5QSr/7DU3NwYlsrtZZTNeMxdEW ZSNLzGhmvOOJ5qgcbeGXbcSGHEVIahTr7gphxesCkXCjuIwI/AZCCgq6kPQOlWAB/hCX Ogut/fGNeVxcKdIPBRfytuc/YEnaAnwv8gWBCrMsr6JKGaero+vaExeKnPYP35E1cQrT K3LhI36kwpAYii95C5AkDb4tiEAq6I/5d0WKqKg5T70cgqXVeIVecoXGzJQi8TuI7z0G YYjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EXYG2g1NZNwHHJLK6hCAmUcr766MA+Rs9bB4I5h4T8A=; b=rI7Gk4NkoH3UcJytw1UUKKR6agDlYOaA45ox1poFhRjB9OOQ9m4KbsxlVnQOxWxZT/ 8uZZy26Mr+wKTnvCMCaTgTMBe6hXkMpGv0g8Im9iHI/Ohz/Jh5vW2rbGkGfSPjwNu/ui A035VBQV6z8+FonEUqAJSsBShRjP+Pd7svvcYHNla18uKhd42oNeF6Jt+Io30NK4ej9C wiSR/C3H/RpMdmV4/drjEAedfWXw4Xx1zhIF/oKUZtagk24x3eI/JiIbDvKDMOHT2lny DlkHtzuxlC4bgTf7KEwt+gISt2rKaef1/UJ1Gq7iauDjK8Aay1fpIeBYiAOA3srcb5aU cfuQ==
X-Gm-Message-State: AOAM531ak+b5u4vFve54yYYt84roOVLVjfqVrQHhtlQGPpr3OQr8X47V 5AA06BEO9eqADYWKSttrU9pe0phwVnk2jzRJCsSWxl+jEkg=
X-Google-Smtp-Source: ABdhPJzrWWJfbQUFX4hPG3VSSQaq4eQNTN8HqQr41bPJTV/1iRCQ6IvyWh1xov5NAKmeAAStUhJNaBqPuK7AGRB1sXA=
X-Received: by 2002:a9d:6113:: with SMTP id i19mr7251453otj.322.1634294421462; Fri, 15 Oct 2021 03:40:21 -0700 (PDT)
MIME-Version: 1.0
References: <85fddbe9-4eb8-7d90-d246-a888fe8bdcd3@joelhalpern.com> <139d72fd-98de-f46a-767f-6a493c4facc9@joelhalpern.com> <1daf3d20-22b2-d111-5131-bd53f51c53a3@gmail.com> <CA+9kkMCk6D-7q-LTu0gwL_ZsyBAaFvn=3_CizK56oHG5dGRwYA@mail.gmail.com> <60f71d8c-8165-111c-4099-7f926a897d22@gmail.com>
In-Reply-To: <60f71d8c-8165-111c-4099-7f926a897d22@gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 15 Oct 2021 11:39:54 +0100
Message-ID: <CA+9kkMAw_TUgmL6kgSbAnaLDf6s6=5K22qPdMvXvhONhtu06YQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073237a05ce61d27b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/xX7GUcA4X_d2ttQHvDMFsTNbM-w>
Subject: Re: [spring] Typo correction Re: Question from SPRING regarding draft-filsfilscheng-spring-srv6-srh-compression
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2021 10:40:29 -0000

On Thu, Oct 14, 2021 at 10:06 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 14-Oct-21 22:41, Ted Hardie wrote:
> > On Wed, Oct 13, 2021 at 9:28 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> >
> >
> >
> >     Including semantics *of any kind* in an IP address is a very
> fundamental
> >     change to the concept of IP.<
> https://www.ietf.org/mailman/listinfo/ipv6>
> >
> >
> > Would you mind elaborating what you mean by semantics in the statement
> above?  Clearly there are semantics in things like the IPv4 multicast and
> experimental address ranges (aka "Class D" and "Class E"); especially for
> the multicast case, the very fundamental semantics of the distribution are
> signalled using the address and there has been significant deployment using
> those semantics.  Isn't that semantics in the meaning above?
>
> Yes, I should have restricted my remark to *unicast* addresses. But there
> is a difference, I think, between semantics that describe the *type of
> address* and semantics that actively describe *what the recipient is going
> to do*. It's the latter that I was getting at.
>
>
Thank you for the clarification, though I'm still struggling a bit with
understanding your concern.  Since we use address ranges for scope
semantics (e.g. ULAs for administratively determined scopes) even within
unicast addressing, I'm not quite seeing the line you are yet.

> (This applies to Carsten's comment too. Port numbers or multiple
addresses per host are not actively describing what the recipient will do;
they're just numbers.)

While this may theoretically be true, we actually associate significant
semantics with port numbers, both in the end hosts (e.g. the ports below
1024 being privileged ports) and in the network (where firewalls use ports
to start the process of analyzing the permissibility of a flow).  A
specific port number very much describes what the host will do:  port 25
will link to the SMTP service, for example.  So I guess I'm not following
this parallel too well either.

regards,

Ted


>
> Also, I tried not to express shock and horror at the notion of semantics
> in address, but concern about how this will impact existing hardware and
> software.
>
> >
> > Thanks for any clarification,
> >
> > Ted
> >
>
>