italobusi
italobusi
It seems that this enumeration should be extensible to allow control of new layer protocols not yet defined: see open issue #264 As discussed in open issues #267 and #268...
I think this enumeration should be extensible to support future higher bit rates (e.g., TBPS): see open issue #264
It seems that many enumerations are not properly marked as extensible and translated as YANG enumeration instead of YANG identity This issue is also discussed in section 6 of: https://tools.ietf.org/html/draft-bryskin-teas-yang-ietf-vs-onf-01...
As discussed in previous TAPI calls the relationship between OpenAPI and RESTCONF/YANG APIs is not fully clear: more clarification is needed also to write correct statements in the TAPI 2.1...
TAPI 2.0 YANG model is not backward compatible with TAPI 1.0 YANG model As outline in section 10 of https://tools.ietf.org/html/rfc6020: > As experience is gained with a module, it may...
As reported in TAPI 1.0 FRS (TR-527): > Service EndPoints, representing shared knowledge between the customer and the provider, needs to be pre-configured, based on customer and provider negotiation I...
I cannot find this UML stereotype indicating the maturity level of this attribute (section 6.2.1 of TR-514) I am not sure we can consider this attribute as "Mature" considering the...
I am not able to find the UML lifecycleState stereotype describing the maturity levels of different TAPI UML artifacts This stereotype is required and defined in section 6.2.1 of the...
The writeAllowed stereotype for this attribute is CREATE_AND_UPDATE However, as indicated in open issue #260 , since SIPs are shared knowledge, I think the stereotype should be WRITE_NOT_ALLOWED It is...
TAPI 1.0 ServiceEndPoint (SEP) has been renamed as ServiceInterfacePoint (SIP) in TAPI 2.0 This Information Model change not only affects the name of the object but also its semantics and...