Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn

Robert Raszuk <robert@raszuk.net> Sun, 31 January 2021 17:24 UTC

Return-Path: <robert@raszuk.net>
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 259E93A1141 for <spring@ietfa.amsl.com>; Sun, 31 Jan 2021 09:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 2Oz50uNKXO3F for <spring@ietfa.amsl.com>; Sun, 31 Jan 2021 09:24:28 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 802423A113E for <spring@ietf.org>; Sun, 31 Jan 2021 09:24:27 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id b2so19603157lfq.0 for <spring@ietf.org>; Sun, 31 Jan 2021 09:24:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lM1kIaDYh5BaC1T7duApvULwW+L+JHn9HoI+ZMcZAN0=; b=Bgy3Ed1Lm6rmIdB6n5GbCvllUaib4Hlcx8ruA/qC1HjhFRhf+OFtlauzmLwoZ9KgxG WKOWp3Df2pbyHkfymGi7fco1jgZPLbRmdjHhRlgTzzfsFM2BKIAkQE2+mLE/7NKk1SBF kqkE587Iq58SaTZzDwgfWtbl7WXSiYAVwKIgm2DPwk6QnSHlTt9o0oo9fPPFYO1KsM08 4wRVKpMRuenCM23IS6o5Wnoycb82dbtRWial3Pfaxu5oUAlo+nVTjJdPBsMyfJX82M73 JJdATWfvaMm9yMnc7Q/G9cvHASVELdnukg+cnb0j3IVK1ijL91Za44nAn+P9jJ90CI5v I1UA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lM1kIaDYh5BaC1T7duApvULwW+L+JHn9HoI+ZMcZAN0=; b=G2LtDtoQjiNNFkp0hpQuUDJA82Eol6TUSFESDn/jm1n3Ne7b98LW5X8s+DDpyv1dUc CHQfP3HD0/HvcsxS5muoUrmyscte1CrYUikgo9CaB2B3nOHnI14bvNw0q5l/V8grlfba L9m6rAyVIk06hL1NZ7hZ7z6gqmMf/Y0FZYDeaKIV7JG/jNeGiAmcdXm2ZDYPFJJn+SU5 PnDXr+PlQ8Zm3faIDWGFBIUZ0SMCknaf1F0yPFWffbxuc4+FmG1g122aRYSVGhAUVmWm hIXnGaRnTYXcl8Cma9tYAV55VmaUStRuqnZLzRTUEnx13qBwYHlhv9xnw2JSnJAYJ90S Z7+Q==
X-Gm-Message-State: AOAM530fTiTS21svh5CxnhGJjmGFamyLOXlM8H0NwiOPYwiagNJA7+EF JpQsedSpoaUiWl+rH2Xi/TESN9bsEh2s19ebutOnnw==
X-Google-Smtp-Source: ABdhPJxt7KThQidH3HxaTw6UFipSqmQGI+mHbrpaP5eE4nHXJpFH0qg32tXs9XC59WcBJoSvmLEZIoAznb8dj+wmP8c=
X-Received: by 2002:a19:6a12:: with SMTP id u18mr6377481lfu.591.1612113865328; Sun, 31 Jan 2021 09:24:25 -0800 (PST)
MIME-Version: 1.0
References: <MN2PR13MB42061AD1E295598F1F2726BDD2BB9@MN2PR13MB4206.namprd13.prod.outlook.com> <05b301d6f756$1485ced0$3d916c70$@olddog.co.uk> <CAOj+MMG4ObcXwCfE9f2yd4Nts4juguX5QO7Hje0TszUAM-62KA@mail.gmail.com> <05e801d6f7c9$7f1184b0$7d348e10$@olddog.co.uk> <CAOj+MMGaWXFFFmc9CabGF4gRL-r_v2aab9hvQNOqAF5iSSvS_g@mail.gmail.com> <BL0PR14MB377920A3EF085308CF7545ECC3B79@BL0PR14MB3779.namprd14.prod.outlook.com>
In-Reply-To: <BL0PR14MB377920A3EF085308CF7545ECC3B79@BL0PR14MB3779.namprd14.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Sun, 31 Jan 2021 18:24:15 +0100
Message-ID: <CAOj+MMHjkc8__0HSDAJ-t8DDaDdGMrGCvUbSzQEtOcfbpN6RmA@mail.gmail.com>
To: Lou Berger <lberger@labn.net>
Cc: Adrian Farrel <adrian@olddog.co.uk>, James Guichard <james.n.guichard@futurewei.com>, SPRING WG <spring@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000047df4405ba35820f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/kUqRJRvcwo8icY1zTxxw00hUIWA>
Subject: Re: [spring] WG Adoption Call for draft-dong-spring-sr-for-enhanced-vpn
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, 31 Jan 2021 17:24:30 -0000

