Hi,

I have a question for clarification, and then a comment.

First, consider these extracts:

> 5.1.  L2VPN/L3VPN Service Delivery
> 
>    In reference to Figure 5, the following steps are performed to
>    deliver the L3VPN service within the network management automation
>    architecture defined in this document:
> 
>    1.  The Customer requests to create two sites (as per service
>        creation operation in Section 4.2.1)...
...
> 5.2.  VN Lifecycle Management
> 
>    In reference to Figure 7, the following steps are performed to
>    deliver the VN service within the network management automation
>    architecture defined in this document:
> 
>    1.  Customer requests (service exposure operation in Section 4.1.1)
>        to create 'VN' based on Access point...
...
>    3.  The Customer exchanges connectivity-matrix on abstract node and
>        explicit path using TE topology model with the orchestrator...

In those examples, how does the customer "request" or "exchange" data? I assume 
this is intended to happen by software, rather than by telefax. So what 
protocol is involved, and which entity on the customer side is doing it?

> 5.3.  Event-based Telemetry in the Device Self Management
> 
>    In reference to Figure 8, the following steps are performed to
>    monitor state changes of managed objects or resources in a network
>    device and provide device self-management within the network
>    management automation architecture defined in this document:
> 
>    1.  To control which state a network device should be in or is
>        allowed to be in at any given time, a set of conditions and
>        actions are defined and correlated with network events (e.g.,
>        allow the NETCONF server to send updates...

Second, this is the first mention of NETCONF in the document, and the only 
other mention is in the Security Considerations. I suggest that there should be 
a short description of the role of NETCONF (and RESTCONF) earlier in the 
document, either in section 3 or more likely in section 4 (Functional Blocks 
and Interactions).

Regards
   Brian Carpenter

_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg

Reply via email to