Re: [ippm] [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

xiao.min2@zte.com.cn Wed, 27 April 2022 09:04 UTC

Return-Path: <xiao.min2@zte.com.cn>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1446C15EE37; Wed, 27 Apr 2022 02:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.897
X-Spam-Level:
X-Spam-Status: No, score=-6.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 g-nP0p0p-q-4; Wed, 27 Apr 2022 02:04:36 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF5D8C15ED7E; Wed, 27 Apr 2022 02:04:35 -0700 (PDT)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4KpCVn40JRz560Wy; Wed, 27 Apr 2022 17:04:33 +0800 (CST)
Received: from njxapp01.zte.com.cn ([10.41.132.200]) by mse-fl2.zte.com.cn with SMTP id 23R93GSZ051003; Wed, 27 Apr 2022 17:03:16 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid201; Wed, 27 Apr 2022 17:03:16 +0800 (CST)
Date: Wed, 27 Apr 2022 17:03:16 +0800 (CST)
X-Zmail-TransId: 2afd626906d4ffffffff85a-7f0b5
X-Mailer: Zmail v1.0
Message-ID: <202204271703160145184@zte.com.cn>
In-Reply-To: <CAMFZu3O-vEAnrBE6rhuFh_POPD5E2i_bHvdBx=GUjRKxk3AOYw@mail.gmail.com>
References: MN2PR13MB4206C91446BA5FBBDA69E233D2FF9@MN2PR13MB4206.namprd13.prod.outlook.com, CA+RyBmVSrdCaO77P4=1vZ2LmxtR65OmspN_wozyGPNwtM5Uv3A@mail.gmail.com, CAMFZu3PaLQrHcBULzsxbdnTJyr-bVDVs1WpnFwLuSkR7DbntuQ@mail.gmail.com, CA+RyBmWeUiTsA7-CvpXSBViB00Y-tmAuSr-P=Vf3vB61zfn6bg@mail.gmail.com, CAMFZu3P45x9Mt5-MUpGO1Puqz57DPcGE4aBsPNxczW-pw9n=AA@mail.gmail.com, MN2PR13MB42066C22CA66B0E1F0FC3FFFD2269@MN2PR13MB4206.namprd13.prod.outlook.com, CAMFZu3NO6J-MM_a7TZm+wTzxbKzY5t0OkW8QNLk0673Fkr16RQ@mail.gmail.com, CA+RyBmVVWdvLZdANV_whtcwwMKVfVpM8VL7BYMM7NTnmooUpcQ@mail.gmail.com, CAMFZu3PEmrarcsp4tXQsx4eKvai8+UvzKSFxfcakX4LUAcayJA@mail.gmail.com, MN2PR13MB420615DA403388EA0144A9C1D22F9@MN2PR13MB4206.namprd13.prod.outlook.com, CAMFZu3MUmuBEDEzdafw2UHEvsTE+7sQ=E1kik5TuQ=_NznFF9w@mail.gmail.com, CA+RyBmW=ZT0EUmSYYfZJjcapBZ5-pg93um5t287LreONLOVnJQ@mail.gmail.com, CAMFZu3NCCmj4u75taEzBiMmkMQ0YrmK5KsUToSOKfwX1yBxePA@mail.gmail.com, 26916_1649050778_624A849A_26916_245_1_aa5a0049026247d9980f4ebbc8c5ac0b@orange.c om, CY4PR11MB1672FCF27DA2A4822C6E1B40DAED9@CY4PR11MB1672.namprd11.prod.outlook.com, 11111_1649774342_62558F05_11111_493_4_a734de5265ca498bbabf9805a6eaf91d@orange.com, CAMFZu3N03E-nWYJNik91e+X=gr3s2TVF03ZCM8i02ru4_Q82og@mail.gmail.com, CA+RyBmWUZcUN2jnpUuyhTmkNpwvh=2prBZDGinWe2v-b3n8+MQ@mail.gmail.com, CAMFZu3N5+GdFk13oWbi8F1qhgRNsKpSFwza61SG2oeMW9TvaLQ@mail.gmail.com, 525_1649935673_62580539_525_487_2_d0a4949b3d9c4424a0261012c7ce6188@orange.com, CA+RyBmX3MdqVX5=hEsO+9SMbpXw+enwnm_qb4+-6smqbsTPPwg@mail.gmail.com, CAMFZu3NZBgKXHrktn04LbwW33S+j+kGG5hx2A+1+jJ8aasCRag@mail.gmail.com, 14665_1651047374_6268FBCD_14665_484_6_addb2a5f712d4307a463d0582cc0a8a0@orange.com, CAMFZu3O-vEAnrBE6rhuFh_POPD5E2i_bHvdBx=GUjRKxk3AOYw@mail.gmail.com
Mime-Version: 1.0
From: <xiao.min2@zte.com.cn>
To: <shwetha.bhandari@thoughtspot.com>
Cc: <mohamed.boucadair@orange.com>, <james.n.guichard@futurewei.com>, <sfc-chairs@ietf.org>, <sfc@ietf.org>, <ippm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-MAIL: mse-fl2.zte.com.cn 23R93GSZ051003
X-Fangmail-Gw-Spam-Type: 0
X-FangMail-Miltered: at cgslv5.04-192.168.250.138.novalocal with ID 62690721.000 by FangMail milter!
X-FangMail-Envelope: 1651050273/4KpCVn40JRz560Wy/62690721.000/10.30.14.239/[10.30.14.239]/mse-fl2.zte.com.cn/<xiao.min2@zte.com.cn>
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 62690721.000/4KpCVn40JRz560Wy
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/UGeh6ln7xTN9Q9-oA3Y1JlqN1o0>
Subject: Re: [ippm] =?utf-8?q?=5Bsfc=5D_WGLC_for_https=3A//datatracker=2Eietf?= =?utf-8?q?=2Eorg/doc/draft-ietf-sfc-ioam-nsh/?=
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2022 09:04:37 -0000

Hi Shwetha,

I agree with Frank and you that the text on Next Protocol should be as is, draft-xzlnp-bier-ioam uses the similar definition while encapsulating IOAM data in BIER.
Besides, I believe the main purpose is that multiple IOAM options can be carried in one NSH/BIER packet, even if only one IOAM namespace is deployed.

Best Regards,
Xiao Min
------------------原始邮件------------------
发件人:ShwethaBhandari
收件人:Med Boucadair;
抄送人:James Guichard;sfc-chairs@ietf.org;sfc@ietf.org;ippm@ietf.org;
日 期 :2022年04月27日 16:46
主 题 :Re: [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/
_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc

Hi Med,
Thanks for the confirmation and quick review.

On,
This means the new requested TBD_IOAM value will also be a valid next protocol. However, I wonder whether IOAM in IOAM in NSH is really something you want to have. If not, I suggest the text is updated to exclude it from the allowed value in the above excerpt.
Per earlier discussion in this thread, quoting Frank's mail here for reference:
In addition, I don’t think that draft-ietf-sfc-ioam-nsh would be the appropriate place to discuss and restrict deployment options. E.g., I’m not sure why we’d want to restrict a deployment to using a single IOAM header only. E.g., one could think of using different headers for different namespaces or groups of namespaces for operational reasons. IMHO, such a discussion – if we really need it - would belong into draft-ietf-ippm-ioam-deployment, rather than into a draft that defines the encap of IOAM into NSH.
I think the text on Next Protocol should be as is. We should not add restrictions on number of IOAM headers that could be added to the packet.

Thanks,
Shwetha




On Wed, Apr 27, 2022 at 1:46 PM <mohamed.boucadair@orange.com> wrote:
Hi Shwetha, all,
The changes look great. Thanks.
There is one specific point not addressed in previous replies. This is related to this text:
Next Protocol:  8-bit unsigned integer that determines the type of
header following IOAM.  The semantics of this field are
identical to the Next Protocol field in [RFC8300].
This means the new requested TBD_IOAM value will also be a valid next protocol. However, I wonder whether IOAM in IOAM in NSH is really something you want to have. If not, I suggest the text is updated to exclude it from the allowed value in the above excerpt.
Other than that, I think that the draft is ready to move forward.
Cheers,
Med
De : Shwetha Bhandari <shwetha.bhandari@thoughtspot.com>
Envoyé : mercredi 27 avril 2022 10:06
À : James Guichard <james.n.guichard@futurewei.com>om>; sfc-chairs@ietf.org
Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>om>; Frank Brockners (fbrockne) <fbrockne=40cisco.com@dmarc.ietf.org>rg>; sfc@ietf.org; ippm@ietf.org; Tal Mizrahi <tal.mizrahi.phd@gmail.com>om>; draft-ietf-sfc-ioam-nsh@ietf.org; Greg Mirsky <gregimirsky@gmail.com>
Objet : Re: [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

Dear SFC chairs,
A new version of the draft I-D.ietf-sfc-ioam-nsh has been submitted per the discussion in this thread.
https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-ioam-nsh-09
Can we please progress this draft to IESG if there are no further comments?
Thanks,
Shwetha

On Thu, Apr 14, 2022 at 6:41 PM Greg Mirsky <gregimirsky@gmail.com> wrote:
Hi Shwetha,
thank you for the proposed resolution. I agree with Med, direct normative reference to I-D.ietf-sfc-oam-packet seems like the logical conclusion of our discussion of the use of the NSH O bit. Please note that we're referring to I-D.ietf-sfc-oam-packet  in the Active SFC OAM draft, e.g.,:
The O bit in NSH MUST be set, according to [I-D.ietf-sfc-oam-packet].
Regards,
Greg

On Thu, Apr 14, 2022 at 4:27 AM <mohamed.boucadair@orange.com> wrote:
Hi Shwetha,
I prefer we go for an explicit reference to I-D.ietf-sfc-oam-packet rather than “any update to RFC8300”. This is consistent  with the usage in the other OAM draft.
Thank you.
Cheers,
Med
De : Shwetha Bhandari <shwetha.bhandari@thoughtspot.com>
Envoyé : jeudi 14 avril 2022 12:06
À : Greg Mirsky <gregimirsky@gmail.com>
Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>om>; Frank Brockners (fbrockne) <fbrockne=40cisco.com@dmarc.ietf.org>rg>; sfc-chairs@ietf.org;  sfc@ietf.org; ippm@ietf.org; James Guichard <james.n.guichard@futurewei.com>om>; Tal Mizrahi <tal.mizrahi.phd@gmail.com>om>; draft-ietf-sfc-ioam-nsh@ietf.org
Objet : Re: [sfc] WGLC for  https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

Hi Med, Greg,
How about this text :
“The O-bit MUST be handled following the rules in and any updates to [RFC8300] ."
Given that I-D.ietf-sfc-oam-packet  will update RF8300 and there could be others in future?
Thanks,
Shwetha

On Tue, Apr 12, 2022 at 9:24 PM Greg Mirsky <gregimirsky@gmail.com> wrote:
Hi Shwetha,
I believe that the text you've quoted is helpful. I would suggest changing references from [RFC8300] to [I-D.ietf-sfc-oam-packet] throughout that paragraph.
Regards,
Greg

On Tue, Apr 12, 2022 at 7:56 AM Shwetha Bhandari <shwetha.bhandari@thoughtspot.com> wrote:
Med,
Thanks for the details: this is exactly what we had before the latest revision:
4.2.  IOAM and the use of the NSH O-bit
[RFC8300] defines an "O bit" for OAM packets.  Per [RFC8300] the O
bit must be set for OAM packets and must not be set for non-OAM
packets.  Packets with IOAM data included MUST follow this
definition, i.e. the O bit MUST NOT be set for regular customer
traffic which also carries IOAM data and the O bit MUST be set for
OAM packets which carry only IOAM data without any regular data
payload.
This was removed as per the discussion in this thread. Please check  https://mailarchive.ietf.org/arch/msg/sfc/srMit5zE8UseNOhxknAw_dqvj6M/
It looks like we are going in a loop here. This definition of SFC OAM packet to include the OAM data that comes in inner packets via the next protocol header chain is introduced in draft-ietf-sfc-oam-packet to update the RFC8300.
Jim, What are you thoughts on this? Should we reintroduce the above text ?
Thanks,
Shwetha
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________  Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.  This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.