Re: [Lime-oam-model] Status

[Tom Taylor <[e-mail]>]

My original E-mail protested against the abbreviations, but now I've 
read enough to understand them. BUT I also in that E-mail gave a list of 
functionalities, and I want to be sure that these are all covered by the 
entities that have been cited.

On 09/03/2015 10:04 PM, Qin Wu wrote:
> 发件人: Gregory Mirsky [mailto:[e-mail]]
> 发送时间: 2015年3月10日 0:12
> 收件人: Qin Wu; Ronald Bonica; [e-mail]
> 抄送: Deepak Kumar (dekumar)
> 主题: RE: Status
>
> Hi Qin, Ron, et. al,
> apologies for the extended absence from the discussion.
> I believe that the statement that:
>> CFM like model as management plane model is orthogonal to data plane
>> OAM protocol and meet all these requirements.
> Does not entirely reflect state of discussion within the DT, especially that "CFM like model … meets all the requirements".
> [Qin]: which requirements are not met by CFM like model.
> In your comparison analysis table, you compare IP OAM, IP/MPLS OAM, MPLS-TP OAM, TRILL OAM, the following components are
> supported by all the OAM technologies:
> 1.Trail Termination Source Information/MEP ID
> 2.MIP ID Implicit
> 3.On-demand Continuity Check
> 4.Proactive Continuity Check
> 5.On-demand Connectivity Verification
> 6.Loss Measurement
> 7.Delay Measurement
> 8.Loss of Continuity Defect
> Therefore I believe CFM like model or layer independent OAM model support these above components.
> As for Other components
> 9.Forward Defect Indication
> 10.Backward Defect Indication
> 11.Miss-merge Defect
> 12.Miss-connection Defect
> These components can be supported by technology-specific data model extensions.
>
> And I cannot agree with the conclusion here either:
>> Also MP (assume that 'MP' stands for 'Maintenance Point') terminologies are widely used in the most of OAM technologies,
>> it is not a good idea to define new terminologies to represent common
>> elements for the OAM model.
> [Qin]: I am just summarizing what we discussed before. I am confused with your statement.
> Tom Taylor proposed to use new terminology to describe OAM model when you disagreed to use MP/MIP like terminologies.
> You suggest not invent new terminologies.
> http://www.ietf.org/mail-archive/web/lime-oam-model/current/msg00056.html
> Isn’t your current statement against what you said to Tom’s proposal before?
>
> It is not about luck of terminology but luck of terminology likely indicates that respective objects not being identified or used. Hence, if we to build common OAM model, objects should be identified and defined, including through terminology. Alternatively, we have OAM technologies that share sufficient commonality to work with.
>
> [Qin]: which objects are not identified besides the above components you listed above?
>
>          Regards,
>                  Greg
>
> -----Original Message-----
> From: Lime-oam-model [mailto:[e-mail]] On Behalf Of Qin Wu
> Sent: Monday, March 09, 2015 2:08 AM
> To: Ronald Bonica; [e-mail]<mailto:[e-mail]>
> Cc: Deepak Kumar (dekumar)
> Subject: Re: [Lime-oam-model] Status
>
> Hi, Ron:
> -----邮件原件-----
> 发件人: Ronald Bonica [mailto:[e-mail]]
> 发送时间: 2015年3月7日 5:28
> 收件人: Qin Wu; [e-mail]<mailto:[e-mail]>
> 抄送: Deepak Kumar (dekumar)
> 主题: RE: Status
>
> Qin,
>
> Thanks for this summary. Unless I hear otherwise, I will assume that this is the group's consensus.
>
> [Qin]: It has been a few days and no-one has disagreed.
>
> IMHO, the design team has three tasks standing between itself and completion:
>
> - craft a slide deck documenting findings
>
> [Qin]: I will write the first draft and we can discuss on this list.
>
> - present that slide deck at IETF 92
>
> [Qin]: I am happy to do this if no one has objection.
>
> - produce an ID recording findings
>
> [Qin]: I can also start this task. I think I can make a first draft before Dallas, but I am not allowed to post it until Monday morning of IETF week in Dallas.
>
> Is that OK?
>
> Thanks.
>
> Do we have volunteers for any of those tasks?
>
>                                                                   Ron
>
>
>> -----Original Message-----
>> From: Lime-oam-model [mailto:[e-mail]] On
>> Behalf Of Qin Wu
>> Sent: Thursday, March 05, 2015 10:38 PM
>> To: Ronald Bonica; [e-mail]<mailto:[e-mail]>
>> Cc: Deepak Kumar (dekumar)
>> Subject: Re: [Lime-oam-model] Status
>>
>> Ron:
>> If my understanding is correct, here is the status of group discussion.
>> Based on first design team discussion ,people agreed to sort out
>> common OAM requirements first, Greg provides OAM (Data) Model Analysis
>> table from his perspective which compares IP OAM, IP/MPLS OAM, MPLS-TP
>> OAM, TRILL OAM from several criteria and lists several common
>> requirements.
>>
>> Based on OAM Model Analysis, common elements used for OAM model are
>> agreed, e.g., testing point, connection oriented vs
>> connectionless,loss of continuity defect,fault domain,technology type,
>> addressing, ECMP, common OAM functions(e.g., cc,cv, path discovery, performance measurement).
>>
>> CFM like model as management plane model is orthogonal to data plane
>> OAM protocol and meet all these requirements.
>> Also MP terminologies are widely used in the most of OAM technologies,
>> it is not a good idea to define new terminologies to represent common
>> elements for the OAM model.
>>
>> Therefore my understanding is that the choice of an OAM model seems to
>> have no impact on the LIME work.
>> LIME model focuses on common part of various OAM technologies,
>> therefore LIME's work can be made "model agnostic".
>>
...