Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

5 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:

  • Continue the discussion of Cisco implementation
  • Overview of TAPI alarm list for 2.4 version
  • Progress the review of the Reference Implementation Agreement 2.0
80 minsCisco implementationGabriele Galimberti 

Gabriele Galimberti presents some slides on the Cisco implementation.

  • The control architecture is based on ACTN architecture.
  • Both optical and packet networks can be multivendor.
  • TAPI is the choice for the Optical Controller
    • because two years ago TAPI was the more stable and mature specification, preferred by Operators.
  • One key aspect is the integration between Optical Line System and the Router pluggable (transceiver).
    • Optical Controller must be informed about which Router optical interface/pluggable is connected to which add/drop ROADM port.
    • The transceiver function in on the Router.
  • Ramon Casellas asks why an optical agent cannot be implemented on the Router. Gabriele Galimberti replies that:
    • Optical Operators do not want to talk to Routers and vice-versa.
    • A lesson learned is not to share the same data plane components between more controllers.
      • Esther confirms that Orange IP experts recommend that separation.
      • Ramon Casellas indicates that Infinera presented a shared management.
  • Gabriele Galimberti clarifies that the information exchange for reconciliation is performed at MDSC (Multi-Domain Service Coordinator) level.
  • Gabriele Galimberti presents the detailed structure of the pluggable information.
    • It is a proprietary / organizational operational mode, where also some technical (explicit) parameters are specified:
    • The operational mode is represented in TAPI 2.1.3 OtsiTerminationConfigPac as:
      • applicationIdentifierType = PROPRIETARY
      • applicationCode = string where the relevant parameters are coded.
    • Similar approach as Open ROADM catalog specs (operational-mode-catalog ?)
    • Andrea Mazzini TAPI 2.4 includes the transceiver profiles derived from draft-ietf-ccamp-optical-impairment-topology-yang
      • We need to evaluate a TAPI synthesis of IETF CCAMP optical-impairment-topology and dwdm-if-param.
  • Discussion on the link between Router pluggable and ROADM port: it can be automatically discovered and/or managed at MDSC level.
  • Gabriele Galimberti will provide a TAPI proposal based on the presented slides.
  • Ramon Casellas we need to understand how the presented architecture can fit in the TAPI Reference Implementation Agreement 2.0.
    • Preliminary agreement that it is the Optical Line System Controller network management scenario, where transceivers/transponders are not included.
      • The MDSC is delegating the complexity of OLS management to the Optical Controller.
  • Gabriele Galimberti confirms that TAPI could also be the  MDSC NBI.

Agreed to continue the discussion on next call.

40 mins

Next steps on TAPI Streaming

Nigel Davis 

Nigel Davis presents two slides with some key items for TAPI streaming future development (otcc2022.ND.002_StreamingNotes.pptx)

  • SDN architecture, the Client Controller is always aligned to the Server Controller.
  • Concept of compact log, where not relevant changes are not included, to simplify a realignment procedure.
    • Compaction delay is longer if history is more relevant.
  • Dominique Verchere is TR-548 relying on existing mechanisms like Kafka?
    • Nigel Davis no, the currently proposed environment is WebSocket.
  • Flow control, the sequence number allows to Client to detect missing records.
  • Snapshot streaming to fulfil the requirement to trigger detailed tracking of parameter(s) under certain condition(s).
  • Explore gNMI and Protobuf for optimization.

...