Return-Path: X-Original-To: mpls@ietfa.amsl.com Delivered-To: mpls@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D167C169426; Wed, 26 Jun 2024 08:38:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.104 X-Spam-Level: X-Spam-Status: No, score=-7.104 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 hGuKt6L6V5GR; Wed, 26 Jun 2024 08:38:39 -0700 (PDT) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 5DD4CC157931; Wed, 26 Jun 2024 08:38:39 -0700 (PDT) Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-e026a2238d8so6644222276.0; Wed, 26 Jun 2024 08:38:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719416318; x=1720021118; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=y1PCO+teZgzJInZ0euiHs4IWF2b4YeTJQHLs3rm9lIo=; b=iwq9w70DplVvKiCtnwvrSLLYwDTt/ifm2baoipOkTmaHUtpEA0p2A6f4cblXisFSRM h7NQkF+5v6chJJwub6CgWxu9mbegAl1Pw9Y2a0ITVBYsnaqyyK+N6ABplZvgSGqgG7QD X+Yh2R/qJewa9gQokUo35Ks822VoF7QmDgyl0sAmLaBzIfvts5mVorkGX3TvDJKCj22z KlpvOLVdy43acSly95BC9JhpAF6/YbHN3Muc+lNLl6OfbFdMG79d3B+8h2fjayb4nNoM tYqkodGWHf157+qZ/za9OZ9IDSra8sGQEILkBRBFG++Wpc3W/RddhORp8NKwfEY95kyK 3UJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719416318; x=1720021118; 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=y1PCO+teZgzJInZ0euiHs4IWF2b4YeTJQHLs3rm9lIo=; b=ZWu9cv/2+BfAZvPnL04kBoE4lJzWeQD5TK1vRg83CJf1ZPUMnZiU4NfZsf01Og8Yam 4NQkksIb2iYZmh8vO+H8bp3LcOAID/avdU4hCWVW5exKWFA1UXWUARWjQuQaKHEN6v40 E63frwhGKn2RKBqcgm/VCjlCxBnkYfLcU6Rvi1sQfQnZbeWXV/ofHvA0wGz9HyRpOCzA G+B9nIrIEGu0jxZ1ul5KeE41GCMRc413d2nPwzntn40w0oYw1/lFfe2q7i1FsK8ZmH5p AguQqMgoih4cuvAbcSkBEeROoBiPGtZFHt5kCixvIrDIDIqLJ04gziWBLfUe5QrkXOUz sIbA== X-Forwarded-Encrypted: i=1; AJvYcCXUXYbAnhqBHTskA1KS8+SuCa/Je13X01LnNzeI5bBYSqNIdd+7krUoE3Yq3cAD5g4yqHAy/4XuzODpH/SSMiIio9EQ0ZkBkcjiHXDb7ccqOcxN4+5SH54pWpKeNYB/CohbtgSSXBeTtwBH1Xj20h005/krc7vN3r4= X-Gm-Message-State: AOJu0YyB0w2Pkbr0Vqrem/UkFTmkCTj/+3nEZNnMpdXNQASSurasbjYp 7C56cSpEPoC8/F0AJCwmLnYi0Y9sTjgQ2P/ZOzGCGzzvyQH1ilWTrwOulHPXjM6CgPE8IbQdlSN 2ytoh8xxTBUbQ2Jx9b51Qs/46KAWAz1Pe X-Google-Smtp-Source: AGHT+IGfa3XKSRAj4cmeafBbGlQRzjWxDONCLnHCbv21r1qK+SnY3A7Z7jPHq7Lkq66UZXkZNMy+wiAUfkGF+YCcMHE= X-Received: by 2002:a25:9307:0:b0:deb:3cce:b158 with SMTP id 3f1490d57ef6-e0304044daamr10447988276.59.1719416317843; Wed, 26 Jun 2024 08:38:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Mirsky Date: Wed, 26 Jun 2024 08:38:27 -0700 Message-ID: To: "Dongjie (Jimmy)" Content-Type: multipart/alternative; boundary="000000000000d8a16d061bcccede" Message-ID-Hash: 2QOUCPB6ZOCIMREOQZ3RBW4BYBPZJ4DK X-Message-ID-Hash: 2QOUCPB6ZOCIMREOQZ3RBW4BYBPZJ4DK X-MailFrom: gregimirsky@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "Jaganbabu Rajamanickam (jrajaman)" , "mpls-chairs@ietf.org" , mpls , "draft-jags-mpls-ps-mna-hdr@ietf.org" X-Mailman-Version: 3.3.9rc4 Precedence: list Subject: =?utf-8?q?=5Bmpls=5D_Re=3A_Request_WG_adoption_for_draft-jags-mpls-ps-mna-hd?= =?utf-8?q?r-03=2Etxt?= List-Id: Multi-Protocol Label Switching WG Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --000000000000d8a16d061bcccede Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Donjie, thank you for sharing your views. Please find my notes below tagged GIM>>. Regards, Greg On Wed, Jun 26, 2024 at 7:42=E2=80=AFAM Dongjie (Jimmy) wrote: > Hi Rakesh and all, > > > > I fully agree that the PSD solution could be useful for the IOAM use case > as described in draft-ietf-mpls-mna-usecases. > GIM>> I think that the question is Which are MNA use cases that cannot be supported using ISD MNA solution? Of course, all cases listed in draft-ietf-mpls-mna-usecases can be done using PSD, but does that mean that the PSD MNA solution is necessary to support these cases? AFAICS, it is not, as these cases can adequately and satisfactorily can be realized using the ISD MNA approach. > > > In addition, both the requirement draft and framework draft has many text > about PSD, which shows PSD is an integral part of the MNA solution. > GIM>> I don't agree with your interpretation. "Integral", although I am not a native English speaker, means that there is no MNA without a PSD part. But that is clearly not the case so far as there has been no case presented that cannot be realized using ISD PSD. IMHO, PSD is an optional but not an integral and necessary component of MNA. > > > Lastly, section 5 of draft-ietf-mpls-mna-hdr mentions that for some type > of data the encoding with ISD would be inefficient, and PSD can be anothe= r > (more efficient?) choice. > GIM>> That reference stresses that PSD is an optional approach for cases that cannot be reasonably solved using ISD. > > > Taking the above into consideration, I would support the request for WG > adoption for draft-jags-mpls-ps-mna-hdr-03. > GIM>> Since no credible technical evidence has been presented that any of the MNA cases that the MPLS WG has agreed with (draft-ietf-mpls-mna-usecases) cannot be realized using the ISD MNA solution, I cannot find any reason for considering the WG's adoption of the PSD MNA mechanism. > > > Best regards, > > Jie > > > > > > *From:* Rakesh Gandhi > *Sent:* Wednesday, June 26, 2024 9:12 PM > > *To:* Jaganbabu Rajamanickam (jrajaman) 40cisco.com@dmarc.ietf.org> > *Cc:* mpls-chairs@ietf.org; mpls ; > draft-jags-mpls-ps-mna-hdr@ietf.org > *Subject:* [mpls] Re: Request WG adoption for > draft-jags-mpls-ps-mna-hdr-03.txt > > > > Thanks Jags. > > > > The PSD solution for MNA defined in draft-jags-mpls-ps-mna-hdr-03 is used > for IOAM and IOAM DEX in draft-gandhi-mpls-mna-ioam-dex-01: > > https://datatracker.ietf.org/doc/html/draft-gandhi-mpls-mna-ioam-dex-01 > > > > IOAM and IOAM DEX use-cases for MNA are defined in > draft-ietf-mpls-mna-usecases-10: > > https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-usecases-10 > > > > The PSD solution is useful for IOAM and IOAM-DEX, I support the request > for WG adoption for draft-jags-mpls-ps-mna-hdr-03 (as co-author). > > > > P.S. I understand this email was not the WG adoption poll initiated by th= e > chairs. > > > > Thanks, > > Rakesh > > > > > > > > > > > > On Tue, Jun 25, 2024 at 10:52=E2=80=AFPM Jaganbabu Rajamanickam (jrajaman= ) > wrote: > > Hello Chairs, > > We would like to request WG adoption for draft-jags-mpls-ps-mna-hdr. > > Updated the draft with the initial review comments and the latest MNA > header format. > > > > Welcome your review comments and suggestions. > > > > > > Thanx, > > Jags > > _______________________________________________ > mpls mailing list -- mpls@ietf.org > To unsubscribe send an email to mpls-leave@ietf.org > > _______________________________________________ > mpls mailing list -- mpls@ietf.org > To unsubscribe send an email to mpls-leave@ietf.org > --000000000000d8a16d061bcccede Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Donj= ie,
thank you for sharing your views. Please find my notes below tagged= GIM>>.

