Re: [bess] SRv6 versus SR-MPLS

Gyan Mishra <hayabusagsm@gmail.com> Mon, 07 October 2019 22:29 UTC

Return-Path: <hayabusagsm@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 352DD12010C for <bess@ietfa.amsl.com>; Mon, 7 Oct 2019 15:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 yZ7qfBSe-kxT for <bess@ietfa.amsl.com>; Mon, 7 Oct 2019 15:29:16 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 24955120073 for <bess@ietf.org>; Mon, 7 Oct 2019 15:29:16 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id y189so14362371qkc.3 for <bess@ietf.org>; Mon, 07 Oct 2019 15:29:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=e+Fu4HyGlC7aEWDAeW68E//A03pXfCto4Z5C5JO9REA=; b=GZDSOnaeEXPASvBut4n3UHO0+noYpGZjFtzeIiFo44OfnDTpdc/CcKoYvPdCNQRDlT Nv8nInMjjpvV4cqCIbakumcaTqCTbBI1T5fdo2lQbdPFTBI6+2R+1AhJTAoMNw4TBKDt BdVuPFxMCMiHxcOZxMoq6uZFdexG4yyg8B4qBVaqFSlrdbY/VgSEMX3yvCaOlvVJqMd0 MVh9c/4siqsHwA24BY4pFFWlFO1UvhHklfuTStcvZkDlxbEoA6b3yrV/HQq5XUDyGW95 AMsYFW+ZAQ6RXq1hgAerTUK9m0Em3glTCONsYJQxU4S/3liaWxuohW+uULwdTpSUDlqa wEKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=e+Fu4HyGlC7aEWDAeW68E//A03pXfCto4Z5C5JO9REA=; b=PK1t1wBSVoPh7JzMqgEPhdpVEuXIuaW14YWEnISxWsGca/ijIJhXAQSJ3Y1GmRYO0X 04TtrnWjNidXSIxnqfKJpYg1jqCd37pjQMZ7dgKchiDWHxLh9Ih/HL6KVM4d1Dg6U0Jw 42rBrYojnvowc82mQc/M5AaeNreRXzKL4kAsEBYz/aXUpr+33YoF1McQ5I9CpvYIOU+e dAyP1aCSPbWOIX5+Us7XRY6TRu+F9wg9U3tVdOMPKaxDYZ8xgkAa42gRwuMg8QLnMdHZ i9DLywsV07dPQS1iEoMBAWN7ROsWKSEsJ+RvcEVweLseH1sj0cpLLifzgHzu9U296fA+ 883A==
X-Gm-Message-State: APjAAAV8/cqYQQFpsgsMxYO/YMlkDigGBi820746XQHjU/6WFL0ei7GR 02q92lHWyY/qeFVVIdMkC6c=
X-Google-Smtp-Source: APXvYqxdYVZHAs7xuIrz4sUpuR68U2NDk1odTEpMsIsHRWslRRmTzSvGmmwxzuak8mIExRPJAD6qAw==
X-Received: by 2002:a37:6789:: with SMTP id b131mr7987888qkc.314.1570487354996; Mon, 07 Oct 2019 15:29:14 -0700 (PDT)
Received: from ?IPv6:2600:1003:b004:b313:7dbb:de4f:3ebd:25c9? ([2600:1003:b004:b313:7dbb:de4f:3ebd:25c9]) by smtp.gmail.com with ESMTPSA id g45sm8757223qtc.9.2019.10.07.15.29.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Oct 2019 15:29:14 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <29c7ff28-36ca-4ce0-b968-4bbcaf7bd760@gmail.com>
Date: Mon, 07 Oct 2019 18:29:13 -0400
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Greg Mirsky <gregimirsky@gmail.com>, BESS <bess@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4248B078-3F7A-472B-B2D7-3F231F7D932B@gmail.com>
References: <8D0ACADB-2F74-4F66-8E67-79E63E1A8FF1@gmail.com> <0C48ECF1-D889-44F9-99F1-AA69B6DD1C28@gmail.com> <CA+RyBmWSUi4ooueQ=D+rq=4UVVVepR8zb6KeAzLQ7MU=4=TFNA@mail.gmail.com> <caca288a-f85e-0d2b-0607-21dc5ebd4a13@joelhalpern.com> <29c7ff28-36ca-4ce0-b968-4bbcaf7bd760@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/7pxHcc2Z7vh6d_CH0yRqhmUNXn4>
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: Mon, 07 Oct 2019 22:29:18 -0000

In-line

Good idea agreed that’s a good way to go using uSID along with SR-MPLS.  

I am going to set that up in my lab all 3 in parallel overlays SR-MPLS, uSID and SRv6.  That may not be a bad idea having the architecture in parallel I wonder and using SRv6 when you don’t have MTU constraints use Ti-LFA and for longer SID lengths paths use SR-MPLS in the same topology.  I believe the interoperability draft that was sent earlier on talks about building both SRv6 v6 data plane and SR-MPLS ipv4 data plane in parallel using uSID.

Gyan

Sent from my iPhone

> On Oct 7, 2019, at 6:19 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
> 
> If you need uSIDs for MTU control or restrictions on the depth that you can parse in the packet, you should also consider regular MPLS-SR, or in an IP only network draft-ietf-mpls-sr-over-ip (RFC editor's queue).
> 
> - Stewart
> 
> 
> 
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess