Skip to end of metadata
Go to start of metadata

Date

28 November 2017

Attendees

Goals

  • Layer Examples for TR-512.A.5 and A.6 v1.3.1 
  • G.8052.1 and IEEE 802 Ethernet OAM 

Discussion Items

TimeItemWhoNotes
AdminKam

Record the meeting

  • recorded

London Dec. 4 - 8, 2017 meeting (Invited by ITU-T)

2018 Face-to-Face meeting proposal

 Layer examples for TR-512 v1.3.1Xiang

For TR-512.A.5 v1.3.1 Circuit Switched examples

    • Also to look at Figure 13 (case B) & Figure 15 (CTP type F) in SD1-18

    • Follow the color convention in the Key diagram in TR-512.1
    • Add text to explain the figures
    • Keep the Trapezoids same size
    • Need to add to TR-512.4 to show termination of a FC on an LTP with encapsulated forwarding function

For TR-512.A.6 v1.3.1 Packet Switched examples (not discussed)

 G.8052.1 and IEEE 802 Ethernet OAMKam

The following was prepared for the call but not discussed due to running out of time. It is deferred for Thursday slot IM-F

Touch Point Consideration for the ITU-T G.8052.1 and IEEE 802 OAM models

  • The G.8052 MepSource, MepSink, MepBidirectional, ETH_TTPSource/Sink, and ETH_CTPSource/Sink be the touch point classes from the G.8052.1 side with the IEEE classes

  • The CFM “component” and “mep” classes be used as the touch point classes from the IEEE CFM model with the G.8052.1 model.

  • Possible approaches for linking the touch point classes
    • Spec approach: The G.8052.1 Mep and ETH TTP/CTP decorate/specify the IEEE MEP and Component classes, as illustrated below

    • Subclassing approach: The G.8052.1 Mep and ETH TTP/CTP are subclassed from IEEE MEP and Component as illustrated below.

    • Referencing approach: The G.8052.1 Mep and ETH TTP/CTP point to the IEEE MEP and Component for the needed properties as illustrated below

 Re-engineering of IEEE 802 OAM YANGBerndThis topic was not discussed due to running out of time. It is deferred for Thursday slot IM-F

Action Items

  •