Re: [spring] Network Programming Interface for Provisioning of Underlay Services to Overlay Networks Using SRv6 (draft-xie-spring-srv6-npi-for-overlay)

Gyan Mishra <hayabusagsm@gmail.com> Sun, 13 March 2022 00:26 UTC

Return-Path: <hayabusagsm@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 1D8363A0D28 for <spring@ietfa.amsl.com>; Sat, 12 Mar 2022 16:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 iadqYnPHbMaS for <spring@ietfa.amsl.com>; Sat, 12 Mar 2022 16:26:41 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 CE9863A0D23 for <spring@ietf.org>; Sat, 12 Mar 2022 16:26:41 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id gj15-20020a17090b108f00b001bef86c67c1so11347812pjb.3 for <spring@ietf.org>; Sat, 12 Mar 2022 16:26:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=67h7AY9+XPDptXCO9HCZO7NIy0Ztwbf3NUJUPvQOSBE=; b=n5HeUKstTe7Jg0g6D72OyhUck8+5zUknnTIPklRW53yozbBgnAo9zmitKT9/CIV5Bd 5xoi/Rvr2zq51LE9GBJTyRXRSCH3dDd4OleQ9ha7HUObXeIien1eExgxKmnewUgIfWgZ 9rqyb2nrppPqOsIq76egruXCZr0hlYY3Rzk5xKadZxMOgZibBFrmvf8EnRPxA1X4ukkW yO4xLIDeH5e/F4UnAsCdKwEbdlh6MhHb2fWkPbiJKnAa17aOYf4IeXAIyCof10EzR8Sg ZQ8Z6u0BZrG4vHuniPhq686i88THc93fEMMoR3JX/UVuQuVarS3Mj3juVyEB7QU7ae2z Y1Dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=67h7AY9+XPDptXCO9HCZO7NIy0Ztwbf3NUJUPvQOSBE=; b=1m40p9BIkPxi+p45MUOJyIq5dA+veQkmlNSG1Op36WRm1yVFO2qJUyOfRrLyUClfQm tXgJhZceJkGG5vEPTttxgoqdgRfaEhN3gA0kEzajrDQbn3UDFJtqSChzykcnY26Zlbk8 4l/3oXuBi3aYdEF/KulKRH5ZfADStQCsV/fYejoWZFf2zP/1h7dqph3X5sIxVol9LuW5 nkm6zUncIPw/B2yLc/7AzBa20UJgDEVYnmDmwnLF9TMZaOR6J6lZkY8WGZfIPAv/2wlo OerY9bMna3aEONaEUWBiwbX50VqeIG5oLIcUEtAIDtEHADW6gL9gez+e2OE74hJKV7WX t7gw==
X-Gm-Message-State: AOAM531hLKjbRz6Y/I8/k8I+6S9jw3+yFEmhANK9cwuFcGZDd2NmXWZB GrVaslPv4hiBu//sdhf0XjMx4dMRCny7eS1wwU3IeAHY
X-Google-Smtp-Source: ABdhPJzyK1U8wkq2QywkU2mwYopoPom5lgFLEXf5VF5DuSNiBl9lnBP6NLWatuj76AE7EvwG1QpYg3ymU2c1mR+pCQY=
X-Received: by 2002:a17:90b:4f4e:b0:1bf:88f6:e5b5 with SMTP id pj14-20020a17090b4f4e00b001bf88f6e5b5mr28267049pjb.47.1647131200649; Sat, 12 Mar 2022 16:26:40 -0800 (PST)
MIME-Version: 1.0
References: <5138b23393b7434fa674eefd1886385d@huawei.com> <f2ba3c4a-e30d-d3f2-211b-0b42d99cd876@ninjabadger.net> <bdff393fee4e484fb364baf56b0391e6@huawei.com> <AM7PR03MB64513AEDE5ED62ECE0F50280EE0B9@AM7PR03MB6451.eurprd03.prod.outlook.com>
In-Reply-To: <AM7PR03MB64513AEDE5ED62ECE0F50280EE0B9@AM7PR03MB6451.eurprd03.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 12 Mar 2022 19:26:29 -0500
Message-ID: <CABNhwV3aw2SO6TBA+bXkpqNbmDSag+k+oL3soE=eMLDgufshSw@mail.gmail.com>
To: Andrew Alston - IETF <andrew-ietf=40liquid.tech@dmarc.ietf.org>
Cc: Tom Hill <tom@ninjabadger.net>, "Xiejingrong (Jingrong)" <xiejingrong=40huawei.com@dmarc.ietf.org>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001cfe8105da0e9ef7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Bld3WuKjz3RFDJX3-4eGRMWRmvM>
Subject: Re: [spring] Network Programming Interface for Provisioning of Underlay Services to Overlay Networks Using SRv6 (draft-xie-spring-srv6-npi-for-overlay)
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: Sun, 13 Mar 2022 00:26:48 -0000

