1. Welcome to join Tutorial Q.7/17 Rapporteur An Introduction to LAPS and MSR Applications To the March 2004 SG17 Meeting

2. Our Liaisons and Communications Q.7/17 Leader SG17 SG15 P802.17 SG13 IETF

3. 1 Delay contribution, August 1998 2 It was acceptable by ITU-T SG7(Data network and Open System Communication) at the September meeting, 1998 3 X.85/Y.1321 on IP over SDH using LAPS was determined at the June 1999 meeting 4 Recommendation X.85/Y.1321) was approved at March 2000 meeting, then new version is available Feb. 2001 X.85/Y.1321 (IP over SDH using LAPS) milestone

4. 1 IETF and ISOC 2 ITU-T SG15 (Optical and other transport networks) 3 ITU-T SG11 (Signaling requirements and protocols) 4 ITU-T SG13 (Multi-protocol and IP-based networks and their internetworking) 6 Nortel 7 NTT 8 Swisscom 9 Lots of email from Vendors and Carriers X.85/Y.1321 Comments received

5. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85) Note: PPP is widely deployed in networks around the world and has been updated and extended over the last 14 years. These slices just emphases a simple LAPS method of high-speed link (e.g. POS) and also provide compatibility with PPP/HDLC.

6. SDH/SONET HDLC PPP IP PPP over SDH/SONET IP over SDH LAPS Why LAPS (X.85)

7. Line Card 0 Line Card 0 Switch Fabric Switch Fabric Scheduler Line Card 1 Line Card 1 Line Card 6 Line Card 6 Line Card 7 Line Card 7 Line Card 8 Line Card 8 Line Card 10 Line Card 10 RE RE or LC11 RE or LC11 The diagram of Router Why LAPS (X.85)

8. O/E STM-16c Transceiver POS Framer Network Processor I/F POS Line Card Memory Switch Fabric 16 x 16 O/E POS Framer I/F Memory STM-16c Transceiver POS PHY Routing Engine POS Line Card Network Processor POS Line Card SPI-4.2 Why LAPS (X.85)

9. Routing Engine SDH/SONET HDLC PPP,LCP,IPCP IP OSPF TCP UDP BGPRIPSNMP Local node Adjacent Node Filter Function POS PHY/Utopia3 Reference Point Fwd/Rcv to/from Forwarding Engine LCP Software Hardware Protocol processing of signaling and Traffic plane Why LAPS (X.85)

10. The major objective of X.85 is to remove PPP protocols including LCP and IPCP in the case of POS. LCP contains 10 configuration packets,16 events, and 12 actions. Why LAPS (X.85)

11. Protocol 8/16 bits Padding RFC 1662 frame Flag 01111110 FCS 16/32 bits Address 11111111 Control 00000011 Flag 01111110 RFC 1661 frame X.85 frame X.86 vs. RFC 2615 (frame)PPP PDU SAPI 16 bits Flag 01111110 FCS 32 bits Address 00000100 Control 00000011 Flag 01111110 IPv4 and IPv6 PDU Why LAPS (X.85)

12. X.85 vs. RFC 2615, specifications including functions and related Network management RFC 2615 RFC 1661 RFC 1662 RFC 1570 RFC 1547 RFC 1340 SNMP & MIB X.85 SNMP & MIB Why LAPS (X.85)

13. LAPS or POS HDLC Framer/Deframer functions: Insertion of HDLC frame into the SPE Framing, Inter-frame fill and transmit FIFO error recovery. Scrambling (X**43 +1), Transparency processing generate a 16/32 bit FCS. Extraction of HDLC frame, Transparency removal, De-scrambling (if enable), FCS error checking, Optional delete the HDLC address and control fields. T R Why LAPS (X.85)

14. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85)

15. Comparison of Protocol states RFC 2615 2+137 LAPS 2 Why LAPS (X.85)

16. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85)

17. RFC 2615 PPP/HDLC LAPS Protocol encapsulationyesyes Inter-frame fillyes yes Scrambling yesyes Transparencyyesyes FCSyesyes Link status monitoring Yes yes Configuration Req./Ack/Nakyes padding function Terminate Req./Ackyes but it is seldom used Protocol Rejectyes but it is seldom used Echo Req./Replyyesyes in SDH/SONET Discard Req.yes but it is seldom used Why LAPS (X.85)

18. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85)

19. Input stream scheduler parsing Search & update Receive editor Queue mgnt. Output Stream scheduler Queue mgnt. Sending editor CPU I/F System I/F Fabric I/F Switch Fabric Framer/Deframer SSRAM SDRAM Pre-search queue Statistics & internal registers CPU The Diagram of Network Processor Why LAPS (X.85)

20. L1 L2 L3 L4 L5 L6 L7 Physical Layer Network Transport Session Presentation Application HDLC Open System Interconnection L2 PPP LCP IPCP Intermediate system 10 bytes Intermediate system 40-1600 bytes End system Why LAPS (X.85)

21. RFC 2615(PPP/HDLC)LAPS Cell based MPS/mPS 1600/10=1601600/40=40 1 Latency NP NP Latency variance4 times good Packet loss4 times very low Capability of Jumbo payload processing relative lower relative power good Congestionprocessing capability low middle relative high QoS 3 times lower normal good Why LAPS (X.85)

22. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85)

23. LAPS PPP/HDLC GbE PPP/HDLC GbE Node1 Node2Node3 Node4 Node5

24. SDH/SON ET HDLC PPP IP PPP over SDH/SONET IP over SDH LAPS How LAPS compatible with PPP/HDLC SDH/SON ET LAPS=HD LC PPP IP PPP over SDH using LAPS Why LAPS (X.85)

25. Protocol 8/16 bits Padding RFC 1662 frame Flag 01111110 FCS 16/32 bits Address 11111111 Control 00000011 Flag 01111110 RFC 1661 frame X.85 frame X.86 vs. RFC 2615PPP PDU SAPI 16 bits Flag 01111110 FCS 32 bits Address 00000100 Control 00000011 Flag 01111110 IPv4 and IPv6 PDU Why LAPS (X.85)

26. When the PPP is used to be encapsulated via SAPI for the compatibility with RFC 2615, it is noted: (1)Both FCS-32 and FCS-16 can be set by provisioning and is not negotiated. The 32-bit FCS must be used for all SDH rates. For STM-1c/VC-4 only, the 16- bit FCS may be used, although the 32-bit FCS is recommended. (2)Regarding the path signal label (C2) of SDH, for compatibility with RFC 2615, the signal label value of (x 43 + 1) scrambling is changed from 24 (18 hex) to 22 (16 hex). Additionally, the LAPS does also provide the signal label value 207 (CF hex) to indicate PPP without scrambling. (3)The data link will be operated as RFC 2615 defines and the Address field is set to 11111111, the padding field followed information field and the functions of Link Control Protocol and Network Control Protocol will be included. Why LAPS (X.85)

27. 1 Simple implementation 2 High efficiency in the POS line card of router 3 Function equivalent to PPP/HDLC 4 Performance of Carrier concern 5 Compatibility with PPP/HDLC 6 Test equipment (share POS) Why LAPS (X.85)

28. Testing equipment 1 Smartbits are used to throughput 2 RouterTest/Adtech is used to traffic and routing protocols Why LAPS (X.85)

29. X.86 (Ethernet over SDH/SONET) introduction

30. 1 Delay contribution from May 1999 2 It was acceptable by ITU-T SG7(Data network and Open System Communication) at the June meeting, 1998 3 X.86 on Ethernet over LAPS was determined at the March 2000 meeting 4 Recommendation X.86 on Ethernet over LAPS (TD 2046/Rev.1) was approved at Feb. 2001 meeting, ten months earlier than that of GFP LAPS (X.86) milestone

31. SONET/WDM GE 2.5Gbps SDH 155Mbps SDH 155Mbps Ethernet ITU-T X.86 (Target at Ethernet over SDH/SONET) 2.5Gbps FE EOS GE 1 3 2 EOS Ethernet Ethernet Ethernet Ethernet GE 1.Telecom based Switch 2.Datacom based SDH/SONET 3.2-port small box solution LAPS (X.86), three types of application

32. Latency Variance Computation Ethernet MAC -15μs Rate Adaptation, Buffer -15μs LAPS mapping, Buffer -15μs LAPS CRC, Buffer -15μs ----------------------------------------- Latency Variance Total:-60μs GE on GE switch -4μs

