1. PWE3 Control Word Mandate: draft-delregno-pwe3-mandatory-control-word Nick DelRegno PWE3 WG IETF 79

2. Agenda Authors/Contributors Review of Control Word Applicability Mandatory Control Word Working Group Draft

3. Authors/Contributors Nick DelRegno, Ed., Verizon Tom Nadeau, Huawei Vishwas Manral, IPInfusion David Ward, Juniper

4. Drivers The road to interop is simplification. Control Word already REQUIRED for most encapsulations VCCV Control Channel Interoperability Issues – See draft-delregno-pwe3-VCCV-mandatory- features-02 Control Word Negotiation Issues (C=1 vs. C=0) – See draft-jin-pwe3-cbit-negotiation-01

5. Control Word Info Per Encap Type Encapsulation TypeControl WordRFC Reference Ethernet (Tagged Mode)Optional4448 Ethernet (Raw Mode)Optional4448 SAToPMandatory4553 PPP/HDLCOptional4618 Frame Relay (1:1 Mode)Mandatory4619 Frame Relay (Port Mode)Optional4619 ATM (N:1 Cell Mode)Optional4717 ATM (1:1 Cell Mode)Mandatory4717 ATM (AAL5 SDU Mode)Mandatory4717 ATM (AAL5 PDU Mode)Mandatory4717 CEPMandatory4842 CESoPSNMandatory5086 TDMoIPMandatory5087 Fiber Channel (Port Mode)Mandatorydraft-ietf-pwe3-fc-encap Application of Ethernet Pseudowires to MPLS Transport Networks Mandatory5994

6. Control Word Deployment Status Ethernet – Widely Supported – Not Widely Used ATM (N:1) Mode – Not Widely Supported – Not Widely Used Purported BW Penalties Reality: N >> 1

7. Control Word Mandate draft-delregno-pwe3-mandatory-control-word-00 Make Control Word MANDATORY for ALL Encaps Sequencing remains OPTIONAL Control Word Preferred (c=1) for Control Word Negotiation = MANDATORY – Section 6.1 of RFC 4447 Not Backwards Compatible with Implementations which don’t support CW – Going Forward Basis Only – Existing encapsulations should be updated to reflect CW Mandate when they go to PS. Future PWE3 solutions MUST support. – Support for legacy hardware via the LDP capability advertisement update in (draft-jin-pwe3-cbit-negotiation)

8. Next Steps Accept as Working Group draft Complete Implementation Survey Update Existing Encaps – New RFCs to Update/Supercede Legacy RFCs? – Legacy Implementations Adhere to Legacy RFCs CW Mandatory for ALL Encaps going forward – WG charter changed to include statement that all existing and new WG work must include CW. – All documents progressing to PS be adjusted to make CW mandatory (and/or point at this document).