Re: [bess] 答复: SRv6 versus SR-MPLS

Krzysztof Szarkowicz <kszarkowicz@gmail.com> Sat, 05 October 2019 14:11 UTC

Return-Path: <kszarkowicz@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F86312081E for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 07:11:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 RCL7NFn973jf for <bess@ietfa.amsl.com>; Sat, 5 Oct 2019 07:11:24 -0700 (PDT)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 8F84212081A for <bess@ietf.org>; Sat, 5 Oct 2019 07:11:24 -0700 (PDT)
Received: by mail-pl1-x62d.google.com with SMTP id t10so4524959plr.8 for <bess@ietf.org>; Sat, 05 Oct 2019 07:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dTduzU57ZuE5Bi3i7HzD18Dv4TSaGBT7oG1j2UPbqpw=; b=inpPV+fIJ2Gg3PI0/H/mLzlEdYm7bKTWw24idT/ZA36FC7yGPatsOfYCU3xb63wrCG z2ClfKZFma3f/CrToah8mFM0j1gliyLtsnzemN8/UWKr4gI/qRNEdelocoPTRmYno5s+ LsG1IFiNqd5WFYg/qpQxDWPIzSfEzBHPHLVnlaD6o6XPOmfZYHHbleqWsw2kw7vMmINL HwGLy1800gED6uqzSY8NAL+hVJaLVpo3bvxdf9Tey/i06DoWkeYOQpK8Qma/oao7eOek x2rxSGBrwfURpQDcycHVZegnof4ANVdFJ29XdRKEh8l5VyDBfoVFZ3epmDTBRPLQsx3C kdlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dTduzU57ZuE5Bi3i7HzD18Dv4TSaGBT7oG1j2UPbqpw=; b=c81AZVN0OQsE/Vy2eRsAP0hbSw9qX12ziDQ6X++2frJM1wzi57XbHDVidQ8XzD4Wxg nTom05w0b9mXEXhPSl3yWeyGpk84qgTx72SVm+Od4V81GquY+kWhHv7yW+DZ3fiCItlT ECqhtJiWetcI6mNEeepzfQ/53DCGhId0ZPYCdRWe1sTen2dhyQ5lu5/VaKaVKMBq8IPY B8EQFIorCeMgBurlt5EdJYC86iBkk2yltY1dYK682PZvSa5fXWxFjKSmrLWYI5s+04SG n7fZHHHUTN1yjdCZmSOgctt1C+PNlFbjqTee852qkpu/ZMlXoO+DWYxXyu5JMU+PO9Wp g2fQ==
X-Gm-Message-State: APjAAAXk4LlyBXVQOZ7gpm7CNtDbrAHg2jgox7OnqewKIBqsotLUJ7Pc 9BFjNNblapEYLuknhb5dkEc2Z8NI
X-Google-Smtp-Source: APXvYqy298uw8Cl8CHB1aK0h14lXx5ZNYMXJKPSjdloTXhln2cwLRnvpFV8NAMryTYaM8aGJZfsA+Q==
X-Received: by 2002:a17:902:7d92:: with SMTP id a18mr20403966plm.243.1570284683868; Sat, 05 Oct 2019 07:11:23 -0700 (PDT)
Received: from kszarkowicz-mbp.jnpr.net (jpams-nat11.juniper.net. [193.110.49.11]) by smtp.gmail.com with ESMTPSA id u18sm9839386pge.69.2019.10.05.07.11.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Oct 2019 07:11:22 -0700 (PDT)
From: Krzysztof Szarkowicz <kszarkowicz@gmail.com>
Message-Id: <25AEE756-8EF5-43C5-9B89-201D46B8AD1D@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AFA8C2E0-0AAA-4361-AE6B-16F5E80C9BE7"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sat, 05 Oct 2019 16:11:18 +0200
In-Reply-To: <CAOj+MMGn-d1pEWxpT7GCA9D29F3tLKdUATc1rOHzhhLV=XyMkA@mail.gmail.com>
Cc: Lizhenbin <lizhenbin@huawei.com>, Gyan Mishra <hayabusagsm@gmail.com>
To: Robert Raszuk <robert@raszuk.net>, "bess@ietf.org" <bess@ietf.org>
References: <8D0ACADB-2F74-4F66-8E67-79E63E1A8FF1@gmail.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D934E764D@DGGEMM532-MBX.china.huawei.com> <CAOj+MMGn-d1pEWxpT7GCA9D29F3tLKdUATc1rOHzhhLV=XyMkA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/hCgoaEl2CzuSsw-D0z0Nz_50TwU>
Subject: Re: [bess] 答复: SRv6 versus SR-MPLS
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Oct 2019 14:11:28 -0000

