Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Update on Photonic Model and other enhancements available in the pull request 524

Agreed Items & Priority

Discussion items

0 minsAdministrative

All



TAPI RIA 2.0 (ONF TAPI RIA):

  • Scheduled two additional, dedicated TAPI calls:
    • Mon 14-16 and Wed 13-15 CEsT

See TAPI Call-in Details and Notes for the details.


TAPI weeky call

Preliminary agenda:

  • Present the updates of photonic model - continue the discussion on spectrum model
  • Progress the review of the Reference Implementation Agreement 2.0
20 mins

Pull request 524

Andrea Mazzini  presents the major updates included in the Pull request 524.

  • Centralization of Alarm Names and PM Metrics in TapiCommon module.
    • This allows to have TapiFm and TapiOam independency.
  • TapiPhotonic:
    • OtsImpairments is now composed by OtsMediaCepSpec, no longer by OtsNodeEdgePointSpec.
    • OmsGeneralOpticalParams is composed by OmsConnectionEndPointSpec.
  • TapiCommon: Agreed to remove ODU layer protocol name.
  • Note that updated yang modules are available in https://github.com/amazzini/TAPI
    • TapiEquipment and TapiStreaming yang modules still under work.
90 mins

Update on Photonic Model

All

Andrea Mazzini presents the TapiPhotonicMedia UML updated diagrams.

  • Discussion on spectrum model
    • Currently the datatype is composed by
      • upper and lower frequency
      • adjustment granularity
      • grid type
    • Agreed that adjustment granularity and grid type are necessary/useful only in specific cases.
    • Noted that TAPI (2.4 draft) currently does not foresee a slot width parameter, useful in case of fixed grid.
  • Gabriele Galimberti and Esther recall that ITU-T and IETF adopt the M, N notation (G.694.1)
    • Agreed that is necessary to clarify the mapping between current TAPI spectrum model and M, N notation.
    • Agreed to explore possible adoption of M, N (and K - IETF) notation in TAPI.
  • Frequency unit of measure, TAPI (2.4 draft) currently specifies integer type (uint64) and MHz unit.
    • Gabriele Galimberti in case of further refinements of granularity we may have sub-MHz values.
    • Preliminary agreement to move to KHz or even Hz, given the dimension of the uint64 number.