1. Pages
2. …
3. OIMT
4. Core Model
5. OIMT minutes
6. 2017 OIMT Minutes

2017-11-30 OIMT Meeting Notes

• ARO shut down
  • ARO has been shut down.
  • The ex-IMP archived documents are available at https://www.dropbox.com/sh/9wp0ojg109qbs5i/AADytB8pHwBU3KV5j4XcjL-Sa?dl=0
  • Regarding the liaison statements, need to find out from Cassandra where the liaison are
    • Action Item - Nigel: To ask Cassandra where the liaisons are and whether they are still private (ONF member only)
• TR-512 v1.3 publication
  • Status: Prod Guru for green light
• London Dec. 4 - 8, 2017 meeting (Invited by ITU-T)
  • Logistic information: Q14-meeting-info-v5.docx
    • "Subway" means walkway in UK.
  • Registration: http://doodle.com/poll/wrzpq2txbnhdnyiv
  • Contributions: https://www.itu.int/ifa/t/2017/sg15/exchange/wp3/q14/2017.12_London/wd/
    
    • ITU-T TIES account is needed for accessing the contributions. Contact Kam (Hing-Kam Lam) if you need access
• 2018 Face-to-Face meeting proposal
  • Proposed meetings: Face-to-Face Meetings
    • Nigel will check the possibility of London

• Final feedback and wrap up
  • 2017 Nov. 6-10 OIMT & OTCC Interim Meeting Agenda & Notes
  • Andrea confirmed that he already finished updating the minutes, which is now considered complete.
• Action items from the meeting
  • Kam and Nigel had run though the meeting minutes and extracted a list of possible work items.
  • The list was brief shared at the call.
  • Action Item - Nigel/Kam: To tune the list into action items.
    • Done: It is now contained in "Action Items from F2F meeting v1" and posted on the OIMT Core Model Planning wiki page Planning & Work Items
      • We now need to ensure we track the actions without using the meetings to do that.  
• Location for posting updated documents
  • Malcolm asked where to post the updated documents in the future (e.g., result from the action items)
  • One suggestion is one central repository. From where the documents can be linked by individual meetings
    • This suggestion needs further investigation so that to avoid future further move.
    • Action Item- Kam/Nigel: Check with Cassandra.

Nigel is drafting the text for a response. May take the opportunity of the f2f meeting next week to work off-line with Andrea and Kam for the response, although there is no explicit deadline for the response in the MEF liaison.

UML-Protobuf Mapping

• Draft from Chris
  • AI - Kam: Create a child page in IISOMI for Protobuf mapping
  • AI - Kam: assign a ad hoc local number, post it for group review (start tomorrow, for two week)
• Next steps to move forward
  • Team review
  • Liaise to ONOS/CORD
  • Code generator

Controller

• Discussed with Chris on Control Component vs Processing Construct, (1) relate to management fragment TMF TR-225, (2) using CC activities to understand where the operation model,

OAM

• No progress, still analyzing TAPI
• Will discuss more next week

Entity Lifecycle

• Updating as discuss in F2F, using pattern, aim at end of this week.
• use the ad hoc doc number, post in the same directory for the F2F for this one.
• Not ready for group review yet, but could be for discussion week after next week

v1.3.1 Layer examples

• Xiang to send the A.5 latest figure and text to Nigel

Touch point of G.8052.1 and IEEE 802 models

• See 2017-11-28 OT-IM Meeting Notes (not discussed in 11/28 OT-IM)
• Spec approach: model federation and run time extension

Analysis of IEEE 802 MEP/MIP/CFM YANG modules

• Bernd presented the draft UML model re-engineered from the ieee802-dot1ag-cfm YANG module.

• Findings (issues) occurring during re-engineering were discussed:

• How to model YANG Built-In Type “bits”?
  --> No solution

• How to model YANG Built-In Type “binary”?
  --> No solution

• How to model simple typedefs?
  Example:
  typedef mep-id-or-zero {
      type uint32 {
        range "0..8191";
      }
  -->Solution: Like already defined in the UML to YANG mapping guidelines: Modeled via DataType with single attribute.

• Different kinds of MAC address in ieee802-dot1ag-cfm.yang:
  type yang:mac-address
  type ieee:mac-address

   

  ieee802-types

  ietf-yang-types

  typedef mac-address {     type string {       pattern '[0-9a-fA-F]{2}(-[0-9a-fA-F]{2}){5}';     }     description       "The mac-address type represents a MAC address in the canonical format and hexadecimal format specified by IEEE Std 802. The hexidecimal representation uses uppercase characters.";     reference       "IEEE 802-2014, Clauses 3.1, 8.1";   }

  typedef mac-address {     type string {         pattern '[0-9a-fA-F]{2}(:[0-9a-fA-F]{2}){5}';     }     description "The mac-address type represents an IEEE 802 MAC address. The canonical representation uses lowercase characters. In the value set and its semantics, this type is equivalent to the MacAddress textual convention of the SMIv2.";     reference "IEEE 802: IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture RFC 2579: Textual Conventions for SMIv2"; }

  --> No solution

• Scott: The IEEE YANG modules are automatically converted from SNMP MIB and therefore an optimization may be required.
• Scott: The IEEE OAM YANG modules are work in progress; this is the reason for temporary inconsistencies between ieee802-dot1ab-lldp.yang, ieee802-dot1q-bridge.yang and ieee802-dot1ag-cfm.yang.