Re: [spring] [**EXTERNAL**] The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"

Daniele Ceccarelli <daniele.ietf@gmail.com> Wed, 24 May 2023 15:32 UTC

Return-Path: <daniele.ietf@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 54C0BC14CE2B for <spring@ietfa.amsl.com>; Wed, 24 May 2023 08:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hM922BzyhCtd for <spring@ietfa.amsl.com>; Wed, 24 May 2023 08:32:03 -0700 (PDT)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63EE5C14CE4F for <spring@ietf.org>; Wed, 24 May 2023 08:31:08 -0700 (PDT)
Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-62383441211so5867586d6.0 for <spring@ietf.org>; Wed, 24 May 2023 08:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684942267; x=1687534267; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=CqE42U6AzqQjsq5M0gEI6iU2C5PnCy2rFVAz1cpoKrA=; b=WUh4IMYQWzFzzcnuNgXHH29lkUXvff+szXyAm8Vfq4gW3K6WDESbaICVnC4w5QeU92 aN3Si9u2kbqZmzRAPAFbeNb40fSFc8cKgnphj+zku2DQKp/ulqyLgrhYxt3difSN0nu3 14hbRZS2H+oU9P5rGci+z8l2Tt0/9qGox8gnnzWjQpq1YlSg9Qo6S92PKqLnGdt8CrBK 2l7eAKCVLUbT8W00zpCpEUBqujixxpgHaLd0jj5yp/dVUe9nq13SyslDYSQdIjsxpw1n OmsRtPIzXSy/NrdDjagDBz5tw+PQDq8d2rEi1s51XGf+KVXgqKIdYlEPshv4pJIaeYvw 51yg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684942267; x=1687534267; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CqE42U6AzqQjsq5M0gEI6iU2C5PnCy2rFVAz1cpoKrA=; b=bpL2hzUiTmNc4osSwTjDdeer7TBBNaTLsxqGg3hsUzsmxu28tw/0vIccYaD0K/bwTI HrgPSBGd7c54I/slHdzKAsvppTY/OzM2k0DE7tV+GWC60t4d0nRvyUY/7Am9HWqzWXQ7 nb4iBNb1Kc/FFcLrX6wH4ngGESVV968QxSQ/YRuPfg1tL56bcB+waUC2svwhYE863dCl myn29G/vTRG+GoEZVXtnP3kAV5J6smh/ElhsMWLIDyAPybVtJWZqOy4kFY4K/x+afgSz U2ex4fOy+u2PH02P3EjvYUZUj6axmi/TlAcOaieXEd63UdhXW1VhG74AmtE3WS82Hmgz PaIQ==
X-Gm-Message-State: AC+VfDw/LCOgZ1lcFx6z4fMs2BdoEF1eR5hkIEdOxkXWui1eViwY1Cm4 mYpGlE+ki0mq7UDL0Z6kD/YW8GRlen+pT/w9Vb2AXXQtlpo=
X-Google-Smtp-Source: ACHHUZ4YSzA5TsC/Rv9iB2PeLIuKMVCNGUm6VVH2WpMnDCRHExiT23fw2Ar7sA9JTZ46/F7Q5ThtKgHEbcksN2ErC1Q=
X-Received: by 2002:a05:6214:410:b0:623:638e:aa33 with SMTP id z16-20020a056214041000b00623638eaa33mr30438787qvx.6.1684942266912; Wed, 24 May 2023 08:31:06 -0700 (PDT)
MIME-Version: 1.0
References: <168424587271.45431.10014516596562429177@ietfa.amsl.com> <SJ0PR04MB8391E5969B27B5360140092BCD7F9@SJ0PR04MB8391.namprd04.prod.outlook.com> <1EDBB134-BE9C-4874-9CCC-513BD6D100D4@nokia.com> <8d03ca72-cc5c-6ea4-69b7-102a9b14a078@joelhalpern.com> <CAB01kMhORQCxFYYWvst_3CCKWUH==F-+U2AcydKw_OFmE4yBCQ@mail.gmail.com> <CAOj+MMEEA1q2pJ6KdWT937QoYLYuTW5FbGOhNL9oOejj6m+t6w@mail.gmail.com> <CAB01kMhPqx-haSn03QjK0y7XQd4Yw6v1trMbsb7ZEHCo=2iY=Q@mail.gmail.com> <CAOj+MMEqZHDWW+25mg6hnErzZYXd-pMeaQpis9QWEv4kJ52A1g@mail.gmail.com>
In-Reply-To: <CAOj+MMEqZHDWW+25mg6hnErzZYXd-pMeaQpis9QWEv4kJ52A1g@mail.gmail.com>
From: Daniele Ceccarelli <daniele.ietf@gmail.com>
Date: Wed, 24 May 2023 17:30:55 +0200
Message-ID: <CAB01kMidwGQdOtqsuXN3rur62Dw6sOEDoBKVX2boS-Pf9i915A@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: Joel Halpern <jmh@joelhalpern.com>, "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004954ef05fc7231d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/PkZxQ1D4l-ma4fwOd-JDBjNEoZQ>
Subject: Re: [spring] [**EXTERNAL**] The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 24 May 2023 15:32:07 -0000

