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

Eduard Metz <etmetz@gmail.com> Thu, 25 May 2023 11:24 UTC

Return-Path: <etmetz@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 EC5E5C151B13; Thu, 25 May 2023 04:24:29 -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 RV0B3sZ21DKV; Thu, 25 May 2023 04:24:26 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 09541C151B15; Thu, 25 May 2023 04:24:26 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-4f4b0a0b557so2250648e87.1; Thu, 25 May 2023 04:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685013864; x=1687605864; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/A8bd/o+0B9OtZGmUDUjh/vALRMae31ZME6IT72QFbg=; b=mi17HaXxbLErYnvfJom+KOFIHYQofew9EkaYH63kBMWfTTniW9s4bxBQkjo3KJVo/g Yuo1BLV0FDSAW3ibQSzYOPcVnmDfelnzlmv7hxRUcjibGbOprA0Qzk5P+68ZYOFQiSq7 dsCGgbUK3d1+AS/8DJsiH9iRK/K2CuTNWi0XMy/azHQBIS6NzhJIp/qBhTWhiHwVD8nb FzldH+2v9cqtfJgP9Wlzv422YHTv5NxziMZoK73jXg8aNcOA0vTEpeq8SieinTYifQYL yGD3maKKkesU4OIfRoLJrB7n9BN0chAEhjloDqyspk5RP+wBpi9z3GF2CD0DYrjC9/qS RpIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685013864; x=1687605864; 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=/A8bd/o+0B9OtZGmUDUjh/vALRMae31ZME6IT72QFbg=; b=fmgyon47Asm2xRX1j7x8BL4/MkwsfPJkPvvz68oGqmEkAdafRjB3hrAqc8im254tQc gUsMHxBtfhopdo8bK8qnpXQ9s+IxIzUSElvh3H42THMxyeQAel0tUfyxyKlsxJBOB9FS r0RRuz6OkathnFWKyK6KxM0rgNngbd9rS8naeyp/naGdcV8sEREgLwpBWkGvlxnpyXbV XRGlHVbUSlnX+4toQGuVmae0TooGJ950pQgxn/xJkHTTAyTaP4F1Yd3txOj5S13xDK+2 x/vzWMa8/7DQI3mUHCNiInEiTwUIOjULV5kCeHxnhE9FOQChjxQSR1bzCmL6v/80wwn/ fslA==
X-Gm-Message-State: AC+VfDzI+qzQAOFPQmhzJvEJaPzlTnSnBb2d7ko0b8ihprW40lzoad8i 4D+dLOKrIXbdOsaaBi6Amhagzfzov/41DrMGq3efP0MUjbY=
X-Google-Smtp-Source: ACHHUZ4x2ubocVFW3qGYnz87lYlQqqkW31scOzk9s3LYwFh83nmNgMwYNPQUdtKQtUe950aOkY668b8xyX/tsMUGsZM=
X-Received: by 2002:ac2:5481:0:b0:4f4:c7ed:8586 with SMTP id t1-20020ac25481000000b004f4c7ed8586mr1817453lfk.2.1685013863381; Thu, 25 May 2023 04:24:23 -0700 (PDT)
MIME-Version: 1.0
References: <168424587271.45431.10014516596562429177@ietfa.amsl.com> <D3F81AF6-7185-43FF-809A-C772886CF741@bell.ca>
In-Reply-To: <D3F81AF6-7185-43FF-809A-C772886CF741@bell.ca>
From: Eduard Metz <etmetz@gmail.com>
Date: Thu, 25 May 2023 13:24:11 +0200
Message-ID: <CAG=3OHfNBLXN+dJvO4wf7hjYTSZR_N9P2bP7fkB4j9vCXTwiwg@mail.gmail.com>
To: "Bernier, Daniel" <daniel.bernier=40bell.ca@dmarc.ietf.org>
Cc: IETF Secretariat <ietf-secretariat-reply@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@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c4c08005fc82dc73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/VI9YLiubPE_JOUiR2OcPL7MfKGU>
Subject: Re: [spring] 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: Thu, 25 May 2023 11:24:30 -0000

Support WG adoption.

I think the draft covers more than just SR policy, e.g. also QoS
requirements / guidelines. This may be reflected in the title and purpose
of the draft. Also SR policy alone is not sufficient to meet all the
requirements described in the introduction.

Couple of review points:
- Terminology / wording of QoS requirements in this draft are slightly
different than that in the PLE document, is this on purpose? (e.g. the
latter describes low loss / low jitter, the policy draft focuses more one
bandwidth available)
- Policing / shaping traffic for an SR policy (3.1) could impact delay /
loss. Not sure if this function should be coupled to the SR path or rather
be part of the "service" function so that shaping is done service aware?
-  Section 7.1, last paragraph, should the second reference be the same as
the first?

   The headend forms the bidirectional SR Policy association using the
   procedure described in [I-D.ietf-pce-sr-bidir-path] and receives the
   information about the reverse segment list from the PCE as described
   in section 4.5 of [I-D.ietf-pce-multipath]


cheers,
  Eduard

On Tue, May 23, 2023 at 3:46 PM Bernier, Daniel <daniel.bernier=
40bell.ca@dmarc.ietf.org> wrote:

> Hi
>
> Support the adoption to WG
>
> Daniel Bernier
>
> On 2023-05-16, 10:04 AM, "spring on behalf of IETF Secretariat" <
> spring-bounces@ietf.org <mailto:spring-bounces@ietf.org> on behalf of
> ietf-secretariat-reply@ietf.org <mailto:ietf-secretariat-reply@ietf.org>>
> wrote:
>
>
>
>
> 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://datatracker.ietf.org/doc/draft-schmutzer-spring-cs-sr-policy/ <
> https://datatracker.ietf.org/doc/draft-schmutzer-spring-cs-sr-policy/>
>
>
> 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 <mailto:spring@ietf.org>
> https://www.ietf.org/mailman/listinfo/spring <
> https://www.ietf.org/mailman/listinfo/spring>
>
> ------------------------------------------------------------------------------
> External Email: Please use caution when opening links and attachments /
> Courriel externe: Soyez prudent avec les liens et documents joints
>
>
>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>