33. The competitive advantages of X.86 Remote Trail Performance Monitoring Remote Fault Indication IEEE802.3x – Active Flow Control in Burst Traffic Condition Low Price and Ease of Use (Compared to LANE) Low Latency and Low Latency Variance 1+1 redundancy based Ethernet and Gigabit Ethernet service Target at existing telecom transport resources

34. IFG Preamble +SFD 802.3 MAC Frame 12 Bytes8 Bytes64 Bytes=84 Bytes FlagAddrContSAPI802.3 MAC32-Bit CRCFlag 10 =84 Bytes 1112644 Flag 1 Time Fill X.86 does match Ethernet and Gigabit Ethernet very well

35. (1)Payload (2)Payload Header (3)Optional Payload FCS (4)PLI value (5)cHEC computation Understand GFP

36. HEC inherits from ITU-T Rec. I.432 Octet based spec. ATM is L2/L3 technologies, based on connection and fixed packet size (cell), IP as a ATM client is flexible rate for the IP over ATM applications in the most case; GFP is L1/L2 technologies, based on connectionless and variable packet size. For the L1-GFP, FE/GE as a GFP client is rigid rate for the Ethernet over SDH applications in the most case In terms of PDH(E1/T1/E3/E4), Jumbo Payload size of IPv6 can be greater to 64Kbits length due to GFP-PLI is 2-Octet definition (2 16 bits=64Kbits=8Kbytes) If PLI is changed to 3-octet or more, how to keep compatibility with existing GFP standard Flow control Rate adaptation? Understand GFP

37. Why Flow control? Why Rate adaptation? (1)FE/GE BandwidthVC or VCs concatenation Bandwidth (2)No difference is applied for the two time-slice (TS) if Ethernet data stream is mapped into VC overhead or/and VC payload during two different time-slice Understand GFP Real-time VC overhead VC payload Mapping octet by octet TS1 TS2

38. Issue of tiny-frame (7 bytes), Client Signal Fail (LOS of Client Signal and Loss of Character Synchronization) 4-octet idle issue Understand GFP

39. L1 L3 L4 L5 L6 L7 Network Transport Session Presentation Application Physical Layer Open System Interconnection L2 Intermediate system 7 bytes Intermediate system 40-1600 octets End system tiny-frame issue for IPv4 over SDH using GFP(1) GFP Understand GFP

40. tiny-frame issue for IPv4 over SDH using GFP(2) Framer POS-PHY bus/SPI-4.2 bus 155M POS ---8 25M 622M POS --- 16 50M 2.5G POS --- 32 100M,64 50M Framer Framer Framer Framer Framer Network Processor Backplane Adaptation Routing and signaling Line Card Understand GFP

41. GFP LAPS Cell based MPS/mPS 1600/7=2281600/40=40 1 Latency variance great middle little tiny-frame issue for IPv4 over SDH using GFP(3) Understand GFP MPS: Maximum packet Size, 1600 octets specified by IETF mPS: Minimum Packet Size, 40 octets specified by IETF

42. Mapping relationship and timing, FE/GE is mapped into GFP, LAPS and RPR(LAPS/GFP) Understand GFP 4-octet idle issue

43. Idle PLI eHEC CID+ Spare tHEC Type cHEC PLI Idle IFG Preamble+SFD 4 22 2 2 812 4 4 2 2 64-1518 Idle 4 IFG Preamble+SFD 8 12 4 4 2 Ethernet Frame GFP frame Real Time FCS GFP Payload Case 1 - Octets Mapping of Ethernet using GFP Understand GFP 64-1522 if VLAN

44. Flag X.86 Frame IFG Preamble +SFD 8 1264-1518 IFG Preamble +SFD 812 Ethernet Frame Real Time Flag Addr Flag 1 1 10 1 1 N 1 1 Addr. 1 CtrlSAPI FCS 4 LAPS Payload 2 Flag 1 2 3 4 5 6 Case 2 - Octets Mapping of Ethernet using LAPS LAPS & GFP 68-1522 if VLAN

45. LAPS & GFP RPR idle format

