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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 13 October 2021 20:27 UTC

Return-Path: <brian.e.carpenter@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 B66663A0DD8; Wed, 13 Oct 2021 13:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 WzdzkKfr-n68; Wed, 13 Oct 2021 13:27:00 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 80E243A0DE7; Wed, 13 Oct 2021 13:26:55 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id g5so2624413plg.1; Wed, 13 Oct 2021 13:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=PbwyFwXmkDLjCN5Ia72re7BPa+DeiMTCb4/NOvb8hUQ=; b=DzZDkTP/VF9V3zKiPsAzx4DdcH2aokqyDusMdKdxZBOZxKu4qDjYGn+eCdfGDhbOie RKYv6ZxbZ8Zc0s3li4oE6DRawnwDnuPAkGQRO7Chp+cN1Y03HUmLoWdVR4c47+Skmq7P HuwDc2gZYz9tgtqHLFcxr0cu5qQXI7UA6Ixz5A0cXgH9KkH/5PS3OrbsGBWQJJTAzcHS xj6bp5n6r2SBlbtk4KEeUYwwY/BPpueYLeIx716vaATybwhZEWtPEf3scUJqrceZvnU9 B5cw1hemVrrmIM3C0ttxl7DlNyHnHsAx4cOE7InfIJl/bbD7o/TSlzdhoaUfe4jHjKt7 nlcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=PbwyFwXmkDLjCN5Ia72re7BPa+DeiMTCb4/NOvb8hUQ=; b=TEp+zhVcTCp6ABJ33Q5LJk9VU1KL+034kJ0VPAWBJmvfZXnKUu7gCQq9Y6rjbHN5EA h5NokwkKXQwh6SdHDPI+dVQYTM4lEnBBtgRdjNHKGhm2yl/ne9MGgHJzzhxLbf8LygTh nNBYl/kFFXBZbE/PWWfxFAmM+6ZWUsBXQ1KSgDhlVkMieFZSM/mx8N77eMN4iW5+B0Ki ZIcIeK0jTvFMOSuecISTma2RQRgftwHAOYaYtvw3oQvBpEsZ/TfHwRbv8zwSLK6BNJl9 xyL9mououlW6kYdXsyMCyfTo/Utc9thniSKgvD7HeP64qs9ykxDVExtEIvHQSFsARhDD RtZA==
X-Gm-Message-State: AOAM5332mi5a9OPiuPb8eTNxzZWJh4jQsIoOS9xb02CWpi5OwMnOpTiA y4Ke9zlwaQgL2Qy/Z8qqfrX/Yl+MoGIqqA==
X-Google-Smtp-Source: ABdhPJxDDoGAEBZ+HaHauTkvpuRcO0CqRQHlOAC3StSAcdgIxvdAEQMiPFIyiQgITo/qmKzyIpQj6A==
X-Received: by 2002:a17:90b:fd0:: with SMTP id gd16mr1526515pjb.157.1634156813864; Wed, 13 Oct 2021 13:26:53 -0700 (PDT)
Received: from ?IPv6:2406:e003:1018:b901:db7:d041:a2d:ce65? ([2406:e003:1018:b901:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id t14sm339158pga.62.2021.10.13.13.26.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 13 Oct 2021 13:26:53 -0700 (PDT)
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Cc: "spring@ietf.org" <spring@ietf.org>
References: <85fddbe9-4eb8-7d90-d246-a888fe8bdcd3@joelhalpern.com> <139d72fd-98de-f46a-767f-6a493c4facc9@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <1daf3d20-22b2-d111-5131-bd53f51c53a3@gmail.com>
Date: Thu, 14 Oct 2021 09:26:49 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <139d72fd-98de-f46a-767f-6a493c4facc9@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/8W0Ql8N9egYg1SVsFdwVp-iPl74>
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: Wed, 13 Oct 2021 20:27:07 -0000

Joel,
On 13-Oct-21 20:37, Joel M. Halpern wrote:

<snip>

>> 1) Does the placement of a list of sids in the IPv6 DA field change the 
>> IPv6 architectural description of that field.


That's why I recently asked for a set of examples of the resulting
"addresses". I don't understand enough of SRV6 to understand what
the bit patterns in such addresses will actually be. And I don't care
about the details of SRV6, given that it will only be used in certain
special types of network. So I can only answer your question based
on concrete examples. Are they compatible with RFC4291 or not?

(There's a subsidiary question which IMHO is in some ways more important
than the architectural question: what existing code and devices will such
addresses break?)

>> 2) Does the operation of shifting information around in the IPv6 
>> destination address field represent a modification or extension of the 
>> IPv6 data plane.


Including semantics *of any kind* in an IP address is a very fundamental
change to the concept of IP. I may be wrong, but I'm not aware that any
RFCs prior to SRV6 have done this, and the founding reference for what 
an address *is* still seems to be IEN19 [1].

So I'm not concerned that srv6-srh-compression has any more fundamental
impact than basic SRV6 or RFC8986. (However, this aspect of SRV6 was
one of my primary motivations for RFC8799. What happens in SRV6 stays
in SRV6.)

[1] https://www.rfc-editor.org/ien/ien19.txt)

<more snip>

Regards
   Brian