Appendix A. Survey Responses
The detailed responses are included in this appendix. The respondent contact info has been removed.A.1. Respondent 1
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 423 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No Response
A.2. Respondent 2
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 SAToP - RFC 4553 CESoPSN - RFC 5086 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 5000 Ethernet Raw Mode - RFC 4448 - 1000 SAToP - RFC 4553 - 50 CESoPSN - RFC 5086 - 1600 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2), TTL Expiry (Type 3) Ethernet Raw Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2), TTL Expiry (Type 3) CESoPSN - RFC 5086: TTL Expiry (Type 3) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: ICMP Ping, LSP Ping Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping SAToP - RFC 4553: LSP Ping
CESoPSN - RFC 5086: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. I'm very interested in this work as we continue to experience interop challenges particularly with newer vendors to the space who are only implementing VCCV via control word. Vendors who have tailed their MPLS OAM set specifically to the cell backhaul space and mandatory CW have been known to fall into this space. That's all I've got.A.3. Respondent 3
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 Frame Relay (Port Mode) - RFC 4619 Frame Relay (1:1 Mode) - RFC 4619 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 800 Ethernet Raw Mode - RFC 4448 - 50 Frame Relay (Port Mode) - RFC 4619 - 2 Frame Relay (1:1 Mode) - RFC 4619 - 2
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. No Response 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. No Response 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.4. Respondent 4
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 1000 Ethernet Raw Mode - RFC 4448 - 200
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. No Response 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping Ethernet Raw Mode - RFC 4448: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. EQUIPMENT MANUFACTURER does not provide options to configure VCCV control-channel and its sub options for LDP based L2Circuits. How can we achieve end-to-end management and fault detection of PW without VCCV in such cases?A.5. Respondent 5
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 PPP - RFC 4618 Frame Relay (Port Mode) - RFC 4619 Frame Relay (1:1 Mode) - RFC 4619 Fiber Channel (Port Mode) - "Encapsulation Methods for Transport of Fibre Channel" (now RFC 6307)
3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 4000 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2) Ethernet Raw Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.6. Respondent 6
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448
3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 1000+ Ethernet Raw Mode - RFC 4448 - 500 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1) Ethernet Raw Mode - RFC 4448: Control Word (Type 1) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: ICMP Ping, LSP Ping Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No Response
A.7. Respondent 7
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Raw Mode - RFC 4448 ATM (1:1 Mode) - RFC 4717 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Raw Mode - RFC 4448 - 20 ATM (1:1 Mode) - RFC 4717 - 100 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. No Response 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Raw Mode - RFC 4448: LSP Ping ATM (1:1 Mode) - RFC 4717: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode), PPP, HDLC, Frame Relay (Port Mode), ATM (N:1 Cell Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share.
We are using L2PVPN AToM like-to-like models - ATMoMPLS - EoMPLS ATMoMPLS : This service offered for transporting ATM cells over IP/MPLS core with Edge ATM CE devices including BPX, Ericsson Media Gateway etc. This is purely a Port mode with cell-packing configuration on it to have best performance. QoS marking is done for getting LLQ treatment in the core for these MPLS encapsulated ATM packets. EoMPLS: This service offered for transporting 2G/3G traffic from network such as Node-B to RNC's over IP/MPLS backbone core network. QoS marking is done for getting guaranteed bandwidth treatment in the core for these MPLS encapsulated ATM packets. In addition to basic L2VPN service configuration, these traffic are routed via MPLS TE tunnels with dedicated path and bandwidth defined to avoid bandwidth related congestion.A.8. Respondent 8
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Raw Mode - RFC 4448 ATM (AAL5 SDU Mode) - RFC 4717 TDMoIP - RFC 5087 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Raw Mode - RFC 4448 - In-Use ATM (AAL5 SDU Mode) - RFC 4717 - In-Use TDMoIP - RFC 5087 - In-Use 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Raw Mode - RFC 4448: Control Word (Type 1) ATM (AAL5 SDU Mode) - RFC 4717: Router Alert Label (Type 2)
5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Raw Mode - RFC 4448: LSP Ping ATM (AAL5 SDU Mode) - RFC 4717: LSP Ping TDMoIP - RFC 5087: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Raw Mode), ATM (N:1 Cell Mode) Used in Network: Ethernet (Raw Mode), ATM (N:1 Cell Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. PW VCCV is very useful tool for finding faults in each PW channel. Without this we can not find fault on a PW channel. PW VCCV using BFD is another better option. Interoperability challenges are with Ethernet OAM mechanism.A.9. Respondent 9
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Frame Relay (1:1 Mode) - RFC 4619 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 19385 Frame Relay (1:1 Mode) - RFC 4619 - 15757
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Frame Relay (1:1 Mode) - RFC 4619: Control Word (Type 1) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Frame Relay (1:1 Mode) - RFC 4619: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode), PPP, HDLC, Frame Relay (Port Mode), ATM (N:1 Cell Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.10. Respondent 10
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Raw Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Raw Mode - RFC 4448 - 325 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Raw Mode - RFC 4448: Control Word (Type 1)
5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: No Response Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.11. Respondent 11
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 PPP - RFC 4618 HDLC - RFC 4618 Frame Relay (1:1 Mode) - RFC 4619 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 2000 Ethernet Raw Mode - RFC 4448 - 100 PPP - RFC 4618 - 500 Frame Relay (1:1 Mode) - RFC 4619 - 200
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. No Response 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: ICMP Ping, LSP Ping Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping Frame Relay (1:1 Mode) - RFC 4619: ICMP Ping, LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode), PPP, HDLC Used in Network: Ethernet (Tagged Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.12. Respondent 12
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Raw Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Raw Mode - RFC 4448 - 50000
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Raw Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2), TTL Expiry (Type 3) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. No Response 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.13. Respondent 13
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 Frame Relay (1:1 Mode) - RFC 4619 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 3 Ethernet Raw Mode - RFC 4448 - 10-20
ATM (1:1 Mode) - RFC 4717 - 3 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1), TTL Expiry (Type 3) Ethernet Raw Mode - RFC 4448: Control Word (Type 1), TTL Expiry (Type 3) Frame Relay (1:1 Mode) - RFC 4619: Control Word (Type 1), TTL Expiry (Type 3) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: ICMP Ping, LSP Ping Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping Frame Relay (1:1 Mode) - RFC 4619: ICMP Ping, LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode), PPP, HDLC, Frame Relay (Port Mode), ATM (N:1 Cell Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode), Frame Relay (Port Mode) 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No Response
A.14. Respondent 14
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 150 Ethernet Raw Mode - RFC 4448 - 100 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2) Ethernet Raw Mode - RFC 4448: Control Word (Type 1), Router Alert Label (Type 2) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping Ethernet Raw Mode - RFC 4448: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode), PPP, HDLC, Frame Relay (Port Mode) Used in Network: Ethernet (Tagged Mode), Ethernet (Raw Mode)
7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. No ResponseA.15. Respondent 15
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 Frame Relay (1:1 Mode) - RFC 4619 ATM (1:1 Mode) - RFC 4717 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 20,000 Ethernet Raw Mode - RFC 4448 - 1000 Frame Relay (1:1 Mode) - RFC 4619 - 30,000 ATM (1:1 Mode) - RFC 4717 - 20,000 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: TTL Expiry (Type 3) Ethernet Raw Mode - RFC 4448: TTL Expiry (Type 3) Frame Relay (1:1 Mode) - RFC 4619: TTL Expiry (Type 3) ATM (1:1 Mode) - RFC 4717: TTL Expiry (Type 3)
5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping Ethernet Raw Mode - RFC 4448: LSP Ping Frame Relay (1:1 Mode) - RFC 4619: LSP Ping ATM (1:1 Mode) - RFC 4717: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: No Response Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. COMPANY has deployed several MPLS network elements, from multiple vendors. COMPANY is seeking a uniform implementation of VCCV Control Channel (CC) capabilities across its various vendor platforms. This will provide COMPANY with significant advantages in reduced operational overheads when handling cross-domain faults. Having a uniform VCCV feature implementation in COMPANY multi-vendor network leads to: o Reduced operational cost and complexity o Reduced OSS development to coordinate incompatible VCCV implementations. o Increased end-end service availability when handing faults. In addition, currently some of COMPANY deployed VCCV traffic flows (on some vendor platforms) are not guaranteed to follow those of the customer's application traffic (a key operational requirement). As a result, the response from the circuit ping cannot faithfully reflect the status of the circuit. This leads to ambiguity regarding the operational status of our networks. An in-band method is highly preferred, with COMPANY having a clear preference for VCCV Circuit Ping using PWE Control Word. This preference is being pursued with each of COMPANY vendors.
A.16. Respondent 16
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 Ethernet Raw Mode - RFC 4448 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - 100 Ethernet Raw Mode - RFC 4448 - 100 4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. No Response 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: ICMP Ping, LSP Ping Ethernet Raw Mode - RFC 4448: ICMP Ping, LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: Ethernet (Tagged Mode), Ethernet (Raw Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share.
Using CV is not required at the momentA.17. Respondent 17
2. In your network in general, across all products, please indicate which pseudowire encapsulations your company has implemented. Ethernet Tagged Mode - RFC 4448 SAToP - RFC 4553 Frame Relay (Port Mode) - RFC 4619 Frame Relay (1:1 Mode) - RFC 4619 ATM (N:1 Mode) - RFC 4717 ATM (1:1 Mode) - RFC 4717 CESoPSN - RFC 5086 TDMoIP - RFC 5087 3. Approximately how many pseudowires are deployed of each encapsulation type. Note, this should be the number of pseudowires in service, carrying traffic, or pre-positioned to do so. ***Note, please indicate "In-Use" for any PW Encap Types which you are using but cannot provide a number. Ethernet Tagged Mode - RFC 4448 - >40k Ethernet Raw Mode - RFC 4448 - In-Use SAToP - RFC 4553 - >20k Frame Relay (Port Mode) - RFC 4619 - >5k Frame Relay (1:1 Mode) - RFC 4619 - >5k ATM (N:1 Mode) - RFC 4717 - >50k ATM (1:1 Mode) - RFC 4717 - >50k CESoPSN - RFC 5086 - >20k TDMoIP - RFC 5087 - >20k
4. Please indicate which VCCV Control Channel is used for each encapsulation type. Understanding that users may have different networks with varying implementations, for your network in general, please select all which apply. Ethernet Tagged Mode - RFC 4448: Control Word (Type 1) SAToP - RFC 4553: Control Word (Type 1) Frame Relay (Port Mode) - RFC 4619: Control Word (Type 1) Frame Relay (1:1 Mode) - RFC 4619: Control Word (Type 1) ATM (N:1 Mode) - RFC 4717: Control Word (Type 1) ATM (1:1 Mode) - RFC 4717: Control Word (Type 1) 5. Please indicate which VCCV Connectivity Verification types are used in your networks for each encapsulation type. Ethernet Tagged Mode - RFC 4448: LSP Ping SAToP - RFC 4553: LSP Ping Frame Relay (Port Mode) - RFC 4619: LSP Ping Frame Relay (1:1 Mode) - RFC 4619: LSP Ping ATM (N:1 Mode) - RFC 4717: LSP Ping ATM (1:1 Mode) - RFC 4717: LSP Ping 6. Please indicate your network's support of and use of the Control Word for encapsulations for which the Control Word is optional. Supported by Network/Equipment: ATM (N:1 Cell Mode) Used in Network: No Response 7. Please use this space to provide any feedback regarding PW and VCCV deployments, VCCV interoperability challenges, this survey or any network/vendor details you wish to share. BFD VCCV Control Channel is not indicated in the survey (may be required for PW redundancy purpose)
Authors' Addresses
Christopher N. "Nick" Del Regno (editor) Verizon Communications, Inc. 400 International Pkwy Richardson, TX 75081 US EMail: nick.delregno@verizon.com Andrew G. Malis (editor) Consultant EMail: agmalis@gmail.com