Proposed amendments of control frames for 802.17c Yan Wang Huawei technologies

1. Proposed amendments of control frames for 802.17cYan WangHuawei technologies 802-17

2. New Control Frames • PIRC frame • Exchange and notify the status messages between the mate stations on the ring. • Peer message • The message between the peer stations. What should it be? • Reversion notify frame • Notify the defect reversion to the inter-ring station when multiple links failure protection is used. It is helpful to loop prevention. 802-17

3. Clause 9 Frame Formats • 9.3 Control frame format • 9.3.2 Control frame fields • Insert the following value 0C16 information field in Table 9.4, after the 0B16 entry. 802-17

4. MSB LSB res pirc sas bf co mu 1 Clause 11: Topology discovery and protection • 11.4 Defined ATT encodings • 11.4.3 Station settings ATT • Replace Figure 11.18 with the following figure. • Replace section 11.4.3.1 with the following text. • 11.4.3.1 res: A 3-bit reserved field. • Insert the following station setting immediately following 11.4.3.1. Renumber as necessary. • 11.4.3.2 pirc: A (protected inter-ring connection) bit that is set to 1 if the station is a inter-ring connection station, based on the value of myTopoInfo.pircUser. Otherwise, this bit has a default 0 value. • Change the last paragraph of 11.4.3 as follows. • When received, this information is copied to the pircUser, sasUser, badFcsUser, conservativeMode, and multichokeUser fields in the topology database. 802-17

5. Clause 12: Operations, administration, and maintenance (OAM) • 12.1 Overview • Add the following item to the end of the list. • f) Provide a mechanism to exchange and notify status messages between the mate stations on the ring. • 12.1.2 OAM functions supported by RPR • Add the following additional OAM frame type supported to the end of the list. • e) PIRC management—For status exchange and notify between the mate stations. • 12.1.7 PIRC management operations • A PIRC frame allows one interconnected station to notify its status and characteristic to its mate station in the same protection group. The PIRC frame is broadcast over the rings with a service class of subclassA0. • PIRC frames are received by all stations, processed by the inter-ring stations. 802-17

6. PIRC Frame 12.3 OAM frame formats • Insert the following section, 12.3.5, after 12.3.4. • 12.3.5 PIRC frame • The PIRC frames are identified by the controlType field value of CT_OAM_PIRC_STATUS and a controlVersion value of 0. The PIRC frame is only sent by the inter-ring station. The PIRC frame contents include information about the sending station’s status and characteristic. Figure 12.13 illustrates the PIRC frame payload with the controlDataUnit portion of the frame indicated. The header fields (specified in 9.3, but not illustrated here) are additionally constrained as specified in Table 12.5. 802-17

7. 1 controlType 1 controlVersion 1 Protection Group ID Status 1 controlDataUnit Priority 1 Device ID 4 PIRC Frame Payload Format Figure 12.13 802-17

8. PIRC Frame Header Field-value Restrictions Table 12.5 802-17

9. MSB LSB res lb fs PIRC Frame Payload • Protection Group ID • Identify a protection group. • Status • The status field consists of multiple sub-fields, as illustrated in the following figure. • res: Reserved. • lb: A load balancing bit marks if the station is working in load balancing mode. • fs: Two forwarding status bits identify the forwarding status. 1 802-17

10. Sub-fields of Status • Traffic sets are the sets of different VLANs, methods such as hashing, manual configuration etc. can be use to decide which set a VLAN belongs to. 802-17

11. PIRC Frame Payload • Priority • The Priority of the inter-ring station. • It is used to decide the role of inter-ring station (active/standby, traffic set1/traffic set 2). Such as the station with higher priority should be the active one. • When forwarding status conflict happens, it can also be used to decide which station should change its forwarding status. This can be used in Manual Switch. • Device ID • The inter-ring station’s device ID. • It can be used for management, and when it happens that two mate stations’ priorities are same, the device ID can also be used to solve the forwarding status conflict. 802-17

12. State Machine 802-17

13. Forwarding States • Normal state: • In the active/standby mode, the station forwards all or none of the inter-ring traffic. In the load balancing mode, the station forwards traffic set 1 or set 2. • Protection state: • Forwarding all inter-ring traffic because of the mate failures or multiple links failure protection. • Failure state: • Inter-ring traffic can’t be forwarded because of self down or peer down. 802-17

14. PIRC Frames and State Transform • PIRC frame is sent periodically by the inter-ring station when it is in normal state. • PIRC frame is sent immediately by the inter-ring station when its forwarding state changes. • Mate up/down messages are carried by PIRC frame. • When received mate status message is incompatible with local inter-ring, forwarding status may be changed according to the priorities. • Hold-off timer is needed to prevent loop when the inter-ring station status changes from non-forwarding to forwarding. 802-17

15. Peer Message • It shall not be the RPR frame. Should it be standardized in a RPR standard? • When the two peer stations are in one equipment, the peer messages may be some interior instructions. • When the two peer stations are two independent equipments and connected by a link, the message format is related with the connecting port. • Few possibilities that peer stations are from different vendors. • We can just request the station has the ability to find the failure between peer stations. 802-17

16. Multiple Links Failure Protection • C2 is selected to forward the inter-ring traffic. • Two links failure makes R1 can’t communicate with C2, inter-ring traffic from R1 fails. • Protection is achieved by both inter-ring nodes C1 and C2 forwarding all inter-ring traffic. 802-17

17. Transient Loop Prevention • When nodes R1 and R2 find the link recovers, they shouldn’t switch to normal status immediately. • They keep in protected status until their timers expire. • Before the timers expire, the correlative interconnected node C1 shall know the reversion and stop forwarding. R1 and R2 can send reversion notify frame to the interconnected node C1 and C2. • Timers should be configured appropriately, timers expire after node C1 stops forwarding and topology converges. 802-17

18. Clause 9 Frame Formats • 9.3 Control frame format • 9.3.2 Control frame fields • Insert the following value 0D16 information field in Table 9.4, after the 0C16 entry. 802-17

19. Clause 12: Operations, administration, and maintenance (OAM) • 12.1 Overview • Add the following item to the end of the list. • g) Provide a mechanism to notify the defect reversion to the inter-ring station when multiple links failure protection is used. • 12.1.2 OAM functions supported by RPR • Add the following additional OAM frame type supported to the end of the list. • f) Reversion notify—Notify the defect reversion to the inter-ring station when multiple links failure protection is used. • 12.1.8 Reversion notify operations • A Reversion notify frame allows one station near the reversion link can notify the interconnected node to change its forwarding status to avoid transient loop when multiple links failure protection is used. The Reversion notify frame is broadcast over the ring with a service class of subclassA0. • Reversion notify frames are received by all stations, processed by the inter-ring stations. 802-17

20. 1 controlType 1 controlVersion 1 Reserved controlDataUnit Reversion Notify Frame 12.3 OAM frame formats • Insert the following section, 12.3.6, after 12.3.5. • 12.3.6 Reversion notify frame • The recover notify frames are identified by the controlType field value of CT_OAM_REVERSION and a controlVersion value of 0. The recover notify frame is sent by the stations which are near the recovered link. Receiving the recover notify frame, the inter-ring station possibly changes its forwarding status according to its current status and configuration. 802-17

21. Reversion Notify Frame Header Field-value Restrictions 802-17