Hi, authors, Thanks for writing this draft. As Adrian mentioned, there is no YANG code in this document. I tried to work it out according to the given YANG tree diagram. Please refer to the attachment, which I hope can help to make this work more complete.
In general, I think the scope still needs to clean up, i.e., what is in the
scope, what is not in the scope. The relation between objectives and
requirements are not clear. I think requirements should completely align with
section 16 of RFC7285.
Requirements in Section 3.2 and Section 3.4 of RFC7971 should also be
considered.
Here are few detailed comments:
1. Section 4
The requirements are only selected from section 16.1, section 16.2.2, section
16.2.4, section 16.2.5, section 16.2.6, what about other sections?
Do we need to configure granularity of the topology map and cost map?
e.g., configure default two PIDs, default cost between source PID and dst PID?
How filter service is modelled? How do we set filter input as empty?
How do we model network information from other entities such as geo-location,
or round trip time measurement?
How do we model using other protocol such as IGP BGP to collect information and
fed into ALTO server
How do we provide monitoring information to service provider? E.g., monitoring
correctness, responsive of ALTO server
How do we allow disable ALTO guidance for a portion of ALTO client by time,
geographical region or other criteria?
2. Section 4
How logging and fault management is modelled in this draft?
Should we configure ALTO server to provide logging service? E.g., using syslog
Do we need to define control module to provide logging or fault management?
You might reference rfc8194 for example
3. Section 4.1 said:
"
Data model for performance monitoring for operation purpose
"
OAM or FCAPS should comprise of not only performance monitoring, but also fault
management, security management, configuration management?
Do we leave fault management beyond scope of this document?
4. Section 4.1 said:
"
* Data structures for how to store/deliver ALTO information
resources (e.g., network map, cost map, property map).
* Specific algorithms for ALTO information resource generation.
* Data structures for how to store information collected from data sources.
"
What is the relationship between bullet 1 and Bullet 3?
5. Section 4.2 title
What is the relation between requirements and Objectives?
6. Section 5.1
s/ adminstrated/administrated
7. Section 5.3
s/resoruce/resource
s/ altorithms/algorithm
Best Regards,
Qiufang Ma
ietf-alto.yang
Description: ietf-alto.yang
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
