From nobody Thu Jun 1 07:14:15 2023 Return-Path: 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 E87C1C14CE5D; Thu, 1 Jun 2023 07:14:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.094 X-Spam-Level: X-Spam-Status: No, score=-2.094 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 BNPn6J61m6PA; Thu, 1 Jun 2023 07:14:13 -0700 (PDT) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 3DA1AC151522; Thu, 1 Jun 2023 07:13:27 -0700 (PDT) Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-97392066d04so119652866b.3; Thu, 01 Jun 2023 07:13:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685628805; x=1688220805; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BE8+FJgUBc/nfD3CIoqpL16pk0MSPpc9mR0ZbaVg6Ps=; b=YV1mNKI1iETZVWG1UT8s1nZgcRJri6E6lpQ1Wx5m9/wNSUJgTos/xIaASKaBQp1PJk Ahx7mIEZiVlgQqx3NJ2ufb+cvUra4y5PcoWRH6WSS62OVRUO4dAUKSc0Vl2FYwszvIov SEMNLWzJi63Y8bP5HX+nKmOeb41gQ7qAA6qZRyTvrikFbCbol2Ob+VOWkgNySxKPVlYL 4679i0JA9n/SSGFgR4aPpbTq0v6cFuC/Db1TZvhYxt4yNWZsFwfBsMTkj0aRc9YYN4rW +wTaEho1es8C66PLd/YrFAlDoZXnNU9KHa16Nvo4igt7L5r56RW1d70ygcg7PtN1+oUL w5uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685628805; x=1688220805; 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=BE8+FJgUBc/nfD3CIoqpL16pk0MSPpc9mR0ZbaVg6Ps=; b=MyV7EQNwh9qPDJDjy478a79XZ+VD+clHnXK4iSbFnzF/oijNIEZ2tKh7nBXETywRkw DSnEOKcFT5Rmdj68VOc+6Y6+XST3pSEZJYFBoDJm/zEfMTFUdGs1TsUgF+rExbyyE0W2 Boc6MpCE/+FxTID8O5g7w/4fnQuohM3/EIVH2C8O2Gla/V+Qz3qwNCWHNTcsdEvBc1ra xKWu3zCAcna7NwcC8Dl2EkNgyW//nJxtcxDnhWd+aiSZsBLGtFoX11lFSSpL5K9Z00MX yRvoa12Vetr6Cu6jKorgNHKFlNIshYpSL52jxlpqo8GdiyGEAcNAvs44USCJTmK4Sevu loGQ== X-Gm-Message-State: AC+VfDzW4dMRrzRGQBu6Z5R8/X9+KLtsoTxSBatAfirXPoKENaYcedlI xQy2lVZOYDfMqetSl17QoulT/38AKoPra5diEsKMRaBv X-Google-Smtp-Source: ACHHUZ6YUgpMLXY7sRmlkkDYIUUx5KgsaNAV/oUIBxXzgnO4FW4IPmzUrczO4w9zs8XrysME3l3WmZHYUvfPA1Zud4w= X-Received: by 2002:a17:907:1c22:b0:94b:cd7c:59f4 with SMTP id nc34-20020a1709071c2200b0094bcd7c59f4mr9164152ejc.16.1685628804693; Thu, 01 Jun 2023 07:13:24 -0700 (PDT) MIME-Version: 1.0 References: <168424587271.45431.10014516596562429177@ietfa.amsl.com> In-Reply-To: <168424587271.45431.10014516596562429177@ietfa.amsl.com> From: Ketan Talaulikar Date: Thu, 1 Jun 2023 19:43:09 +0530 Message-ID: To: spring@ietf.org Cc: draft-schmutzer-spring-cs-sr-policy@ietf.org, spring-chairs@ietf.org Content-Type: multipart/alternative; boundary="0000000000002092ad05fd120a7f" Archived-At: 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\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2023 14:14:14 -0000 --0000000000002092ad05fd120a7f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello All, I support the adoption of this document since it provides an excellent starting point for the WG to address the very important use case for SR Policy deployment for delivering private line services with bandwidth guarantee over SR networks. Documenting this solution will help the implementation and deployment in a multi-vendor SR network. One suggestion to the authors (not blocking for adoption) would be also perhaps briefly touch upon the services that may be steered over CS SR Policies - e.g. PWs. Thanks, Ketan On Tue, May 16, 2023 at 7:34=E2=80=AFPM IETF Secretariat < 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/ > > 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 th= e > 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 > --0000000000002092ad05fd120a7f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello All,

I support the adoption of th= is document since it provides an excellent starting point for the WG to add= ress the very important use case for SR Policy deployment for delivering pr= ivate line services with bandwidth guarantee over SR networks. Documenting = this solution will help the implementation and deployment in a multi-vendor= SR network.

One suggestion to the authors (not bl= ocking for adoption) would be also perhaps briefly touch upon the services = that may be steered over CS SR Policies - e.g. PWs.

Thanks,
Ketan


On Tue, May 16, 2023 at 7:34= =E2=80=AFPM IETF Secretariat <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/do= c/draft-schmutzer-spring-cs-sr-policy/

Comment:
This starts a two week adoption call for the subject draft.=C2=A0 Please sp= eak up
if you support or object to WG adoption.=C2=A0 Two notes: 1) WG adoption is= the
start of the process.=C2=A0 The basic question is whether you agree that th= e
subject is worth the working group time to work on, and whether this
represents a good starting point for the work. 2) Please include explanatio= n
for your view.=C2=A0 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 Chai= rs)

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
--0000000000002092ad05fd120a7f--