Hi Jingrong

I reads the draft and was trying to understand the problem statement as
well as the solution.

So I believe the problem statement is how to interconnect desperate sites
over the internet using a managed IPSEC VPN or SDWAN solution or managed
MPLS and complexity of provisioning CE attachment.

The solution is an automated solution using SRv6 over the internet using
BSID.  This involves running SRv6 over the internet, however SRv6 is
limited to closed domains.  It appears an E2E pseudowire is used in
provisioning the service.  Have you though of using NG L2 VPN EVPN all or
single active multi home over SRv6.

Does all the provisioning use a PCE / SDN controller?


Thanks

Gyan

On Thu, Mar 10, 2022 at 9:59 AM Andrew Alston - IETF <andrew-ietf=
40liquid.tech@dmarc.ietf.org> wrote:

> Hi Jingrong,
>
>
>
> I’m struggling to entirely understand this.  I think the question for me
> is – if you are sending packets with SID’s over the open internet – are you
> encapsulating those packets and is this encapsulation cryptographically
> protected – I.E the SID’s are not visible outside of the encapsulation, to
> preserve the limited domain.
>
>
>
> Limited domains are typically extended via tunnel mechanisms, very often
> with cryptographic protection, hence the question
>
>
>
> Thanks
>
>
>
> Andrew
>
>
>
>
>
> *From:* spring <spring-bounces@ietf.org> *On Behalf Of *Xiejingrong
> (Jingrong)
> *Sent:* Thursday, March 10, 2022 9:40 AM
> *To:* Tom Hill <tom@ninjabadger.net>; spring@ietf.org
> *Subject:* Re: [spring] Network Programming Interface for Provisioning of
> Underlay Services to Overlay Networks Using SRv6
> (draft-xie-spring-srv6-npi-for-overlay)
>
>
>
> Hi Tom,
>
> Thanks for reading the draft and raise discussions.
>
> In the proposal the SRv6 domain is the overlay network, belonging to one
> administrative domain -- the overlay network operator(say ONO).
>
> For your concern about use of SIDs "across" the public Internet. Let me
> try to explain using following figure (hope it works):
>
> CPE1 CPE2 CPE3
> + + + +
> | +--------+ | | +----------+ |
> +---[1] TN1 [1]---+ +---+ Internet |---+
> +--------+ +----------+
>
> In the perspective of the ONO, it has the following SIDs:
> SID1/2/3: allocated on CPE1/CPE2/CPE3 by the ONO.
> SID4/5: allocated by TN operator but serves for the ONO (Tenant-1 of TN,
> marked [1] in the figure).
> The ONO can use these SIDs, and I would think they are all "in the overlay
> network", and are running "Over the Internet".
>
> You mentioned in the last sentence "the use of SIDs over the public
> Internet". That is what I am modeling above.
>
> Thanks
> Jingrong
>
>
> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org <spring-bounces@ietf.org>]
> On Behalf Of Tom Hill
> Sent: Wednesday, March 9, 2022 10:43 PM
> To: spring@ietf.org
> Subject: Re: [spring] Network Programming Interface for Provisioning of
> Underlay Services to Overlay Networks Using SRv6
> (draft-xie-spring-srv6-npi-for-overlay)
>
> Hi Jinrong,
>
> On 08/03/2022 01:58, Xiejingrong (Jingrong) wrote:
> > I just posted a draft that specifies a framework and some more detail
> > of the idea for provisioning of underlay services
> > (Slice/SR-policy/Mcast/etc) to overlay networks(SD-WAN/CDN/etc), using
> SRv6.
> >
> > https://datatracker.ietf.org/doc/html/draft-xie-spring-srv6-npi-for-ov
> > erlay
> > <https://datatracker.ietf.org/doc/html/draft-xie-spring-srv6-npi-for-o
> > verlay>
> >
> > Please comment and send any feedback.
> >
> > I would like to discuss this document over e-mail/mail-list.
>
>
> I'm concerned that this draft is explicitly violating the concept of
> SRv6 as a protocol that operates within a Limited Domain.
>
> As per Section 3.2 of this draft, "... the network operator of AN, TN and
> Internet can be different from each other."
>
> Further, "In some scenarios, the AN can be an Internet exchange provider
> (IXP) independent of ISP and NSP. In some other scenarios, the AN can be
> an ISP that running Internet backbone as well."
>
> This would read to me that the proposal is explicitly intended to be
> inter-domain, and not at all limited to any one administrative domain.
> Additionally, I cannot determine if the draft implicitly requires the use
> of SIDs across the public Internet?
>
> Could I ask for some clarification on the scope of the draft, with respect
> to Limited Domains, and also the use of SIDs over the public Internet?
>
> Kind regards,
>
> --
> Tom
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*