Regards,
Greg
<= br>
On Wed,= Jun 26, 2024 at 7:42=E2=80=AFAM Dongjie (Jimmy) <jie.dong=3D40huawei.com@dmarc.ietf.org> wro= te:

Hi Rakesh and all,

=C2=A0

I fully agree that the PSD solution could be use= ful for the IOAM use case as described in draft-ietf-mpls-mna-usecases. =C2= =A0

GIM>> I think that = the question is Which are MNA use cases that cannot be supported using ISD = MNA solution? Of course, all cases listed in=C2=A0draft-ietf-mpls-mna-useca= ses=C2=A0can be done using PSD, but does that mean that the PSD MNA sol= ution is necessary to support these cases? AFAICS, it is not, as these case= s can adequately and satisfactorily can be realized using the ISD MNA appro= ach.=C2=A0

<= /p>

=C2=A0

In addition, both the requirement draft and fram= ework draft has many text about PSD, which shows PSD is an integral part of= the MNA solution.

GIM>>= ; I don't agree with your interpretation. "Integral", althoug= h I am not a native English speaker, means that there is no MNA without a P= SD part. But that is clearly not the case so far as there has been no case = presented that cannot be realized using ISD PSD. IMHO, PSD is an optional b= ut not an integral and necessary component of MNA.

