Re: [Lime] LIME OAM Yang Model Applicability

["Zhuangyan (Yan)" <[e-mail]>]

Hi Greg,

Thank you very much for the suggestion and suggested documents.
And yes, we’re working on the draft based on Chair’s suggestion of these specific OAM model work.
The main idea of applicability document is to prove that the LIME base model can be used/applied to specific OAM technologies instead of defining the specific OAM models. Hence, the applicability document will investigate and evaluate specific OAM features/parameters from both these existing technology specific OAM model work as well as OAM protocols themselves, and then demonstrate how these specific features/parameters can be represented by augmenting the LIME base model to prove the extensibility and usability of the LIME base model.

Regarding the PM, agree that we’ll have much discussion on this. And definitely, we’d love to get input from groups or work with them to make our work more concrete.

Last but not least, comments and suggestions are welcomed and appreciated.

Regards,

Yan

发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2015年9月16日 0:34
收件人: Zhuangyan (Yan); Carlos Pignataro (cpignata); [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]; [e-mail]
抄送: [e-mail]; [e-mail]; [e-mail]; Benoit Claise (bclaise)
主题: RE: LIME OAM Yang Model Applicability

Hi Yan,
thank you for the update regarding your work on the applicability document. As pointed in the mail from Carlos, work on YANG model of MPLS-TP OAM already in progress. In addition to that work I can refer you to RFC 7487 and draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf that respectively present MPLS-TP OAM configuration model through RSVP-TE and LSP Ping extensions.
RE: Performance Monitoring. I think we’ll have much to discuss and work on with proactive and on-demand Continuity Check and Connectivity Verification mechanisms. Perhaps analysis of PM may be in done in its own document.

                Regards,
                                Greg

From: Zhuangyan (Yan) [mailto:[e-mail]]
Sent: Monday, September 14, 2015 6:39 PM
To: Gregory Mirsky; Carlos Pignataro (cpignata); [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Benoit Claise (bclaise)
Subject: Re: LIME OAM Yang Model Applicability

Dear Greg, and all,

Thanks for the email to bring the applicability document discussion back to the mailing list.
Yes, we’re working on the update. It takes a little time to gather as many comments as we can from people in different groups, including authors of specific OAM models.

Here we’d  like to share the initial update 01 version *soon* for people’s review based on comments received until now. Apologize to keep you wait…

The proposed changes we have already made in the new version include:

l  Updates based on Greg’s comments (thanks Greg for your comments and suggestions).

l  Rewrite guideline section to tell the location in the common structure of LIME base model we can insert the data.

l  Separate MPLS-TP OAM from MPLS OAM, Add MPLS-TP OAM support.

l  Add performance management support in the base model structure.

Please let us know if you have any other suggestions on the scope of LIME applicability.

Regards,

Yan

发件人: Gregory Mirsky [mailto:[e-mail]]
发送时间: 2015年9月15日 4:56
收件人: Carlos Pignataro (cpignata); [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
抄送: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Benoit Claise (bclaise)
主题: RE: LIME OAM Yang Model Applicability

Dear All,
I haven’t seen any discussion after the invitation from LIME WG chairs. Earlier I’ve sent my comments to authors of the applicability draft and, I understand, they are working on the update. Perhaps it would be more productive if we start our discussion of the new, updated version of the applicability document.

                Regards,
                                Greg



From: Carlos Pignataro (cpignata) [mailto:[e-mail]]
Sent: Tuesday, August 18, 2015 3:49 PM
To: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; Benoit Claise (bclaise)
Subject: LIME OAM Yang Model Applicability

Hi, All,

I am starting this thread, based on a discussion during the LIME meeting in Prague and subsequent action item.

LIME (https://datatracker.ietf.org/wg/lime) has a deliverable as follows:
- Applicability document: The YANG model(s) specified in this working group must be usable and extensible by the existing OAM technologies. This usability and extensibility must be demonstrated, for example with IP Ping, traceroute, BFD, and LSP Ping. Note the technology-specific data model extensions should ideally be worked on in the respective working groups.
which basically builds a working dependency on efforts that are building protocol-based OAM YANG models.
Based on this, I am copying the authors of the following 5 documents, and the chairs of the target WGs:

  1.  LIME Applicability http://datatracker.ietf.org/doc/draft-zhuang-lime-yang-oam-model-applicability
  2.  LIME YANG Model http://datatracker.ietf.org/doc/draft-tissa-lime-yang-oam-model
  3.  MPLS http://datatracker.ietf.org/doc/draft-zhang-mpls-tp-yang-oam
  4.  MPLS http://datatracker.ietf.org/doc/draft-zheng-mpls-lsp-ping-yang-cfg
  5.  BFD http://datatracker.ietf.org/doc/draft-zheng-bfd-yang
The main goal of this note is to explicitly connect all these streams of work, and ensure there is coherence and alignment. As LIME defines a protocol-independent YANG model (1), the Applicability document (2) should show how the model can be used, extended, and augmented to realize protocol-specific ones (3) (4) (5).

We would be happy to help facilitate this dialogue, which BTW can take the shape of an informal meeting or a virtual interim (thinking aloud) before next IETF.

Discuss!!! :-)

— Carlos.