46. Idle GFP frame RPR Frame IFG Preamble+SFD 8 1264-1518 IFG Preamble+SFD 812 Ethernet Frame Real Time Idle PLI eHEC CID+ Spare tHEC Type cHEC PLI Idle 4 22 2 2 4 4 2 2 4 4 4 2 FCS Ring Control 2 DA 66 SA 2 Protocol Type 2 Header CRC FCS 16 RPR Payload GFP Payload Case 3 - Octets Mapping of Ethernet/RPR/GFP 1 2 3 4 5 6 7 8 9 10 4 4 64 ?Packet Loss Timing border 12346 5789 10 Delay 12346 5789 10 No Delay Variable Next frame 44 LAPS & GFP 68-1522 if VLAN

47. LAPS & GFP Flag GFP frame RPR Frame IFG Preamble+SFD 8 1264-1518 IFG Preamble+SFD 812 Ethernet Frame Real Time Flag SAPI Ctrl Addr Flag 1 1 1 1 N 2 Idle 4 1 1 1 FCS Ring Control 2 DA 66 SA 2 Protocol Type 2 Header CRC FCS 16 RPR Payload LAPS Payload Case 4 - Bytes Mapping of Ethernet/RPR/LAPS 1 2 3 4 5 6 7 8 9 10 1 1 64 Good No Packet Loss Timing border 12346 5789 10 Delay 12346 5789 10 No Delay Variable Fixed N Flag N Next frame 68-1522 if VLAN

48. GFPLAPS/X.86Percentage 64bytes10.520 µs9.658 µs8.9% 1518bytes203.620 µs133.967 µs51.9% 9.6Kbytes-769.567 µs Comparison of Measurement LAPS & GFP

49. Flow-control and rate adaptation are very useful for BW mismatch between Ethernet and SDH VC (or concatenation) and time-slice difference between VC overhead and VC payload Application of Both SDH and PDH(E1/T1/E3/E4) for LAPS, Both SDH and PDH(DS3) for GFP High efficiency LAPS is compatible with POS and PPP/HDLC LAPS Idle(Flag) has good performance for line- speed Ethernet over SDH/SONET applications X.86 was approved ten months earlier than that of GFP Advantage of using LAPS

50. Disadvantage of LAPS and PPP/HDLC (1) Escape Code LAPS & GFP

51. An Introduction to MSR Applications What is MSR? Why MSR? MSR Scope Multi-service capabilityMulti-service capability

52. TCE (1) MSR (2) TCE (2) What is MSR(1)

53. Station A Big pipe: Aggregate Small pipe: tributary (just like PVC) Station B What is MSR(2)

54. An Introduction to MSR Applications What is MSR? Why MSR? MSR Scope Multi-service capabilityMulti-service capability

55. Focus on Metro Sync. to async., TDM to packet, Physical transmission from SDH/SONET to MAC, High- order VC and Lower-order VC to tributary (packet) MSPP/MSTP from TDM based to packet based Push multi-service transport issue to LLC(L2) Basic Consideration(1)

56. Differentiated SLA, controllable and configurable service operation Static and dynamic resource management Both connection and connectionless Bridge and back-to-back connection between MSR/RPRs Lower cost and little maintenance Basic Consideration(2)

57. differentiates RPR transport capabilities and provides multi-congeneric-service and multi- heterogeneous-service transport including Ethernet, Gigabit Ethernet, FR, G.702 PDH circuit -- Synchronous and asynchronous circuit transport, Video signal, voice-band signal, Digital channel etc. Why MSR(1)

58. Differentiates RPR ring protection function and provides service (or tributary) based standby (protection) of 1+1, 1:1, and 1:N models within 50 ms. Why MSR(2)

59. Reassembly a single packet based multicast and broadcast of RPR to form service (stream) multicast and broadcast capabilities, and provide Service (or tributary) based multicast and broadcast. Why MSR(3)

60. Adding bandwidth management function for each service (tributary) and provides service bandwidth management with either symmetry or asymmetry. Why MSR(4)

61. Adding bandwidth merging function for congeneric-service (congeneric-tributary) and provides tributary merging with either symmetry or asymmetry. Why MSR(5)

62. Adding the simple security filtering function for each tributary service and provides line-rate filtering to monitor and manage service security. Why MSR(6)

