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

[[e-mail]]

Hi Jim, all,

I support advancing the document.

Below some few items that might be considered by the authors:

* I'm not sure to understand the following:

   If "proof-of-transit" is used in
   conjunction with NSH, the implementation of proof of transit MUST
   follow [I-D.ietf-sfc-proof-of-transit].

Rather than such statement, I think it would be better to explain why proof of transit is useful for ioam.



* IOAM-Data-Fields is not shown in the figure (Section 3).

* Please define what is meant by "NSH tunnel endpoints" as RFC7565 does not define such nodes.

* Section 4.1 says:

   An encapsulation of IOAM-Data-Fields in NSH should be friendly to an

   implementation in both hardware as well as software forwarders and

   support a wide range of deployment cases, including large networks

   that desire to leverage multiple IOAM-Data-Fields at the same time.

It would be good to have a technical characterization about what is meant by "friendly" in this excerpt. Is this what is discussed in the paragraph right after or you had something else in mind? If so, please make it explicit.

* I'm afraid that the security considerations section is under-specified. I would cite at least those in 8300 and the draft-ietf-sfc-nsh-integrity.

Cheers,
Med

De : sfc [mailto:[e-mail]] De la part de James Guichard
Envoyé : jeudi 2 septembre 2021 20:02
À : James Guichard <[e-mail]>; [e-mail]
Cc : [e-mail]
Objet : Re: [sfc] WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

Dear WG:

The chairs have extended the WGLC for a further 2 weeks due to the lack of feedback from the WG on the original WGLC.

Please read the document and provide comments to the SFC WG mailing list no later than September 17th 2021. Note that this document is a normative reference for https://datatracker.ietf.org/doc/html/draft-ietf-sfc-proof-of-transit that is currently in AD review and we would therefore like to conclude this WGLC so that its dependent documents can further progress.

Thanks!

Jim & Joel

From: James Guichard <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, August 18, 2021 8:32 AM
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: WGLC for https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/

Dear WG:

This email starts a 2 week Working Group Last Call for draft-ietf-sfc-ioam-nsh [1].

Please read this document if you haven't read the most recent version and send your comments to the SFC WG list no later than September 1st 2021.

If you are raising a point which you expect will be specifically debated on the mailing list, consider using a specific email/thread for this point.

Lastly, if you are an author or contributor please response to indicate whether you know of any undisclosed IPR related to this document.

Thanks!

Jim & Joel

[1] https://datatracker.ietf.org/doc/draft-ietf-sfc-ioam-nsh/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-sfc-ioam-nsh%2F&data=04%7C01%7Cjames.n.guichard%40futurewei.com%7C5d6bc76f69df4c2a8cdb08d962443814%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637648867414771153%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YC18mVsN4Kfw%2BAP2OfZBWkj8jLGembb1HEXsR1vAzLo%3D&reserved=0>




_________________________________________________________________________________________________________________________

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.