Child pages
  • TAPI Contributions and Presentations

1.1.                    Simple Bug fixing & Enhancements over current use cases.

 

Bugs

Item

Section TR-547

Telefonica Proposal

Comments

tapi-photonic-media:otsi-service-interface-point-spec

6.1.1.1

total-power-warn-threshold attribute is optional.

Agreed. The TCA/threshold topic will be discussed in a wider scope.

Service-interface-point/name

6.1.1.1

Typo. There might be subsequent updates by the tapi-server

Agreed.

6.2.1 Use case 1a: Unconstrained DSR Service Provisioning single wavelength (<=100G).

6.2.1

Include less or equal to <=100

Agreed.

lower-connection

6.2.1.1

This attribute is only mandatory for connections representing multiple hops, (Top Connection). This clarification should be included in the RIA.

There are two cases where the lower-connection list attribute may be not applicable or be empty:

  • Cross-connections
  • Top-connections where the representation of lower partitioning levels does not provide further information (e.g., OTSi where the XC is encapsulated in the termination point). As described in [TAPI-CONN-MODEL-REQ-16]

Action points :

  • Discuss the general approach of null versus present and empty.
  • In the short term, include the above clarifications in Table 16.

switch-control

6.2.1.1

This attribute is only mandatory for connections in resiliency scenarios. This clarification should be included in the RIA.

The use of this attribute is only applicable on the relevant connection objects which implement the protection logic described in UCs 5a, 5b, 5c.

 

Action points:

  • Discuss the general approach of null versus present and empty.
  • Agreed. In the short term, include the above clarifications in Table 16.

supported-layer-protocol-qualifier

6.2.1.1

Wrong attribute in CSEP and CEP definition, the name shall be modified to "layer-protocol-qualifier" and the attribute type is an string (ENUM) instead of a LIST of strings (ENUMs).

Agreed .

wait-to-revert-time

6.5.2.2

This attribute is only mandatory in connection objects when the reversion-mode=REVERTIVE. This clarification should be included in the RIA.

Conceptually agreed but to be further discussed when new use case 9 will be covered.

Action points:

  • Agreed. Include a clarification note in Table 34.
  • Present UC9.

otsi-connection-end-point-spec/laser-properties

6.2.1.1

It is proposed to make it optional.

Agreed .

Equipment/ equipment-location

6.4.2.1

It is proposed to make it optional.

Action points:

  • Refinement on the description is pending.
  • Agreed . As a short term, the modification of the supported level for equipment object can be modified to "optional".

Equipment/ geographical-location

6.4.2.1

It is proposed to make it optional. The geographic-location is sufficient to be included within the device object, given that the device object in TAPI does not contain this attribute, the less redundant way to use this parameters is to include it only in the top-level equipment object (i.e., generally SUBRACKS).

Action points:

  • A discussion whether the device object may include this attribute and the inheritance towards equipment objects is pending.
  • Agreed . As a short term, the modification of the supported level for equipment object can be modified to "optional" with the clarification proposed.

Equipment/ manufacturer-identifier

6.4.2.1

It is proposed to make it optional. We will generally rely on manufacturer-name instead.

Agreed.

Equipment/common-actual-properties/is-powered

6.4.2.1

It is proposed to make it optional. is-powered attribute will only be required where applicable i.e., in SUBRACK equipment.

Action points:

  • Find cases where this is mandatory.
  • Agreed . As a short term, the modification of the supported level for equipment object can be modified to "optional", no further clarifications will be provided so far.

Equipment/common-actual-properties/temperature

6.4.2.1

It is proposed to make it optional. temperature attribute will only be required where applicable i.e., in FAN equipment.

Proposal to add a remark associated to the parameter: " * The temperature SHOULD be provided for any equipment when it is supported and available on the HW  equipment. "

Action points:

  • Agreed . As a short term, the modification of the supported level for equipment object can be modified to "optional" with the clarification proposed.

Device/GATEWAY

6.4.2.1

It is proposed to make it optional.

There is a typo in the value description " { NE_ Name_Gateway_Device}".

It should be filled with the NE_NAME of the Gateway device, it is only mandatory if there is another NE acting as IP GATEWAY for this NE in the DCN. Thus, this paramter will be set as "Optional" in the next specification version.

"It SHOULD be present if the Device DCN is connected to another Device acting as GATEWAY within the Subnet."

Action points:

  • Agreed . As a short term, the modification of the supported level for equipment object can be modified to "optional" with the clarification proposed.

Device/creation_time

6.4.2.1

Proposed to specify to use the tapi-common: date-and-time typedef.

 

Action point:

  • Telefonica to provide the purpose of this attribute, in order to decide whether this parameter should be formalized in TAPI v2.1.4 as a device's object attribute.

Device/uuid

6.4.2.1

It must be provided by the tapi-server .

Agreed.

RO paramters tapi client role

 

 

Action point:

  • It is pending a full review by Telefonica of all parameters required to be provided by the TAPI-Client which are Read-only.
  • Device/name
  •