Network Working Group Lou Berger (Movaz) - Editor Internet Draft Yakov Rekhter (Juniper) - Editor Expiration Date: September 2002 March 2002 Generalized MPLS Signaling - Implementation Survey draft-ietf-ccamp-gmpls-signaling-survey-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To view the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in an Internet-Drafts Shadow Directory, see http://www.ietf.org/shadow.html. Abstract This document provides a survey of GMPLS signaling implementations. The primary focus of this survey are the signaling protocol mechanisms specified in [GMPLS-SIG], [GMPLS-RSVP], [GMPLS-LDP] and [GMPLS-SONET]. Other specifications and documents are listed if included in the submitted form. The survey form and latest version of this document are available from http://www.labn.net/gmpls-survey. Berger, Rekhter - Editors [Page 1] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Contents 1 Survey Summary .............................................. 3 2 Survey Forms ................................................ 7 2.1 Agilent Technologies ........................................ 7 2.2 Calient Networks ............................................ 10 2.3 Data Connection Ltd ......................................... 15 2.4 Firstwave Intelligent Optical Networks ...................... 20 2.5 HCL Technologies Ltd., India ................................ 24 2.6 Intel Corporation ........................................... 27 2.7 Japan Telecom Co., Ltd. ..................................... 30 2.8 Juniper Networks ............................................ 34 2.9 Lumentis AB ................................................. 37 2.10 Marconi ..................................................... 40 2.11 Movaz Networks .............................................. 43 2.12 Nortel Networks ............................................. 46 2.13 Tellium, Inc. ............................................... 49 2.14 Tropic Networks Inc ......................................... 52 2.15 Anonymous 1 ................................................. 54 2.16 Anonymous 2 ................................................. 58 2.17 Anonymous 3 ................................................. 60 3 Acknowledgments ............................................. 62 4 Security Considerations ..................................... 62 5 IANA Considerations ......................................... 62 6 References .................................................. 62 7 Editors' Addresses .......................................... 63 Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 1. Survey Summary This document is a compilation of responses to the GMPLS Signaling implementation form found at http://www.labn.net/gmpls-survey/sig- survey.txt. After a brief summary, each response in it's entirety is listed. (The editors, make no claim as to the accuracy of the information provided nor do they endorse the statements made within each response.) Anonymous submissions were handled by Scott Bradner, sob@harvard.edu. All identifying information was removed prior to these submissions being forwarded to the editors. Generalized MPLS signaling is specified in the documents [GMPLS-SIG], [GMPLS-RSVP], [GMPLS-LDP] and [GMPLS-SONET]. Table 1 summarizes the results of the GMPLS signaling aspects of survey. Many included implementation details for other specifications or drafts. These details are included in the full response section, but not in the summary table. Table 2 provides total results by feature/question. The categories covered in summary Table 1 are: o Type Indicates type of implementation. Indicated types include: tester, (network) equipment, (portable or internal use) code. If the type was not evident, "unknown" is used. o Drafts Indicates supported drafts. [GMPLS-SIG] is assumed. "R" is used to indicate [GMPLS-RSVP], "L" indicates [GMPLS-LDP] and "S" indicates [GMPLS-SONET]. o Software (S/w) Genealogy Indicates the source of the implementation. Two sub-categories are listed. The "external" category indicates the original source of the code, or "yes" if not indicated. The "internal" indicates the part of the code developed by the respondent. o Switch Capabilities Indicates the type of switching supported. "P" indicates PSC, "T" indicates TDM, "L" indicates LSC and "F" indicates FSC. o Label Types Indicates the supported label types. "M" indicates MPLS labels, "G" indicates the generalized label, "W" indicates waveband labels and "S" indicates SONET/SDH label. Berger, Rekhter - Editors [Page 3] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 o Feature Summary Summarizes supported features, by sub-category broken out in the survey form. Sub-categories are indicated in the table header. The "L" sub-category is used for form section 11, "Label Related". "B" is used for form section 13, "Bidirectional LSPs". "N" is used for form section 14, "Notification". "O" is used for form section 15, "Other features". In the table, an "F" indicates that all sub-category features list in the form are supported. A "P" indicates partial support, i.e., some boxes were not checked. Berger, Rekhter - Editors [Page 4] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 +===================================================================+ |Ref. | Type |Draft| S/w Genealogy |Switch |Label |Feature| |Section | | |External:Internal|Caps. |Types |L:B:N:O| +===================================================================+ | 2.1 |Tester |R S| :All |P T L F|M G W S|F:F:F:F| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.2 |Equip. |R |Yes :TE | L F| G |P:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.3 |Code |R S|Yes :GMPLS |P T L F|M G W S|F:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.4 |Code |R L | :All | L F| G W |F:F:F:F| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.5 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.6 |Equip. |R S| :All |P T |M G S|P:F:F:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.7 |Code |R S| :All | n/a | G |P:F: :P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.8 |Equip. |R S| :All |P |M G S|P:F: :P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.9 |Equip. |R |Yes :GMPLS | L | G | :F: : | +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.10 |Equip. |R S| :All | T L F| G W S|P:F:F:F| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.11 |Equip. |R S|LabN :GMPLS | L | G S|F:F:F:F| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.12 |Code | L | n/a | n/a |M G W S|F:F:F: | +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.13 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.14 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.15 |Unknown|R S|Yes :n/a | T L F| G W S|P:F:F:F| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.16 |Unknown|R |Yes :n/a | L | G |P:F:P:P| +-----------+-------+-----+-----------------+-------+-------+-------+ | 2.17 |Code |R n/a| :All |P T L F|M G S |F:F:F:P| +===================================================================+ "n/a" indicates that no answer was provided. Table 1: Survey Results Summary Berger, Rekhter - Editors [Page 5] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 +==================================================================+ | Total | Total | | |GMPLS-RSVP|GMPLS-LDP|Section, Description | +==================================================================+ | 17 |Total participants | 16 | - |6. Reference Draft - [GMPLS-RSVP] | | - | 2 |6. Reference Draft - [GMPLS-LDP] | | 10 |6. Reference Draft - [GMPLS-SONET] | | 6 | |5.1 Switching capabilities - PSC | | 8 | |5.2 Switching capabilities - TDM | | 12 | 1 |5.3 Switching capabilities - LSC | | 9 | 1 |5.4 Switching capabilities - FSC | | 1 | |9.1 Implementation based on - Purchased code| | 1 | |9.2 Implementation based on - Free code | | 9 | 1 |9.3 Implementation based on - Internal | | 9 | |9.4 Implementation based on - Combination | | 7 | 1 |10.1 MPLS Label | | 16 | 2 |10.2 Generalized Label | | 7 | 2 |10.3 Waveband Label | | 11 | 1 |10.4 SONET/SDH Label | | 13 | 2 |11.1 Suggested Label | | 10 | 2 |11.2 Label Set | | 8 | - |12.1 Traffic Parameters - Intserv | | - | 4 |12.2 Traffic Parameters - CR-LDP | | 16 | 2 |12.3 GMPLS Bandwidth Encoding | | 11 | 1 |12.4 Traffic Parameters - SONET/SDH | | 16 | 2 |13. Bidirectional LSPs | | 9 | 2 |14.1 Acceptable Label Set | | 10 | - |14.2 Notify Request Objects | | 11 | - |14.3 Notify Message | | 12 | - |14.4 Removing State with a PathErr message | | 11 | 1 |15.1 Explicit Label Control | | 12 | 1 |15.2 Protection Information | | 11 | 1 |15.3 Administrative Status Information | | 12 | 1 |15.4 Interface Identification | | 11 | 1 |15.5 Errored Interface Identification | | 12 | 1 |15.6 Link Fault Handling | | 11 | 1 |15.7 Nodal Fault Handling | +==================================================================+ "-" indicates that items is not relevant to protocol. Table 2: Survey Totals Berger, Rekhter - Editors [Page 6] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2. Survey Forms 2.1. Agilent Technologies GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Agilent Technologies 1.1 Organization url(s): www.agilent.com/comms/RouterTester 2. Product title(s): Agilent RouterTester System. GMPLS RSVP Conformance Test Suite - E5172A GMPLS, MPLS & OIF UNI RSVP Protocol Software - E5173A 2.1 Brief description(s): The Agilent RouterTester platform has 2 software modules for testing GMPLS: E5172A- Automated protocol conformance test suite that tests GMPLS extensions to RSVP and LMP. Operates over in-band or out of band signaling interfaces. http://advanced.comms.agilent.com/RouterTester/datasheets/e5172a.htm E5173A - Provides realistic Internet-scale GMPLS, MPLS, OIF UNI and LMP protocol emulation. This software operates with routing protocol software and traffic generation tools to provide comprehensive multiprotocol verification and stressing of GMPLS-capable devices and networks. Operates over in-band or out of band signaling interfaces. http://advanced.comms.agilent.com/RouterTester/datasheets/e5173a.htm ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Sashi Vyravipillai 3.2 Title: Product Marketing Engineer 3.3 E-mail: sashi_vyravipillai@agilent.com 3.4 Organization/department: Agilent Technologies, Advanced Networks Division 3.5 Postal address: Berger, Rekhter - Editors [Page 7] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Locked Bag 810 Blackburn Vic. 3130 Australia 3.6 Phone: +61-3-9210-5646 3.7 Fax: +61-3-9210-5550 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [X] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [X] PSC 5.2 [X] TDM 5.3 [X] LSC 5.4 [X] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [X] draft-ietf-mpls-generalized-signaling-07 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-06 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-03 6.4 [X] draft-ietf-mpls-rsvp-unnum-04 6.5 [X] draft-ietf-mpls-bundle-01 6.6 [X] draft-ietf-ccamp-lmp-03 6.7 [X] RFC2961 Refresh Reduction 6.8 [X] draft-ietf-ccamp-ospf-gmpls-extensions-04 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [X] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free Berger, Rekhter - Editors [Page 8] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 8.3 [X] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [X] MPLS Label (when using MPLS software) 10.2 [X] Generalized Label 10.3 [X] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [X] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [X] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: [X] Link Management Protocol Berger, Rekhter - Editors [Page 9] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 17. Other features supported: [X] In band control channel on OC48 and OC192 DCC interfaces [X] Out of band control channel on Ethernet/GigE 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: [X] GRE Tunneling Support for control plane transport [X] Unnumbered interface support [X] Bundled interface support ============================================================== Person filling out this form: Name: Cary Wright E-mail: cary_wright@agilent.com Tel.: +61-3-9210-5843 Title: R&D Project Manager Company: Agilent Technologies Date prepared: 8 March 2002 2.2. Calient Networks GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Calient Networks 1.1 Organization url(s): http://www.calient.net 2. Product title(s): DiamondWave Photonic Switch 2.1 Brief description(s): MEMS-based photonic switch, leveraging GMPLS to provide dynamic provisioning and mesh-based protection/restoration. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: james scott Berger, Rekhter - Editors [Page 10] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 3.2 Title: s/w arch 3.3 E-mail: jscott@calient.net 3.4 Organization/department: san jose/engineering 3.5 Postal address: 5853 rue ferrari san jose, CA 95138 3.6 Phone: 408.972.3709 3.7 Fax: 408.972.3800 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [X] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [X] LSC 5.4 [X] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [X] draft-ietf-ccamp-lmp-03.txt 6.2 [X] RFC 2784 : GRE Tunneling 6.3 [X] RFC 2205 : RSVP 6.4 [X] RFC 3209 : RSVP-TE 6.5 [X] draft-ietf-mpls-generalized-rsvp-te-05.txt 6.6 [X] RFC 2961 : RSVP Refresh Reduction 6.7 [X] draft-ietf-mpls-rsvp-unnum-03.txt 6.8 [X] RFC 2328 : OSPFv2 6.9 [X] RFC 2370 : OSPF Opaque LSA 6.10 [X] draft-katz-yeung-ospf-traffic-06.txt 6.11 [X] draft-ietf-ccamp-ospf-gmpls-extensions-00.txt 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [X] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) Berger, Rekhter - Editors [Page 11] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [X] Other (describe): device is transparent. all defined LSP encoding types are supported. 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [X] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [X] Internal implementation on top of purchased or free code 9.4.1 [X] List portions from external source OSPFv2 RSVP 9.4.2 [X] List portions developed internally OSPF-TE distributed RSVP-TE LMP 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [X] Generalized Label 10.3 [ ] Waveband Label 10.4 [ ] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Please list which) PATH Session IF_ID RSVP Hop Time Values Sender Template Sender Tspec Message_ID/Message_ID_ACK/Message_ID_NACK ERO RRO Generalized Label Request (LSC/FSC only) Suggested Label Berger, Rekhter - Editors [Page 12] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Upstream Label Recovery Label Protection Notify Req AdminStatus PATHErr Session Sender Template Sender Tspec Message_ID/Message_ID_ACK/Message_ID_NACK ErrorSpec RRO RESV Session Time Values Message_ID/Message_ID_ACK/Message_ID_NACK IF_ID RSVP Hop Resv Confirm Notify Request AdminStatus Style (FF or SE) Flowspec Filterspec RSVP Label RRO Generalized Label RESVErr Session IF_ID RSVP Hop Message_ID/Message_ID_ACK/Message_ID_NACK ErrorSpec Style (FF and SE) NOTIFY Session Sender Template Message_ID/Message_ID_ACK/Message_ID_NACK AdminStatus ErrorSpec HELLO Hello Restart Capabilities Summary Refresh Berger, Rekhter - Editors [Page 13] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Session Message_ID/Message_ID_ACK/Message_ID_NACK Message ID List 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [ ] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [ ] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: Resilient GMPLS control channels LSP hierarchy (static) 18. Currently-defined GMPLS signaling features not supported: Label Set Waveband Switching SONET/SDH extensions 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ==================================================================== Berger, Rekhter - Editors [Page 14] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Person filling out this form: Name: james scott E-mail: jscott@calient.net Tel.: 408.972.3709 Title: s/w arch Company: calient Date prepared: 02.03.11 2.3. Data Connection Ltd GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Data Connection Ltd 1.1 Organization url(s): www.dataconnection.com 2. Product title(s): DC-MPLS 2.1 Brief description(s): MPLS and GMPLS signaling software product, including RSVP, LDP, CR-LDP and OIF UNI support. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Toby Eccles 3.2 Title: MPLS Product Manager 3.3 E-mail: thme@dataconnection.com 3.4 Organization/department: Network Convergence Group 3.5 Postal address: Data Connection Ltd 100 Church Street Enfield Middlesex EN2 6BQ Berger, Rekhter - Editors [Page 15] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 UK 3.6 Phone: +44 20 8366 1177 3.7 Fax: +44 20 8363 1468 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [X] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [X] PSC 5.2 [X] TDM 5.3 [X] LSC 5.4 [X] FSC DC-MPLS software can control all of these switching types. 6. Reference Drafts (please list, include version numbers) Draft support is constantly being updated to the latest versions. RFC 2205 Resource ReSerVation Protocol (RSVP) RFC 2207 RSVP Extensions for IPSEC Data Flows RFC 2208 Resource ReSerVation Protocol (RSVP) Version 1 Applicability Statement RFC 2209 Resource ReSerVation Protocol (RSVP) Version 1 Message Processing Rules RFC 2210 The Use of RSVP with IETF Integrated Services RFC 2547 BGP/MPLS VPNs RFC 2702 Requirements for Traffic Engineering Over MPLS RFC 2745 RSVP Diagnostic Messages RFC 2764 Framework for IP-based Virtual Private Networks RFC 2961 RSVP Refresh Overhead Reduction Extensions RFC 3031 Multiprotocol Label Switching Architecture RFC 3032 MPLS Label Stack Encoding RFC 3034 Use of Label Switching on Frame Relay Networks Specification RFC 3035 MPLS using LDP and ATM VC Switching RFC 3036 LDP specification RFC 3037 LDP Applicability RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels RFC 3210 Applicability statement for the extensions to RSVP for LSP Tunnels Berger, Rekhter - Editors [Page 16] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 RFC 3212 Constraint-Based LSP Setup using LDP RFC 3213 Applicability Statement for CR-LDP draft-ietf-mpls-ldp-mib Definitions of Managed Objects for the Multiprotocol Label Switching Label Distribution Protocol (LDP) draft-ietf-mpls-lsr-mib MPLS Label Switch Router Management Information Base Using SMIv2 draft-ietf-mpls-te-mib MPLS Traffic Engineering Management Information Base Using SMIv2 draft-ietf-mpls-generalized-signaling Generalized MPLS - Signaling Functional Description draft-ietf-mpls-generalized-rsvp-te Generalized MPLS Signaling - RSVP-TE Extensions draft-ietf-mpls-diff-ext MPLS Support of Differentiated Services draft-ietf-mpls-lsp-hierarchy LSP Hierarchy with MPLS TE draft-ietf-mpls-rsvp-unnum Signaling Unnumbered Links in RSVP-TE draft-ietf-mpls-bundle Link Bundling in MPLS Traffic Engineering draft-ietf-mpls-bundle-mib Link Bundling Management Information Base Using SMIv2 draft-ietf-mpls-tc-mib Definition of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management draft-ietf-mpls-mgmt-overview Multiprotocol Label Switching (MPLS) Management Overview draft-ietf-mpls-rsvp-lsp-fastreroute-00.txt Fast Reroute Extensions to RSVP-TE for LSP Tunnels draft-ietf-ccamp-gmpls- sonet-sdh GMPLS Extensions for SONET and SDH Control draft-ietf-ccamp-gmpls- architecture Generalized Multi-Protocol Label Switching (GMPLS) Architecture draft-ietf-ccamp-gmpls- sonet-sdh-extensions GMPLS Extensions to Control Non-Standard SONET and SDH Features draft-iwata-mpls-crankback Crankback Routing Extensions for MPLS Signaling draft-martini-l2circuit-trans- mpls Transport of Layer 2 Frames Over MPLS draft-martini-l2circuit-encap-mpls Encapsulation Methods for Transport of Layer 2 Frames Over IP draft-azad-mpls-oam-messaging MPLS user-plane OAM messaging 7. Interface technologies 7.1 [X] Frame Relay 7.2 [X] ATM 7.3 [X] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [X] FiberChannel Berger, Rekhter - Editors [Page 17] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7.10 [ ] Other (describe): DC-MPLS software can handle all these interface types. 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [X] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X] Internal implementation (no outside code, just from specs) 9.4 [X] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally External code was used as a basis for the very initial development of the RSVP protocol piece for packet MPLS. All other components have been developed internally. Since then, all externally-derived code has been either rewritten or substantially revised and enhanced - it is now unrecognisable; also, large new components (including all the GMPLS protocol handling) have been developed purely from the specifications. 10. Supported Label Types 10.1 [X] MPLS Label 10.2 [X] Generalized Label 10.3 [X] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [X] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Controlled load and Guaranteed service) 12.2 [X] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) Berger, Rekhter - Editors [Page 18] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: OIF2000.125 User Network Interface (UNI) 1.0 Signaling Specification 17. Other features supported: Control plane restart (as in both the pan-restart and generalized-rsvp-te signalling drafts) Fault tolerance (hot backup and persistent store) Software distribution across distributed processing architectures Protection switching Bundled links Non-associated (out of band) signaling Graceful deletion LSP hierarchy Reverse LSPs Diffserv Resource affinities 18. Currently-defined GMPLS signaling features not supported: Errored Interface Identification Acceptable Label Set 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) DC-MPLS is a source code implementation of the MPLS, GMPLS, and OIF UNI protocols that has been architected, designed, coded and tested for the most demanding environments: high performance, unlimited scalability, resilience and fault tolerance have been designed in from the outset. It is in use with a large number of OEMs building a wide variety of types of switch, many of which are using GMPLS. DCL also supplies implementations of LMP and IP routing protocols for implementation of a complete control plane. 20. If you feel the above categories are not complete, add others which will better describe your project: ======================================================================= Berger, Rekhter - Editors [Page 19] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Person filling out this form: Name: Tim Hall E-mail: timhall@dataconnection.com Tel.: +44 20 8366 1177 Title: DC-MPLS Development Manager Company: Data Connection Ltd. Date prepared: 13th March 2002 2.4. Firstwave Intelligent Optical Networks GMPLS Signaling Implementation Survey Form [V 1.1] 1. Organization: FirstWave Intelligent Optical Networks 1.1 Organization url(s): http://www.fwion.com 2. Product title(s): 2.1 Brief description(s): ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Michael Mandelberg 3.2 Title: Sr. MTS 3.3 E-mail: mmandelberg@fwion.com 3.4 Organization/department: Control Plane Embedded Software Group 3.5 Postal address: 6301 Ivy Lane, Suite 700, Greenbelt, MD 20770 3.6 Phone: (301) 345-2137 x1008 Berger, Rekhter - Editors [Page 20] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 3.7 Fax: (301) 345-3612 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [x] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities [GMPLS- [GMPLS- RSVP] LDP] 5.1 [ ] [ ] PSC 5.2 [ ] [ ] TDM 5.3 [x] [x] LSC 5.4 [x] [x] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [x] [GMPLS-SIG] 6.2 [x] [GMPLS-RSVP] 6.3 [x] [GMPLS-LDP] 6.4 [ ] [GMPLS-SONET] 6.5 [x] draft-ietf-ccamp-lmp-03.txt 6.6 [x] draft-ietf-ccamp-gmpls-architecture-02.txt 6.7 [x] draft-ietf-ccamp-ospf-gmpls-extensions-04.txt 6.8 [x] draft-nadeau-ccamp-gmpls-label-mib-01.txt 6.9 [x] draft-nadeau-ccamp-gmpls-tc-mib-01.txt 6.10 [x] draft-nadeau-ccamp-gmpls-lsr-mib-01.txt 6.11 [x] draft-nadeau-ccamp-gmpls-te-mib-01.txt 6.12 [x] draft-ietf-mpls-lsp-hierarchy-04.txt 6.13 [x] draft-ietf-mpls-bundle-01.txt 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [x] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [x] Other (describe): All optical and transparent to transport technology 8. Availability [GMPLS- [GMPLS- Berger, Rekhter - Editors [Page 21] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 RSVP] LDP] 8.1 [ ] [ ] Public and free 8.2 [ ] [ ] Only to selected organizations/companies but free 8.3 [ ] [ ] On sale. 8.4 [x] [x] For internal company use only 8.5 [ ] [ ] Other: 9. Implementation based on: (check all that apply) [GMPLS- [GMPLS- RSVP] LDP] 9.1 [ ] [ ] Purchased code (please list source if possible) 9.2 [ ] [ ] Free code (please list source if possible) 9.3 [x] [x] Internal implementation (no outside code, just from specs) 9.4 [ ] [ ] Internal implementation on top of purchased or free code 9.4.1 List portions from external source: (Identify protocol if appropriate) 9.4.2 List portions developed internally: (Identify protocol if appropriate) 10. Supported Label Types [GMPLS- [GMPLS- RSVP] LDP] 10.1 [ ] [ ] MPLS Label 10.2 [x] [x] Generalized Label 10.3 [x] [x] Waveband Label 10.4 [ ] [ ] SONET/SDH Label 11. Label Related [GMPLS- [GMPLS- RSVP] LDP] 11.1 [x] [x] Suggested Label 11.2 [x] [x] Label Set 12. Traffic Parameters [GMPLS- [GMPLS- RSVP] LDP] 12.1 [ ] [ ] Intserv (Please list which) 12.2 [x] [x] CR-LDP 12.3 [x] [x] GMPLS Bandwidth Encoding 12.4 [ ] [ ] SONET/SDH 13. Bidirectional LSPs [GMPLS- [GMPLS- RSVP] LDP] Berger, Rekhter - Editors [Page 22] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 [x] [x] Bidirectional LSPs 14. Notification [GMPLS- [GMPLS- RSVP] LDP] 14.1 [x] [x] Acceptable Label Set 14.2 [x] Notify Request Objects (GMPLS-RSVP) 14.3 [x] Notify Message (GMPLS-RSVP) 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features [GMPLS- [GMPLS- RSVP] LDP] 15.1 [x] [x] Explicit Label Control 15.2 [x] [x] Protection Information 15.3 [x] [x] Administrative Status Information 15.4 [x] [x] Interface Identification 15.5 [x] [x] Errored Interface Identification 15.6 [x] [x] Link Fault Handling 15.7 [x] [x] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 17.1 related to [GMPLS-RSVP] 17.2 related to [GMPLS-LDP] 17.3 Other 18. Currently-defined GMPLS signaling features not supported: 18.1 related to [GMPLS-RSVP] 18.2 related to [GMPLS-LDP] 18.3 related to [GMPLS-SONET] 18.4 Other 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ==================================================================== Person filling out this form: Name: Michael Mandelberg E-mail: mmandelberg@fwion.com Tel.: (301) 345-2137 x1008 Title: Sr. MTS Berger, Rekhter - Editors [Page 23] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Company: FirstWave Intelligent Optical Networks Date prepared: 3-15-02 2.5. HCL Technologies Ltd., India GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: HCL TECHNOLOGIES LTD., INDIA 1.1 Organization url(s): www.hcltechnologies.com (Corporate Website) 2. Product title(s): HCL LMP , HCL RSVP-TE 2.1 Brief description(s): * HCL LMP:- ++++++++++++ The design and implementation of the product is as per the working draft mentioned for Link Management Protocol. This product includes all the features irrespective of optional and mandatory procedures. Specific API implementation is also being done in order to match different possible environments in which it can be used. * HCL RSVP-TE:- ++++++++++++++++ This product is being developed internally for Signalling and LSP establishment in GMPLS Environment. The design and implementation is done on top of existing base RSVP (RFC 2205 ) implementation, by adding provisions so that it can be used for Signalling & LSP establishment in GMPLS scenario. This product can work standalone as GMPLS RSVP TE stack as well as in regular IP Resource Reservation environment & in MPLS Label Distribution and LSP establishment environment. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: S. Shankar 3.2 Title: Project Manager Berger, Rekhter - Editors [Page 24] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 3.3 E-mail: shanky@npd.hcltech.com 3.4 Organization/department: HCL Technologies Limited, Networking Products Division 3.5 Postal address: 49-50 Nelson Manickam Road, Chennai - 600029, India 3.6 Phone: +91-44-3741939 3.7 Fax: +91-44-3741038 ---------------------------------------------------------------- 4. Status: 4.1 [*] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [*] TDM 5.3 [ ] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [*] draft-ietf-ccamp-lmp-02.txt 6.2 [*] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 6.3 [*] draft-ietf-ccamp-gmpls-architecture-02.txt 6.4 [*] draft-ietf-mpls-generalized-rsvp-te-06.txt 6.5 [*] draft-ietf-mpls-rsvp-unnum-04.txt 6.6 [*] draft-ietf-mpls-bundle-01.txt 6.7 [*] rfc3209.txt 6.9 [*] rfc2205.txt 7.0 [*] rfc2961.txt 7.1 [*] draft-ietf-mpls-generalized-signaling-07 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [*] SDH 7.6 [*] SONET 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel Berger, Rekhter - Editors [Page 25] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [ ] For internal company use only 8.5 [*] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [*] Internal implementation on top of purchased or free code 9.4.1 [*] List portions from external source RSVP base code implemented by ISI. Conformance to RFC 2205 9.4.2 [*] List portions developed internally GMPLS RSVP TE Extensions ( As per Drafts ) LMP 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [*] Generalized Label 10.3 [ ] Waveband Label 10.4 [*] SONET/SDH Label 11. Label Related 11.1 [ ] Suggested Label 11.2 [*] Label Set 12. Traffic Parameters 12.1 [*] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [*] GMPLS Bandwidth Encoding 12.4 [*] SONET/SDH 13. [*] Bidirectional LSPs 14. Notification 14.1 [*] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [*] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [*] Explicit Label Control 15.2 [ ] Protection Information Berger, Rekhter - Editors [Page 26] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 15.3 [*] Administrative Status Information 15.4 [*] Interface Identification 15.5 [*] Errored Interface Identification 15.6 [*] Link Fault Handling 15.7 [*] Nodal Fault Handling 16. Other specification(s) which apply: OIF-UNI-01.0 17. Other features supported: a) RECOVERY_LABEL as per OIF UNI specification b) Service Discovery as per OIF UNI specification 18. Currently-defined GMPLS signaling features not supported: a) Channel Status procedure 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ==================================================================== Person filling out this form: Name: S. Shankar E-mail: shanky@npd.hcltech.com Tel.: +91-44-374-1939 Title: Project Manager Company: HCL Technologies Limited, Networking Products Division Date prepared: 13-March-2002 2.6. Intel Corporation GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Intel Corporation 1.1 Organization url(s):htp://www.intel.com 2. Product title(s):Intelligent Optical Networking using GMPLS 2.1 Brief description(s): The product utilizes the benefits of GMPLS to provision smart, Berger, Rekhter - Editors [Page 27] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 scalable and extensible Optical Networks. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name:Christian Maciocco, Manav Mishra 3.2 Title: 3.3 E-mail:christian.maciocco@intel.com;manav.mishra@intel.com 3.4 Organization/department:Intel Labs 3.5 Postal address:2111 NE 25th Avenue, Hillsboro, OR 97124 3.6 Phone:503-712-1843 3.7 Fax:503-264-3483 ---------------------------------------------------------------- 4. Status: 4.1 [X ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [X] PSC 5.2 [X] TDM 5.3 [ ] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-rsvp-te-06.txt ] 6.2 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-sonet-sdh-02.txt ] 6.3 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-architecture-01.txt ] 6.4 [http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-07.txt ] 6.5 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-lmp-02.txt ] 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [X] ATM 7.3 [X] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET Berger, Rekhter - Editors [Page 28] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [ ] For internal company use only 8.5 [X] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [X] MPLS Label 10.2 [X] Generalized Label 10.3 [ ] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [ ] Suggested Label 11.2 [X] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Please list which) RSVP-TE 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [X] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information Berger, Rekhter - Editors [Page 29] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 15.4 [ ] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: Acceptable Label Set, Suggested Label Set, Contention resolution, non-standard SONET/SDH extensions to GMPLS. 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: Real World Deployment scenarios-- To get a fair idea as to how the real world sees GMPLS deployment to happen. How does GMPLS sees quick fail-over support to be provided to non-SONET/SDH networks. ===================================================================== Person filling out this form: Name:Manav Mishra E-mail:manav.mishra@intel.com Tel.:503-712-1843 Title:Senior Network Software Engineer Company:Intel Corporation Date prepared:03/12/2002 2.7. Japan Telecom Co., Ltd. GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: JAPAN TELECOM CO., LTD. 1.1 Organization url(s): Berger, Rekhter - Editors [Page 30] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 http://www.icl.japan-telecom.co.jp 2. Product title(s): JT's virtual GMPLS signaling node 2.1 Brief description(s): JT's virtual GMPLS signaling node is a GMPLS signaling emulator running on Linux/UNIX environment in order to do some GMPLS signaling tests. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Hirokazu Ishimatsu 3.2 Title: Assistant Manager 3.3 E-mail: hirokazu@japan-telecom.co.jp 3.4 Organization/department: Information and Communication Laboratories 3.5 Postal address: Shuwa Higashi Yaesu Bldg., 5F 2-9-1 Hachobori, Chuo-ku, Tokyo, 104-0032 Japan 3.6 Phone: +81 3 5540 8493 3.7 Fax: +81 3 5540 8485 ---------------------------------------------------------------- 4. Status: 4.1 [X ] Development 4.2 [ ] Alpha 4.3 [ ] Beta Berger, Rekhter - Editors [Page 31] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [ ] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 draft-ietf-ccamp-ospf-gmpls-extentions-00.txt 6.2 draft-ietf-mpls-generalized-signaling-07.txt 6.3 draft-ietf-mpls-generalized-rsvp-te-06.txt 6.4 draft-ietf-ccamp-lmp-02.txt 6.5 [ ] 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [X ] Ethernet 802.3 for singaling channel 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [X ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X ] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [X ] Generalized Label 10.3 [ ] Waveband Label Berger, Rekhter - Editors [Page 32] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 10.4 [ ] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [X ] GMPLS Bandwidth Encoding 12.4 [ ] SONET/SDH 13. [X ] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X ] Explicit Label Control 15.2 [X ] Protection Information 15.3 [ ] Administrative Status Information 15.4 [ ] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [ ] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) GMPLS lab tests & field trial 20. If you feel the above categories are not complete, add others which will better describe your project: Berger, Rekhter - Editors [Page 33] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.8. Juniper Networks GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Juniper Networks 1.1 Organization url(s): www.juniper.net 2. Product title(s): GMPLS signaling 2.1 Brief description(s): This implementation aims at being able to dynamically signal generalized LSPs initiated by the router, across an optical core. It uses RSVP for signaling. The initial focus is on the signaling aspects rather than routing in a GMPLS domain. The purpose is to come up with an interoperable signaling solution and then move forward. The attributes for the label-switched path (encoding type, bandwidth, switching type; etc) will be configurable on the router, and will be translated into an appropriate RSVP signaling request. Bidirectional LSP setup is supported and so is control-data plane separation. Other specifics are listed below. - ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Arthi Ayyangar 3.2 Title: Member of Technical Staff 3.3 E-mail: arthi@juniper.net 3.4 Organization/department: Engineering / Software 3.5 Postal address: 1194 N. Mathilda Ave, Sunnyvale, CA 94089 3.6 Phone: (408) 745 2110 3.7 Fax: (408) 745 8905 - ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [*] Beta Berger, Rekhter - Editors [Page 34] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [*] PSC 5.2 [ ] TDM 5.3 [ ] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [*] draft-ietf-mpls-generalized-signaling-07.txt 6.2 [*] draft-ietf-mpls-generalized-rsvp-te-06.txt 6.3 [*] draft-ietf-mpls-lsp-hierarchy-04.txt (portions of this) 6.4 [*] draft-ietf-mpls-bundle-01.txt 6.5 [*] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 6.6 [*] IANA proposed values sent by Lou 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [*] Ethernet V2/DIX 7.4 [*] Ethernet 802.3 7.5 [*] SDH 7.6 [*] SONET 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [*] Other (describe): Packet 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [*] For internal company use only 8.5 [*] Other: Field trials 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [*] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [*] MPLS Label 10.2 [*] Generalized Label 10.3 [ ] Waveband Label Berger, Rekhter - Editors [Page 35] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 10.4 [*] SONET/SDH Label 11. Label Related 11.1 [*] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [*] Intserv (Please list which) (Token Bucket) 12.2 [ ] CR-LDP 12.3 [*] GMPLS Bandwidth Encoding 12.4 [*] SONET/SDH 13. [*] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [ ] Explicit Label Control 15.2 [*] Protection Information 15.3 [ ] Administrative Status Information 15.4 [*] Interface Identification 15.5 [*] Errored Interface Identification 15.6 [ ] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: ** Graceful restart (link and node failures), ** Notify ** Admin Status 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ** Control channel separation ** Refresh reduction ==================================================================== Berger, Rekhter - Editors [Page 36] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Person filling out this form: Name: Arthi Ayyangar E-mail: arthi@juniper.net Tel.: (408) 745 2110 Title: Member of Techical Staff Company: Juniper Networks Date prepared: 03/12/02 2.9. Lumentis AB GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Lumentis AB 1.1 Organization url(s): www.lumentis.se 2. Product title(s): Mentis systems 2.1 Brief description(s): DWDM systems for the metro environment ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Mats Dahlgren 3.2 Title: 3.3 E-mail: Mats.Dahlgren@lumentis.se 3.4 Organization/department: Lumentis AB 3.5 Postal address: Jakobsdalsgatan 17, SE-12653 Hagersten, Sweden 3.6 Phone: +46 8 52 76 75 50 3.7 Fax: +46 8 52 76 75 99 ---------------------------------------------------------------- 4. Status: 4.1 [x] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities Berger, Rekhter - Editors [Page 37] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [x] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [ ] 6.2 [ ] 6.3 [ ] 6.4 [ ] 6.5 [ ] 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [x] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [x] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4.1 [X] List portions from external source OSPFv2 9.4.2 [X] List portions developed internally OSPF-TE RSVP-TE LMP 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [x] Generalized Label 10.3 [ ] Waveband Label Berger, Rekhter - Editors [Page 38] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 10.4 [ ] SONET/SDH Label 11. Label Related 11.1 [ ] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [x] GMPLS Bandwidth Encoding 12.4 [ ] SONET/SDH 13. [x] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [ ] Explicit Label Control 15.2 [ ] Protection Information 15.3 [ ] Administrative Status Information 15.4 [ ] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [ ] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ============================================================== Person filling out this form: Name: see contact for GMPLS information E-mail: Tel.: Berger, Rekhter - Editors [Page 39] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Title: Company: Date prepared: 03/13/02 2.10. Marconi GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Marconi. 1.1 Organization url(s): www.marconi.com 2. Product title(s): Transport Network Control Plane 2.1 Brief description(s): Unified Control Plane for the SDH/SONET/Photonics product family ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Piergiorgio Sessarego 3.2 Title: ASON Strategy Director 3.3 E-mail: piergiorgio.sessarego@marconi.com 3.4 Organization/department: ASON Strategy 3.5 Postal address: Via A. Negrone 1/A 16153 Cornigliano (GE) Italy 3.6 Phone: +390106003902 3.7 Fax: --------------------------------------------------------------- 4. Status: 4.1 [X] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [X] Other (describe): An early GMPLS development is in place in a photonic ring of Marconi equipment (PMA-32) 5. Switching capabilities 5.1 [ ] PSC 5.2 [X] TDM Berger, Rekhter - Editors [Page 40] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 5.3 [X] LSC 5.4 [X] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [draft-ietf-ccamp-gmpls-architecture-01] 6.2 [draft-ietf-mpls-generalized-signaling-07] 6.3 [draft-ietf-mpls-generalized-rsvp-te-06] 6.4 [draft-ietf-ccamp-gmpls-sonet-sdh-02] 6.5 [draft-ietf-mpls-rsvp-unnum-03] 6.6 [draft-ietf-mpls-lsp-hierarchy-04] 6.7 [draft-ietf-mpls-bundle-01] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [X] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [X] Generalized Label 10.3 [X] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [ ] Suggested Label 11.2 [X] Label Set Berger, Rekhter - Editors [Page 41] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [X] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: OIF 1.0 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ======================================================================= Person filling out this form: Name: Diego Caviglia E-mail: diego.caviglia@marconi.com Tel.: +390106003808 Title: ASON Strategy Company: Marconi Date prepared: 11/03/02 Berger, Rekhter - Editors [Page 42] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.11. Movaz Networks GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Movaz Networks. 1.1 Organization url(s): www.movaz.com 2. Product title(s): RAYstar, RAYexpress 2.1 Brief description(s): RAYstar integrates the values of a very-high-density OADM (optical add/drop multiplexer) and a compact, distributed optical switching platform into a single 7 foot bay. The RAYexpress OADM (optical add/drop multiplexer) provides a versatile, cost effective, and compact platform for wavelength services in access and regional applications. ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Adrian Farrel 3.2 Title: Director Protocol Development 3.3 E-mail: afarrel@movaz.com 3.4 Organization/department: 3.5 Postal address: 7926 Jones Branch Drive Suite 615 McLean, VA 22102 3.6 Phone: 703-847-1867 3.7 Fax: 703-847-3975 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [x] Product Swi [ ] Other (describe): 5. Switching capabilities Berger, Rekhter - Editors [Page 43] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [x] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 draft-ietf-mpls-generalized-signaling-07.txt 6.2 draft-ietf-mpls-generalized-rsvp-te-06.txt 6.3 draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 6.4 RFC3209 6.5 RFC2961 6.6 RFC2205 6.7 draft-nadeau-ccamp-gmpls-tc-mib-01.txt 6.8 draft-nadeau-ccamp-gmpls-te-mib-01.txt Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [x] SDH 7.6 [x] SONET 7.7 [x] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [x] Other (describe): GigEthernet 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [x] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [x] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source Base RSVP-TE code from LabN 9.4.2 [ ] List portions developed internally RSVP-TE for GMPLS MIB support 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [x] Generalized Label Berger, Rekhter - Editors [Page 44] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 10.3 [ ] Waveband Label 10.4 [x] SONET/SDH Label 11. Label Related 11.1 [x] Suggested Label 11.2 [x] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [x] GMPLS Bandwidth Encoding 12.4 [x] SONET/SDH 13. [x] Bidirectional LSPs 14. Notification 14.1 [x] Acceptable Label Set 14.2 [x] Notify Request Objects (GMPLS-RSVP) 14.3 [x] Notify Message (GMPLS-RSVP) 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [x] Explicit Label Control 15.2 [x] Protection Information 15.3 [x] Administrative Status Information 15.4 [x] Interface Identification 15.5 [x] Errored Interface Identification 15.6 [x] Link Fault Handling 15.7 [x] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: OSPF and OSPF extensions for TE and GMPLS 18. Currently-defined GMPLS signaling features not supported: CR-LDP 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ============================================================== Person filling out this form: Berger, Rekhter - Editors [Page 45] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 Name: Adrian Farrel E-mail: Tel.: Title: Company: Date prepared: 3/13/02 2.12. Nortel Networks GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Nortel Networks 1.1 Organization url(s): www.nortelnetworks.com 2. Product title(s): Automatic Switched Optical Networks (ASON) 2.1 Brief description(s): optical control plane ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Don Fedyk 3.2 Title:Senior Advisor 3.3 E-mail: dwfedyk@nortelnetworks.com 3.4 Organization/department: 3.5 Postal address: 600 Technology Park, Billerica, MA 01450 3.6 Phone:978 288 3041 3.7 Fax: ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities Berger, Rekhter - Editors [Page 46] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [ ] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [x] draft-ietf-mpls-generalized-signaling-07.txt 6.2 [x] draft-ietf-mpls-generalized-cr-ldp-05.txt 6.3 [ ] 6.4 [ ] 6.5 [ ] 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [x] MPLS Label 10.2 [x] Generalized Label 10.3 [x] Waveband Label 10.4 [x] SONET/SDH Label 11. Label Related 11.1 [x] Suggested Label Berger, Rekhter - Editors [Page 47] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 11.2 [x] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [x] CR-LDP 12.3 [x] GMPLS Bandwidth Encoding 12.4 [x] SONET/SDH 13. [x] Bidirectional LSPs 14. Notification 14.1 [x] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [ ] Explicit Label Control 15.2 [ ] Protection Information 15.3 [ ] Administrative Status Information 15.4 [ ] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [ ] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ======================================================================= Person filling out this form: Name:Don Fedyk E-mail:see above Tel.: Title: Company: Date prepared: Berger, Rekhter - Editors [Page 48] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.13. Tellium, Inc. GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Tellium, Inc. 1.1 Organization url(s): www.tellium.com 2. Product title(s): Aurora Optical Switch, Aurora 128 2.1 Brief description(s): Wavelength optical switch, managing wavelengths which are today at -48 and -192 levels of granularity ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Dimitrios Pendarakis 3.2 Title: Manager, Internetworking and Applications 3.3 E-mail: dpendarakis@tellium.com 3.4 Organization/department: Tellium, Inc. 3.5 Postal address: 2 Crescent Place, P.O. Box 901, Oceanport, NJ 07757-0901 3.6 Phone: 732 923-4254 3.7 Fax: 732 728-9862 ---------------------------------------------------------------- 4. Status: 4.1 [ ] Development 4.2 [X] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [X] TDM 5.3 [X] LSC 5.4 [X] FSC Berger, Rekhter - Editors [Page 49] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 6. Reference Drafts (please list, include version numbers) 6.1 [X] draft-ietf-mpls-generalized-signaling-07.txt 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-06.txt 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 6.4 [X] draft-ietf-mpls-rsvp-unnum-04.txt 6.5 [X] draft-ietf-mpls-bundle-01.txt 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [X] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [X] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [X] Generalized Label 10.3 [ ] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [X] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP Berger, Rekhter - Editors [Page 50] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [ ] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: ===================================================================== Person filling out this form: Same as above Name: E-mail: Tel.: Title: Company: Date prepared: March 12, 2002 Berger, Rekhter - Editors [Page 51] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.14. Tropic Networks Inc GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: Tropic Networks Inc 1.1 Organization url(s): http://www.tropicnetworks.com 2.1 Brief description(s): The product is a switching device in the area of Optical Packet Networking ---------------------------------------------------------------- 3. Contact for GMPLS information 3.1 Name: Nabil Seddigh 3.3 E-mail: nseddigh@tropicnetworks.com 3.5 Postal address: 135 Michael Cowpland Dr Kanata, ON K2M 2E9 3.6 Phone: 613-270-6936 ---------------------------------------------------------------- 4. Status: 4.1 [X] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [X] PSC 5.2 [ ] TDM 5.3 [X] LSC 5.4 [X] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [ ] draft-ietf-mpls-generalized-signaling-07.txt 6.2 [ ] draft-ietf-mpls-generalized-rsvp-te-06.txt 6.3 [ ] draft-ietf-mpls-rsvp-unnum-04.txt 6.4 [ ] draft-ietf-mpls-lsp-hierarchy-04.txt 6.5 [ ] draft-ietf-mpls-bundle-01.txt 6.6 [ ] RFC 3032 7. Interface technologies 7.1 [ ] Frame Relay Berger, Rekhter - Editors [Page 52] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [X] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) 9.4 [X] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [X] MPLS Label 10.2 [X] Generalized Label 10.3 [X] Waveband Label 10.4 [ ] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [ ] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) Berger, Rekhter - Editors [Page 53] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 15 Other features 15.1 [ ] Explicit Label Control 15.2 [ ] Protection Information 15.3 [ ] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling =============================================================== Person filling out this form: Name: Nabil Seddigh E-mail: nseddigh@tropicnetworks.com Tel.: 613-270-6936 Company: Tropic Networks Date prepared: March 13, 2002 2.15. Anonymous 1 GMPLS Signaling Implementation Survey Form [V 1.0] 1. Organization: ANONYMOUS 1.1 Organization url(s): 2. Product title(s): 2.1 Brief description(s): ------------------------------------------------------------ 3. Contact for GMPLS information 3.1 Name: 3.2 Title: 3.3 E-mail: 3.4 Organization/department: 3.5 Postal address: 3.6 Phone: Berger, Rekhter - Editors [Page 54] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 3.7 Fax: ------------------------------------------------------------ 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [x] TDM 5.3 [x] LSC 5.4 [x] FSC 6. Reference Drafts (please list, include version numbers) 6.1 RFC2205 - Resource Reservation Protocol, September 1997 6.2 RFC2961 - RSVP Summary Refresh and bundling, April 2001 6.3 RFC3209 - RSVP extensions for Tunnel Setup, December 2001 6.4 Draft-ietf-mpls-generalized-signaling-07.txt - Generalized Signaling extensions for RSVP and CR_LDP 6.5 Draft-ietf-mpls-generalized-rsvp-te-06.txt - GMPLS RSVP extensions from Generalized Signaling 6.6 Draft-ietf-mpls-rsvp-unnum-04.txt - RSVP extensions for unnumbered interfaces 6.7 Draft-ietf-ccamp-gmpls_sonet-sdh-02.txt - GMPLS extensions for SDH/SONET Network Control 6.8 Draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS Traffic Engineering 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [x] ATM 7.3 [x] Ethernet V2/DIX 7.4 [x] Ethernet 802.3 7.5 [x] SDH 7.6 [x] SONET 7.7 [x] Lambda (photonic) 7.8 [x] Fiber 7.9 [x] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [x] On sale. Berger, Rekhter - Editors [Page 55] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [x] Purchased code (please list source if possible) 9.2 [x] Free code (please list source if possible) 9.3 [x] Internal implementation (no outside code, just from specs) 9.4 [x] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [x] Generalized Label 10.3 [x] Waveband Label 10.4 [x] SONET/SDH Label 11. Label Related 11.1 [x] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [x] GMPLS Bandwidth Encoding 12.4 [x] SONET/SDH 13. [x] Bidirectional LSPs 14. Notification 14.1 [x] Acceptable Label Set 14.2 [x] Notify Request Objects (GMPLS-RSVP) 14.3 [x] Notify Message (GMPLS-RSVP) 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 15. Other features 15.1 [x] Explicit Label Control 15.2 [x] Protection Information 15.3 [x] Administrative Status Information 15.4 [x] Interface Identification 15.5 [x] Errored Interface Identification 15.6 [x] Link Fault Handling 15.7 [x] Nodal Fault Handling 16. Other specification(s) which apply: - RSVP COPS - 16.1 RFC 2206 - RSVP Management Information Base using SMIv2 Berger, Rekhter - Editors [Page 56] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 16.2 RFC 2748 - The COPS (Common Open Policy Service) Protocol 16.3 RFC 2749 - COPS usage for RSVP 16.4 RFC 2753 - A Framework for Policy-based Admission Control 16.5 draft-ietf-rap-new-rsvpext-00.txt - RSVP Extension for Policy Control - SNMP - 16.6 RFC 2571 - An architecture for Describing SNMP Management Frameworks 16.7 RFC 2574 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) 16.8 RFC 2575 - Viewer-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) 16.9 RFC2863 - The Interfaces Group MIB 16.10 draft-nadeau-ccamp-gmpls-label-mib-01.txt - Generalized Multiprotocol Label Switching (GMPLS) Label Management Information Base 16.11 draft-nadeau-ccamp-gmpls-lsr-mib-01.txt - Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router Management Information Base 16.12 draft-nadeau-ccamp-gmpls-tc-mib-01.txt - Definition of Textual Conventions and OBJECT-IDENTITIES for Generalized Multiprotocol Label Switching (GMPLS) Management 16.13 draft-nadeau-ccamp-gmpls-te-mib-01.txt - Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base - LMP - 16.14 draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (v1) 16.15 draft-ietf-ccamp-lmp-mib-00.txt - Link Management Protocol Management Information Base Using SMIv2 - OIF - 16.16 User Network Interface (UNI) 1.0 Signaling Specification - OIF Oct'01 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: Berger, Rekhter - Editors [Page 57] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.16. Anonymous 2 GMPLS Signaling Implementation Survey Form [V 1.0] 4. Status: 4.1 [X] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [ ] Product 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [ ] PSC 5.2 [ ] TDM 5.3 [X] LSC 5.4 [ ] FSC 6. Reference Drafts (please list, include version numbers) 6.1 [ ] 6.2 [ ] 6.3 [ ] 6.4 [ ] 6.5 [ ] 6.6 [ ] 7. Interface technologies 7.1 [ ] Frame Relay 7.2 [ ] ATM 7.3 [ ] Ethernet V2/DIX 7.4 [ ] Ethernet 802.3 7.5 [ ] SDH 7.6 [ ] SONET 7.7 [ ] Lambda (photonic) 7.8 [ ] Fiber 7.9 [ ] FiberChannel 7.10 [X] Other (describe): Lambda O-E-O 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [ ] On sale. 8.4 [X] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [ ] Internal implementation (no outside code, just from specs) Berger, Rekhter - Editors [Page 58] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 9.4 [X] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [ ] List portions developed internally 10. Supported Label Types 10.1 [ ] MPLS Label 10.2 [X] Generalized Label 10.3 [ ] Waveband Label 10.4 [ ] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [ ] Label Set 12. Traffic Parameters 12.1 [ ] Intserv (Please list which) 12.2 [ ] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [ ] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [ ] Acceptable Label Set 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [ ] Explicit Label Control 15.2 [ ] Protection Information 15.3 [ ] Administrative Status Information 15.4 [ ] Interface Identification 15.5 [ ] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [X] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 20. If you feel the above categories are not complete, add others which will better describe your project: Berger, Rekhter - Editors [Page 59] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 2.17. Anonymous 3 GMPLS Signaling Implementation Survey Form [V 1.0] 4. Status: 4.1 [ ] Development 4.2 [ ] Alpha 4.3 [ ] Beta 4.4 [X] Product: All products listed above are General Availability Released products 4.5 [ ] Other (describe): 5. Switching capabilities 5.1 [X] PSC 5.2 [X] TDM 5.3 [X] LSC 5.4 [X] FSC 6. Reference Drafts (please list, include version numbers) 7. Interface technologies 7.1 [X] Frame Relay 7.2 [X] ATM 7.3 [X] Ethernet V2/DIX 7.4 [X] Ethernet 802.3 7.5 [X] SDH 7.6 [X] SONET 7.7 [X] Lambda (photonic) 7.8 [X] Fiber 7.9 [ ] FiberChannel 7.10 [ ] Other (describe): 8. Availability 8.1 [ ] Public and free 8.2 [ ] Only to selected organizations/companies but free 8.3 [X] On sale. 8.4 [ ] For internal company use only 8.5 [ ] Other: 9. Implementation based on: (check all that apply) 9.1 [ ] Purchased code (please list source if possible) 9.2 [ ] Free code (please list source if possible) 9.3 [X] Internal implementation (no outside code, just from specs) 9.4 [ ] Internal implementation on top of purchased or free code 9.4.1 [ ] List portions from external source 9.4.2 [X] List portions developed internally Too many details to list here, but generally develop some Berger, Rekhter - Editors [Page 60] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 proprietary items to support incomplete sections of IETF Drafts, when required 10. Supported Label Types 10.1 [X] MPLS Label 10.2 [X] Generalized Label 10.3 [ ] Waveband Label 10.4 [X] SONET/SDH Label 11. Label Related 11.1 [X] Suggested Label 11.2 [X] Label Set 12. Traffic Parameters 12.1 [X] Intserv (Please list which) 12.2 [X] CR-LDP 12.3 [X] GMPLS Bandwidth Encoding 12.4 [X] SONET/SDH 13. [X] Bidirectional LSPs 14. Notification 14.1 [X] Acceptable Label Set 14.2 [X] Notify Request Objects (GMPLS-RSVP) 14.3 [X] Notify Message (GMPLS-RSVP) 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 15 Other features 15.1 [X] Explicit Label Control 15.2 [X] Protection Information 15.3 [X] Administrative Status Information 15.4 [X] Interface Identification 15.5 [X] Errored Interface Identification 15.6 [X] Link Fault Handling 15.7 [ ] Nodal Fault Handling 16. Other specification(s) which apply: 17. Other features supported: 18. Currently-defined GMPLS signaling features not supported: Generally support all GMPLS signaling requirements which are adequately defined in the IETF drafts today. 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) Berger, Rekhter - Editors [Page 61] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 provide software source code to many types of Network Equipment Providers 20. If you feel the above categories are not complete, add others which will better describe your project: 3. Acknowledgments The survey form was derived from V2.2 of the "RSVP and QoS Implementation Survey Information Form" authored by Gene Gaines and Marco Festa . See http://www.iit.nrc.ca/IETF/RSVP_survey/rsvp-qos_quest_980210.txt. Scott Bradner, sob@harvard.edu, provided the "anonymous submission" service for this survey. 4. Security Considerations This document does not address any security issues. 5. IANA Considerations No parameters are defined in this document. 6. References [GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - CR-LDP Extensions", Internet Draft, draft-ietf-mpls-generalized-cr-ldp-05.txt, November 2001. [GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - RSVP-TE Extensions", Internet Draft, draft-ietf-mpls-generalized-rsvp-te-06.txt, November, 2001. [GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS - Signaling Functional Description", Internet Draft, draft-ietf-mpls-generalized-signaling-07.txt, November 2001. [GMPLS-SONET] Ashwood-Smith, P. et al, "GMPLS - SONET / SDH Specifics", Internet Draft, draft-ietf-ccamp-gmpls-sonet-sdh-03.txt, April, 2001. Berger, Rekhter - Editors [Page 62] Internet Draft draft-ietf-ccamp-gmpls-signaling-survey-01.txt March 2002 7. Editors' Addresses Lou Berger Movaz Networks, Inc. 7926 Jones Branch Drive Suite 615 McLean VA, 22102 Phone: +1 703 847-1801 Email: lberger@movaz.com Yakov Rekhter Juniper Networks, Inc. Email: yakov@juniper.net Berger, Rekhter - Editors [Page 63] Generated on: Tue Mar 19 10:33:48 2002