Hi, Mahesh:
Just want to clarify.
I think what Routing DT team is doing is complementary to what LIME WG is doing.
what routing DT team is doing is to identify all the existing models and the
models that are under development for OAM, routing, interface, etc, to see how
these models for different technology, protocol, feature(e.g., ACL, QoS) can
fit together to form comprehensive structure and deliver the service.
LIME work wants to provide common structure for various OAM technologies by
defining generic YANG model for OAM. But the focus is to define generic YANG
model for OAM.
Based on LIME WG charter All the technology specific models are extension to
this generic model. The relationship between these OAM related models can
depicted as following:
+-+-+-+-+-+
| LIME gen|
|OAM YANG |
+-+-+-+-+-+
|
|
+---------------------------------------------------------+
| | | | |
+-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+
| CFM | | MPLS-TP | | MPLS | | IP | . . .| foo |
|OAM YANG | |OAM YANG | |OAM YANG | |OAM YANG | |OAM YANG |
+-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+ +-+-+-+-+-+
| | | | |
| +-+-+-+-+-+ +-+-+-+-+-+ | +-+-+-+-+-+
| | MPLS-TP | | MPLS | | . . .| foo |
| |sub tech | |sub tech | | |sub tech |
The example given by Acee is to provide a list of OAM protocols which need to
be ready to configure a network instance. There is no overlapping.
-Qin
发件人: netmod [mailto:[email protected]] 代表 Mahesh Jethanandani
发送时间: 2015年8月29日 7:44
收件人: Acee Lindem (acee)
抄送: [email protected]
主题: Re: [netmod] Motivations for Structuring Models
Acee,
This is going to become very interesting very quickly. Routing DT has decided
to define a container for oam-protocols. LIME has decided it wants to define a
generic YANG module for all OAM in draft-tissa-lime-yang-oam-model.
Which model does BFD augment? Or did you just kill the whole charter for LIME??
On Aug 28, 2015, at 6:20 AM, Acee Lindem (acee) <[email protected]> wrote:
Why doesn’t it help? In the next revision of the Routing YANG DT model,
we’ve switched from including specific models to defining classes of
models with identities. For example,
grouping oam-protocols {
container oam-protocols {
list oam-protocol {
key "type";
leaf type {
type identityref {
base oam-protocol-type;
}
mandatory true;
description
"The Operations, Administration, and
Maintenance (OAM) protocol type, e.g., BFD,
TWAMP, CFM, etc.";
}
description
"List of OAM protocols configured for a
networking instance.";
}
description
"Container for list of OAM protocols configured for a
networking instance.";
}
description
"Grouping for OAM protocols configured for a
networking instance.";
}
Then the grouping is include the networking-instances. By doing this, the
intent is that it would be evident as to where a particular model would be
found.
Mahesh Jethanandani
[email protected]
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
