draft-ietf-ccamp-gmpls-signaling-survey-00.txt   draft-ietf-ccamp-gmpls-signaling-survey-01.txt 
Network Working Group Lou Berger (Movaz) - Editor Network Working Group Lou Berger (Movaz) - Editor
Internet Draft Yakov Rekhter (Juniper) - Editor Internet Draft Yakov Rekhter (Juniper) - Editor
Expiration Date: September 2002 Expiration Date: November 2002
March 2002 May 2002
Generalized MPLS Signaling - Implementation Survey Generalized MPLS Signaling - Implementation Survey
draft-ietf-ccamp-gmpls-signaling-survey-01.txt draft-ietf-ccamp-gmpls-signaling-survey-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
skipping to change at page 1, line 33 skipping to change at page 1, line 33
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To view the current status of any Internet-Draft, please check the To view the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in an Internet-Drafts Shadow "1id-abstracts.txt" listing contained in an Internet-Drafts Shadow
Directory, see http://www.ietf.org/shadow.html. Directory, see http://www.ietf.org/shadow.html.
Abstract Abstract
This document provides a survey of GMPLS signaling implementations. This document provides a survey of GMPLS signaling implementations.
The primary focus of this survey are the signaling protocol The primary focus of this survey are the signaling protocol
mechanisms specified in [GMPLS-SIG], [GMPLS-RSVP], [GMPLS-LDP] and mechanisms specified in the Generalized MPLS signaling documents.
[GMPLS-SONET]. Other specifications and documents are listed if Other specifications and documents are listed if included in the
included in the submitted form. The survey form and latest version submitted form. The survey form and latest version of this document
of this document are available from http://www.labn.net/gmpls-survey. are available from http://www.labn.net/gmpls-survey.
Contents Contents
1 Survey Summary .............................................. 3 1 Survey Summary .............................................. 3
2 Survey Forms ................................................ 7 2 Survey Forms ................................................ 7
2.1 Agilent Technologies ........................................ 7 2.1 Agilent Technologies ........................................ 7
2.2 Calient Networks ............................................ 10 2.2 Calient Networks ............................................ 10
2.3 Data Connection Ltd ......................................... 15 2.3 Ciena Corporation ........................................... 15
2.4 Firstwave Intelligent Optical Networks ...................... 20 2.4 Data Connection Ltd ......................................... 18
2.5 HCL Technologies Ltd., India ................................ 24 2.5 Equipe Communications Corp. ................................. 24
2.6 Intel Corporation ........................................... 27 2.6 Firstwave Intelligent Optical Networks ...................... 27
2.7 Japan Telecom Co., Ltd. ..................................... 30 2.7 HCL Technologies Ltd., India ................................ 31
2.8 Juniper Networks ............................................ 34 2.8 Intel Corporation ........................................... 34
2.9 Lumentis AB ................................................. 37 2.9 Japan Telecom Co., Ltd. ..................................... 37
2.10 Marconi ..................................................... 40 2.10 Juniper Networks ............................................ 42
2.11 Movaz Networks .............................................. 43 2.11 Lumentis AB ................................................. 45
2.12 Nortel Networks ............................................. 46 2.12 Marconi ..................................................... 48
2.13 Tellium, Inc. ............................................... 49 2.13 Movaz Networks .............................................. 51
2.14 Tropic Networks Inc ......................................... 52 2.14 NetPlane Systems ............................................ 54
2.15 Anonymous 1 ................................................. 54 2.15 Nippon Telegraph and Telephone Corporation .................. 59
2.16 Anonymous 2 ................................................. 58 2.16 Nortel Networks ............................................. 62
2.17 Anonymous 3 ................................................. 60 2.17 Tellium, Inc. ............................................... 65
3 Acknowledgments ............................................. 62 2.18 Tropic Networks Inc ......................................... 68
4 Security Considerations ..................................... 62 2.19 Wipro Technologies .......................................... 71
5 IANA Considerations ......................................... 62 2.20 Anonymous 1 ................................................. 74
6 References .................................................. 62 2.21 Anonymous 2 ................................................. 78
7 Editors' Addresses .......................................... 63 3 Acknowledgments ............................................. 80
4 Security Considerations ..................................... 80
5 IANA Considerations ......................................... 80
6 References .................................................. 80
7 Editors' Addresses .......................................... 81
1. Survey Summary 1. Survey Summary
This document is a compilation of responses to the GMPLS Signaling This document is a compilation of responses to the GMPLS Signaling
implementation form found at http://www.labn.net/gmpls-survey/sig- implementation form found at http://www.labn.net/gmpls-survey/sig-
survey.txt. After a brief summary, each response in it's entirety is 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 listed. (**The editors, make no claim as to the accuracy of the
information provided nor do they endorse the statements made within information provided nor do they endorse the statements made within
each response.) Anonymous submissions were handled by Scott Bradner, each response.**) Anonymous submissions were handled by Scott
sob@harvard.edu. All identifying information was removed prior to Bradner, sob@harvard.edu. All identifying information was removed
these submissions being forwarded to the editors. Generalized MPLS prior to these submissions being forwarded to the editors.
signaling is specified in the documents [GMPLS-SIG], [GMPLS-RSVP], Generalized MPLS signaling is specified in the documents [GMPLS-SIG],
[GMPLS-LDP] and [GMPLS-SONET]. [GMPLS-RSVP], [GMPLS-LDP] and [GMPLS-SONET].
Table 1 summarizes the results of the GMPLS signaling aspects of Table 1 summarizes the results of the GMPLS signaling aspects of
survey. Many included implementation details for other survey. Many included implementation details for other
specifications or drafts. These details are included in the full specifications or drafts. These details are included in the full
response section, but not in the summary table. Table 2 provides response section, but not in the summary table. Table 2 provides
total results by feature/question. total results by feature/question.
The categories covered in summary Table 1 are: The categories covered in summary Table 1 are:
o Type o Type
skipping to change at page 5, line 13 skipping to change at page 5, line 13
some boxes were not checked. some boxes were not checked.
+===================================================================+ +===================================================================+
|Ref. | Type |Draft| S/w Genealogy |Switch |Label |Feature| |Ref. | Type |Draft| S/w Genealogy |Switch |Label |Feature|
|Section | | |External:Internal|Caps. |Types |L:B:N:O| |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.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.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.3 |Code |R S|Yes :n/a | T | S| :F: : |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.4 |Code |R L | :All | L F| G W |F:F:F:F| | 2.4 |Code |R S|Yes :GMPLS |P T L F|M G W S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.5 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P| | 2.5 |Equip. |R S| :All |P T | G S| :F:P: |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.6 |Equip. |R S| :All |P T |M G S|P:F:F:P| | 2.6 |Code |R L | :All | L F| G W |F:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.7 |Code |R S| :All | n/a | G |P:F: :P| | 2.7 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.8 |Equip. |R S| :All |P |M G S|P:F: :P| | 2.8 |Equip. |R S| :All |P T |M G S|P:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.9 |Equip. |R |Yes :GMPLS | L | G | :F: : | | 2.9 |Code |R S| :All | n/a | G |P:F: :P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.10 |Equip. |R S| :All | T L F| G W S|P:F:F:F| | 2.10 |Equip. |R S| :All |P |M G S|P:F: :P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.11 |Equip. |R S|LabN :GMPLS | L | G S|F:F:F:F| | 2.11 |Equip. |R |Yes :GMPLS | L | G | :F: : |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.12 |Code | L | n/a | n/a |M G W S|F:F:F: | | 2.12 |Equip. |R S| :All | T L F| G W S|P:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.13 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P| | 2.13 |Equip. |R S|LabN :GMPLS | L | G S|F:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.14 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P| | 2.14 |Code |R S| :All |P T L F|M G W S|F:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.15 |Unknown|R S|Yes :n/a | T L F| G W S|P:F:F:F| | 2.15 |Equip. |R S|Yes :n/a |P L |M G W |F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.16 |Unknown|R |Yes :n/a | L | G |P:F:P:P| | 2.16 |Code | L | n/a | n/a |M G W S|F:F:F: |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.17 |Code |R n/a| :All |P T L F|M G S |F:F:F:P| | 2.17 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.18 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.19 |Code |R L | :All |P T |M G S|F:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.20 |Unknown|R S|Yes :n/a | T L F| G W S|P:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.21 |Unknown|R |Yes :n/a | L | G |P:F:P:P|
+===================================================================+ +===================================================================+
"n/a" indicates that no answer was provided. "n/a" indicates that no answer was provided.
Table 1: Survey Results Summary Table 1: Survey Results Summary
+==================================================================+ +==================================================================+
| Total | Total | | | Total | Total | |
|GMPLS-RSVP|GMPLS-LDP|Section, Description | |GMPLS-RSVP|GMPLS-LDP|Section, Description |
+==================================================================+ +==================================================================+
| 17 |Total participants | 21 |Total participants
| 16 | - |6. Reference Draft - [GMPLS-RSVP] | | 20 | - |6. Reference Draft - [GMPLS-RSVP] |
| - | 2 |6. Reference Draft - [GMPLS-LDP] | | - | 3 |6. Reference Draft - [GMPLS-LDP] |
| 10 |6. Reference Draft - [GMPLS-SONET] | | 13 |6. Reference Draft - [GMPLS-SONET] |
| 6 | |5.1 Switching capabilities - PSC | | 9 | 2 |5.1 Switching capabilities - PSC |
| 8 | |5.2 Switching capabilities - TDM | | 11 | 1 |5.2 Switching capabilities - TDM |
| 12 | 1 |5.3 Switching capabilities - LSC | | 13 | 2 |5.3 Switching capabilities - LSC |
| 9 | 1 |5.4 Switching capabilities - FSC | | 9 | 1 |5.4 Switching capabilities - FSC |
| 1 | |9.1 Implementation based on - Purchased code| | 1 | |9.1 Implementation based on - Purchased code|
| 1 | |9.2 Implementation based on - Free code | | 1 | |9.2 Implementation based on - Free code |
| 9 | 1 |9.3 Implementation based on - Internal | | 11 | 2 |9.3 Implementation based on - Internal |
| 9 | |9.4 Implementation based on - Combination | | 11 | 1 |9.4 Implementation based on - Combination |
| 7 | 1 |10.1 MPLS Label | | 9 | 3 |10.1 MPLS Label |
| 16 | 2 |10.2 Generalized Label | | 20 | 3 |10.2 Generalized Label |
| 7 | 2 |10.3 Waveband Label | | 9 | 3 |10.3 Waveband Label |
| 11 | 1 |10.4 SONET/SDH Label | | 14 | 2 |10.4 SONET/SDH Label |
| 13 | 2 |11.1 Suggested Label | | 15 | 3 |11.1 Suggested Label |
| 10 | 2 |11.2 Label Set | | 12 | 3 |11.2 Label Set |
| 8 | - |12.1 Traffic Parameters - Intserv | | 8 | - |12.1 Traffic Parameters - Intserv |
| - | 4 |12.2 Traffic Parameters - CR-LDP | | - | 6 |12.2 Traffic Parameters - CR-LDP |
| 16 | 2 |12.3 GMPLS Bandwidth Encoding | | 18 | 3 |12.3 GMPLS Bandwidth Encoding |
| 11 | 1 |12.4 Traffic Parameters - SONET/SDH | | 14 | 2 |12.4 Traffic Parameters - SONET/SDH |
| 16 | 2 |13. Bidirectional LSPs | | 20 | 4 |13. Bidirectional LSPs |
| 9 | 2 |14.1 Acceptable Label Set | | 10 | 3 |14.1 Acceptable Label Set |
| 10 | - |14.2 Notify Request Objects | | 12 | - |14.2 Notify Request Objects |
| 11 | - |14.3 Notify Message | | 14 | - |14.3 Notify Message |
| 12 | - |14.4 Removing State with a PathErr message | | 15 | - |14.4 Removing State with a PathErr message |
| 11 | 1 |15.1 Explicit Label Control | | 13 | 2 |15.1 Explicit Label Control |
| 12 | 1 |15.2 Protection Information | | 14 | 2 |15.2 Protection Information |
| 11 | 1 |15.3 Administrative Status Information | | 13 | 2 |15.3 Administrative Status Information |
| 12 | 1 |15.4 Interface Identification | | 14 | 2 |15.4 Interface Identification |
| 11 | 1 |15.5 Errored Interface Identification | | 13 | 2 |15.5 Errored Interface Identification |
| 12 | 1 |15.6 Link Fault Handling | | 12 | 1 |15.6 Link Fault Handling |
| 11 | 1 |15.7 Nodal Fault Handling | | 11 | 1 |15.7 Nodal Fault Handling |
+==================================================================+ +==================================================================+
"-" indicates that items is not relevant to protocol. "-" indicates that items is not relevant to protocol.
Table 2: Survey Totals Table 2: Survey Totals
2. Survey Forms 2. Survey Forms
2.1. Agilent Technologies 2.1. Agilent Technologies
skipping to change at page 15, line 13 skipping to change at page 15, line 13
==================================================================== ====================================================================
Person filling out this form: Person filling out this form:
Name: james scott Name: james scott
E-mail: jscott@calient.net E-mail: jscott@calient.net
Tel.: 408.972.3709 Tel.: 408.972.3709
Title: s/w arch Title: s/w arch
Company: calient Company: calient
Date prepared: 02.03.11 Date prepared: 02.03.11
2.3. Data Connection Ltd 2.3. Ciena Corporation
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Ciena Corporation
1.1 Organization url(s): www.ciena.com
2. Product title(s): MetroDirector, CoreDirector
2.1 Brief description(s): Metro and core optical switches with STS-1
granularity. GMPLS is implemented using the OIF UNI 1.0
Implementation agreement in order to support interoperability.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Lyndon Ong
3.2 Title: Dir., Net. Control and Management
3.3 E-mail: lyong@ciena.com
3.4 Organization/department: CTO
3.5 Postal address: 10480 Ridgeview Court, Cupertino, CA 95014
3.6 Phone: 408-366-3358
3.7 Fax:
----------------------------------------------------------------
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 [X] [ ] TDM
5.3 [ ] [ ] LSC
5.4 [ ] [ ] FSC
6. Reference Drafts (please list, include version numbers)
6.1 [X] draft-ietf-mpls-generalized-signaling-06.txt
6.2 [X] draft-ietf-mpls-generalized-rsvp-te-05.txt
6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-02.txt
6.4 [ ]
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 [ ] Lambda (photonic)
7.8 [ ] Fiber
7.9 [ ] FiberChannel
7.10 [ ] Other (describe):
8. Availability
[GMPLS- [GMPLS-
RSVP] LDP]
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)
[GMPLS- [GMPLS-
RSVP] LDP]
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:
(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 [ ] [ ] Generalized Label
10.3 [ ] [ ] Waveband Label
10.4 [X] [ ] SONET/SDH Label
11. Label Related
[GMPLS- [GMPLS-
RSVP] LDP]
11.1 [ ] [ ] Suggested Label
11.2 [ ] [ ] Label Set
12. Traffic Parameters
[GMPLS- [GMPLS-
RSVP] LDP]
12.1 [ ] Intserv (Please list which)
12.2 [ ] CR-LDP
12.3 [ ] [ ] GMPLS Bandwidth Encoding
12.4 [X] [ ] SONET/SDH
13. Bidirectional LSPs
[GMPLS- [GMPLS-
RSVP] LDP]
[X] [ ] Bidirectional LSPs
14. Notification
[GMPLS- [GMPLS-
RSVP] LDP]
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
[GMPLS- [GMPLS-
RSVP] LDP]
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:
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)
Based on OIF UNI 1.0 Implementation Agreement, which is a subset of GMPLS
but includes the most stable and commonly agreed features. The purpose of
the implementation is for interoperability with client devices.
20. If you feel the above categories are not complete, add others which
will better describe your project:
====================================================================
Person filling out this form:
Name: as above
E-mail:
Tel.:
Title:
Company:
Date prepared: March 22, 2002
2.4. Data Connection Ltd
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: 1. Organization:
Data Connection Ltd Data Connection Ltd
1.1 Organization url(s): 1.1 Organization url(s):
www.dataconnection.com www.dataconnection.com
2. Product title(s): 2. Product title(s):
DC-MPLS DC-MPLS
2.1 Brief description(s): 2.1 Brief description(s):
MPLS and GMPLS signaling software product, including RSVP, LDP, CR-LDP and MPLS and GMPLS signaling software product, including RSVP, LDP, CR-LDP and
OIF UNI support. OIF UNI support.
---------------------------------------------------------------- ----------------------------------------------------------------
3. Contact for GMPLS information 3. Contact for GMPLS information
skipping to change at page 20, line 24 skipping to change at page 24, line 5
Title: Title:
DC-MPLS Development Manager DC-MPLS Development Manager
Company: Company:
Data Connection Ltd. Data Connection Ltd.
Date prepared: Date prepared:
13th March 2002 13th March 2002
2.4. Firstwave Intelligent Optical Networks 2.5. Equipe Communications Corp.
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Equipe Communications Corp.
1.1 Organization url(s): www.equipecom.com
2. Product title(s): E3200
2.1 Brief description(s): O-UNI implementation for Multi-service
switch
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Nik Langrind
3.2 Title: Prin SW Eng
3.3 E-mail: nik@equipecom.com
3.4 Organization/department: Engineering
3.5 Postal address: 100 Nagog Park, Acton MA 01720
3.6 Phone: (978) 795 2012
3.7 Fax: (978) 635 0095
----------------------------------------------------------------
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 [x] [ ] PSC
5.2 [x] [ ] TDM
5.3 [ ] [ ] LSC
5.4 [ ] [ ] FSC
6. Reference Drafts (please list, include version numbers)
6.1 [ ] draft-ietf-mpls-generalized-signaling-08
6.2 [ ] draft-ietf-mpls-generalized-rsvp-te-07
6.3 [ ] draft-ietf-ccamp-gmpls-sonet-sdh-03
6.4 [ ] draft-ietf-ccamp-lmp-03
6.5 [ ] RFC2961 Refresh Reduction
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 [ ] Lambda (photonic)
7.8 [ ] Fiber
7.9 [ ] FiberChannel
7.10 [ ] Other (describe):
8. Availability
[GMPLS- [GMPLS-
RSVP] LDP]
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)
[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] [ ] 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] [ ] Generalized Label
10.3 [ ] [ ] Waveband Label
10.4 [x] [ ] SONET/SDH Label
11. Label Related
[GMPLS- [GMPLS-
RSVP] LDP]
11.1 [ ] [ ] Suggested Label
11.2 [ ] [ ] Label Set
12. Traffic Parameters
[GMPLS- [GMPLS-
RSVP] LDP]
12.1 [ ] Intserv (Please list which)
12.2 [ ] CR-LDP
12.3 [ ] [ ] GMPLS Bandwidth Encoding
12.4 [x] [ ] SONET/SDH
13. Bidirectional LSPs
[GMPLS- [GMPLS-
RSVP] LDP]
[x] [ ] Bidirectional LSPs
14. Notification
[GMPLS- [GMPLS-
RSVP] LDP]
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
[GMPLS- [GMPLS-
RSVP] LDP]
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:
17.1 related to [GMPLS-RSVP]
17.2 related to [GMPLS-LDP]
17.3 Other
18. Currently-defined GMPLS signaling features not supported:
Suggested Label, Label Set etc.
19. Notes (please describe purpose of project, give any information that
might be useful to those interested in developing or using GMPLS)
The goal is to provide OIF O-UNI 1.0, User Side.
20. If you feel the above categories are not complete, add others which
will better describe your project:
====================================================================
Person filling out this form:
Name: Nik Langrind
E-mail: nik@equipecom.com
Tel.: (978) 795-2012
Title: Prin SW Eng
Company: Equipe Communications Corp
Date prepared: 5/30/02
2.6. Firstwave Intelligent Optical Networks
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: FirstWave Intelligent Optical Networks 1. Organization: FirstWave Intelligent Optical Networks
1.1 Organization url(s): http://www.fwion.com 1.1 Organization url(s): http://www.fwion.com
2. Product title(s): 2. Product title(s):
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 24, line 7 skipping to change at page 31, line 9
Person filling out this form: Person filling out this form:
Name: Michael Mandelberg Name: Michael Mandelberg
E-mail: mmandelberg@fwion.com E-mail: mmandelberg@fwion.com
Tel.: (301) 345-2137 x1008 Tel.: (301) 345-2137 x1008
Title: Sr. MTS Title: Sr. MTS
Company: FirstWave Intelligent Optical Networks Company: FirstWave Intelligent Optical Networks
Date prepared: 3-15-02 Date prepared: 3-15-02
2.5. HCL Technologies Ltd., India 2.7. HCL Technologies Ltd., India
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: HCL TECHNOLOGIES LTD., INDIA 1. Organization: HCL TECHNOLOGIES LTD., INDIA
1.1 Organization url(s): www.hcltechnologies.com (Corporate Website) 1.1 Organization url(s): www.hcltechnologies.com (Corporate Website)
2. Product title(s): HCL LMP , HCL RSVP-TE 2. Product title(s): HCL LMP , HCL RSVP-TE
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 27, line 37 skipping to change at page 34, line 39
Person filling out this form: Person filling out this form:
Name: S. Shankar Name: S. Shankar
E-mail: shanky@npd.hcltech.com E-mail: shanky@npd.hcltech.com
Tel.: +91-44-374-1939 Tel.: +91-44-374-1939
Title: Project Manager Title: Project Manager
Company: HCL Technologies Limited, Company: HCL Technologies Limited,
Networking Products Division Networking Products Division
Date prepared: 13-March-2002 Date prepared: 13-March-2002
2.6. Intel Corporation 2.8. Intel Corporation
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Intel Corporation 1. Organization: Intel Corporation
1.1 Organization url(s):htp://www.intel.com 1.1 Organization url(s):htp://www.intel.com
2. Product title(s):Intelligent Optical Networking using GMPLS 2. Product title(s):Intelligent Optical Networking using GMPLS
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 30, line 39 skipping to change at page 37, line 40
Person filling out this form: Person filling out this form:
Name:Manav Mishra Name:Manav Mishra
E-mail:manav.mishra@intel.com E-mail:manav.mishra@intel.com
Tel.:503-712-1843 Tel.:503-712-1843
Title:Senior Network Software Engineer Title:Senior Network Software Engineer
Company:Intel Corporation Company:Intel Corporation
Date prepared:03/12/2002 Date prepared:03/12/2002
2.7. Japan Telecom Co., Ltd. 2.9. Japan Telecom Co., Ltd.
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: 1. Organization:
JAPAN TELECOM CO., LTD. JAPAN TELECOM CO., LTD.
1.1 Organization url(s): 1.1 Organization url(s):
http://www.icl.japan-telecom.co.jp http://www.icl.japan-telecom.co.jp
2. Product title(s): 2. Product title(s):
JT's virtual GMPLS signaling node JT's virtual GMPLS signaling node
2.1 Brief description(s): 2.1 Brief description(s):
JT's virtual GMPLS signaling node is a GMPLS signaling emulator running on JT's virtual GMPLS signaling node is a GMPLS signaling emulator
Linux/UNIX environment in order to do some GMPLS signaling tests. running on Linux/UNIX environment in order to do some GMPLS signaling
tests.
---------------------------------------------------------------- ----------------------------------------------------------------
3. Contact for GMPLS information 3. Contact for GMPLS information
3.1 Name: 3.1 Name:
Hirokazu Ishimatsu Hirokazu Ishimatsu
3.2 Title: 3.2 Title:
skipping to change at page 33, line 11 skipping to change at page 40, line 13
10.1 [ ] MPLS Label 10.1 [ ] MPLS Label
10.2 [X ] Generalized Label 10.2 [X ] Generalized Label
10.3 [ ] Waveband Label 10.3 [ ] Waveband Label
10.4 [ ] SONET/SDH Label 10.4 [ ] SONET/SDH Label
11. Label Related 11. Label Related
11.1 [X] Suggested Label 11.1 [X] Suggested Label
11.2 [ ] Label Set 11.2 [ ] Label Set
12. Traffic Parameters 12. Traffic Parameters
12.1 [ ] Intserv (Please list which) 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
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)
12.2 [ ] CR-LDP 12.2 [ ] CR-LDP
12.3 [X ] GMPLS Bandwidth Encoding 12.3 [X ] GMPLS Bandwidth Encoding
12.4 [ ] SONET/SDH 12.4 [ ] SONET/SDH
13. [X ] Bidirectional LSPs 13. [X ] Bidirectional LSPs
14. Notification 14. Notification
14.1 [ ] Acceptable Label Set 14.1 [ ] Acceptable Label Set
14.2 [ ] Notify Request Objects (GMPLS-RSVP) 14.2 [ ] Notify Request Objects (GMPLS-RSVP)
14.3 [ ] Notify Message (GMPLS-RSVP) 14.3 [ ] Notify Message (GMPLS-RSVP)
skipping to change at page 34, line 5 skipping to change at page 42, line 5
18. Currently-defined GMPLS signaling features not supported: 18. Currently-defined GMPLS signaling features not supported:
19. Notes (please describe purpose of project, give any information that 19. Notes (please describe purpose of project, give any information that
might be useful to those interested in developing or using GMPLS) might be useful to those interested in developing or using GMPLS)
GMPLS lab tests & field trial GMPLS lab tests & field trial
20. If you feel the above categories are not complete, add others which 20. If you feel the above categories are not complete, add others which
will better describe your project: will better describe your project:
2.8. Juniper Networks 2.10. Juniper Networks
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Juniper Networks 1. Organization: Juniper Networks
1.1 Organization url(s): www.juniper.net 1.1 Organization url(s): www.juniper.net
2. Product title(s): GMPLS signaling 2. Product title(s): GMPLS signaling
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 37, line 13 skipping to change at page 45, line 13
==================================================================== ====================================================================
Person filling out this form: Person filling out this form:
Name: Arthi Ayyangar Name: Arthi Ayyangar
E-mail: arthi@juniper.net E-mail: arthi@juniper.net
Tel.: (408) 745 2110 Tel.: (408) 745 2110
Title: Member of Techical Staff Title: Member of Techical Staff
Company: Juniper Networks Company: Juniper Networks
Date prepared: 03/12/02 Date prepared: 03/12/02
2.9. Lumentis AB 2.11. Lumentis AB
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Lumentis AB 1. Organization: Lumentis AB
1.1 Organization url(s): www.lumentis.se 1.1 Organization url(s): www.lumentis.se
2. Product title(s): Mentis systems 2. Product title(s): Mentis systems
2.1 Brief description(s): DWDM systems for the metro environment 2.1 Brief description(s): DWDM systems for the metro environment
skipping to change at page 40, line 9 skipping to change at page 48, line 9
Person filling out this form: Person filling out this form:
Name: see contact for GMPLS information Name: see contact for GMPLS information
E-mail: E-mail:
Tel.: Tel.:
Title: Title:
Company: Company:
Date prepared: 03/13/02 Date prepared: 03/13/02
2.10. Marconi 2.12. Marconi
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Marconi. 1. Organization: Marconi.
1.1 Organization url(s): www.marconi.com 1.1 Organization url(s): www.marconi.com
2. Product title(s): Transport Network Control Plane 2. Product title(s): Transport Network Control Plane
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 43, line 5 skipping to change at page 51, line 5
Person filling out this form: Person filling out this form:
Name: Diego Caviglia Name: Diego Caviglia
E-mail: diego.caviglia@marconi.com E-mail: diego.caviglia@marconi.com
Tel.: +390106003808 Tel.: +390106003808
Title: ASON Strategy Title: ASON Strategy
Company: Marconi Company: Marconi
Date prepared: 11/03/02 Date prepared: 11/03/02
2.11. Movaz Networks 2.13. Movaz Networks
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Movaz Networks. 1. Organization: Movaz Networks.
1.1 Organization url(s): www.movaz.com 1.1 Organization url(s): www.movaz.com
2. Product title(s): RAYstar, RAYexpress 2. Product title(s): RAYstar, RAYexpress
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 46, line 12 skipping to change at page 54, line 12
Person filling out this form: Person filling out this form:
Name: Adrian Farrel Name: Adrian Farrel
E-mail: E-mail:
Tel.: Tel.:
Title: Title:
Company: Company:
Date prepared: 3/13/02 Date prepared: 3/13/02
2.12. Nortel Networks 2.14. NetPlane Systems
GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: NetPlane Systems, a division of Conexant Systems
1.1 Organization url(s): www.netplane.com
2. Product title(s):
LTCS (Label Traffic Control System)- Optical and Classical, LTCS-LMP
2.1 Brief description(s):
3. Portable software protocol products which support multiple ietf
drafts and RFCs, and implementation agreements coming out of the OIF.
MPLS and GMPLS Signaling Products, which includes RSVP, LDP, CR-LDP,
OUNI. Also have LMP to support optical network requirements.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Sandra Herforth
3.2 Title: Sr. Product Manager
3.3 E-mail: sherforth@netplane.com
3.4 Organization/department: Marketing
3.5 Postal address: 200 Lowder Brook Drive, Westwood, MA 02090
3.6 Phone: 781-251-5363
3.7 Fax: 781-329-6703
----------------------------------------------------------------
4. Status:
4.1 [ ] Development
4.2 [ ] Alpha
4.3 [ ] Beta
4.4 [X] Product: All products listed above are released and are generally available.
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)
RFC 2205 Resource ReSerVation Protocol (RSVP)
RFC 2206 RSVP Management Information Base using SMIv2
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 2750 RSVP Extensions for Policy Control
RFC 2764 Framework for IP-based Virtual Private Networks
RFC 2961 RSVP Refresh Overhead Reduction Extensions
RFC 2997 Specification of the Null Service Type
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
RFC 3212 Contraint-Based LSP Setup using LDP
RFC 3213 Applicability Statement for CR-LDP
draft-ietf-ccamp-gmpls-architecture-02 Generalized Multi-Protocol Label Switching (GMPLS) Architecture
draft-ietf-mpls-generalized-signaling-04 Generalized MPLS-Signaling Functional Description
draft-ietf-mpls-generalized-rsvp-te-02 Generalized MPLS Signaling - RSVP-TE Extensions
draft-ietf-ccamp-gmpls-architecture-02 Generalized Multi-Protocol Label Switching (GMPLS) Architecture
draft-many-ccamp-gmpls-framework-00 A Framework for Generalized Multi-protocol Label Switching (GMPLS)
draft-ietf-mpls-rsvp-unnum-04 Signalling Unnumbered Links in RSVP-TE
draft-ietf-mpls-lsp-hierarchy-03 LSP Hierarchy with MPLS TE
draft-ietf-mpls-bundle-01 Link Bundling in MPLS Traffic Engineering
draft-ietf-ccamp-gmpls-sonet-sdh-02 GMPLS Extensions for SONET and SDH Control
draft-oetf-ccamp-gmpls-sonet-sdh-extensions GMPLS Extensions to Control Non-Standard SONET and SDH Features
draft-ietf-mpls-diff-ext-09 MPLS Support of Differentiated Services
draft-ietf-mpls-lsr-mib-07 Multiprotocol Label Switching (MPLS) LSR Management Information Base
draft-ietf-mpls-mpls-te-mib-06 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base
draft-ietf-mpls-ldp-mib-08 Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)
draft-ietf-mpls-ftn-mib-03 Multiprotocol Label Switching (MPLS) FEC-To-NHLFE (FTN) Management Information Base
draft-ietf-mpls-rsvp-lsp-tunnel-09 RSVP-TE: Extensions to RSVP for LSP Tunnels
draft-ietf-mpls-rsvp-tunnel-applicability-02 Applicability Statement for Extensions to RSVP for LSP-Tunnels
draft-ietf-mpls-cr-ldp-06 Constraint-Based LSP Setup using LDP
draft-ietf-mpls-crisp-modify-03 LSP Modification Using CR-LDP
draft-ietf-mpls-ldp-state-04 LDP State Machine
draft-ietf-mpls-tc-mib-02 Definition of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management
draft-martini-l2circuit-trans-mpls-08 Transport of Layer 2 Frames Over MPLS
draft-martini-l2-encap-mpls-04 Encapsulation Methods for Transport of Layer 2 Frames Over IP and MPLS Networks
draft-ietf-ppvpn-rfc2547bis-01 BGP/MPLS VPNs
draft-ietf-mpls-mgmt-overview Multiprotocol Label Switching (MPLS) Management Overview
draft-ietf-ipo-ason-02 Automatic Switched Optical Network (ASON) Architecture and Its Related Protocols
draft-ietf-ccamp-lmp-02 Link Management Protocol (LMP)
draft-fredette-lmp-wdm-03 Link Management Protocol (LMP) for DWDM Optical Line Systems
draft-ietf-ccamp-lmp-mib-00 Link Management Protocol Management Information Base Using SMIv2
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
All of NetPlane Systems' Implementations are based completely on
internally developed code. NetPlane owns all intellectual property
relating to its products and provides full indemnification against 3rd
party claims for possible future royalties, etc.
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, Guaranteed Service, and Null Service Type)
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 [ ] Errored Interface Identification
15.6 [X] Link Fault Handling
15.7 [X] Nodal Fault Handling
- Supported by Redundant and Distributed Product Packages
16. Other specification(s) which apply:
OIF UNI 1.0 Signaling Implementation Agreement, oif2000.125.7
ITU-T G.8080/Y.1304-Architecture and Specifications for Automatically
Switched Optical Network
ITU-T G.7713/Y.1704-Distributed Call and Connection Management
ITU-T G.7712/Y.1703-Architecture and Specification of Data Communication Network
17. Other features supported:
Support of Redundant Architectures to support Nodal and Control Plane Failure
Fault Tolerance (hot backup)
Flexible Software to support multiple types of distributed architectures
Bundled links
Non-associated (out of band) signaling
Graceful deletion
LSP hierarchy
Reverse LSPs
Diffserv
Resource Affinities
Wavelength Conversion Incapable
18. Currently-defined GMPLS signaling features not supported:
Generally support all GMPLS signaling requirements which are adequately
defined in the IETF drafts today. There are a few items like Graceful
Restart and Persistence which have IETF Drafts or industry solutions
which carriers are resistant to deploy in their current networks.
NetPlane is taking a measured approach to support more appropriate and
effective solutions. Fast Restart Link Bundling MIB is currently
supported by an Enterprise MIB which was developed to support an early
version of the Link Bundle MIB.
19. Notes (please describe purpose of project, give any information that
might be useful to those interested in developing or using GMPLS)
NetPlane's LTCS product line supports a unified code base which
(optionally) supports MPLS (RSVP-TE, LDP, CR-LDP), GMPLS (RSVP-TE) and
OIF O-UNI (RSVP-TE).It has been used a majority of OEMs for a wide range
of applications, including core optical network devices, where
scalability and high availability is a critical requirement, a variety
of optical "edge" devices where architectural flexibility, scalability
and performance are key, including support for O-UNI and it has been
field deployed in carrier networks for classical MPLS applications.
To fully support GMPLS applications, NetPlane also offers LMP.
Additionally NetPlane offers a full range of routing protocols,
including OSPF and BGP4. The OSPF implementation is complemented by
Traffic Engineering (TE) extensions and a Constrained Shortest Path
First (CSPF) engine to calculate explicit paths for both IP and optical
applications MPLS/GMPLS.
Provide Software Source code to many types of Network Equipment
Providers, NetPlane Systems has over 200 customers worldwide for all of
their products.
20. If you feel the above categories are not complete, add others which
will better describe your project:
=======================================================================
Person filling out this form:
Name: Sandra Herforth
E-mail: sherforth@netplane.com
Tel.: 781-251-5363
Title: Sr. Product Manager
Company: NetPlane Systems
Date prepared: April 3, 2002
2.15. Nippon Telegraph and Telephone Corporation
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Nippon Telegraph and Telephone Corporation
1.1 Organization url(s): http://www.onlab.ntt.co.jp/
2. Product title(s): HIKARI router
2.1 Brief description(s):
NTT's HIKARI router is an integrated GMPLS router
with L1/L2/L3 switching capabilities.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Satoru Okamoto
3.2 Title: Senior Research Engineer
3.3 E-mail: okamoto@exa.onlab.ntt.co.jp
3.4 Organization/department: NTT Network Innovation Laboratories
3.5 Postal address: 9-11 Midori-Cho 3-Chome, Musashino-shi,
Tokyo 180-8585 JAPAN
3.6 Phone: +81 422 59 4353
3.7 Fax: +81 422 59 6387
----------------------------------------------------------------
4. Status:
4.1 [X] Development
4.2 [ ] Alpha
4.3 [ ] Beta
4.4 [ ] Product
4.5 [ ] Other (describe):
5. Switching capabilities
[GMPLS- [GMPLS-
RSVP] LDP]
5.1 [X] [X] PSC
5.2 [ ] [ ] TDM
5.3 [X] [X] LSC
5.4 [ ] [ ] FSC
6. Reference Drafts (please list, include version numbers)
6.1 [RFC-3212]
6.2 [draft-ietf-mpls-generalized-rsvp-te-06.txt]
6.3 [draft-ietf-mpls-generalized-signaling-07.txt]
6.4 [draft-ietf-ccamp-ospf-gmpls-extensions-05.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
7.5 [X] SDH
7.6 [X] SONET
7.7 [X] Lambda (photonic)
7.8 [ ] Fiber
7.9 [ ] FiberChannel
7.10 [ ] Other (describe):
8. Availability
[GMPLS- [GMPLS-
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 [ ] [ ] Internal implementation
(no outside code, just from specs)
9.4 [X] [X] 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 [X] [X] MPLS Label
10.2 [X] [ ] Generalized Label
10.3 [X] [X] Waveband Label
10.4 [ ] [ ] SONET/SDH Label
11. Label Related
[GMPLS- [GMPLS-
RSVP] LDP]
11.1 [X] [ ] Suggested Label
11.2 [X] [ ] Label Set
12. Traffic Parameters
[GMPLS- [GMPLS-
RSVP] LDP]
12.1 [ ] Intserv (Please list which)
12.2 [X] CR-LDP
12.3 [X] [ ] GMPLS Bandwidth Encoding
12.4 [ ] [ ] SONET/SDH
13. Bidirectional LSPs
[GMPLS- [GMPLS-
RSVP] LDP]
[X] [X] Bidirectional LSPs
14. Notification
[GMPLS- [GMPLS-
RSVP] LDP]
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
[GMPLS- [GMPLS-
RSVP] LDP]
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:
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: Satoru Okamoto
E-mail: okamoto@exa.onlab.ntt.co.jp
Tel.: +81 422 59 4353
Title: Senior Research Engineer
Company: Nippon Telegraph and Telephone Corporation
Date prepared: 05/31/2002
2.16. Nortel Networks
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Nortel Networks 1. Organization: Nortel Networks
1.1 Organization url(s): www.nortelnetworks.com 1.1 Organization url(s): www.nortelnetworks.com
2. Product title(s): Automatic Switched Optical Networks (ASON) 2. Product title(s): Automatic Switched Optical Networks (ASON)
2.1 Brief description(s): optical control plane 2.1 Brief description(s): optical control plane
---------------------------------------------------------------- ----------------------------------------------------------------
3. Contact for GMPLS information 3. Contact for GMPLS information
3.1 Name: Don Fedyk 3.1 Name: Don Fedyk
skipping to change at page 49, line 5 skipping to change at page 65, line 35
Person filling out this form: Person filling out this form:
Name:Don Fedyk Name:Don Fedyk
E-mail:see above E-mail:see above
Tel.: Tel.:
Title: Title:
Company: Company:
Date prepared: Date prepared:
2.13. Tellium, Inc. 2.17. Tellium, Inc.
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Tellium, Inc. 1. Organization: Tellium, Inc.
1.1 Organization url(s): www.tellium.com 1.1 Organization url(s): www.tellium.com
2. Product title(s): Aurora Optical Switch, Aurora 128 2. Product title(s): Aurora Optical Switch, Aurora 128
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 52, line 5 skipping to change at page 68, line 30
===================================================================== =====================================================================
Person filling out this form: Same as above Person filling out this form: Same as above
Name: Name:
E-mail: E-mail:
Tel.: Tel.:
Title: Title:
Company: Company:
Date prepared: March 12, 2002 Date prepared: March 12, 2002
2.14. Tropic Networks Inc 2.18. Tropic Networks Inc
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Tropic Networks Inc 1. Organization: Tropic Networks Inc
1.1 Organization url(s): http://www.tropicnetworks.com 1.1 Organization url(s): http://www.tropicnetworks.com
2.1 Brief description(s): 2.1 Brief description(s):
The product is a switching device in the area of The product is a switching device in the area of
skipping to change at page 54, line 23 skipping to change at page 71, line 5
=============================================================== ===============================================================
Person filling out this form: Person filling out this form:
Name: Nabil Seddigh Name: Nabil Seddigh
E-mail: nseddigh@tropicnetworks.com E-mail: nseddigh@tropicnetworks.com
Tel.: 613-270-6936 Tel.: 613-270-6936
Company: Tropic Networks Company: Tropic Networks
Date prepared: March 13, 2002 Date prepared: March 13, 2002
2.15. Anonymous 1 2.19. Wipro Technologies
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Wipro Technologies
1.1 Organization url(s): www.wipro.com
2. Product title(s): Wipro MPLS stacks
2.1 Brief description(s):
WIP-MPLS product line offers GMPLS/MPLS control plane stacks:
GMPLS extension to CRLDP, GMPLS extension to RSVP-TE, LDP, CRLDP,
RSVP-TE and other related stacks.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Rana Pratap Sircar
3.2 Title: Architect
3.3 E-mail: rana.sircar@wipro.com
3.4 Organization/department: Wipro Technologies/Telecom and
Internetworking Solutions
3.5 Postal address: Wipro Technologies
No. 26, Hosur Main Road, Bomannahalli,
Bangalore - 560068
3.6 Phone: +91-80-5732296/3 ext 1040
3.7 Fax: +91-80-5732696 / 5732441
----------------------------------------------------------------
4. Status:
4.1 [X] Development
4.2 [ ] Alpha
4.3 [ ] Beta
4.4 [ ] Product
4.5 [ ] Other (describe):
5. Switching capabilities
[GMPLS- [GMPLS-
RSVP] LDP]
5.1 [X] [X] PSC
5.2 [X] [X] TDM
5.3 [ ] [ ] LSC
5.4 [ ] [ ] FSC
6. Reference Drafts (please list, include version numbers)
6.1 [draft-ietf-mpls-generalized-cr-ldp-05.txt]
6.2 [draft-ietf-mpls-generalized-signaling-07.txt]
6.3 [draft-ietf-ccamp-gmpls-architecture-02.txt]
6.4 [draft-ietf-mpls-generalized-rsvp-te-06.txt]
6.5 [RFC 2205 : RSVP ]
6.6 [RFC 3209 : RSVP-TE ]
6.7 [RFC 3212 : CR-LDP ]
6.8 [RFC 3214 : LSP Modification Using CR-LDP ]
7. Interface technologies
7.1 [X] 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 [ ] Lambda (photonic)
7.8 [ ] Fiber
7.9 [ ] FiberChannel
7.10 [ ] Other (describe):
8. Availability
[GMPLS- [GMPLS-
RSVP] LDP]
8.1 [ ] [ ] Public and free
8.2 [ ] [ ] Only to selected organizations/companies but free
8.3 [X] [X] On sale.
8.4 [ ] [ ] 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 [X] [X] MPLS Label
10.2 [X] [X] Generalized Label
10.3 [ ] [ ] Waveband Label
10.4 [X] [X] 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] CR-LDP
12.3 [X] [X] GMPLS Bandwidth Encoding
12.4 [X] [X] SONET/SDH
13. Bidirectional LSPs
[GMPLS- [GMPLS-
RSVP] LDP]
[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 [ ] [ ] Link Fault Handling
15.7 [ ] [ ] Nodal Fault Handling
16. Other specification(s) which apply: Contention Resolution supported
17. Other features supported:
17.1 related to [GMPLS-RSVP] A Node level Admission controller and Resource
Manager.
17.2 related to [GMPLS-LDP] A Node level Admission controller and Resource
Manager.
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)
Wipro Technologies offers a carrier-class GMPLS/MPLS protocol
stacks to OEM vendors. Our product line includes source code
architected, developed and tested in a well defined quality
framework.
20. If you feel the above categories are not complete, add others which
will better describe your project:
====================================================================
Person filling out this form:
Name: Chetan Kumar S
E-mail: chetan.kumar@wipro.com
Tel.: +91 80 5732296
Title: Protocol Specialist
Company: Wipro Technologies
Date prepared: 28-03-02 (dd-mm-yy)
2.20. Anonymous 1
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: ANONYMOUS 1. Organization: ANONYMOUS
1.1 Organization url(s): 1.1 Organization url(s):
2. Product title(s): 2. Product title(s):
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 58, line 5 skipping to change at page 78, line 17
17. Other features supported: 17. Other features supported:
18. Currently-defined GMPLS signaling features not supported: 18. Currently-defined GMPLS signaling features not supported:
19. Notes (please describe purpose of project, give any information that 19. Notes (please describe purpose of project, give any information that
might be useful to those interested in developing or using GMPLS) might be useful to those interested in developing or using GMPLS)
20. If you feel the above categories are not complete, add others which 20. If you feel the above categories are not complete, add others which
will better describe your project: will better describe your project:
2.16. Anonymous 2 2.21. Anonymous 2
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
4. Status: 4. Status:
4.1 [X] Development 4.1 [X] Development
4.2 [ ] Alpha 4.2 [ ] Alpha
4.3 [ ] Beta 4.3 [ ] Beta
4.4 [ ] Product 4.4 [ ] Product
4.5 [ ] Other (describe): 4.5 [ ] Other (describe):
skipping to change at page 60, line 5 skipping to change at page 80, line 19
17. Other features supported: 17. Other features supported:
18. Currently-defined GMPLS signaling features not supported: 18. Currently-defined GMPLS signaling features not supported:
19. Notes (please describe purpose of project, give any information that 19. Notes (please describe purpose of project, give any information that
might be useful to those interested in developing or using GMPLS) might be useful to those interested in developing or using GMPLS)
20. If you feel the above categories are not complete, add others which 20. If you feel the above categories are not complete, add others which
will better describe your project: will better describe your project:
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
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)
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 3. Acknowledgments
The survey form was derived from V2.2 of the "RSVP and QoS The survey form was derived from V2.2 of the "RSVP and QoS
Implementation Survey Information Form" authored by Gene Gaines Implementation Survey Information Form" authored by Gene Gaines
<ggaines@generation.net> and Marco Festa <festa@cefriel.it>. See <ggaines@generation.net> and Marco Festa <festa@cefriel.it>. See
http://www.iit.nrc.ca/IETF/RSVP_survey/rsvp-qos_quest_980210.txt. http://www.iit.nrc.ca/IETF/RSVP_survey/rsvp-qos_quest_980210.txt.
Scott Bradner, sob@harvard.edu, provided the "anonymous submission" Scott Bradner, sob@harvard.edu, provided the "anonymous submission"
service for this survey. service for this survey.
skipping to change at line 2855 skipping to change at line 3742
Movaz Networks, Inc. Movaz Networks, Inc.
7926 Jones Branch Drive 7926 Jones Branch Drive
Suite 615 Suite 615
McLean VA, 22102 McLean VA, 22102
Phone: +1 703 847-1801 Phone: +1 703 847-1801
Email: lberger@movaz.com Email: lberger@movaz.com
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
Email: yakov@juniper.net Email: yakov@juniper.net
Generated on: Tue Mar 19 10:33:48 2002
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/