Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Admin
    • Agenda for next TAPI virtual meeting
  • OAM: NCM and TCM provisioning and resource model
  • Review the updated TR-547-TAPI Reference Implementation Agreement_v1.1.docx
    • New use cases: 0d, 1g, 1h, 2a, 2b, 2c, 3d, 3e, 3f, 5d, 11a, 11b, 13b, 13c, 16a, 16b.
      • Review 16a/b Alarm/TCA notification
      • Link model, agree a general rule
      • OTS and OMS model
  • Clean up of “Experimental” stereotypes

Agreed Items & Priority

  • Below the list of the agreed items and related priority.
  • An item is blocking when its resolution is necessary precondition for the delivery.

TAPI 2.1.3 and RIA 1.1

  1. OTU(+ODUCn) CEP/CSEP as single point for OTU/OTSiA ConnectivityService provisioning (solved)
  2. ENNI/INNI Asymmetric service provisioning for multi-domain scenarios, agree UCs (solved)
  3. Alarm / TCA notification (blocking, 1)
    1. Subscription
    2. Notification contents
      • Probable Causes / Elementary alarms (e.g. ITU-T cZZZ fault causes), including TCA PM Parameters
  4. OTS and OMS model (blocking, 2)
  5. Path Computation Use Cases (blocking, 3)

TAPI 2.3 and RIA 1.2

  1. MEP/MIP model vs. direct inclusion of OAM parameters in the CEP (blocking, 1)
    1. ODU OAM
    2. Photonic OAM
    3. TCA provisioning
  2. Physical impairments (not blocking)
    • OFC is augmenting TAPI Link, others the AbstractStrand.
    • Type of amplifier, fibre attenuation, etc.
  3. Photonic model capability (not blocking)
  4. Lifecycle management of ConnectivityService at every layer, necessary to identify UCs (not blocking)
    • Lifecycle management of single ConnectivityService, necessary to identify UCs
  5. 3R (not blocking)
  6. UNI Client interfaces modelling. DSR/ODU multiplexing over ODU (not blocking)
  7. RESTCONF Response codes for use cases (not blocking)
  8. TAPI OAS, action points to be assigned (not blocking)
  9. Routing Constraints (not blocking)
  10. Physical Route (not blocking)

Discussion items

20 minsAdministrative

All



Next TAPI virtual meeting. candidate week is

  • 12-23 April - consider 2+1 days/5 hours - focus on limited number of items.

Virtual meeting preliminary agenda:

  1. Path Computation
  2. 3R
  3. UNI Client interfaces modelling. DSR/ODU multiplexing over ODU
  4. Physical Route and Physical impairments (GNPy as main reference)


Nigel Davis will set up an additional separate call for clarification regarding TR-548 scope, involving Jack Pugaczewski (MEF and TMF).

Ramon Casellas plans to provide an updated RIA 1.1 draft by the virtual meeting.


 TAPI Call: 2 hours

Review the updated TR-547-TAPI Reference Implementation Agreement_v1.1.docx

  • New use cases: 0d, 1g, 1h, 2a, 2b, 2c, 3d, 3e, 3f, 5d, 11a, 11b, 13b, 13c, 16a, 16b.
  • Alarm / TCA notification.
  • Link model, agree a general rule.
  • OTS and OMS model.
  • Physical Route.
60 mins

OAM: NCM and TCM provisioning and resource model

All

Andrea Mazzini presents some slides on NCM and TCM provisioning and resource model:


  • General agreement on the table contents.
    • Preliminary agreement that the "NCM Provisioning for Maintenance" can be deferred.
  • Nigel Davis suggests to add the "intermediate blind spot" case to:

Andrea Mazzini then presents the current ODU OAM UML diagrams.

  • Agreed that the OamService and its OamServicePoints can be created through Restconf POST operation.
    1. Agreed the relationship between OamServicePoint and the monitored CEP, to allow "TCM Provisioning for Maintenance".
    2. Ramon Casellas highlights that currently defined OAM RPCs would anyway need a thorough review.
      1. Confirmed the decision to deprecate RPCs - which are replaceable by Restconf operations.
      2. Already identified candidates for new RPCs are the:
        • Get by UUID (to overcome the constraints of the tree structure)
        • Stateless Path Computation

Discussion on OamJob.

  • Agreed that the collection policy (e.g. streaming, get history data, ASCII files) is more in the OamContext scope.
  • Agreed to remove NCM_AND_DELAY, TCM_AND_DELAY entries from OduOamJobType.
  • Agreed that the OduDelayPerformanceData shall augment OamJob (one shot operation) instead of CurrentData.
    • Is there any defined sampling mechanism for delay measurements?

60 mins

Review 16a/b Alarm/TCA notification

All

Continued the analysis of the new TapiAlarm module:

  • rootCauseAlarm, we need to define the exact meaning.
    • At least is agreed to add the "unknown" value.
  • Nigel Davis points out that the currently defined AlarmInfo and TcaInfo can be restructured following the augmentation pattern, to allow a better decoupling between purpose-specific parameters:
    • e.g. SecurityAlarmInfo can augment AlarmInfo - as it applies only to the alarms with security AlarmCategory.
    • Similar consideration for some TcaInfo attributes, e.g. tcaChangedTime and tcaClearedTime are applicable to controllers supporting alarm lifecycle.
    • Hing-Kam Lam suggests to comment all augmentations.
  • Ronald indicates that TCA can be related to OAM PM.
    • Discussion on the distinction between an "alarm" and a "threshold crossing alarm".
    • Preliminary agreement that a TCA applies when a threshold is defined (either through specific provisioning or by server controller or by equipment constraints).
    • Mentioned that granularity may not apply to gauging.