Lou,

If you mean ingress policing that this is not what I was referring to -
however for most if not all shipping RSVP-TE aka MPLS-TE implementation I
am not aware of any per TE-LSP data plane resource allocation in the date
plane. Keen on being corrected, but with facts and proof not with claims
and statements.

If there are any please kindly enumerate what resources are being reserved
and how (ie. what RE/RP tells LC to "reserve"). No need to reveal the
implementation name(s), but if you provide a detailed pointer it would
be helpful.

Cheers,
R.


On Sun, Jan 31, 2021 at 6:10 PM Lou Berger <lberger@labn.net> wrote:

> Robert,
>
> I'm amazed that after all these decades of RSVP and rsvp-te
> implementations there are those who still state that there is no resource
> allocation or management in the data plane. The RFCs are quiet on the topic
> of how reservations are managed/enforced and it is up to the vendor to
> choose what to implement and the user to decide what features are important
> to them, i.e., that they are willing to pay for.
>
> While it is certainly true that there is a well-known vendor that doesn't
> do much in the data plane and there are some who wish that this was the
> only choice, there are certainly TE implementations that do manage/allocate
> resources in the data plane to match reservations established via RSVP or
> more modern sdn-te techniques.
>
> Lou
> ------------------------------
>
> On January 31, 2021 8:08:31 AM Robert Raszuk <robert@raszuk.net> wrote:
>
>> Hi Adrian,
>>
>> > To your 3209 comments: I believe that **some** implementations have
>> pushed the “reservation”
>> > into the data plane so that in-network policing is performed to conform
>> data flows with reservations or,
>>
>> Sure thing that any decent TE implementation and deployment must provide
>> ingress policing into TE-LSPs. But this is ingress policing not reservation
>> of actual data plane resources which explicitly Jie explained as the
>> intention here.
>>
>> Best,
>> R.
>>
>>
>> > On Sun, Jan 31, 2021 at 1:06 PM Adrian Farrel <adrian@olddog.co.uk>
>> wrote:
>>
>>> Yeah, thanks Robert.
>>>
>>>
>>>
>>> Actually, removing the comparison with other protocols is probably wise.
>>> This is a document describing how to do stuff with SR. In that context we
>>> don’t need to talk about the benefits or limitations of other protocols.
>>>
>>>
>>>
>>> To your 3209 comments: I believe that **some** implementations have
>>> pushed the “reservation” into the data plane so that in-network policing is
>>> performed to conform data flows with reservations or, at least, ensure that
>>> the parts of any flow that exceed reservation are treated as best effort.
>>> But this is an aside to the discussion of the draft at hand.
>>>
>>>
>>>
>>> I think that the document should note that the SR control plane does not
>>> currently have the capability to make reservations (in the control plane)
>>> at the network nodes. This can be achieved using a central controller to
>>> keep tabs on all resource accounting, and it could use a southbound
>>> interface to install that information in the (management/control parts of
>>> the) network nodes.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Adrian
>>>
>>>
>>>
>>> *From:* Robert Raszuk <robert@raszuk.net>
>>> *Sent:* 31 January 2021 00:46
>>> *To:* Adrian Farrel <adrian@olddog.co.uk>
>>> *Cc:* James Guichard <james.n.guichard@futurewei.com>om>; SPRING WG <
>>> spring@ietf.org>gt;; spring-chairs@ietf.org
>>> *Subject:* Re: [spring] WG Adoption Call for
>>> draft-dong-spring-sr-for-enhanced-vpn
>>>
>>>
>>>
>>> Hi Adrian,
>>>
>>>
>>>
>>> Just to make sure my point was correctly understood ... I am not
>>> questioning if either data plane or control plane resource reservations
>>> should or should not be done for SR.
>>>
>>>
>>>
>>> What I am questioning is that the draft says:
>>>
>>>
>>>
>>>    When
>>>    compared with RSVP-TE [RFC3209], SR currently does not have the
>>>    capability to reserve network resources or identify different sets of
>>>    network resources reserved for different customers and/or services.
>>>
>>>
>>>
>>> The crux of the matter is that RFC3209 DOES NOT reserve anything in the
>>> data plane of any network element while this spec clearly intends to.
>>> RSVP-TE keeps all reservations in control plane counters only.
>>> Constrained based path computation/selection happens based on those
>>> control plane information. (Yes nearly 20 years after this feature shipped
>>> I am still meeting people who believe otherwise :).
>>>
>>>
>>>
>>> So to start I recommend we remove any reference to RSVP-TE as this is
>>> purely not applicable to what this document is trying to accomplish.
>>>
>>>
>>>
>>> I admit I did not follow all the recent advancements in TEAS nor in
>>> DETNET as far as actually reserving data plane resources in data plane for
>>> some traffic types. If authors want to build a solution with that - by all
>>> means green light and full speed ahead - market will decided - especially
>>> when it will really understand the cost :) But let's make sure the document
>>> is crystal clear on what building blocks it is talking about.
>>>
>>>
>>>
>>> Best,
>>> R.
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Jan 30, 2021 at 11:20 PM Adrian Farrel <adrian@olddog.co.uk>
>>> wrote:
>>>
>>> Thanks, Jim,
>>>
>>>
>>>
>>> I’ve been following the enhanced VPN work in TEAS and I see it as a key
>>> piece of the network slicing work.
>>>
>>>
>>>
>>> It’s time that we had some protocol solutions that serve the VPN
>>> framework, and this is a suitable starting point. I like that it is not
>>> specifying additional protocol widgets but has looked at what we already
>>> have and is pointing up ways to use those tools to deliver new function.
>>>
>>>
>>>
>>> I see Robert’s point about the resource reservation aspects of traffic
>>> engineering applied to an SR network, but this is not an insurmountable
>>> problem. The question might be asked, “Why would you want to do that?” but
>>> that is a question that (as Yakov would have said) the market can decide.
>>> It seems that there are a couple of vendors and a couple of operators who
>>> have an interest.
>>>
>>>
>>>
>>> So I think we should adopt this draft and see whether we can turn it
>>> into something that has great utility.
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Adrian
>>>
>>>
>>>
>>> *From:* spring <spring-bounces@ietf.org> *On Behalf Of *James Guichard
>>> *Sent:* 27 January 2021 11:47
>>> *To:* spring@ietf.org
>>> *Cc:* spring-chairs@ietf.org
>>> *Subject:* [spring] WG Adoption Call for
>>> draft-dong-spring-sr-for-enhanced-vpn
>>>
>>>
>>>
>>> Dear WG:
>>>
>>>
>>>
>>> This message starts a 2 week WG adoption call for
>>> https://datatracker.ietf.org/doc/draft-dong-spring-sr-for-enhanced-vpn/
>>> ending February 10th 2021.
>>>
>>>
>>>
>>> After review of the document please indicate support (or not) for WG
>>> adoption to the mailing list and if you are willing to work on the
>>> document, please state this explicitly. This gives the chairs an indication
>>> of the energy level of people in the working group willing to work on this
>>> document. Please also provide comments/reasons for your support (or lack
>>> thereof) as this is a stronger way to indicate your (non) support as this
>>> is not a vote.
>>>
>>>
>>>
>>> Thanks!
>>>
>>>
>>>
>>> Jim, Bruno & Joel
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> spring mailing list
>>> spring@ietf.org
>>> https://www.ietf.org/mailman/listinfo/spring
>>>
>>>