Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

  • Admin
  • TAPI v3 Resilience Enhancements
  • TAPI v3 Connectivity Enhancements

Discussion items

TimeItemWhoNotes
10 minsAdministrative
  • Next TAPI Call: Next Tuesday  

    • TAPI Reference Implementation Arturo Mayoral
    • TAPI Equipment model in a new TAPI branch - 2.1.3
  • All-day Virtual Meeting on Friday

    • Central Europe time zone
      • 12:00 PM CET - 15:00 CET
      • 15:30 PM CET - 18:30 CET
    • 2 Topics for discussion:
      • 1st Session: Topology
      • 2nd Session: Connectivity
      • backup (in case if we have time): Resilience
  • Skip TAPI call the following week  
  • Next F2F Meeting Plan - discuss on the OTCC/OIMT TST call on  
    • Week of 
      • Should we schedule it earlier? In April time-frame?
    • Location: Telefonica, Madrid
60 minsResilience Enhancements
  •  
  • Is TE Route same as Intended Route?
    • similar in concept.
  • Are all these constructs P2P?
    • too early to say
  • The above protection scenario 2 is more correctly represented as follows
  • But the about setup may not be legal as protection-switch control domains should not overlap
  • Consensus on this call is to follow the protection-switch control domain approach to model routes and explore further.
    • In this approach, switch domains should not overlap
    • the switches here can be probably controlled by restoration schemes as opposed to protection schemes
  • On slide 1, are the installed and current routes just statuses on the "alternative" routes
  • Is a Switch Control Domain a special case of Forwarding Domain or Forwarding Construct?
  • Does a Switch Control domain need to coincide with the switch controls or on the effect of the switches?. See below...
  • Is the concept of "installed" Route same as "ConnectionHasLowerLevelConnections"?
60 minsConnectivity Enhancements

Action items

  •