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 3FAF3120DF3;
 Sat,  7 Sep 2019 04:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level: 
X-Spam-Status: No, score=-0.498 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,
 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 qQNmliZY5i0r; Sat,  7 Sep 2019 04:14:25 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com
 [IPv6:2607:f8b0:4864:20::22c])
 (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 23C681200A4;
 Sat,  7 Sep 2019 04:14:25 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id k20so7149399oih.3;
 Sat, 07 Sep 2019 04:14:25 -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:content-transfer-encoding;
 bh=OXVMYYuDg/iYKLc8m2oB6aG3DTR3Asc6a6gbOW3K7lc=;
 b=kp4+SKomrbQM3x51LiutlKziUgJK6dfCVXM8wBuTlKhfpO7jpCAW+ZERnkszplT1Xx
 P9r4ncFPOeiooi1okPdtkjz68LN2T5lRdTg0uoiJNLRA1ms5mZIL0H2zcqfdFG/SgPP+
 w2qr2sT6XKZcUvHsjLmtOYsJOHJH17oak+ZxdCSaTgfCxbMPb8eloFGhDAYpbl0nECS9
 XxCgS1iIXJ9BTZESuIdFmYIUfKVO+guy3LL5k3OUvjys6xWDxxztJuHu64zEzeoDgoBx
 9pzzCwUYmlBxOfaUfvOpkXPEKQTYTHfkDkL1OHO2AlRk7t6Gokut0VuXRFnsfgNVuHTv
 mVvQ==
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:content-transfer-encoding;
 bh=OXVMYYuDg/iYKLc8m2oB6aG3DTR3Asc6a6gbOW3K7lc=;
 b=mZA5B7Buf6DxZnKKrCIhSTRxqlV4liCLFxqAYdMOQnigdr5CLccZTf9j2NzmaG8/8I
 AjzymUdJxIZHvQJhPFp5wZSzFAMVXE2XPW1T9P5q1HPoNHK4BUDiokE+j3So+ignw8k0
 chKtoYeRW0qYWbpoNs+k3ipYz6l9gyJO7xK7ebJDT1A5mJMURw7JOgTFxPfFFVgssXjx
 hH69ysa0jlbtYmWL4yEG/K7daM3656j6xJ9Z0bSE2RI0Uha0p/lBnFvWBe/Eic+i+ZmU
 4/uBkVl2sLNQf6lb2jpBicI00ZsyqnY1QImgVpR33n3Rgl7DfmkTW+QS+4XnrQIR4hlc
 BL7g==
X-Gm-Message-State: APjAAAWG2uMyorqwv1V7HM48ElFE/Jas2mNPNdlziKtONqoZxqfYhE9X
 FIZFo3YPg27T7PS4SoclRS5+vpCmmIHB11pg7GM=
X-Google-Smtp-Source: APXvYqzGVc6BQ0+m8uBLICFd4E+1+EkaALnHLaSQBBpYGwyGticNOGqnzPihZ2UlDEmQi+H8CK+Zdq3WXO1L9oL9sKw=
X-Received: by 2002:aca:c088:: with SMTP id q130mr10722350oif.54.1567854864469; 
 Sat, 07 Sep 2019 04:14:24 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR05MB5463153B47BFE83350C566E7AEBA0@BYAPR05MB5463.namprd05.prod.outlook.com>
 <CA+b+ERm4x072JQZQovX0MVcea3=0DOCSESopAXj_SE1vMi8qkQ@mail.gmail.com>
 <06CF729DA0D6854E8C1E5121AC3330DFAE9362F9@dggemm529-mbs.china.huawei.com>
 <CAO42Z2y-hq71wr9ogzmn2=rO0xySy63iXhNXrFDuqO7r5Pwa7A@mail.gmail.com>
 <CAOj+MMFN5pbaVePWrJA61jd7f9d_2bU-Nu9oppFDsAc_B7APDw@mail.gmail.com>
In-Reply-To: <CAOj+MMFN5pbaVePWrJA61jd7f9d_2bU-Nu9oppFDsAc_B7APDw@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 7 Sep 2019 21:13:57 +1000
Message-ID: <CAO42Z2x4-9-1YseuyqnCRh7c+J-zb2ksGXpk_Hs17H5uLz4Hvg@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Huzhibo <huzhibo@huawei.com>,
 Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, 
 "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>,
 Robert Raszuk <rraszuk@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/VxPi2HonKJtSJ8544loYSsuXh6k>
Subject: Re: [spring] Regaining Focus on SRv6 and SRv6+
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: Sat, 07 Sep 2019 11:14:27 -0000

On Sat, 7 Sep 2019 at 19:56, Robert Raszuk <robert@raszuk.net> wrote:
>
> > It's tempting to write up SR over IPv4
>
> You don't have to write anything ... it is already written and looks like=
 moving fwd :)
