Re: [sfc] Way forward for draft-ao-sfc-oam-return-path-specified

[Gyan Mishra <[e-mail]>]

Hi Greg, Med, Joel, all

As co-author of “draft-so-sfc-oam” I support moving the two TLVs to the
multi layer oam draft.

As Greg mentioned and I agree that both drafts could progress separately
and there maybe an advantage of doing so.

I think from the WG feedback we would have to determine those advantages if
we decide to keep separate.  I will noodle that some more as well.


Kind Regards

Gyan

On Tue, Jun 1, 2021 at 1:46 AM <[e-mail]> wrote:

> Hi Joel, all,
>
> I support moving these two TLVs to the main OAM document. Thanks.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : Joel M. Halpern [mailto:[e-mail]]
> > Envoyé : samedi 29 mai 2021 02:34
> > À : [e-mail]; [e-mail]
> > Cc : BOUCADAIR Mohamed TGI/OLN <[e-mail]>
> > Objet : Re: Way forward for draft-ao-sfc-oam-return-path-specified
> >
> > While that sounds reasonable, I (and I presume Jim) would like to hear
> from
> > members of the working group.  The base document is adopted by the WG,
> > so the WG owns change control.
> > Do people think adding the substantive comment from the otehr two
> > referenced drafts would be helpful?
> >
> > Thank you,
> > Joel
> >
> > On 5/28/2021 7:56 PM, [e-mail] wrote:
> > > Dear Jim, Joel, et al.,
> > >
> > > in the course of discussing draft-ietf-sfc-multi-layer-oam
> > > <https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/>,
> > > Med has pointed out that it seems useful to merge the substantive part
> > > of
> > >
> > > draft-ao-sfc-oam-return-path-specified
> > > <https://datatracker.ietf.org/doc/draft-ao-sfc-oam-return-path-specifi
> > > ed/>to
> > > the draft-ietf-sfc-multi-layer-oam:
> > >
> > > GIM>> I propose adding informational reference
> > > to draft-ao-sfc-oam-return-path-specified as follows:
> > >
> > > /[Med] I would prefer to have the content of
> > > ao-sfc-oam-return-path-specified included in
> > > draft-ietf-sfc-multi-layer-oam unless you are confident to progress
> > > that I-D separately. It is up to you./
> > >
> > >
> > > Thinking of Med's suggestion, I've realized that the same step can be
> > > considered for draft-ao-sfc-oam-path-consistency
> > > <https://datatracker.ietf.org/doc/draft-ao-sfc-oam-path-consistency/>.
> > > Both individual drafts extend SFC NSH Echo Request/Reply defined in
> > > draft-ietf-sfc-multi-layer-oam and might be progressed independently.
> > > On the other hand, mechanisms described in these individual drafts are
> > > useful in an SFC NSH.
> > >
> > > Much appreciate your suggestions, guidance.
> > >
> > >
> > > Regards,
> > >
> > > Greg Mirsky
> > >
> > >
> > > Sr. Standardization Expert
> > > 预研标准部/有线研究院/有线产品经营部 Standard Preresearch
> > Dept./Wireline Product R&D
> > > Institute/Wireline Product Operation Division
> > >
> > >
> > >
> > > E: [e-mail] <mailto:[e-mail]>
> > > www.zte.com.cn <http://www.zte.com.cn/>
> > >
>
>
> _________________________________________________________________________________________________________________________
>
> 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.
>
> _______________________________________________
> sfc mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sfc
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [e-mail] <[e-mail]>*



*M 301 502-1347*