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

[Greg Mirsky <[e-mail]>]

Dear Med,
the authors are indebted to you for your thorough review of the draft,
thoughtful comments, and helpful suggestions.
We've accepted all editorial; suggestions and applied them to the new
version <https://tools.ietf.org/html/draft-ietf-sfc-multi-layer-oam-09>.
We've discussed your comments and suggestions and updated the draft
resulting from these discussions. We hope that these updates address your
concerns.
Attached, please find the diff highlighting changes in the new version and
09 version of the draft.
Once again, many thanks for your help in improving this document.

Kind regards,
Greg

On Wed, Jan 13, 2021 at 5:53 AM <[e-mail]> wrote:

> Hi Greg,
>
>
>
> FWIW, some comments on the first part of the document can be seen at:
>
>
>
> ·         doc:
> https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-ietf-sfc-multi-layer-oam-07-rev%20Med.doc
>
> ·         pdf:
> https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-sfc-multi-layer-oam-07-rev%20Med.pdf
>
>
>
> Hope this helps.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* sfc [mailto:[e-mail]] *De la part de* Greg Mirsky
> *Envoyé :* mardi 15 décembre 2020 02:18
> *À :* Service Function Chaining IETF list <[e-mail]>;
> [e-mail]
> *Objet :* [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt
>
>
>
> Dear All,
>
> in addition to a number of nits being fixed, updates in this version
> include:
>
>    - a change in the format of the TLV used in the SFC Echo
>    Request/Reply. The shorter Type field seems not to affect extensibility but
>    an additional one-octet-long filed can be used in some cases (one being the
>    new Authentication TLV);
>    - a new Authentication TLV that can be used to protect the base SFC
>    Echo Request/Reply as well as any optional TLV.
>
> Authors welcome your comments, questions, and suggestions.
>
>
>
> Regards,
>
> Greg
>
>
>
> ---------- Forwarded message ---------
> From: <[e-mail]>
> Date: Mon, Dec 14, 2020 at 5:10 PM
> Subject: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-07.txt
> To: <[e-mail]>
> Cc: <[e-mail]>
>
>
>
>
> 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 Chains in
> Networks
>         Authors         : Greg Mirsky
>                           Wei Meng
>                           Bhumip Khasnabish
>                           Cui Wang
>         Filename        : draft-ietf-sfc-multi-layer-oam-07.txt
>         Pages           : 22
>         Date            : 2020-12-14
>
> Abstract:
>    A set of requirements for active Operation, Administration and
>    Maintenance (OAM) of Service Function Chains (SFCs) in networks is
>    presented.  Based on these requirements, an encapsulation of active
>    OAM message in SFC and a mechanism to detect and localize defects
>    described.  Also, this document updates RFC 8300 in the definition of
>    O (OAM) bit in the Network Service Header (NSH) and defines how the
>    active OAM message is identified in SFC NSH.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-sfc-multi-layer-oam-07
> https://datatracker.ietf.org/doc/html/draft-ietf-sfc-multi-layer-oam-07
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-07
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> 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.
>
>