From nobody Thu May 25 14:51:50 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 3A945C1519AC for ; Thu, 25 May 2023 14:51:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.085 X-Spam-Level: X-Spam-Status: No, score=-2.085 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net 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 yx59eyhvJUBm for ; Thu, 25 May 2023 14:51:46 -0700 (PDT) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 0F844C151B00 for ; Thu, 25 May 2023 14:51:45 -0700 (PDT) Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-3f606a80d34so756535e9.0 for ; Thu, 25 May 2023 14:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; t=1685051503; x=1687643503; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sKsnWGyt18aFoPrs86JJub0/AjRMoZiugEc+lhw4bRM=; b=CPw0XROPWWysmyEnzoyreimFwyo5sYJMmxxsT7YgfbrBFLpqha7Kk1uTdVOTknfhc0 JIw7HJjkmTI5e7I681mSQEw/bhv91jRntWakqTzbgHtLD7k+piyfCa4nUbMydcs81Ow7 BDR992HQODogn85vf+CR9tudnJ5go+/f5Qi1VJtfV9WvYPSBEA43QAMthZn6uzUikqVp CwerWLEYL7QjFas1fgTkbiJoufE9p2WspYGbv7AtbePTRA3f9bHErlTEg1sozWyPHxdq t+TpR3DpfC4azy3GvRi2iS7WIzRljzKrSweK2ScrUVmDLiVYdAqnZbflI+6zYiD/a1k4 P1GQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685051503; x=1687643503; 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=sKsnWGyt18aFoPrs86JJub0/AjRMoZiugEc+lhw4bRM=; b=fqE+8flA+qy8M8MaR3eaUE4u6/0oXILA2KKZIP9JKqOJnlRGXc58AYahFHLUyIg+lH MrRLz1es3tH2zm8hMe/ZgTjVfNTDjYE6ivZrx/AhljKMMZ+6ksOg+ffmlclql9rBNu7C 8cRhsp1TxkmJy1+t5qbvD8UBVhnFwphd708z/rLZ3m7kwtN6/SlTmkyUXCV5xa/M2w9z FrJ/4Fzuq+VIXG2EsBiwpYOxMaPoHdpnjf5d1V1O0IvBkS1WFHtG6Sdy+Zcv97SNHEo8 pnNwsq9YBh18OglImzkhHusEiBsIPN79pYTJ8Nin7m7xxFAJdEI0dKvZnYsUcFmuMO9C XGIg== X-Gm-Message-State: AC+VfDyDAP7N7fLb0ZRmYdpkG32MdFyNJwgIEAZ7ZUrMF87Khm35YdcI bXNGX/OrFkH4vVRulOG9GVp9+5EFHGx/LdMbGAlGPA== X-Google-Smtp-Source: ACHHUZ7cZ0scFDr33k8+stv3NmrAIy6Z/5B5vJHic/By9r5S4UqAIrmgO40vIN8tnYlQsVgeC/kgyh3EpiAa2gTauRo= X-Received: by 2002:a7b:c456:0:b0:3f5:ff24:27de with SMTP id l22-20020a7bc456000000b003f5ff2427demr3857594wmi.32.1685051503353; Thu, 25 May 2023 14:51:43 -0700 (PDT) MIME-Version: 1.0 References: <168424587271.45431.10014516596562429177@ietfa.amsl.com> In-Reply-To: From: Robert Raszuk Date: Thu, 25 May 2023 23:51:32 +0200 Message-ID: To: Gyan Mishra Cc: IETF Secretariat , draft-schmutzer-spring-cs-sr-policy@ietf.org, spring@ietf.org, spring-chairs@ietf.org Content-Type: multipart/alternative; boundary="00000000000049446705fc8ba0fc" 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, 25 May 2023 21:51:50 -0000 --00000000000049446705fc8ba0fc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Gyan, While I do consider some use cases for what the draft is partially describing what you wrote as justification is really the crux of the matter why IMO this work should not be adopted in SPRING nor any other IETF WG. Namely quote: "IP based optical networks" "IP over optical hop by hop routed optical transport" etc ... Please observe that this draft does not provide a control plane to optical transport stitching. Quite contrary it attempts to mimic characteristics of fixed channel transport to stuff it into an IP connection-less paradigm. Regards, R. On Thu, May 25, 2023 at 8:27=E2=80=AFPM Gyan Mishra = wrote: > > I support adoption. > > The draft is well written. > > This is very important work for operators migrating from legacy TDM > optical to IP based optical networks using Segment Routing. > > The requirements is for IP over optical hop by hop routed optical > transport, either SR-MPLS or SRv6 uSID based networks to provide the sa= me > circuit switched 50ms optical bypass available on legacy OTN optical UPSR= / > BLSR rings, now on SR based IP / Optical networks having the same working > and protect make before break MOB scheme for 1:1 protection revertive or > non revertive with stateful PCE based hop by hop Co-routed disjoint stati= c > SID list for protected path that has QOS LLQ style bandwidth guarantee f= or > transport traffic prioritization over other IP traffic in a converged co= re > scenario carrying both IP non transport traffic and IP based optical > transport based traffic. > > Thank you > > Gyan > > On Tue, May 16, 2023 at 10:04 AM 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 spea= k >> up >> if you support or object to WG adoption. Two notes: 1) WG adoption is t= he >> 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 >> > -- > > > > *Gyan Mishra* > > *Network Solutions A**rchitect * > > *Email gyan.s.mishra@verizon.com * > > > > *M 301 502-1347* > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring > --00000000000049446705fc8ba0fc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Gyan,

While I do consider some use case= s for what the draft is partially describing what you wrote as justificatio= n is really the crux of the matter why IMO this work should not be adopted = in SPRING nor any other IETF WG.=C2=A0

Namely quot= e:=C2=A0

"IP based optical networks"
=

"IP over optical hop by hop routed optical = =C2=A0transport"

etc ...=C2=A0
=
Please observe that this draft does not provide a control pl= ane to optical transport stitching. Quite contrary it attempts to mimic cha= racteristics of fixed channel transport to stuff it into an IP connection-l= ess paradigm.=C2=A0

Regards,
R.

On = Thu, May 25, 2023 at 8:27=E2=80=AFPM Gyan Mishra <hayabusagsm@gmail.com> wrote:

I = support adoption.

The dr= aft is well written.

Thi= s is very important work for operators migrating from legacy TDM optical to= IP based optical networks using Segment Routing.
The requirements is for IP over optical hop by ho= p routed optical =C2=A0transport, either =C2=A0SR-MPLS or SRv6 uSID based n= etworks to provide the same circuit switched 50ms optical bypass available = on legacy OTN optical UPSR / BLSR rings, now on SR based IP / Optical netwo= rks having the same working and protect make before break MOB scheme for 1:= 1 protection revertive or non revertive with stateful PCE based hop by hop = Co-routed disjoint static SID list for protected path that has QOS LLQ styl= e =C2=A0bandwidth guarantee for =C2=A0transport traffic prioritization over= other IP traffic in a converged core scenario carrying both IP non transpo= rt traffic and IP based optical transport based traffic.

Thank you=C2=A0
Gyan

On Tue, May 16, 2023 at 10:04 AM IETF Sec= retariat <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
-- <= br>


Gyan Mishra

= Network Solutions Architect=C2=A0

Email gyan.s.mishra@verizon.com

= M 301 502-1347


_______________________________________________
spring mailing list
spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
--00000000000049446705fc8ba0fc--