Re: [spring] Question about SRv6 Insert function

Mark Smith <markzzzsmith@gmail.com> Wed, 11 September 2019 02:08 UTC

Return-Path: <markzzzsmith@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 B2FFA120273; Tue, 10 Sep 2019 19:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.497
X-Spam-Level:
X-Spam-Status: No, score=-0.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 DF2bBSwLXO7U; Tue, 10 Sep 2019 19:08:10 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 EC2A11207FE; Tue, 10 Sep 2019 19:08:09 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id 7so12864840oip.5; Tue, 10 Sep 2019 19:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bKimizBGw72jnm5Lo2gsRJwG39VAL4a9L+mhznh2O80=; b=YNwPmNrr3JgTpg+r4i6+bu4OgzC3thtu8Kdbbgli+fGHftkjRn6/x59N4vuC/+rEQr u+fW+0PWlSoiffJvXJATdmrF2IExKx9C/tvOrd9KMGVBhMWWlFozA8b+94J6UNZluqiP sZbjxJl01E8RYiwOaoPErce5acy7/qQGCbKYGusE+4rwG38wNxdLUOYtl5I1FLAbxFTQ UKuFd6Vf6EM2jJxQ/b/8CosLERTbZKMkTwYXxhQdr1/qOK20MTELCeXCdsbWj65EpT1s L3gwIOfLukUz2wBlGT+OvJFrGXKtDoHqw5DBZT84aV2dsyFfRtlg06+an0gJpgbah5uS 1zPQ==
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=bKimizBGw72jnm5Lo2gsRJwG39VAL4a9L+mhznh2O80=; b=rCmdlK0X1tVBXY1AUMiI8YwHZWTEElnmw8niCI4Wy7/cTlk9DrgBGWV0UvcjbKegXf ztHF2iWMsvwfj7858769ai5pgnMzf7McOC2WNduY2Q83I+RUZ1Ce9nelloAFerP0lbrK CPtDxWfDk7jrag2Pxo/CK38F1Avn5KkPg7gh20ZvMieuYfT/Cgn/9il7ZAtoIJF+hL6N 0scF/GCeLo7dn/I6O7V/kaJeZZjZ2EOd/glWQMd9nDbyUnYV+CWfVS59rEJ9DvCLwYEO V4vecp4ZuhQgcSVbEC814dTABINRFXh+pizWmeo2v70FKKymaxo0rM8e1H9zbxBol198 Iblw==
X-Gm-Message-State: APjAAAWsER2B5qtbH0kL2yyP8DiSYtXNsu1IcP7jH892rb6dBkvP7fHn 1rnzS+Lx6KSWRc36UImZgxvkahR4WdxHdH8oRWc=
X-Google-Smtp-Source: APXvYqwnoynG5hMTjMp9gqJFDeYx5KY5xXVNBBBjWnLV8Vr0Ag+ZZqhBThv04y6Mq9E7kgEO2m4e5feRywrxxxU/TV4=
X-Received: by 2002:aca:c088:: with SMTP id q130mr2216513oif.54.1568167689241; Tue, 10 Sep 2019 19:08:09 -0700 (PDT)
MIME-Version: 1.0
References: <HK0PR03MB3970C6DCC635E7CD802D65FDFCBD0@HK0PR03MB3970.apcprd03.prod.outlook.com> <BYAPR05MB54636A2332FED916A26A6F14AEBD0@BYAPR05MB5463.namprd05.prod.outlook.com> <3e31873a-278a-2154-0e71-4d820bba323d@gont.com.ar> <4012D854-2F10-4476-951D-FFFE73C5083C@gmail.com> <cb2f56f8-acdc-d68d-0878-9609cb3d7b1b@gont.com.ar> <28214_1567694772_5D711FB4_28214_238_1_53C29892C857584299CBF5D05346208A48BFA9F3@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <b83a7060-0517-c6ad-f6b0-bc9e61e4667f@si6networks.com> <17120_1567700712_5D7136E8_17120_341_1_53C29892C857584299CBF5D05346208A48BFAEF1@OPEXCAUBM43.corporate.adroot.infra.ftgroup> <HK0PR03MB4066C9D767D4D462B4C59D73FCB60@HK0PR03MB4066.apcprd03.prod.outlook.com> <6833faa5-943c-d7d5-21f8-2a933defe492@gmail.com> <CA+b+ERmgZ6g1rd6K3nGjpcuJEY59Ghp8YEiFZo=n3P3tnx52tQ@mail.gmail.com>
In-Reply-To: <CA+b+ERmgZ6g1rd6K3nGjpcuJEY59Ghp8YEiFZo=n3P3tnx52tQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 11 Sep 2019 11:37:57 +0930
Message-ID: <CAO42Z2wOUCt82wUJKq_jHfjfCXPZMF=9mztXn+fEQpJK9rLidA@mail.gmail.com>
To: Robert Raszuk <rraszuk@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-voyer-6man-extension-header-insertion <draft-voyer-6man-extension-header-insertion@ietf.org>, Suresh Krishnan <suresh.krishnan@gmail.com>, Fernando Gont <fernando@gont.com.ar>, draft-ietf-spring-srv6-network-programming <draft-ietf-spring-srv6-network-programming@ietf.org>, Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary="00000000000010c73f05923d7e86"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/rtf3hKSMLUEVQx4fYj8taoWmtr4>
Subject: Re: [spring] Question about SRv6 Insert function
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, 11 Sep 2019 02:08:12 -0000

On Wed, 11 Sep 2019, 06:49 Robert Raszuk, <rraszuk@gmail.com> wrote:

> Hi Brian,
>
> > the first discussion should be whether we (as a community) believe we
> should
> > standardise features that only work within a specified domain, or
> continue with
> > the assumption that standardised features must work across the open
> Internet.
>
> Indeed I agree.
>
> Just to rephrase the question:
>
> Is IPv6 to be used only as end to end host to host protocol or should IPv6
> also be used as transport protocol natively in the networks..
>
> Solid deployments prove it can be used for both. Many people think it can
> and should be used for both.
>
> But if there is solid IETF formal statement that it is *only* to be used
> as end to end host protocol then we should really start putting more work
> into other encapsulations which will allow to simply transport IPv6
> datagrams as payload or alternatively industry will seek other standards to
> conitinue work on IPv6 as transport protocol.
>

If IPv6 can't meet your requirements without dodgy hacks that decommodifies
IPv6, makes it not interoperable with existing IPv6 implementations and
deployments, and makes it much harder to troubleshoot, then no, you should
not use IPv6.

I'm reminded of advice from my Father. Don't use a good blade screwdriver
to open the lid of paint can, because you'll ruin the screwdriver. It's not
the right tool for the job.





Just imagine how it can be called ... IPv6+ :)
>
> Many thx,
> R.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>