63. Adding the performance management function for each tributary service and provides tributary performance monitoring in 15-minute and 24-hour. Why MSR(7)

64. QoS Guarantee Customers separation Addresses separation Topologies separation Why MSR(8)

65. Topology supported Two fiber ring Link Broadcast topology Why MSR(9)

66. Dynamic resource management Static resource management Tributary transport Why MSR(10) Next job

67. An Introduction to MSR Applications What is MSR? Why MSR? MSR Scope Multi-service capabilityMulti-service capability

68. S[62 ] S[8] S[7] S[6] S[5] S[0] S[1] S[2] S[4] WEST PHY EAST PHY MAC Data Req. Ind. RPR MAC client: X.87 layer Ringlet 1 Ringlet 0 X.87 layer client Reference Point T1/T2 Reference Point G1/G2 X.87 XP UNACK Data Req. Ind. MAC Ctrl Req. Ind. X.87 scope SDH/SONET RPR-MSR protocol stack RPR X.87 GFP/HDLCLAPS MSR Client IP RPR MAC GFP/HDLCLAPS

69. Ethernet LAPS SDH/SONET IP Ethernet over SDH/SONETIP over SDH X.85 X.86 GFP LAPSGFP/PPP LLC IP SDH/SONET RPR-MSR RPR X.87 GFP/HDLCLAPS MSR Ethernet Multi-serv. IP Layered Model (1)

70. Layered Model (2) 802.3 PHY 802.3 MAC-MSR protocol stack X.87 802.3 MAC MSR Multi-service IP Other

71. Reference Point G1/G2 RPR IEEE 802.3MAC X.87 protocol L3 packet forwarding Reference Point T1/T2 TCE(2) Ethernet GE TCE(1) VLAN CS & NM MPLS Layered model of Multi-service node

72. Link+ADM MSR node Agg Trib

73. Broadcast MSR node Agg. MSR node Agg.

74. An Introduction to MSR Applications What is MSR? Why MSR? MSR Scope Multi-service capabilityMulti-service capability

75. Differentiate RPR (1) FeaturesRPR+MSRRPR Operation mode MAC+LLCMAC Supported tributary service multi-congeneric-service and multi-heterogeneous- service transport including Ethernet, GE, FR, G.702 PDH circuit, Video signal, voice-band signal, Digital channel etc. Class A/B/C but does not support multi-congeneric- service transport within a station

76. FeaturesRPR+MSRRPR Multicast and broadcast Based on packet and tributary service,support multi-congeneric- service within a station Based on packet Protection1+1,1:1 and 1:N standby, support multi-congeneric- service within a station Station based protection switch Differentiate RPR (2)

77. FeaturesRPR+MSRRPR Topology Two-fiber ring, link, broadcast Two-fiber ring Bridge across a ring 802.1 Bridge or back- to-back connection, regeneration of service tributary improves tributary QoS 802.1 Bridge Differentiate RPR (3)

78. FeaturesRPR+MSR RPR Link addressGlobal MAC address or local MAC address Global MAC address Bandwidth management Support- Differentiate RPR (4)

79. FeaturesRPR+MACRPR Security filtering Support - Asymmetrical service Support - Differentiate RPR (5)

80. FeaturesRPR+MACRPR Performance monitoring Loopback test Performance monitoring and Loopback test for tributary Loopback Differentiate RPR (6)

81. Access MSR MAN/STM-64 Backbone Applications Backbone MSR Access MSR

82. Applications: POP Interconnect POS/EOS RPR 2X2.5 Gbps STM-16 2.5 Gbps RPR+MSR 2X2.5 Gbps

83. Further study in Q.C/17 (old Q.7/17) Maintenance of X.85/Y.1321 and X.86/Y.1323, Update and extension of X.87/Y.1324; Progress draft Recommendation X.msr, including associated Ethernet/Gigabit Ethernet/10G Ethernet aspects; Develop Requirements for MSDN, areas of study and development include: - Identification of market needs - architectural considerations, for L2 data networks; - multi-service multicast aspects; - Ethernet UNI and NNI aspects. Enhance existing packet protocols or, if required, develop new packet protocols to support the developed MSDN requirements, including service mechanisms; Develop associated MIBs (Management Information Base) to support item (iv);