[L2sm] draft-ietf-l2sm-l2vpn-service-model

[Ashish Mittal <[e-mail]>]

Hello,

The way contains are organized in this service model will cause problems for software implementation.

To identify Sites associated with a service, implementation shall iterate all the sites list. Also VPLS kind of services when orchestrator is sending service creation request to SDN Controller Application, then when shall application assume that all Sites have been received.

A slightly modified organization shall help getting rid of above problems. Please suggest.

Current Organization of Yang:

container l2vpn-svc {
container vpn-profiles {
uses vpn-profile-cfg;
}
container vpn-services {
list vpn-svc {
key "vpn-id";
leaf vpn-id {
type svc-id;
description
"Defining a service id.";
}
leaf vpn-svc-type {
type identityref {
base service-type;
}
description
"Service type";
}
leaf customer-name {
type string;
description
"Customer name";
}
leaf svc-topo {
type identityref {
base vpn-topology;
}
....
}
}

container sites {
list site {
key "site-id site-type";
leaf site-id {
type string;
description
"Site id";
}
...
}
}
}

Proposed Organization of Yang:

container l2vpn-svcs
{
               list l2vpn-svc
               {
key "vpn-id";
leaf vpn-id {
type svc-id;
description
"Defining a service id.";
}
               container vpn-services {
               leaf vpn-svc-type {
type identityref {
base service-type;
}
description
"Service type";
}
leaf customer-name {
type string;
description
"Customer name";
}
leaf svc-topo {
type identityref {
base vpn-topology;
}
....
               }
               container sites
               {
list site {
key "site-id site-type";
leaf site-id {
type string;
description
"Site id";
}
...
}
               }
}

Regards

Ashish Mittal

"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."