=C2=A0

Lastly, section 5 of draft-ietf-mpls-mna-hdr men= tions that for some type of data the encoding with ISD would be inefficient= , and PSD can be another (more efficient?) choice.

GIM>> That reference stresses that PSD is an op= tional approach for cases that cannot be reasonably solved using ISD.
=

=C2=A0

Taking the above into consideration, I would sup= port the request for WG adoption for draft-jags-mpls-ps-mna-hdr-03.<= /p>

GIM>> Since no credible techni= cal evidence has been presented that any of the MNA cases that the MPLS WG = has agreed with (draft-ietf-mpls-mna-usecases) cannot be realized using the= ISD MNA solution, I cannot find any reason for considering the WG's=C2= =A0adoption of the PSD MNA mechanism.

=

=C2=A0

Best regards,

Jie

=C2=A0

=C2=A0

From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Sent: Wednesday, June 26, 2024 9:12 PM

=C2=A0

Thanks Jags.

=C2=A0

The PSD solution for MNA define= d in draft-jags-mpls-ps-mna-hdr-03 is used for IOAM and IOAM DEX in draft-g= andhi-mpls-mna-ioam-dex-01:

=C2=A0

IOAM and IOAM DEX use-cases for= MNA are defined in draft-ietf-mpls-mna-usecases-10:

=C2=A0

The PSD solution is useful for = IOAM and IOAM-DEX, I support the request for WG adoption for draft-jags-mpl= s-ps-mna-hdr-03 (as co-author).

=C2=A0

P.S. I understand this email wa= s not the WG adoption poll initiated by the chairs.

=C2=A0

Thanks,

Rakesh

=C2=A0

=C2=A0

=C2=A0

=C2=A0

=C2=A0

On Tue, Jun 25, 2024 at 10:52=E2=80=AFPM Jaganbabu Rajamanickam (jraj= aman) <jrajaman=3D40cisco.com@dmarc.ietf.org> wrote:

Hello = Chairs,

=C2=A0= =C2=A0 We would like to request WG adoption for draft-jags-mpls-ps-mna-hdr.=

=C2=A0= =C2=A0 Updated the draft with the initial review comments and the latest MN= A header format.

=C2=A0=

=C2=A0= Welcome your review comments and suggestions.<= u>

=C2=A0=

=C2=A0=

Thanx,=

Jags

_______________________________= ________________
mpls mailing list -- mpl= s@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org

_______________________________________________
mpls mailing list -- mpl= s@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org
--000000000000d8a16d061bcccede--