Re: [spring] WG Last Call draft-ietf-spring-nsh-sr

Greg Mirsky <> Wed, 17 February 2021 07:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 186C03A162F; Tue, 16 Feb 2021 23:38:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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 nx68Jh8AKirN; Tue, 16 Feb 2021 23:38:35 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::12d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CFBF23A162D; Tue, 16 Feb 2021 23:38:34 -0800 (PST)
Received: by with SMTP id h125so705259lfd.7; Tue, 16 Feb 2021 23:38:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=x9vZ+raK9RiJkolnrhebu2htbUk0zSQrCwBtoYCCIUY=; b=RTgSfkB9GtKQFJc9QaQrIXz05qVdVGlDDldfl/KXRFWMV29SD/HkUsTo9jMJyJ3vSN fDdVNE0wa3fvU0dDzo+cORsCJaglJwmJpZL2T8qZknLVD5wM+6Jod5k4jJC5XkxU+Vu1 wn/AvIz6O4qpOGLIC4CqVlHFINPw6fnJESAl9stULWoql3kYMUH/4SKrzG8PtUeciCWr cRsKWtwVfkjAvqyDfnJ5obONpIvfTBblqkMy6B193aOu5wjoUzZat2yBkJWZzfB78stV D74S3sKaw/TXazFNvhz96k7c+AAq0SsLFUsWIIiosK2mCK0rQz5tq0JXgEfgxgo8xeDd 7y2w==
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=x9vZ+raK9RiJkolnrhebu2htbUk0zSQrCwBtoYCCIUY=; b=b2LBdUouMlMg/p8YTUnKZt09MN9kfy+eNQCbmWsMMjLsDD9fLzZl0soTDvJuh1KDRl rQJkJrtJQ94dnFZ8LoHSOQBSz8tXqaBfn0Ms0LqqXcuAHMQkwVVaWTk0kOaQIryCAeyZ NubLwLXhBLTJGYlGTjwP74/Mv2eMbfIHXaxdgd36Oh8hDtKBwvatMLfc8Wkq48JzG9Fk 0AI6fNT/NmrUCe/T4HaqHGeNuRdjhRg9KDLqDRxQjdkr1hsdUIRiCO2ulD/xmWIF9DQY Dsz4Vx4UnA+Nk3OoLhUF6cz42lBAyKVwRqDRz1kX2fAlFaF/z7dgQ0rxnoJQVMT8n/ad /71Q==
X-Gm-Message-State: AOAM530Ioq9rnJXpY4QSqsds2JO4Jc0y1eqd/QEuh3xknIYNR9BLL9j7 ORePOpXE2jWpkFHNivoavmRHb3iw7HSboGqtRPI=
X-Google-Smtp-Source: ABdhPJw3teg+R9VZgJWaur3/5KopnbE57kUj7LUOz4mrusg1w8tZ8yyLsE4r7PQCfTumNAJeXSMNgs5KZ4MFfTGdoG8=
X-Received: by 2002:a19:7e09:: with SMTP id z9mr14088114lfc.35.1613547513031; Tue, 16 Feb 2021 23:38:33 -0800 (PST)
MIME-Version: 1.0
References: <25012_1612895472_6022D4F0_25012_72_1_53C29892C857584299CBF5D05346208A490C4A3A@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <25012_1612895472_6022D4F0_25012_72_1_53C29892C857584299CBF5D05346208A490C4A3A@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
From: Greg Mirsky <>
Date: Tue, 16 Feb 2021 23:38:22 -0800
Message-ID: <>
To: Bruno Decraene <>
Cc: "" <>, "" <>
Content-Type: multipart/alternative; boundary="00000000000057b18705bb834ea2"
Archived-At: <>
Subject: Re: [spring] WG Last Call draft-ietf-spring-nsh-sr
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, 17 Feb 2021 07:38:37 -0000

Dear All,
I have several questions about the draft:

   - When using the approach described in Section 4, i.e., SR-based SFC
   with the integrated NSH, how does a re-Classifier scenario be handled? If I
   understand it correctly, a re-Classifier can change the SPI of the
   NSH coming back from the SF. If that is the case, the SFF will not match it
   to the saved SR information because the SPI had changed. How would SFF
   forward the NSH and the payload?
   - Related to the scenario from the above. The stored SR information that
   is not being used appears to become stale. It seems that it creates a leak
   of resources in a system that should be controlled somehow.


On Tue, Feb 9, 2021 at 10:31 AM <> wrote:

> Dear WG,
> This message starts a 2 weeks WG last call for draft-ietf-spring-nsh-sr
> [1].
> After review of the document please indicate whether you believe this
> document should be progressed to the IESG.
> In addition to yes/no, please consider providing a technical review of
> this document; in particular if you care for this document.
> Indeed, since WG adoption, this document had benefited from little reviews
> from the WG, so we need more review from the SPRING WG.
> If you are aware of an implementation of this document, please report the
> implementation either on the list or to the chairs so that the shepherd can
> report implementations in the writeup.
> Note that I’ll forward that call to the SFC WG.
> Thanks!
> [1]
> --Bruno
> _________________________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> spring mailing list