I second Robert.

SRv6 is yet another tool in the overall toolset, and, as with every tool, there are situations (use cases) where using this particular tool might be the optimal solution, whereas there are use cases, where other tools do the job better, and, there are use cases where using this particular tools is complete misunderstanding. There as are as well use cases, where combinations of multiple tools bring the best effect.

Thanks,
Krzysztof


> On 2019-Oct-05, at 13:23, Robert Raszuk <robert@raszuk.net> wrote:
> 
> 
> IMHO the question of SR-MPLS vs SRv6 is wrong as it all depends what are you trying to accomplish in your network and what services you need to run on it.
> 
> For example some networks need TE some do not. 
> 
> Some may like to carry L2/L3VPNs some do not. 
> 
> Some may think about requirements associated with special packet handling perhaps augmented with in house development of P4 based fancy services so do not.. 
> 
> Last some network are IPv4 only, some are IPv4+MPLS, some may be dual stack and some may be IPv6 only. 
> 
> For some the overhead associated with attaching additional data to each packet matters - so do not care and do not even realize it :).. 
> 
> So this is very loaded question. It is like asking should I go left or should I go right without stating your ultimate destination. Sure likely you may end up there regardless how you turn but it may not be optimal path. 
> 
> And last as this is BESS WG ... I would really seriously consider for BESS services use of RFC4797 and RFC7510. 
> 
> Cheers,
> R.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Sat, Oct 5, 2019 at 11:35 AM Lizhenbin <lizhenbin@huawei.com <mailto:lizhenbin@huawei.com>> wrote:
> Hi Gyna,
> 
> We proposed following the draft which has relation with your question. Hope it may be helpful.
> 
>  
> https://tools.ietf.org/html/draft-xie-spring-srv6-network-migration-00 <https://tools.ietf.org/html/draft-xie-spring-srv6-network-migration-00>
>  
> From my point of view, one of the best advantages of SRv6 is easy incremental deployment.
> 
> I believe there will more deployments of SRv6 soon.
> 
>  
>  
> Best Regards,
> 
> Zhenbin (Robin)
> 
>  
>  
>  
> 发件人: BESS [bess-bounces@ietf.org <mailto:bess-bounces@ietf.org>] 代表 Gyan Mishra [hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com>]
> 发送时间: 2019年10月5日 8:22
> 收件人: bess@ietf.org <mailto:bess@ietf.org>
> 主题: [bess] SRv6 versus SR-MPLS
> 
> 
> Bess,
> 
> What is the benefit of SRv6 over SR-MPLS for greenfield deployments or existing mpls deployments.
> 
> Regards,
> 
> Gyan Mishra 
> IT Network Engineering & Technology 
> Verizon Communications Inc. (VZ)
> 13101 Columbia Pike <https://www.google.com/maps/search/13101+Columbia+Pike?entry=gmail&source=g> FDC1 3rd Floor
>  <https://imailcn01.huawei.com/owa/UrlBlockedError.aspx>Silver Spring, MD 20904 <https://imailcn01.huawei.com/owa/UrlBlockedError.aspx>
> United States <https://imailcn01.huawei.com/owa/UrlBlockedError.aspx>
> Phone: 301 502-1347 <tel:301%20502-1347>
> Email: gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com>
> www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT <http://www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT>
> 
> Sent from my iPhone
> _______________________________________________
> BESS mailing list
> BESS@ietf.org <mailto:BESS@ietf.org>
> https://www.ietf.org/mailman/listinfo/bess <https://www.ietf.org/mailman/listinfo/bess>
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess