30 likes | 156 Views
LDP Implementation Survey Results. 12 Responses 10 Public, 2 Anonymous. 10 Product; 2 Beta 11 On sale; 1 Other Implementation Approach 7 From spec; 4 Purchased/free code + additions; 1 Purchased code. Highlights Every item in survey questionnaire implemented by at least 2 respondents.
E N D
LDP Implementation Survey Results 12 Responses • 10 Public, 2 Anonymous. • 10 Product; 2 Beta • 11 On sale; 1 Other • Implementation Approach 7 From spec; 4 Purchased/free code + additions; 1 Purchased code. Highlights • Every item in survey questionnaire implemented by at least 2 respondents. • Each of the 8 Label Distribution Modes implemented and tested; 8t 2y 2n DU, Ord Cntl, Lib Reten 6t 1y 5n DU, Ord Cntl, Con Reten 7t 1y 4n DU Ind Cntl, Lib Reten 6t 0y 6n DU, Ind Cntl, Con Reten 7t 1y 4n DoD Ord Cntl, Cons Reten 4t 3y 5n DoD, Ord Cntl, Lib Reten 6t 1y 5n DoD, Ind Cntl, Cons Reten 4t 2y 6n DoD, Ind, Cntl, Lib Reten • Platform and Interface Label Spaces both widely supported. 12t 0y 0n Per Platform 7t 1y 4n Per Interface • Basic and Targeted Sessions both widely supported. 12t 0y 0n Basic/Directly Connected 11t 1y 0n Targeted • TCP MD5 Option not widely implemented. 3t 1y 8n
LDP Implementation Survey Results • Interface Types 12t 0y 0n Packet 6t 2y 4n ATM 2t 3y 7n Frame Relay • LDP Messages 12t 0y 0n Address, Address Withdraw, Hello, Initialization, Keep Alive, Label Mapping, Label Withdraw, Notification 11t 0y 1n Label Release 9t 2y 1n Label Abort Request 9t 0y 3n Label Request 2t 5y 5n Vendor Private 1t 5y 6n Experimental • LDP TLVs 12t 0y 0n Address List, Common Hello Parameters, Common Session Parameters, Generic Label, Status, IPv4 Transport Address 10t … Label Request Message ID, Hop Count 9t … Path Vector, Extended Status 7t 3y 2n Configuration Sequence Number 6t … ATM Session Parameters, ATM Label, Returned Message, Returned PDU 2t 3y 7n FR Session Parameters, FR Label 2t 5y 5n Vendor Private 1t 5y 6n Experimental 1t 1y 10n IPv6 Transport Address
Additional Information • Legend t Tested against another independent implementation y Implemented by not tested against another independent implementation n Not implemented. Survey also included reasons for not implementing including: Item not required for feature set implemented Utility of feature unclear RFC specification unclear, confusing or inadequate. • 10 Public Respondents. Agilent Technologies Trillium / Intel Celox Networks, Inc. Redback Networks Cisco Systems, Inc. Riverstone Networks Data Connection Ltd Vicace Networks, Inc. Netplane Systems, Inc. Wipro Technologies 2 Anonymous Respondents