draft-ietf-ccamp-gmpls-signaling-survey-02.txt   draft-ietf-ccamp-gmpls-signaling-survey-03.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: December 2002 Expiration Date: April 2003
June 2002 October 2002
Generalized MPLS Signaling - Implementation Survey Generalized MPLS Signaling - Implementation Survey
draft-ietf-ccamp-gmpls-signaling-survey-02.txt draft-ietf-ccamp-gmpls-signaling-survey-03.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,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 3, line ? skipping to change at page 2, line 8
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 the Generalized MPLS signaling documents. mechanisms specified in the Generalized MPLS signaling documents.
Other specifications and documents are listed if included in the Other specifications and documents are listed if included in the
submitted form. The survey form and latest version of this document submitted form. The survey form and latest version 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 ................................................ 8
2.1 AcceLight Networks .......................................... 7 2.1 AcceLight Networks .......................................... 8
2.2 Agilent Technologies ........................................ 12 2.2 Agilent Technologies ........................................ 13
2.3 Calient Networks ............................................ 15 2.3 Alcatel ..................................................... 16
2.4 Ciena Corporation ........................................... 20 2.4 Calient Networks ............................................ 22
2.5 Data Connection Ltd ......................................... 23 2.5 Ciena Corporation ........................................... 27
2.6 Equipe Communications Corp. ................................. 29 2.6 Data Connection Ltd ......................................... 30
2.7 Firstwave Intelligent Optical Networks ...................... 32 2.7 Equipe Communications Corp. ................................. 35
2.8 HCL Technologies Ltd., India ................................ 36 2.8 Firstwave Intelligent Optical Networks ...................... 39
2.9 Intel Corporation ........................................... 39 2.9 HCL Technologies Ltd., India ................................ 43
2.10 Japan Telecom Co., Ltd. ..................................... 42 2.10 Intel Corporation ........................................... 46
2.11 Juniper Networks ............................................ 47 2.11 Japan Telecom Co., Ltd. ..................................... 49
2.12 Lumentis AB ................................................. 50 2.12 Juniper Networks ............................................ 53
2.13 Marconi ..................................................... 53 2.13 Lumentis AB ................................................. 57
2.14 Movaz Networks .............................................. 56 2.14 Marconi ..................................................... 60
2.15 NetPlane Systems ............................................ 59 2.15 Movaz Networks .............................................. 63
2.16 Nippon Telegraph and Telephone Corporation .................. 64 2.16 NEC Corporation ............................................. 66
2.17 Nortel Networks ............................................. 67 2.17 NetPlane Systems ............................................ 70
2.18 Tellium, Inc. ............................................... 70 2.18 Nippon Telegraph and Telephone Corporation .................. 75
2.19 Tropic Networks Inc ......................................... 73 2.19 Nortel Networks ............................................. 79
2.20 Wipro Technologies .......................................... 76 2.20 Polaris Networks Inc ........................................ 82
2.21 Anonymous 1 ................................................. 79 2.21 Sycamore Networks Inc. ..................................... 86
2.22 Anonymous 2 ................................................. 83 2.22 Tellium, Inc. ............................................... 89
3 Acknowledgments ............................................. 85 2.23 Tropic Networks Inc ......................................... 92
4 Security Considerations ..................................... 85 2.24 Wipro Technologies .......................................... 94
5 IANA Considerations ......................................... 85 2.25 Anonymous 1 ................................................. 98
6 References .................................................. 85 3 Acknowledgments ............................................. 100
7 Editors' Addresses .......................................... 86 4 Security Considerations ..................................... 100
5 IANA Considerations ......................................... 101
6 References .................................................. 101
7 Editors' Addresses .......................................... 101
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 each response.**) Anonymous submissions were handled by Scott
Bradner, sob@harvard.edu. All identifying information was removed Bradner, sob@harvard.edu. All identifying information was removed
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 |Equip. |R S|Yes :n/a |P T L |M G S|F:F:P:P| | 2.1 |Equip. |R S|Yes :n/a |P T L |M G S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.2 |Tester |R S| :All |P T L F|M G W S|F:F:F:F| | 2.2 |Tester |R S| :All |P T L F|M G W S|F:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.3 |Equip. |R |Yes :TE | L F| G |P:F:P:P| | 2.3 |Equip. |R S|Yes :n/a | T L F| G W S|P:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.4 |Code |R S|Yes :n/a | T | S| :F: : | | 2.4 |Equip. |R |Yes :TE | L F| G |P:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.5 |Code |R S|Yes :GMPLS |P T L F|M G W S|F:F:P:P| | 2.5 |Code |R S|Yes :n/a | T | S| :F: : |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.6 |Equip. |R S| :All |P T | G S| :F:P: | | 2.6 |Code |R S|Yes :GMPLS |P T L F|M G W S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.7 |Code |R L | :All | L F| G W |F:F:F:F| | 2.7 |Equip. |R S| :All |P T | G S| :F:P: |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.8 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P| | 2.8 |Code |R L | :All | L F| G W |F:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.9 |Equip. |R S| :All |P T |M G S|P:F:F:P| | 2.9 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.10 |Code |R S| :All | n/a | G |P:F: :P| | 2.10 |Equip. |R S| :All |P T |M G S|P:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.11 |Equip. |R S| :All |P |M G S|P:F: :P| | 2.11 |Code |R S| :All | n/a | G |P:F: :P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.12 |Equip. |R |Yes :GMPLS | L | G | :F: : | | 2.12 |Equip. |R S| :All |P |M G S|P:F: :P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.13 |Equip. |R S| :All | T L F| G W S|P:F:F:F| | 2.13 |Equip. |R |Yes :GMPLS | L | G | :F: : |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.14 |Equip. |R S|LabN :GMPLS | L | G S|F:F:F:F| | 2.14 |Equip. |R S| :All | T L F| G W S|P:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.15 |Code |R S| :All |P T L F|M G W S|F:F:F:P| | 2.15 |Equip. |R S|LabN :GMPLS | T L F| G S|F:F:F:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.16 |Equip. |R S|Yes :n/a |P L |M G W |F:F:P:P| | 2.16 |Equip. |R S|Yes :n/a | T | S|F:F:P:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.17 |Code | L | n/a | n/a |M G W S|F:F:F: | | 2.17 |Code |R S| :All |P T L F|M G W S|F:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.18 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P| | 2.18 |Equip. |R S|Yes :n/a |P L |M G W |F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.19 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P| | 2.19 |Code | L | n/a | n/a |M G W S|F:F:F: |
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.20 |Code |R L | :All |P T |M G S|F:F:F:P| | 2.20 |Equip. |R S|Yes :n/a | T | S|P:F:P:F|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.21 |Unknown|R S|Yes :n/a | T L F| G W S|P:F:F:F| | 2.21 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+ +-----------+-------+-----+-----------------+-------+-------+-------+
| 2.22 |Unknown|R |Yes :n/a | L | G |P:F:P:P| | 2.22 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.23 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.24 |Code |R L | :All |P T |M G S|F:F:F:P|
+-----------+-------+-----+-----------------+-------+-------+-------+
| 2.25 |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 |
+==================================================================+ +==================================================================+
| 22 |Total participants | 25 |Total participants
| 21 | - |6. Reference Draft - [GMPLS-RSVP] | | 24 | - |6. Reference Draft - [GMPLS-RSVP] |
| - | 3 |6. Reference Draft - [GMPLS-LDP] | | - | 3 |6. Reference Draft - [GMPLS-LDP] |
| 17 |6. Reference Draft - [GMPLS-SONET] | | 20 |6. Reference Draft - [GMPLS-SONET] |
| 10 | 2 |5.1 Switching capabilities - PSC | | 10 | 2 |5.1 Switching capabilities - PSC |
| 12 | 1 |5.2 Switching capabilities - TDM | | 15 | 1 |5.2 Switching capabilities - TDM |
| 14 | 2 |5.3 Switching capabilities - LSC | | 15 | 2 |5.3 Switching capabilities - LSC |
| 9 | 1 |5.4 Switching capabilities - FSC | | 10 | 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 |
| 11 | 2 |9.3 Implementation based on - Internal | | 12 | 2 |9.3 Implementation based on - Internal |
| 12 | 1 |9.4 Implementation based on - Combination | | 15 | 1 |9.4 Implementation based on - Combination |
| 10 | 3 |10.1 MPLS Label | | 10 | 3 |10.1 MPLS Label |
| 21 | 3 |10.2 Generalized Label | | 22 | 3 |10.2 Generalized Label |
| 9 | 3 |10.3 Waveband Label | | 9 | 3 |10.3 Waveband Label |
| 15 | 2 |10.4 SONET/SDH Label | | 18 | 2 |10.4 SONET/SDH Label |
| 16 | 3 |11.1 Suggested Label | | 19 | 3 |11.1 Suggested Label |
| 13 | 3 |11.2 Label Set | | 15 | 3 |11.2 Label Set |
| 9 | - |12.1 Traffic Parameters - Intserv | | 10 | - |12.1 Traffic Parameters - Intserv |
| - | 6 |12.2 Traffic Parameters - CR-LDP | | - | 6 |12.2 Traffic Parameters - CR-LDP |
| 19 | 3 |12.3 GMPLS Bandwidth Encoding | | 21 | 3 |12.3 GMPLS Bandwidth Encoding |
| 15 | 2 |12.4 Traffic Parameters - SONET/SDH | | 18 | 2 |12.4 Traffic Parameters - SONET/SDH |
| 21 | 4 |13. Bidirectional LSPs | | 24 | 4 |13. Bidirectional LSPs |
| 10 | 3 |14.1 Acceptable Label Set | | 10 | 3 |14.1 Acceptable Label Set |
| 13 | - |14.2 Notify Request Objects | | 15 | - |14.2 Notify Request Objects |
| 15 | - |14.3 Notify Message | | 18 | - |14.3 Notify Message |
| 16 | - |14.4 Removing State with a PathErr message | | 19 | - |14.4 Removing State with a PathErr message |
| 14 | 2 |15.1 Explicit Label Control | | 17 | 2 |15.1 Explicit Label Control |
| 15 | 2 |15.2 Protection Information | | 17 | 2 |15.2 Protection Information |
| 14 | 2 |15.3 Administrative Status Information | | 17 | 2 |15.3 Administrative Status Information |
| 15 | 2 |15.4 Interface Identification | | 18 | 2 |15.4 Interface Identification |
| 13 | 2 |15.5 Errored Interface Identification | | 16 | 2 |15.5 Errored Interface Identification |
| 13 | 1 |15.6 Link Fault Handling | | 16 | 1 |15.6 Link Fault Handling |
| 11 | 1 |15.7 Nodal Fault Handling | | 13 | 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. AcceLight Networks 2.1. AcceLight Networks
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
skipping to change at page 7, line 36 skipping to change at page 8, line 36
switching photonic fabric (POS, GE, SONET/SDH), and the control switching photonic fabric (POS, GE, SONET/SDH), and the control
plane with GMPLS extensions. plane with GMPLS extensions.
The PXS 540 can be deployed as a classical MPLS LSR, Broadband TDM The PXS 540 can be deployed as a classical MPLS LSR, Broadband TDM
crossconect (BXC), and/or an opaque Optical crossconnect crossconect (BXC), and/or an opaque Optical crossconnect
(OXC). With service integration or any combination of functions (OXC). With service integration or any combination of functions
can also be configured such as BXC+OXC, MPLS LSR+OXC, MPLS+BXC or can also be configured such as BXC+OXC, MPLS LSR+OXC, MPLS+BXC or
MPLS LSR+BXC+OXC. MPLS LSR+BXC+OXC.
---------------------------------------------------------------- ----------------------------------------------------------------
3. Contact for GMPLS information 3. Contact for GMPLS information
3.1 Name: Johnson Kuruvila 3.1 Name: Debashis Basak
3.2 Title: Lead Engineer 3.2 Title: Lead Engineer
3.3 E-mail: johnson@accelight.com 3.3 E-mail: dbasak@accelight.com
3.4 Organization/department: 3.4 Organization/department: Software - Routing & Signaling
3.5 Postal address: 3.5 Postal address: 70 Abele Rd, Suite 1200, Bridgeville, PA 15017
26 Auriga Dr, Ottawa, ON, Canada K2E 8B7
3.6 Phone: 613-596-4804 3.6 Phone: 412-220-2102 x 115
3.7 Fax: 613-596-2399 3.7 Fax: 412-220-2450
---------------------------------------------------------------- ----------------------------------------------------------------
4. Status: 4. Status:
4.1 [ ] Development 4.1 [ ] Development
4.2 [ ] Alpha 4.2 [ ] Alpha
4.3 [X] Beta 4.3 [X] Beta
4.4 [ ] Product 4.4 [ ] Product
4.5 [ ] Other (describe): 4.5 [ ] Other (describe):
5. Switching capabilities 5. Switching capabilities
skipping to change at page 15, line 29 skipping to change at page 16, line 29
Person filling out this form: Person filling out this form:
Name: Cary Wright Name: Cary Wright
E-mail: cary_wright@agilent.com E-mail: cary_wright@agilent.com
Tel.: +61-3-9210-5843 Tel.: +61-3-9210-5843
Title: R&D Project Manager Title: R&D Project Manager
Company: Agilent Technologies Company: Agilent Technologies
Date prepared: 8 March 2002 Date prepared: 8 March 2002
2.3. Calient Networks 2.3. Alcatel
GMPLS Signaling Implementation Survey Form
1. Organization: Alcatel
1.1 Organization url(s): www.alcatel.com
------------------------------------------------------------
2. Product title(s): Alcatel Lambda Gate with Generalized
Multiprotocol Routing Engine (GMRE)
2.1 Brief description(s): The Lambda Gate family, which supports
crossconnects on SDH/SONET and OTH, provides with the GMRE the
GMPLS functionality in networks.
------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Gert Grammel
Stefan Ansorge
Papadimitriou Dimitri
3.2 Title:
3.3 E-mail: gert.grammel@netit.alcatel.it
stefan.ansorge@alcatel.de
dimitri.papadimitriou@alcatel.be
3.4 Organization/department: Alcatel TND
Alcatel Optical NA
3.5 Postal address: Via Trento 30,
I-20059 Vimercate, Italy
Lorenzstrasse, 10
70435 Stuttgart, Germany
Francis Wellesplein, 1
B-2018 Antwerpen, Belgium
3.6 Phone: +39 039 686 7060
+49 7 11 821 33744
+32 3 240 8491
3.7 Fax:
------------------------------------------------------------
4. Status:
4.1 [ ] Development
4.2 [x] Alpha (Supercom 2002 Demo)
4.3 [x] Beta (End 2002)
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 RFC2208 - Resource Reservation Protocol Applicability Statement
6.3 RFC2961 - RSVP Summary Refresh and bundling, April 2001
6.4 RFC3209 - RSVP extensions for Tunnel Setup, December 2001
6.5 RFC3210 - Applicability statement for the extensions to RSVP
for LSP Tunnels
6.6 Draft-ietf-ccamp-gmpls-architecture-02.txt
- Generalized Multi-Protocol Label Switching (GMPLS)
Architecture
6.7 Draft-ietf-mpls-generalized-signaling-07.txt
- Generalized MPLS - Signaling Functional Description
6.8 Draft-ietf-mpls-generalized-rsvp-te-06.txt
- Generalized MPLS Signaling - RSVP-TE Extensions
6.9 Draft-ietf-mpls-rsvp-unnum-04.txt
- Signalling Unnumbered Links in RSVP-TE
6.10 Draft-ietf-ccamp-gmpls_sonet-sdh-03.txt
- Generalized MPLS extensions for SDH/SONET Network Control
6.11 Draft-ietf-mpls-bundle-01.txt
- Link Bundling in MPLS Traffic Engineering
6.12 RFC2328 - OSPF Version 2, April 1998
6.13 RFC2370 - Opaque LSA Types, July 1998
6.14 Draft-katz-yeung-ospf-traffic-06.txt
- Traffic Engineering Extensions to OSPF
6.15 Drat-ccamp-opsf-gmpls-extensions-04.txt
- OSPF Extensions in Support of Generalized MPLS
6.16 Draft-mannie-ccamp-gmpls-sonet-sdh-ospf-isis-00.txt
- Extensions to OSPF and IS-IS for GMPLS for SDH/SONET
Control
------------------------------------------------------------
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
7.8 [x] Fiber (future)
7.9 [x] FiberChannel (future)
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 [x] 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 (future)
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 2748 - The COPS (Common Open Policy Service) Protocol
16.2 RFC 2749 - COPS usage for RSVP
16.3 RFC 2753 - A Framework for Policy-based Admission Control
16.4 draft-ietf-rap-new-rsvpext-00.txt - RSVP Extension for Policy
Control
- SNMP -
16.5 RFC 2571 - An architecture for Describing SNMP Management
Frameworks
16.6 RFC 2574 - User-based Security Model (USM) for version 3 of the
Simple
Network Management Protocol (SNMPv3)
16.7 RFC 2575 - Viewer-based Access Control Model (VACM) for the
Simple
Network Management Protocol (SNMP)
16.8 RFC2863 - The Interfaces Group MIB
16.9 draft-nadeau-ccamp-gmpls-label-mib-01.txt
- Generalized Multiprotocol Label Switching (GMPLS) Label
Management
Information Base
16.10 draft-nadeau-ccamp-gmpls-lsr-mib-01.txt
- Generalized Multiprotocol Label Switching (GMPLS) Label
Switching
Router Management Information Base
16.11 draft-nadeau-ccamp-gmpls-tc-mib-01.txt
- Definition of Textual Conventions and OBJECT-IDENTITIES
for
Generalized Multiprotocol Label Switching (GMPLS)
Management
16.12 draft-nadeau-ccamp-gmpls-te-mib-01.txt
- Generalized Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base
16.13 draft-ietf-ospf-mib-update-05.txt, November 2000
- OSPFv2 Management Information Base
16.14 RFC2206, September 1997
- RSVP Management Information Base using SMIv2
16.15 draft-ietf-mpls-tc-mib-03.txt, December 2001
- Definition of Textual Conventions and OBJECT-IDENTITIES
for Multi-Protocol Label Switching (MPLS) Management
16.16 draft-ietf-mpls-te-mib-08.txt, December 2001
- MPLS Traffic Engineering Management Information Base Using
SMIv2
16.17 draft-ietf-mpls-bundle-mib-00.txt, September 2001.
- Link Bundling Management Information Base Using SMIv2
16.18 draft-ietf-tewg-mib-01.txt, October 2001
- Traffic Engineering MIB
- LMP -
16.19 draft-ietf-ccamp-lmp-03.txt
- Link Management Protocol (v1)
16.20 draft-ietf-ccamp-lmp-mib-01.txt
- Link Management Protocol Management Information Base
Using
SMIv2
- OIF -
16.21 User Network Interface (UNI) 1.0 Signaling Specification -
OIF October'01
------------------------------------------------------------
17. Other features supported:
17.1 OIF-UNI - GMPLS Interworking
17.2 Out of Band Signaling
17.3 Graceful Deletion
------------------------------------------------------------
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:
------------------------------------------------------------
2.4. Calient Networks
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: Calient Networks 1. Organization: Calient Networks
1.1 Organization url(s): http://www.calient.net 1.1 Organization url(s): http://www.calient.net
2. Product title(s): DiamondWave Photonic Switch 2. Product title(s): DiamondWave Photonic Switch
2.1 Brief description(s): MEMS-based photonic switch, leveraging 2.1 Brief description(s): MEMS-based photonic switch, leveraging
skipping to change at page 20, line 12 skipping to change at page 27, line 5
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.4. Ciena Corporation 2.5. Ciena Corporation
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Ciena Corporation 1. Organization: Ciena Corporation
1.1 Organization url(s): www.ciena.com 1.1 Organization url(s): www.ciena.com
2. Product title(s): MetroDirector, CoreDirector 2. Product title(s): MetroDirector, CoreDirector
2.1 Brief description(s): Metro and core optical switches with STS-1 2.1 Brief description(s): Metro and core optical switches with STS-1
skipping to change at page 23, line 38 skipping to change at page 30, line 31
Person filling out this form: Person filling out this form:
Name: as above Name: as above
E-mail: E-mail:
Tel.: Tel.:
Title: Title:
Company: Company:
Date prepared: March 22, 2002 Date prepared: March 22, 2002
2.5. Data Connection Ltd 2.6. 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):
skipping to change at page 29, line 5 skipping to change at page 35, line 42
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.6. Equipe Communications Corp. 2.7. Equipe Communications Corp.
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Equipe Communications Corp. 1. Organization: Equipe Communications Corp.
1.1 Organization url(s): www.equipecom.com 1.1 Organization url(s): www.equipecom.com
2. Product title(s): E3200 2. Product title(s): E3200
2.1 Brief description(s): O-UNI implementation for Multi-service 2.1 Brief description(s): O-UNI implementation for Multi-service
switch switch
---------------------------------------------------------------- ----------------------------------------------------------------
3. Contact for GMPLS information 3. Contact for GMPLS information
3.1 Name: Nik Langrind 3.1 Name: Nik Langrind
3.2 Title: Prin SW Eng 3.2 Title: Prin SW Eng
skipping to change at page 32, line 27 skipping to change at page 39, line 16
Person filling out this form: Person filling out this form:
Name: Nik Langrind Name: Nik Langrind
E-mail: nik@equipecom.com E-mail: nik@equipecom.com
Tel.: (978) 795-2012 Tel.: (978) 795-2012
Title: Prin SW Eng Title: Prin SW Eng
Company: Equipe Communications Corp Company: Equipe Communications Corp
Date prepared: 5/30/02 Date prepared: 5/30/02
2.7. Firstwave Intelligent Optical Networks 2.8. 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 36, line 9 skipping to change at page 43, line 5
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.8. HCL Technologies Ltd., India 2.9. 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 39, line 39 skipping to change at page 46, line 31
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.9. Intel Corporation 2.10. 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 42, line 40 skipping to change at page 49, line 33
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.10. Japan Telecom Co., Ltd. 2.11. 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
skipping to change at page 47, line 5 skipping to change at page 53, line 41
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.11. Juniper Networks 2.12. 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):
This implementation aims at being able to dynamically signal This implementation aims at being able to dynamically signal
generalized LSPs initiated by the router, across an optical core. It generalized LSPs initiated by the router, across an optical core. It
uses RSVP for signaling. The initial focus is on the signaling uses RSVP for signaling. The initial focus is on the signaling
aspects rather than routing in a GMPLS domain. The purpose is to aspects rather than routing in a GMPLS domain. The purpose is to
come up with an interoperable signaling solution and then move come up with an interoperable signaling solution and then move
forward. The attributes for the label-switched path (encoding type, forward. The attributes for the label-switched path (encoding type,
bandwidth, switching type; etc) will be configurable on the router, bandwidth, switching type; etc) will be configurable on the router,
and will be translated into an appropriate RSVP signaling and will be translated into an appropriate RSVP signaling
skipping to change at page 50, line 4 skipping to change at page 56, line 39
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:
** Control channel separation ** Control channel separation
** Refresh reduction ** Refresh reduction
==================================================================== ====================================================================
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.12. Lumentis AB 2.13. 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 53, line 4 skipping to change at page 59, line 42
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:
============================================================== ==============================================================
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.13. Marconi 2.14. 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 56, line 5 skipping to change at page 63, 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.14. Movaz Networks 2.15. 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 57, line 5 skipping to change at page 64, line 5
4. Status: 4. Status:
4.1 [ ] Development 4.1 [ ] Development
4.2 [ ] Alpha 4.2 [ ] Alpha
4.3 [ ] Beta 4.3 [ ] Beta
4.4 [x] Product 4.4 [x] Product
Swi [ ] Other (describe): Swi [ ] Other (describe):
5. Switching capabilities 5. Switching capabilities
5.1 [ ] PSC 5.1 [ ] PSC
5.2 [ ] TDM 5.2 [x] TDM
5.3 [x] LSC 5.3 [x] LSC
5.4 [ ] FSC 5.4 [x] FSC
6. Reference Drafts (please list, include version numbers) 6. Reference Drafts (please list, include version numbers)
6.1 draft-ietf-mpls-generalized-signaling-07.txt 6.1 draft-ietf-mpls-generalized-signaling-07.txt
6.2 draft-ietf-mpls-generalized-rsvp-te-06.txt 6.2 draft-ietf-mpls-generalized-rsvp-te-06.txt
6.3 draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 6.3 draft-ietf-ccamp-gmpls-sonet-sdh-03.txt
6.4 RFC3209 6.4 RFC3209
6.5 RFC2961 6.5 RFC2961
6.6 RFC2205 6.6 RFC2205
6.7 draft-nadeau-ccamp-gmpls-tc-mib-01.txt 6.7 draft-nadeau-ccamp-gmpls-tc-mib-01.txt
6.8 draft-nadeau-ccamp-gmpls-te-mib-01.txt 6.8 draft-nadeau-ccamp-gmpls-te-mib-01.txt
Interface technologies Interface technologies
7.1 [ ] Frame Relay 7.1 [ ] Frame Relay
7.2 [ ] ATM 7.2 [ ] ATM
7.3 [ ] Ethernet V2/DIX 7.3 [ ] Ethernet V2/DIX
7.4 [ ] Ethernet 802.3 7.4 [ ] Ethernet 802.3
7.5 [x] SDH 7.5 [x] SDH
7.6 [x] SONET 7.6 [x] SONET
7.7 [x] Lambda (photonic) 7.7 [x] Lambda (photonic)
7.8 [ ] Fiber 7.8 [x] Fiber
7.9 [ ] FiberChannel 7.9 [ ] FiberChannel
7.10 [x] Other (describe): 7.10 [x] Other (describe):
GigEthernet GigEthernet
8.1 [ ] Public and free 8.1 [ ] Public and free
8.2 [ ] Only to selected organizations/companies but free 8.2 [ ] Only to selected organizations/companies but free
8.3 [x] On sale. 8.3 [x] On sale.
8.4 [ ] For internal company use only 8.4 [ ] For internal company use only
8.5 [ ] Other: 8.5 [ ] Other:
skipping to change at page 59, line 12 skipping to change at page 66, 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.15. NetPlane Systems 2.16. NEC Corporation
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization:
NEC Corporation
1.1 Organization url(s):
www.nec.com
2. Product title(s):
SpectralWave Networking Software for U-Node, DWDM
2.1 Brief description(s):
SpectralWave family supports crossconnects on SDH/SONET and wavelength
multiplexing for metro and core network with GMPLS/ASON based control
plane.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name:
Su-Hun YUN
3.2 Title:
Assistant Manager
3.3 E-mail:
s-yun@bl.jp.nec.com
3.4 Organization/department:
Systems Development Department
First Optical Network Division
3.5 Postal address:
1753 Shimonumabe Nakahara-ku
Kawasaki, 211-8666, Japan
3.6 Phone:
+81 44 396 3247
3.7 Fax:
+81 44 435 5161
----------------------------------------------------------------
4. Status:
4.1 [ ] Development
4.2 [ ] Alpha
4.3 [X] Beta
4.4 [X] 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-08.txt
6.2 [X] draft-ietf-mpls-generalized-rsvp-te-07.txt
6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-05.txt
6.4 [X] draft-ietf-mpls-rsvp-unnum-02.txt
6.5 [X] draft-ietf-mpls-bundle-03.txt
6.6 [X] draft-ietf-mpls-lmp-02.txt
6.7 [X] draft-ietf-ccamp-gmpls-routing-04.txt
6.8 [X] draft-ietf-ccamp-ospf-gmpls-extensions-07.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 [ ] 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] [ ] 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 [X] [ ] 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:
(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 [X] [ ] Suggested Label
11.2 [X] [ ] Label Set
12. Traffic Parameters
[GMPLS- [GMPLS-
RSVP] LDP]
12.1 [ ] Intserv (Please list which)
12.2 [ ] CR-LDP
12.3 [X] [ ] 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 [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:
17.1 related to [GMPLS-RSVP]
OIF UNI 1.0 is supported.
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:
As a part of SpectralWave Networking Software, SepctralWave Control
Plane fully controls SpectralWave DWDM and U-Node by interacting with
SpectralWave Manager (NMS) and SpectralWave Planning Tool.
====================================================================
Person filling out this form:
Name: Su-Hun YUN
E-mail: s-yun@bl.jp.nec.com
Tel.: +81 44 396 3247
Title: Assistant Manager
Company: NEC Corporation
Date prepared: Sep. 20, 2002
2.17. NetPlane Systems
GMPLS Signaling Implementation Survey Form [V 1.0] GMPLS Signaling Implementation Survey Form [V 1.0]
1. Organization: NetPlane Systems, a division of Conexant Systems 1. Organization: NetPlane Systems, a division of Conexant Systems
1.1 Organization url(s): www.netplane.com 1.1 Organization url(s): www.netplane.com
2. Product title(s): 2. Product title(s):
LTCS (Label Traffic Control System)- Optical and Classical, LTCS-LMP LTCS (Label Traffic Control System)- Optical and Classical, LTCS-LMP
skipping to change at page 64, line 16 skipping to change at page 75, line 25
======================================================================= =======================================================================
Person filling out this form: Person filling out this form:
Name: Sandra Herforth Name: Sandra Herforth
E-mail: sherforth@netplane.com E-mail: sherforth@netplane.com
Tel.: 781-251-5363 Tel.: 781-251-5363
Title: Sr. Product Manager Title: Sr. Product Manager
Company: NetPlane Systems Company: NetPlane Systems
Date prepared: April 3, 2002 Date prepared: April 3, 2002
2.16. Nippon Telegraph and Telephone Corporation 2.18. Nippon Telegraph and Telephone Corporation
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Nippon Telegraph and Telephone Corporation 1. Organization: Nippon Telegraph and Telephone Corporation
1.1 Organization url(s): http://www.onlab.ntt.co.jp/ 1.1 Organization url(s): http://www.onlab.ntt.co.jp/
2. Product title(s): HIKARI router 2. Product title(s): HIKARI router
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 67, line 42 skipping to change at page 79, line 5
Person filling out this form: Person filling out this form:
Name: Satoru Okamoto Name: Satoru Okamoto
E-mail: okamoto@exa.onlab.ntt.co.jp E-mail: okamoto@exa.onlab.ntt.co.jp
Tel.: +81 422 59 4353 Tel.: +81 422 59 4353
Title: Senior Research Engineer Title: Senior Research Engineer
Company: Nippon Telegraph and Telephone Corporation Company: Nippon Telegraph and Telephone Corporation
Date prepared: 05/31/2002 Date prepared: 05/31/2002
2.17. Nortel Networks 2.19. 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 70, line 35 skipping to change at page 82, line 5
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.18. Tellium, Inc. 2.20. Polaris Networks Inc
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Polaris Networks Inc.
1.1 Organization url(s): www.polarisnetworks.com
2. Product title(s): OMX
2.1 Brief description(s):
The OMX is a Terabit-scalable optical transport
switch that combines the functions of SONET ADM
with a Wideband, Broadband and Super-broadband
Digital Cross-connect System (DCS) in a single
consolidated footprint. The control plane on the
OMX is IP and GMPLS based to support the end-to-end
provisioning of services.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Dean Cheng
3.2 Title: Principal Network Architect
3.3 E-mail: dcheng@polarisnetworks.com
3.4 Organization/department: Architecture
3.5 Postal address:
6810 Santa Teresa Bl., San Jose CA 95119
3.6 Phone: (408) 284-8061
3.7 Fax: (408) 281-7463
---------------------------------------------------------------
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 [ ] [ ] PSC
5.2 [x] [ ] TDM
5.3 [ ] [ ] LSC
5.4 [ ] [ ] FSC
6. Reference Drafts (please list, include version numbers)
6.1 [x] RFC 2328 OSPF v2
6.2 [x] RFC 2370 OSPF Opaque LSA
6.3 [x] draft-katz-yeung-ospf-traffic-06.txt
6.4 [x] draft-ietf-ccamp-gmpls-routing-04.txt
6.5 [x] draft-ietf-ccamp-gmpls-ospf-gmpls-extensions-07.txt
6.6 [x] RFC 2205 RSVP
6.7 [x] RFC 3209 Traffic Engineering Extensions to RSVP
6.8 [x] draft-ietf-mpls-generalized-signaling-07.txt
6.9 [x] draft-ietf-mpls-generalized-rsvp-te-06.txt
6.10 [x] draft-ietf-ccamp-gmpls-sonet-sdh-05.txt
6.11 [x] draft-ietf-mpls-rsvp-unnum-06.txt
6.12 [x] draft-ietf-mpls-bundle-03.txt
6.13 [x] draft-ietf-ccamp-lmp-02.txt
6.14 [x] RFC 2784 GRE
6.14 [x] RFC 1661 PPP in HDLC-like Framing
6.15 [x] RFC 1662 PPP
6.16 [x] RFC 1332 IPCP
7. Interface technologies
7.1 [ ] Frame Relay
7.2 [ ] ATM
7.3 [x] Ethernet V2/DIX
7.4 [x] Ethernet 802.3
7.5 [ ] 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 [x] [ ] 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 [x] [ ] 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 [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:
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: Same as above.
E-mail:
Tel.:
Title:
Company:
Date prepared: 9/16/2002
2.21. Sycamore Networks Inc.
GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Sycamore Networks Inc.
1.1 Organization url(s): www.sycamorenetworks.com
2. Product title(s): SN 3000 optical switch, SN 16000 optical switch
2.1 Brief description(s):
Metro and core optical switches with STS-1 level granularity, integrated
routing, signaling and management software. GMPLS is implemented using
the IETF CCAMP Working Group Internet Drafts in order to support
standards-based compatibility and provide the foundation for
multi-vendor interoperability. Validated multiple GMPLS
interoperability configurations (peer, overlay, hybrid) during the MPLS
Forum-sponsored GMPLS testing activity conducted at University of New
Hampshire InterOperability Lab, September 30 - October 4, 2002.
Testing included signaling (RSVP-TE) and control plane interoperability
with multiple (edge LSR) devices from vendors including Cisco, Juniper,
Agilent, Data Connection Ltd., NetTest, and NetPlane.
----------------------------------------------------------------
3. Contact for GMPLS information
3.1 Name: Tom DiMicelli
3.2 Title: Senior Product Manager
3.3 E-mail: tdimicelli@sycamorenet.com
3.4 Organization/department: Product Management/Network Switching
3.5 Postal address: 220 Mill Road, Chelmsford, MA
3.6 Phone: 978-367-7978
3.7 Fax: 978-250-9207
----------------------------------------------------------------
4. Status:
4.1 [ ] Development
4.2 [] Alpha
4.3 [X] Beta
4.4 [ ] Product
4.5 [ ] Other (describe):
5. Switching capabilities
[GMPLS- RSVP] [GMPLS-LDP]
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 [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-02.txt
6.4 [X] draft-iwata-mpls-crankback-00.txt
6.5 [X] draft-pan-mpls-restart-01.txt
Drafts implemented as part of the October 2002 UNH and NGN GMPLS interoperability testing and demonstration:
. draft-ietf-mpls-generalized-signaling-08.txt
. draft-ietf-mpls-generalized-rsvp-te-07.txt
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-RSVP] [GMPLS- LDP]
8.1 [ ] [ ] Public and free
8.2 [X] [ ] 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)
[GMPLS-RSVP] [GMPLS-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-RSVP] [GMPLS-LDP]
10.1 [ ] [ ] MPLS Label
10.2 [X] [ ] Generalized Label
10.3 [ ] [ ] Waveband Label
10.4 [X] [ ] SONET/SDH Label
11. Label Related
[GMPLS-RSVP] [GMPLS-LDP]
11.1 [X] [ ] Suggested Label
11.2 [X] [ ] Label Set
12. Traffic Parameters
[GMPLS-RSVP] [GMPLS-LDP]
12.1 [X] Intserv (Please list which)
12.2 [ ] CR-LDP
12.3 [ ] [ ] GMPLS Bandwidth Encoding
12.4 [X] [ ] SONET/SDH
13. Bidirectional LSPs
[GMPLS-RSVP] [GMPLS-LDP]
[X] [ ] Bidirectional LSPs
14. Notification
[GMPLS-RSVP] [GMPLS-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-RSVP] [GMPLS-LDP]
15.1 [X] [ ] Explicit Label Control
15.2 [ ] [ ] 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:
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:
Sycamore is actively engaged in the investigation and development of a variety of additional GMPLS protocols, including OSPF-TE, LMP; as well as strategies for implementing protection and restoration mechanisms.
Parallel to our interoperability activities with GMPLS, Sycamore continues to actively participate in and monitor standards development activities within the OIF and ITU-T.
2.22. 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 73, line 30 skipping to change at page 92, line 16
===================================================================== =====================================================================
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.19. Tropic Networks Inc 2.23. 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 76, line 5 skipping to change at page 94, line 37
=============================================================== ===============================================================
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.20. Wipro Technologies 2.24. Wipro Technologies
GMPLS Signaling Implementation Survey Form [V 1.1] GMPLS Signaling Implementation Survey Form [V 1.1]
1. Organization: Wipro Technologies 1. Organization: Wipro Technologies
1.1 Organization url(s): www.wipro.com 1.1 Organization url(s): www.wipro.com
2. Product title(s): Wipro MPLS stacks 2. Product title(s): Wipro MPLS stacks
2.1 Brief description(s): 2.1 Brief description(s):
skipping to change at page 79, line 41 skipping to change at page 98, line 28
Person filling out this form: Person filling out this form:
Name: Chetan Kumar S Name: Chetan Kumar S
E-mail: chetan.kumar@wipro.com E-mail: chetan.kumar@wipro.com
Tel.: +91 80 5732296 Tel.: +91 80 5732296
Title: Protocol Specialist Title: Protocol Specialist
Company: Wipro Technologies Company: Wipro Technologies
Date prepared: 28-03-02 (dd-mm-yy) Date prepared: 28-03-02 (dd-mm-yy)
2.21. Anonymous 1 2.25. 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:
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.
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
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:
2.22. 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 85, line 41 skipping to change at page 101, line 13
This document does not address any security issues. This document does not address any security issues.
5. IANA Considerations 5. IANA Considerations
No parameters are defined in this document. No parameters are defined in this document.
6. References 6. References
[GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - [GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling -
CR-LDP Extensions", Internet Draft, CR-LDP Extensions", Internet Draft,
draft-ietf-mpls-generalized-cr-ldp-05.txt, draft-ietf-mpls-generalized-cr-ldp-07.txt,
November 2001. August 2002.
[GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - [GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling -
RSVP-TE Extensions", Internet Draft, RSVP-TE Extensions", Internet Draft,
draft-ietf-mpls-generalized-rsvp-te-06.txt, draft-ietf-mpls-generalized-rsvp-te-09.txt,
November, 2001. October 2002.
[GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS - [GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS -
Signaling Functional Description", Internet Draft, Signaling Functional Description", Internet Draft,
draft-ietf-mpls-generalized-signaling-07.txt, draft-ietf-mpls-generalized-signaling-09.txt,
November 2001. August 2002.
[GMPLS-SONET] Ashwood-Smith, P. et al, "GMPLS - SONET / SDH Specifics", [GMPLS-SONET] Ashwood-Smith, P. et al, "GMPLS - SONET / SDH Specifics",
Internet Draft, draft-ietf-ccamp-gmpls-sonet-sdh-03.txt, Internet Draft, draft-ietf-ccamp-gmpls-sonet-sdh-03.txt,
April, 2001. April, 2001.
7. Editors' Addresses 7. Editors' Addresses
Lou Berger Lou Berger
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: Thu Jun 20 16:56:23 2002 Generated on: Mon Oct 28 08:21:34 2002
 End of changes. 

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