Hi Robert,

i wouldn't just focus on the guaranteed bandwidth (which in any case has
been working with RSVP-TE and this solution will provide something as good
as that), but also on the other key requirements that SR-CS can meet (like
correctly identified in the draft):
- Predictable E2E TE paths with predictable bidirectional delay
- E2E recovery (i.e. protection and restoration)
- Path integrity
- Data plane remaining up while control plane is down

These requirements are not less important that the guaranteed bandwidth.

Moreover, pardon me for asking, why intense admission control would be a
problem in the network ?

Cheers,
Daniele

On Wed, May 24, 2023 at 4:35 PM Robert Raszuk <robert@raszuk.net> wrote:

> > If you want to have a network slice for remote surgery probably you
> > need something more reliable, but otherwise it's a good enough solution.
>
> Spot on !
>
> And that is my main point. We are reusing notion of completely different
> technology like SONET/SDH containers.
>
> And that is to create only a poor approximation of it assuming very
> strong/tight admission control to the entire network, no multicast
> which can spoil the game at any replication node and with huge pray and
> hope that there is going to be no unplanned and unaccounted traffic in the
> underlay.
>
> See till today I still meet folks who believe reading marketing slides
> that RSVP-TE (incl. GB) does actual data plane reservation.
>
> Here we are going step further and claim that SONET/SDH can be sold when
> running over IP :)
>
> Cheers,
> R
>
>
>
>
>
>
>
>
> On Wed, May 24, 2023 at 3:23 PM Daniele Ceccarelli <daniele.ietf@gmail.com>
> wrote:
>
>> Hi Robert,
>>
>> i had in mind something with the same capabilities/characteristics of
>> RSVP-TE.
>> The same problem has been addressed for decades by operators using LDP
>> for 90% of the traffic and RSVP-TE just for a small portion of the traffic
>> (e.g. phone call back in the days).
>> With mix of admission control and proper planning it is possible to
>> achieve decent performances. If you want to have a network slice for remote
>> surgery probably you need something more reliable, but otherwise it's a
>> good enough solution.
>>
>> Cheers,
>> Daniele
>>
>> On Wed, May 24, 2023 at 11:27 AM Robert Raszuk <robert@raszuk.net> wrote:
>>
>>> Hi Daniele,
>>>
>>> Could you kindly elaborate on what level of "guaranteed bandwidth" you
>>> expect SR to provide ? Especially in the context of _circuit_ emulation ?
>>>
>>> And even if you build the mechanism to account for bandwidth on a per
>>> class of service basis and use controller to push your policies everywhere
>>> in the network it is still only done in the control plane.
>>>
>>> So how are you going to assure that in your default IGP topology there
>>> is no traffic of a given class (external or internal or accidental) which
>>> would impact the promise of your emulated circuits ?
>>>
>>> This draft in section 1 makes IMO a very dangerous illusion that you can
>>> accomplish analogy to SONET/SDH in IP networks. I do not agree neither that
>>> this is the case nor that it should be the case.
>>>
>>> Cheers,
>>> Robert
>>>
>>>
>>> On Wed, May 24, 2023 at 9:15 AM Daniele Ceccarelli <
>>> daniele.ietf@gmail.com> wrote:
>>>
>>>> Hi Joel,
>>>>
>>>> the phrase "circuit style" attracted my attention and reviewed the
>>>> draft.
>>>> I think segment routing should provide good support for proper traffic
>>>> engineering (guaranteed bandwidth, recovery, path constraints etc.) hence i
>>>> believe the draft should be adopted.
>>>>
>>>> Cheers,
>>>> Daniele
>>>>
>>>> On Fri, May 19, 2023 at 5:13 PM Joel Halpern <jmh@joelhalpern.com>
>>>> wrote:
>>>>
>>>>> In case it is not clear to folks, the chairs are particularly
>>>>> itnerested in hearing from folks who are not authors of the document, but
>>>>> have opinions on whether this is good work for the WG to undertake.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Joel
>>>>> On 5/19/2023 10:11 AM, Andrew Stone (Nokia) wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>>
>>>>> As co-author, also support adoption.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Andrew
>>>>>
>>>>>
>>>>>
>>>>> *From: *"Rokui, Reza" <rrokui@ciena.com> <rrokui@ciena.com>
>>>>> *Date: *Thursday, May 18, 2023 at 7:29 AM
>>>>> *To: *IETF Secretariat <ietf-secretariat-reply@ietf.org>
>>>>> <ietf-secretariat-reply@ietf.org>,
>>>>> "draft-schmutzer-spring-cs-sr-policy@ietf.org"
>>>>> <draft-schmutzer-spring-cs-sr-policy@ietf.org>
>>>>> <draft-schmutzer-spring-cs-sr-policy@ietf.org>
>>>>> <draft-schmutzer-spring-cs-sr-policy@ietf.org>,
>>>>> "spring-chairs@ietf.org" <spring-chairs@ietf.org>
>>>>> <spring-chairs@ietf.org> <spring-chairs@ietf.org>, "spring@ietf.org"
>>>>> <spring@ietf.org> <spring@ietf.org> <spring@ietf.org>, "Rokui, Reza"
>>>>> <rrokui@ciena.com> <rrokui@ciena.com>
>>>>> *Subject: *Re: [**EXTERNAL**] The SPRING WG has placed
>>>>> draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
>>>>> *Resent-From: *<alias-bounces@ietf.org> <alias-bounces@ietf.org>
>>>>> *Resent-To: *<andrew.stone@nokia.com> <andrew.stone@nokia.com>,
>>>>> <praveen.maheshwari@airtel.com> <praveen.maheshwari@airtel.com>,
>>>>> <zali@cisco.com> <zali@cisco.com>, <rrokui@ciena.com>
>>>>> <rrokui@ciena.com>, <cschmutz@cisco.com> <cschmutz@cisco.com>
>>>>> *Resent-Date: *Thursday, May 18, 2023 at 7:29 AM
>>>>>
>>>>>
>>>>>
>>>>> You don't often get email from rrokui@ciena.com. Learn why this is
>>>>> important <https://aka.ms/LearnAboutSenderIdentification>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *CAUTION:* This is an external email. Please be very careful when
>>>>> clicking links or opening attachments. See the URL nok.it/ext for
>>>>> additional information.
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> As co-author, I support the adoption.
>>>>>
>>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Reza
>>>>>
>>>>>
>>>>>
>>>>> *From: *IETF Secretariat <ietf-secretariat-reply@ietf.org>
>>>>> <ietf-secretariat-reply@ietf.org>
>>>>> *Date: *Tuesday, May 16, 2023 at 10:04 AM
>>>>> *To: *draft-schmutzer-spring-cs-sr-policy@ietf.org
>>>>> <draft-schmutzer-spring-cs-sr-policy@ietf.org>
>>>>> <draft-schmutzer-spring-cs-sr-policy@ietf.org>, spring-chairs@ietf.org
>>>>> <spring-chairs@ietf.org> <spring-chairs@ietf.org>, spring@ietf.org
>>>>> <spring@ietf.org> <spring@ietf.org>
>>>>> *Subject: *[**EXTERNAL**] The SPRING WG has placed
>>>>> draft-schmutzer-spring-cs-sr-policy in state "Candidate for WG Adoption"
>>>>>
>>>>>
>>>>> The SPRING WG has placed draft-schmutzer-spring-cs-sr-policy in state
>>>>> Candidate for WG Adoption (entered by Joel Halpern)
>>>>>
>>>>> The document is available at
>>>>>
>>>>> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-schmutzer-spring-cs-sr-policy/__;!!OSsGDw!PrF5MLj2VoK47BuWO76oeewImBaGMafe294qNONXqhmq7i57ixXHdL_zK2azlh1DsID1fgczKQ2sDmGvgCW8AZU$
>>>>> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-schmutzer-spring-cs-sr-policy/__;!!OSsGDw!PrF5MLj2VoK47BuWO76oeewImBaGMafe294qNONXqhmq7i57ixXHdL_zK2azlh1DsID1fgczKQ2sDmGvgCW8AZU$>
>>>>> [datatracker[.]ietf[.]org]
>>>>>
>>>>> Comment:
>>>>> This starts a two week adoption call for the subject draft.  Please
>>>>> speak up
>>>>> if you support or object to WG adoption.  Two notes: 1) WG adoption is
>>>>> the
>>>>> start of the process.  The basic question is whether you agree that the
>>>>> subject is worth the working group time to work on, and whether this
>>>>> represents a good starting point for the work. 2) Please include
>>>>> explanation
>>>>> for your view.  Yes or no are not very helpful answers, as this is not
>>>>> a vote
>>>>> but an evaluation of support and concerns. Thank you, Joel (for the WG
>>>>> Chairs)
>>>>>
>>>>> We expect to close this call at the end of May, 2023.
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>