>
> https://tools.ietf.org/html/draft-ietf-mpls-sr-over-ip-07
>

That's tunnelling MPLS over SR over IPv4. I'm talking about native SR
over IPv4 e.g. "SRv4".


> Thx,
> R.
>
> On Sat, Sep 7, 2019 at 8:05 AM Mark Smith <markzzzsmith@gmail.com> wrote:
>>
>> On Sat, 7 Sep 2019 at 14:58, Huzhibo <huzhibo@huawei.com> wrote:
>> >
>> > Hi Robert:
>> >
>> >
>> >
>> > Agree with you.
>> >
>> > SRv6 is a completely different technology from SR MPLS. The biggest di=
fference is that SRv6's Sid itself has routing capabilities. For example, i=
t is aggregatable, it is programmable, it is globally unique over a larger =
scope. of. Sid's routing capabilities bring many benefits to the network. F=
or example: network scalability, reliability, and simplified Overlay progra=
mming. So, I think that any optimization we do for SRv6 should not sacrific=
e Sid's own routing capabilities. If we just want to solve the interoperabi=
lity problem between MPLS network and IP network, we can solve this problem=
 in the field of SR MPLS.
>> >
>> >
>>
>> Does any network need a SID space that is literally bigger than the
>> combination of both the current and and any possible future IPv6
>> unicast address space?
>>
>> It's tempting to write up SR over IPv4, because IPv4 is currently a
>> far more commodity technology than both MPLS and IPv6, probably on
>> some metrics in the order of one or more magnitudes, well known, well
>> proven, well understood, would leverage existing IPv4 implementations
>> of which there are many, and would have only have 32 bit SIDs, so the
>> tunnelling overhead cost would be much lower than 128 bit SIDs as a
>> result of using IPv6 addresses for SIDs.
>>
>>
>> >
>> > Thank you,
>> >
>> > Zhibo
>> >
>> >
>> >
>> > From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Robert Rasz=
uk
>> > Sent: Friday, September 06, 2019 9:33 PM
>> > To: Ron Bonica <rbonica=3D40juniper.net@dmarc.ietf.org>
>> > Cc: spring@ietf.org; 6man@ietf.org
>> > Subject: Re: [spring] Regaining Focus on SRv6 and SRv6+
>> >
>> >
>> >
>> > Dear Ron,
>> >
>> >
>> >
>> > I think you forgot few main points in the summary:
>> >
>> >
>> >
>> > * Many operators use SR-MPLS successfully and it has been both standar=
dized and successfully deployed in the network with interoperable implement=
ations
>> >
>> >
>> >
>> > * The overhead on the data plane of SRv6+ is very comparable to overhe=
ad of SR-MPLS
>> >
>> >
>> >
>> > * The control plane extensions BGP, IGP are available for SR-MPLS and =
non are available for SRv6+
>> >
>> >
>> >
>> > * SRv6+ requires a new mapping of SIDs to prefixes to be distributed b=
y control plane
>> >
>> >
>> >
>> > * If operators choose not to use MPLS transport SR-MPLS can be easily =
transported over IPv4 or IPv6 vanilla data plane
>> >
>> >
>> >
>> > * Extensions for additional applications like L3VPNs or L2VPNs will re=
quire another set of protocol and implementation changes.
>> >
>> >
>> >
>> > * If there are vendors who do not want to provide SR-MPLS SID mapping =
to IPv6 addresses in their control planes let's focus standardization and i=
ndustry work in this direction.
>> >
>> >
>> >
>> > With all of the above I think it would be a serious mistake - at this =
point of time - to continue work on SRv6+ in the IETF.
>> >
>> >
>> >
>> > Thank you,
>> >
>> > Robert.
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Sep 6, 2019 at 3:08 PM Ron Bonica <rbonica=3D40juniper.net@dma=
rc.ietf.org> wrote:
>> >
>> > Folks,
>> >
>> >
>> >
>> > We have explored many facets of SRv6 and SRv6, sometime passionately. =
I think that this exploration is a good thing. In the words of Tolkien, =E2=
=80=9CAll who wander are not lost.=E2=80=9D
>> >
>> >
>> >
>> > But it may be time to refocus on the following:
>> >
>> >
>> >
>> > For many operators, SRv6 is not deployable unless the problem of heade=
r length is addressed
>> > Many objections the uSID proposal remain unanswered
>> > SRv6+ offers an alternative solution
>> >
>> >
>> >
>> > Given these three facts, I think that it would be a mistake to discont=
inue work on SRv6+.
>> >
>> >
>> >
>> >                                                                       =
             Ron
>> >
>> >
>> >
>> >
>> >
>> > Juniper Business Use Only
>> >
>> > --------------------------------------------------------------------
>> > IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> > --------------------------------------------------------------------
>> >
>> > --------------------------------------------------------------------
>> > IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> > --------------------------------------------------------------------
>>
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring

