Re: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-11.txt

[[e-mail]]

Hi Greg, 

Thank you for taking care of most of the comments. This version is much better. 

I see that no changes were made to show how the requirements in Section 3 are met with the proposed solution. I'm sure you have good reasons for that. 

Also, I have one clarification question about the following: 

(1)
   The sender of the Echo Request MAY use TLVs to
   request that the corresponding Echo Reply is transmitted over the
   specified path.

(2)

   *  Reply via Specified Path (TBA8) value to enforce the use of the
      particular return path specified in the included TLV to verify bi-
      directional continuity and also increase the robustness of the
      monitoring by selecting a more stable path.

I fail to see which TLVs will be used to specify the "return path". Did I missed something? 

Thank you for your efforts.

Cheers,
Med

> -----Message d'origine-----
> De : sfc [mailto:[e-mail]] De la part de internet-
> [e-mail]
> Envoyé : mardi 25 mai 2021 15:51
> À : [e-mail]
> Cc : [e-mail]
> Objet : [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-11.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Service Function Chaining WG of the
> IETF.
> 
>         Title           : Active OAM for Service Function Chaining
>         Authors         : Greg Mirsky
>                           Wei Meng
>                           Bhumip Khasnabish
>                           Cui Wang
> 	Filename        : draft-ietf-sfc-multi-layer-oam-11.txt
> 	Pages           : 24
> 	Date            : 2021-05-25
> 
> Abstract:
>    A set of requirements for active Operation, Administration, and
>    Maintenance (OAM) of Service Function Chains (SFCs) in a network
> is
>    presented in this document.  Based on these requirements, an
>    encapsulation of active OAM messages in SFC and a mechanism to
> detect
>    and localize defects are described.
> 
>    This document updates RFC 8300.  Particularly, it updates the
>    definition of O (OAM) bit in the Network Service Header (NSH) and
>    defines how an active OAM message is identified in the NSH.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-sfc-multi-layer-oam-
> 11.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-11
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> sfc mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sfc

_________________________________________________________________________________________________________________________

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.