Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »


26 September 2017



Discussion Items

  • Proposed that the Wireless Transport sub-project calls be moved from Tuesday to Wednesday so that to avoid time conflict with the TAPI call
    • Could use the 6:00 - 8:00 AM Pacific Time slot
      • Noted that the IISOMI UML-YANG Mapping call is Wednesday 5:00 - 6:00 AM Pacific Time and IISOMI Infrastructure call is 8:00 - 9:00 AM Pacific Time
    • Will alternate bi-weekly for the WT and PHY topics in the new Wednesday calls
  • Proposed what should be discussed in the WT calls verses in the OTIM call
    • High-level modeling topic and Core-model related topic will be discussed in OT-IM call
    • Technology details of WT and PHY wll be discussed in the WT call
    • High-level interface, including YANG, will be discussed in the TAPI call
  • Presented slide deck (presentation slides) on the structure and coverage of the future TR document on PHY interface description
    • Need much more (as compared to previous TRs) explanation/clarification of the generic model and concepts, such as recursion, association, etc.
      • Note that TR-512 v1.3 (now in the approval stage) includes a A.x series documents, which provides example usage of the core model. This series should be helpful
    • Need to specify how the interface handle cases where the product does not support the full range of capability/feature as defined in the model.
    • Need to describe Netconf & YANG specification in the TR.
      • Note that TAPI documented the requirement and interface specification separately. It uses TR for requirement and separately the SDK (Software Development Kid) for the interface specification, including YANG.
        • The SDK could be published as TR.
 WT SpecMartinNot discussed due to time constraint

Action Items

  • No labels