Versions Compared


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

Updated 29 Nov  

The content and scheduling of a TAPI release is described at TAPI Roadmap 20212023 page.

Any major TAPI release (vX.Y) must be associated to a TAPI RIA version (vA.B)


The vote is extended to all contributors, where a contriburs is attending TAPI calls regularly (definition of "regularly").

The vote should be extended to all downstream consumers of TAPI.

The possible votes are yes, no and abstain. For approval, a certain percentage of yes votes shall be defined (e.g. the 1/3 of MEF).

  • The review period shall not exceed two full working weeks.
  • As a general rule, no further modifications are allowed during the review period.
    • During TAPI regular calls small fixes can be agreed and tracked in the voting page.
  • Deadline date for voting shall be specified in the TAPI call minutes and in the dedicated voting page.
  • Comments can be added to the voting page (once I find how to add comment box...)
    • A negative vote must be motivated by specific comment(s), otherwise will be considered as a "void vote".
  • The review period can end in only two ways:
    • Delivery is agreed: there are enough yes votes according to the rules.
    • Delivery is not agreed: all other cases.
      • In this case, the The delivery release process must be repeated.
        • Explore "fast process" option.
        • Explore "deadlock avoidance" process, e.g. after two failed reviews reduce quorum, and/or dedicated vote to solve a conflict.


Current editors of the model are listed in the Yang modules:

  • Ramon Casellas
  • Nigel Davis
  • Arturo Mayoral
  • Andrea Mazzini
  • Karthik Sethuraman

To split the review work, each editor is required to focus on a specific subset of the modules:

  • Ramon Casellas 
    1. TapiNotification
    2. TapiFm
    3. TapiConnectivity
    4. TapiOam
  • Nigel Davis 
    1. TapiCommon
    2. TapiStreaming
    3. TapiTopology
    4. TapiEquipment
  • Arturo Mayoral
    1. TapiTopology
    2. TapiConnectivity
    3. TapiOam
    4. TapiPhotonicMedia
  • Andrea Mazzini 
    1. TapiNotification
    2. TapiTopology
    3. TapiConnectivity
    4. TapiOdu
    5. TapiEth
  • Karthik Sethuraman 
    • TapiCommon
    • TapiTopology
    • TapiPathComputation
    • TapiConnectivity

TapiDsr and TapiVirtualNetwork are not assigned given their current slow pace of evolution, which

  • will be informally agreed,
  • will include the modules subject of the modifications.