Re: [spring] Understanding the replication draft

Robert Raszuk <> Wed, 01 July 2020 19:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AA9783A0C55 for <>; Wed, 1 Jul 2020 12:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
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=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hCaGAyMxW3yM for <>; Wed, 1 Jul 2020 12:27:43 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A35A93A0C52 for <>; Wed, 1 Jul 2020 12:27:43 -0700 (PDT)
Received: by with SMTP id rk21so26229307ejb.2 for <>; Wed, 01 Jul 2020 12:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lEiWsvdz0dI91CHBuqQzv9d5uJ797n3y54DCYSZ2J5M=; b=CIcpwNKfHw6pgAf2Wu1pzEmd2W7UK73BYfvGKM/95l0U5ZLlklC40Iwif+K4ChZrIR KtYEkeQPNDWOYvYI0TOxcwG4sMRFqX5zr9xp4hK2PtlAwH4cZVKVMbFsmYV1RNUujTho DqSQBKj1YE+bZElhz7K+53cs1zkuwuuAkbR4BWKWP69v16wShJuo/wvEsN4cwx4Z6+WK CPqi+1OgMIeT91+suv7bCwmEZLViCUgr3nw1D7KZRLX1wDqJxrH1WkiFuEXVkWWRlLB0 NkwmiPu4wdDVg3V/y9p9QZUNnMXV2hlA++Oe3f8wcPpdwNSOHUGtRKGutgi/qy2sEmkp 1bmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lEiWsvdz0dI91CHBuqQzv9d5uJ797n3y54DCYSZ2J5M=; b=Abo2j2Uv7Dmocbrt34jFyUBrXGEOMTRwFrG4ZlcWyRl2SkzJAT2VGWrvENXkpAMdP6 cxAsQSlGvgMYefVJqBiwWX8Pu1W1MDcA80pNM6Vs199aftCSeVYP0fR0wl/KBMbizIpX 5AuiHUACUtOHpkC8cWXbSXpINHgpqNY6/xd5z9ffXxOeqdSODwblvfrqxOz4t7VidwdQ vBDpOilwCDbzp/1QV1lbXrAy+Xp4CuwlP45j7vIxg4Eu6F5bwZYAaOac1mFSL/ehHALG oJ8s56s6R0PI0e3Dxcd99fsJ0x+ZrZLM7+Bd1yT0+L0FisqFi0v9ZXv6vnkCTpD0SSHg C2dw==
X-Gm-Message-State: AOAM533/4rfZMaBZ+A0HEhAC1/ZHEc4oHbu3dYZhJeu4y3xW6pRX2z+R izOA8ZAhjTpbr2MrIBIs6j7RVI4hTuq7hMw05R4O6A==
X-Google-Smtp-Source: ABdhPJx+67hSW4IpN7rq3LC2tGBfwZZkmX8oD45PHlOhyBlyQcA5axCz4aDJKpwckLZNQ14TQzoOcrDuZv9Yc8aLTBQ=
X-Received: by 2002:a17:906:3a04:: with SMTP id z4mr18495279eje.441.1593631662017; Wed, 01 Jul 2020 12:27:42 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Robert Raszuk <>
Date: Wed, 1 Jul 2020 21:27:33 +0200
Message-ID: <>
To: Rishabh Parekh <>
Cc: Joel Halpern Direct <>, "" <>
Content-Type: multipart/alternative; boundary="0000000000001e35f905a9664970"
Archived-At: <>
Subject: Re: [spring] Understanding the replication draft
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 01 Jul 2020 19:27:46 -0000

Hi Rishabh,

 > Of course, care must be
> taken to avoid the "explosion" as you describe it. G-SID-2 has to map
> to a unique node; for example, it may be an Anycast-SID that takes
> packet to distinct nodes from each of the downstream node, or the
> downstream nodes can be border nodes connecting to other segment
> routing domains where G-SID-2 resolves to distinct nodes in each
> domain.

I think you are stretching it too thin.

See even if G-SID-2 is anycast SID you have zero assurance that physical
nodes packets will land on would be at all diverse.

Likewise crossing domains yet providing identical global SID now to be a
different node in each such domain to me is not a realistic example.

I think we have two options:

A) Firmly state that replication SID MUST be the last one on the stack

B) Instead of real SID after the replication SID provide a binding SID
which locally will be mapped to a different SID list imposed to
each replicated flow.

What is currently in the draft seems to be very counterintuitive and IMHO
will result in operational difficulties.

Thx a lot,