Re: [spring] Is srv6 PSP a good idea

Robert Raszuk <robert@raszuk.net> Thu, 27 February 2020 00:29 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D233A0C86 for <ipv6@ietfa.amsl.com>; Wed, 26 Feb 2020 16:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 YDJ9nqCEAfrP for <ipv6@ietfa.amsl.com>; Wed, 26 Feb 2020 16:29:35 -0800 (PST)
Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 331EF3A0CC1 for <ipv6@ietf.org>; Wed, 26 Feb 2020 16:29:35 -0800 (PST)
Received: by mail-ot1-x32c.google.com with SMTP id h9so1261856otj.11 for <ipv6@ietf.org>; Wed, 26 Feb 2020 16:29:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yHb6mWnPh5czYy8loY2Q4xaM6DrWFd+lztcB8Sg2cw8=; b=fMq53AEdTLRteMkEKs4Y73A5Zzo7qqQdi2VoYUNECBwd3GoQN44zb2rovPfvbMfGFz qtHcKAGv6BF0k1vV9dMimR86Q85r2DM5DCyTQXUV8Y5wjDQ+liswSCKyuq5QYR1ocORf thYo6SJkB2Z8l+GGj2xhRSOIVvwvSwjVQDki6G2NCvK3lsiYwSuA/GiFErk7s5hOmJbr tXvJIfxRxg/G5iWNhLkSAY8awVzn2HgCNOSqlxjJt0ynbliY04Obd+KqwZ34tlFMAfdn vd88A08gPg1RryU/yywlXmgXjJcPlqCapX1J5jqsoDxsTRI3VAC3Po8UpdDLgAia61E6 1lEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yHb6mWnPh5czYy8loY2Q4xaM6DrWFd+lztcB8Sg2cw8=; b=Tr92C6uVZ/YckptBxUasqVr5e5qQFQOS6D+SZv5Z0phXvjbGRLPkYvjHCYgZdN3WKp 7xhO/arMfjaO1qJdY7y2Oks0vgiDszTg82jXRO8tPxhbI9GS8eyI8FzUs0rxBvqUCccL 5FZfcxQdq45RvT90fJSeUevOUwJxZEhUWQ5ce/uwqlCGc9RZ1YDmh6Jwd5msu5uJOBw4 EOwq3LpPvtsjL/jZ8+rdObiLu9CEFAEiZST/QWXAy3jKVEIcHcooRpJbZZ3u8d/sOtdb mG9NReev4UA2MFDQqVeWMR53adHFJymbyBrRUdiqPVe+8K/6I3Gof55hOK4ua6IMgKI7 PwHA==
X-Gm-Message-State: APjAAAWthlA1q15EGaVg3tKQFWTIo3g1Ocf4U/cyp0+o5rlNHJfJbABv 6HarKqS1W6KEvdwSFQT4pC9h8va1nM5rEzXfTzoo4A==
X-Google-Smtp-Source: APXvYqxgDul3Ke+SI1U9MAFC6jZvBINXkgBAnPkadkFYk3Ku4bmdBCKL4y+YBOumZL2VUO/RNjeZckoGL4MCmKVPbEE=
X-Received: by 2002:a05:6830:1385:: with SMTP id d5mr1233846otq.61.1582763374188; Wed, 26 Feb 2020 16:29:34 -0800 (PST)
MIME-Version: 1.0
References: <7B51F0BE-CE40-42B8-9D87-0B764B6E00C5@steffann.nl> <47B4D89B-D752-4F4C-8226-41FCB0A610F0@retevia.net> <CAOj+MMGYtGOi2n_E57TTfD_3kWvkqWGWhhfev4Z2GVwJD5oSnQ@mail.gmail.com> <CAO42Z2wOHTZRz=h0kN=evrkqAZUf6HiaOkskH-vD2a3d4OpysQ@mail.gmail.com>
In-Reply-To: <CAO42Z2wOHTZRz=h0kN=evrkqAZUf6HiaOkskH-vD2a3d4OpysQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 27 Feb 2020 01:29:23 +0100
Message-ID: <CAOj+MMEdti3r0zrAPiN+BxjoVs7bbYooz6hz9TUj+1_UaLv_ww@mail.gmail.com>
Subject: Re: [spring] Is srv6 PSP a good idea
To: Mark Smith <markzzzsmith@gmail.com>, Sander Steffann <sander@retevia.net>, Fernando Gont <fgont@si6networks.com>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aeb144059f83d064"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vYRb6ct2LSlLPLRMX8clEtyjugs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 00:29:37 -0000

>
> You realise that the 3 musketeers were heroes in that story?
>

Oh I do.

And I want to sincerely congratulate three of you to be very effective to
discourage touching IPv6, its dogmas and principles. If this is good for
the industry, time will tell.

To me I got even more assurance now that IPv6 with its 40 octet fixed
header is a broken concept and deserves to be obsolete very soon -
especially for intra-domain use cases.

Btw new data plane much more efficient can be easily made compatible with
all existing and deployed v6 capable data plane hardware. If I would work
for a vendor perhaps I would have some cycles to propose it, but otherwise
it is just impossible to get sufficient support and get through with new
technology.

Kind regards,
RR.

PS. @Fernando ... you keep forgetting in your post and your errata about
RFC2473. I recommend you take a new read of it including section 3.1 and
match it against your IPv6 end to end principle. It is roto operational
principle behind SRv6.