Subject: [L3sm] Notification support on L3SM

From: "Ogaki, Kenichi" <[email-masked]>
Date: Tue, 5 Jan 2016 14:13:26 +0900

Dear All,

I would like to ask you if a notification support is necessary on the model.
I don't want to stick to this at this phase, but there are some use cases.

Operators must sometimes notify various information to customers under each SLA with them.
-maintenance schedule (planned, in operation)
-proactive report when a failure occurred(, even if the customer is not aware)

YANG1.1 will allow notifications to be tied to data nodes.
https://tools.ietf.org/html/draft-ietf-netmod-rfc6020bis-09#section-7.16

https://mailarchive.ietf.org/arch/msg/l3sm/35eO1KXYYBEhQ5TXI0ijWe5Nqj4
--
*notification
How about defining notification node under vpn-svc and site-network-access?
We sometimes have to actively inform our customers of a failure or something.
What kind of the information depends on each operator, then anydata or anyxml suits this.

[SLI] Notification are normally not part of the tree, we can create rpcs or notifications if necessary to retrieve operational infos.
Could you raise a separate thread to discuss the need of notifications ?

ex.)
container site-network-accesses {
    list site-network-access {
        key site-network-access-id;
        ...
        notification info {
            anydata data;
        }
        ...
}
--

-- 
Kenichi Ogaki
KDDI Corp. | IP Network Dept.
+81-(0)80-5945-9138 | www.kddi.com