idnits 2.17.1 draft-ietf-ccamp-gmpls-signaling-survey-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 197 instances of too long lines in the document, the longest one being 142 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1912 has weird spacing: '... stack as we...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2002) is 7863 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'X' is mentioned on line 4570, but not defined == Missing Reference: 'RFC-3212' is mentioned on line 3453, but not defined == Missing Reference: 'GMPLS- RSVP' is mentioned on line 3947, but not defined == Missing Reference: 'GMPLS- LDP' is mentioned on line 3977, but not defined == Outdated reference: A later version (-08) exists of draft-ietf-ccamp-gmpls-sonet-sdh-03 Summary: 7 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Lou Berger (Movaz) - Editor 2 Internet Draft Yakov Rekhter (Juniper) - Editor 3 Expiration Date: April 2003 5 October 2002 7 Generalized MPLS Signaling - Implementation Survey 9 draft-ietf-ccamp-gmpls-signaling-survey-03.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, 16 and its working groups. Note that other groups may also distribute 17 working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as "work in progress." 24 To view the current status of any Internet-Draft, please check the 25 "1id-abstracts.txt" listing contained in an Internet-Drafts Shadow 26 Directory, see http://www.ietf.org/shadow.html. 28 Abstract 30 This document provides a survey of GMPLS signaling implementations. 31 The primary focus of this survey are the signaling protocol 32 mechanisms specified in the Generalized MPLS signaling documents. 33 Other specifications and documents are listed if included in the 34 submitted form. The survey form and latest version of this document 35 are available from http://www.labn.net/gmpls-survey. 37 Contents 39 1 Survey Summary .............................................. 3 40 2 Survey Forms ................................................ 8 41 2.1 AcceLight Networks .......................................... 8 42 2.2 Agilent Technologies ........................................ 13 43 2.3 Alcatel ..................................................... 16 44 2.4 Calient Networks ............................................ 22 45 2.5 Ciena Corporation ........................................... 27 46 2.6 Data Connection Ltd ......................................... 30 47 2.7 Equipe Communications Corp. ................................. 35 48 2.8 Firstwave Intelligent Optical Networks ...................... 39 49 2.9 HCL Technologies Ltd., India ................................ 43 50 2.10 Intel Corporation ........................................... 46 51 2.11 Japan Telecom Co., Ltd. ..................................... 49 52 2.12 Juniper Networks ............................................ 53 53 2.13 Lumentis AB ................................................. 57 54 2.14 Marconi ..................................................... 60 55 2.15 Movaz Networks .............................................. 63 56 2.16 NEC Corporation ............................................. 66 57 2.17 NetPlane Systems ............................................ 70 58 2.18 Nippon Telegraph and Telephone Corporation .................. 75 59 2.19 Nortel Networks ............................................. 79 60 2.20 Polaris Networks Inc ........................................ 82 61 2.21 Sycamore Networks Inc. ..................................... 86 62 2.22 Tellium, Inc. ............................................... 89 63 2.23 Tropic Networks Inc ......................................... 92 64 2.24 Wipro Technologies .......................................... 94 65 2.25 Anonymous 1 ................................................. 98 66 3 Acknowledgments ............................................. 100 67 4 Security Considerations ..................................... 100 68 5 IANA Considerations ......................................... 101 69 6 References .................................................. 101 70 7 Editors' Addresses .......................................... 101 72 1. Survey Summary 74 This document is a compilation of responses to the GMPLS Signaling 75 implementation form found at http://www.labn.net/gmpls-survey/sig- 76 survey.txt. After a brief summary, each response in it's entirety is 77 listed. (**The editors, make no claim as to the accuracy of the 78 information provided nor do they endorse the statements made within 79 each response.**) Anonymous submissions were handled by Scott 80 Bradner, sob@harvard.edu. All identifying information was removed 81 prior to these submissions being forwarded to the editors. 82 Generalized MPLS signaling is specified in the documents [GMPLS-SIG], 83 [GMPLS-RSVP], [GMPLS-LDP] and [GMPLS-SONET]. 85 Table 1 summarizes the results of the GMPLS signaling aspects of 86 survey. Many included implementation details for other 87 specifications or drafts. These details are included in the full 88 response section, but not in the summary table. Table 2 provides 89 total results by feature/question. 91 The categories covered in summary Table 1 are: 93 o Type 94 Indicates type of implementation. Indicated types include: 95 tester, (network) equipment, (portable or internal use) code. If 96 the type was not evident, "unknown" is used. 98 o Drafts 99 Indicates supported drafts. [GMPLS-SIG] is assumed. "R" is used 100 to indicate [GMPLS-RSVP], "L" indicates [GMPLS-LDP] and "S" 101 indicates [GMPLS-SONET]. 103 o Software (S/w) Genealogy 104 Indicates the source of the implementation. Two sub-categories 105 are listed. The "external" category indicates the original source 106 of the code, or "yes" if not indicated. The "internal" indicates 107 the part of the code developed by the respondent. 109 o Switch Capabilities 110 Indicates the type of switching supported. "P" indicates PSC, "T" 111 indicates TDM, "L" indicates LSC and "F" indicates FSC. 113 o Label Types 114 Indicates the supported label types. "M" indicates MPLS labels, 115 "G" indicates the generalized label, "W" indicates waveband labels 116 and "S" indicates SONET/SDH label. 118 o Feature Summary 119 Summarizes supported features, by sub-category broken out in the 120 survey form. Sub-categories are indicated in the table header. 121 The "L" sub-category is used for form section 11, "Label Related". 122 "B" is used for form section 13, "Bidirectional LSPs". "N" is 123 used for form section 14, "Notification". "O" is used for form 124 section 15, "Other features". 126 In the table, an "F" indicates that all sub-category features list 127 in the form are supported. A "P" indicates partial support, i.e., 128 some boxes were not checked. 130 +===================================================================+ 131 |Ref. | Type |Draft| S/w Genealogy |Switch |Label |Feature| 132 |Section | | |External:Internal|Caps. |Types |L:B:N:O| 133 +===================================================================+ 134 | 2.1 |Equip. |R S|Yes :n/a |P T L |M G S|F:F:P:P| 135 +-----------+-------+-----+-----------------+-------+-------+-------+ 136 | 2.2 |Tester |R S| :All |P T L F|M G W S|F:F:F:F| 137 +-----------+-------+-----+-----------------+-------+-------+-------+ 138 | 2.3 |Equip. |R S|Yes :n/a | T L F| G W S|P:F:F:F| 139 +-----------+-------+-----+-----------------+-------+-------+-------+ 140 | 2.4 |Equip. |R |Yes :TE | L F| G |P:F:P:P| 141 +-----------+-------+-----+-----------------+-------+-------+-------+ 142 | 2.5 |Code |R S|Yes :n/a | T | S| :F: : | 143 +-----------+-------+-----+-----------------+-------+-------+-------+ 144 | 2.6 |Code |R S|Yes :GMPLS |P T L F|M G W S|F:F:P:P| 145 +-----------+-------+-----+-----------------+-------+-------+-------+ 146 | 2.7 |Equip. |R S| :All |P T | G S| :F:P: | 147 +-----------+-------+-----+-----------------+-------+-------+-------+ 148 | 2.8 |Code |R L | :All | L F| G W |F:F:F:F| 149 +-----------+-------+-----+-----------------+-------+-------+-------+ 150 | 2.9 |Code |R S|ISI :TE,GMPLS| T | G S|P:F:P:P| 151 +-----------+-------+-----+-----------------+-------+-------+-------+ 152 | 2.10 |Equip. |R S| :All |P T |M G S|P:F:F:P| 153 +-----------+-------+-----+-----------------+-------+-------+-------+ 154 | 2.11 |Code |R S| :All | n/a | G |P:F: :P| 155 +-----------+-------+-----+-----------------+-------+-------+-------+ 156 | 2.12 |Equip. |R S| :All |P |M G S|P:F: :P| 157 +-----------+-------+-----+-----------------+-------+-------+-------+ 158 | 2.13 |Equip. |R |Yes :GMPLS | L | G | :F: : | 159 +-----------+-------+-----+-----------------+-------+-------+-------+ 160 | 2.14 |Equip. |R S| :All | T L F| G W S|P:F:F:F| 161 +-----------+-------+-----+-----------------+-------+-------+-------+ 162 | 2.15 |Equip. |R S|LabN :GMPLS | T L F| G S|F:F:F:F| 163 +-----------+-------+-----+-----------------+-------+-------+-------+ 164 | 2.16 |Equip. |R S|Yes :n/a | T | S|F:F:P:F| 165 +-----------+-------+-----+-----------------+-------+-------+-------+ 166 | 2.17 |Code |R S| :All |P T L F|M G W S|F:F:F:P| 167 +-----------+-------+-----+-----------------+-------+-------+-------+ 168 | 2.18 |Equip. |R S|Yes :n/a |P L |M G W |F:F:P:P| 169 +-----------+-------+-----+-----------------+-------+-------+-------+ 170 | 2.19 |Code | L | n/a | n/a |M G W S|F:F:F: | 171 +-----------+-------+-----+-----------------+-------+-------+-------+ 172 | 2.20 |Equip. |R S|Yes :n/a | T | S|P:F:P:F| 173 +-----------+-------+-----+-----------------+-------+-------+-------+ 174 | 2.21 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P| 175 +-----------+-------+-----+-----------------+-------+-------+-------+ 176 | 2.22 |Equip. |R S|Yes :n/a | T L F| G S|F:F:P:P| 177 +-----------+-------+-----+-----------------+-------+-------+-------+ 178 | 2.23 |Equip. |R |Yes :n/a |P L F|M G W |P:F:P:P| 179 +-----------+-------+-----+-----------------+-------+-------+-------+ 180 | 2.24 |Code |R L | :All |P T |M G S|F:F:F:P| 181 +-----------+-------+-----+-----------------+-------+-------+-------+ 182 | 2.25 |Unknown|R |Yes :n/a | L | G |P:F:P:P| 183 +===================================================================+ 184 "n/a" indicates that no answer was provided. 186 Table 1: Survey Results Summary 188 +==================================================================+ 189 | Total | Total | | 190 |GMPLS-RSVP|GMPLS-LDP|Section, Description | 191 +==================================================================+ 192 | 25 |Total participants 193 | 24 | - |6. Reference Draft - [GMPLS-RSVP] | 194 | - | 3 |6. Reference Draft - [GMPLS-LDP] | 195 | 20 |6. Reference Draft - [GMPLS-SONET] | 196 | 10 | 2 |5.1 Switching capabilities - PSC | 197 | 15 | 1 |5.2 Switching capabilities - TDM | 198 | 15 | 2 |5.3 Switching capabilities - LSC | 199 | 10 | 1 |5.4 Switching capabilities - FSC | 200 | 1 | |9.1 Implementation based on - Purchased code| 201 | 1 | |9.2 Implementation based on - Free code | 202 | 12 | 2 |9.3 Implementation based on - Internal | 203 | 15 | 1 |9.4 Implementation based on - Combination | 204 | 10 | 3 |10.1 MPLS Label | 205 | 22 | 3 |10.2 Generalized Label | 206 | 9 | 3 |10.3 Waveband Label | 207 | 18 | 2 |10.4 SONET/SDH Label | 208 | 19 | 3 |11.1 Suggested Label | 209 | 15 | 3 |11.2 Label Set | 210 | 10 | - |12.1 Traffic Parameters - Intserv | 211 | - | 6 |12.2 Traffic Parameters - CR-LDP | 212 | 21 | 3 |12.3 GMPLS Bandwidth Encoding | 213 | 18 | 2 |12.4 Traffic Parameters - SONET/SDH | 214 | 24 | 4 |13. Bidirectional LSPs | 215 | 10 | 3 |14.1 Acceptable Label Set | 216 | 15 | - |14.2 Notify Request Objects | 217 | 18 | - |14.3 Notify Message | 218 | 19 | - |14.4 Removing State with a PathErr message | 219 | 17 | 2 |15.1 Explicit Label Control | 220 | 17 | 2 |15.2 Protection Information | 221 | 17 | 2 |15.3 Administrative Status Information | 222 | 18 | 2 |15.4 Interface Identification | 223 | 16 | 2 |15.5 Errored Interface Identification | 224 | 16 | 1 |15.6 Link Fault Handling | 225 | 13 | 1 |15.7 Nodal Fault Handling | 226 +==================================================================+ 227 "-" indicates that items is not relevant to protocol. 229 Table 2: Survey Totals 231 2. Survey Forms 233 2.1. AcceLight Networks 235 GMPLS Signaling Implementation Survey Form [V 1.1] 237 1. Organization: 238 AcceLight Networks 240 1.1 Organization url(s): 242 www.accelight.com 244 2. Product title(s): 246 PXS 540 248 2.1 Brief description(s): 250 The PXS 540 is a new class of network element. The 'Photonic 251 Service Switch' intgerates data plane switching across a fast 252 switching photonic fabric (POS, GE, SONET/SDH), and the control 253 plane with GMPLS extensions. 255 The PXS 540 can be deployed as a classical MPLS LSR, Broadband TDM 256 crossconect (BXC), and/or an opaque Optical crossconnect 257 (OXC). With service integration or any combination of functions 258 can also be configured such as BXC+OXC, MPLS LSR+OXC, MPLS+BXC or 259 MPLS LSR+BXC+OXC. 261 ---------------------------------------------------------------- 262 3. Contact for GMPLS information 264 3.1 Name: Debashis Basak 266 3.2 Title: Lead Engineer 268 3.3 E-mail: dbasak@accelight.com 270 3.4 Organization/department: Software - Routing & Signaling 272 3.5 Postal address: 70 Abele Rd, Suite 1200, Bridgeville, PA 15017 274 3.6 Phone: 412-220-2102 x 115 276 3.7 Fax: 412-220-2450 277 ---------------------------------------------------------------- 279 4. Status: 280 4.1 [ ] Development 281 4.2 [ ] Alpha 282 4.3 [X] Beta 283 4.4 [ ] Product 284 4.5 [ ] Other (describe): 286 5. Switching capabilities 287 [GMPLS- [GMPLS- 288 RSVP] LDP] 289 5.1 [X] [ ] PSC 290 5.2 [X] [ ] TDM 291 5.3 [X] [ ] LSC 292 5.4 [ ] [ ] FSC 294 6. Reference Drafts (please list, include version numbers) 296 6.1 [X] draft-ietf-ccamp-gmpls-architecture-02.txt 297 6.2 [X] draft-many-ccamp-gmpls-framework-00.txt 299 6.3 [X] draft-ietf-ccamp-gmpls-routing-03.txt 300 6.4 [X] draft-ietf-ccamp-ospf-gmpls-extensions-05.txt 301 6.5 [X] draft-ietf-isis-gmpls-extensions-09.txt 303 6.6 [X] draft-ietf-mpls-generalized-signaling-07.txt 304 6.7 [X] draft-ietf-mpls-generalized-rsvp-te-06.txt 305 6.8 [X] draft-ietf-mpls-lsp-hierarchy-04.txt 306 6.9 [X] draft-ietf-mpls-rsvp-unnum-04.txt 307 6.10 [X] draft-ietf-ccamp-lmp-02.txt 309 6.11 [X] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 311 6.12 [X] draft-mannie-gmpls-recovery-terminology-00.txt 312 6.13 [X] draft-design-team-gmpls-recovery-analysis-00.txt 313 6.14 [X] RFC2961 Refresh Reduction 314 6.15 [X] draft-ietf-mpls-bundle-01.txt 316 7. Interface technologies 317 7.1 [ ] Frame Relay 318 7.2 [ ] ATM 319 7.3 [X] Ethernet V2/DIX 320 7.4 [X] Ethernet 802.3 321 7.5 [X] SDH 322 7.6 [X] SONET 323 7.7 [X] Lambda 324 7.8 [ ] Fiber 325 7.9 [ ] FiberChannel 326 7.10 [X] Other (describe): Gigabit Ethernet (GE) 327 7.11 [X] Other (describe): POS (Packet over SONET) 329 8. Availability 330 [GMPLS- [GMPLS- 331 RSVP] LDP] 332 8.1 [ ] [ ] Public and free 333 8.2 [ ] [ ] Only to selected organizations/companies but free 334 8.3 [ ] [ ] On sale. 335 8.4 [ ] [ ] For internal company use only 336 8.5 [x] [ ] Other: As part of the Photonic Service Switch Platform 338 9. Implementation based on: (check all that apply) 339 [GMPLS- [GMPLS- 340 RSVP] LDP] 341 9.1 [ ] [ ] Purchased code 342 (please list source if possible) 343 9.2 [ ] [ ] Free code 344 (please list source if possible) 345 9.3 [ ] [ ] Internal implementation 346 (no outside code, just from specs) 347 9.4 [X] [ ] Internal implementation on top of purchased 348 or free code 349 9.4.1 List portions from external source: 350 (Identify protocol if appropriate) 351 9.4.2 List portions developed internally: 352 (Identify protocol if appropriate) 354 10. Supported Label Types 355 [GMPLS- [GMPLS- 356 RSVP] LDP] 357 10.1 [X] [ ] MPLS Label 358 10.2 [X] [ ] Generalized Label 359 10.3 [ ] [ ] Waveband Label 360 10.4 [X] [ ] SONET/SDH Label 362 11. Label Related 363 [GMPLS- [GMPLS- 364 RSVP] LDP] 365 11.1 [X] [ ] Suggested Label 366 11.2 [X] [ ] Label Set 368 12. Traffic Parameters 369 [GMPLS- [GMPLS- 370 RSVP] LDP] 371 12.1 [X] [ ] Intserv (Please list which) 372 12.2 [ ] [ ] CR-LDP 373 12.3 [X] [ ] GMPLS Bandwidth Encoding 374 12.4 [X] [ ] SONET/SDH 376 13. Bidirectional LSPs 377 [GMPLS- [GMPLS- 378 RSVP] LDP] 379 [X] [ ] Bidirectional LSPs 381 14. Notification 382 [GMPLS- [GMPLS- 383 RSVP] LDP] 384 14.1 [ ] [ ] Acceptable Label Set 385 14.2 [X] Notify Request Objects (GMPLS-RSVP) 386 14.3 [X] Notify Message (GMPLS-RSVP) 387 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 389 15 Other features 390 [GMPLS- [GMPLS- 391 RSVP] LDP] 392 15.1 [X] [ ] Explicit Label Control 393 15.2 [X] [ ] Protection Information 394 15.3 [X] [ ] Administrative Status Information 395 15.4 [X] [ ] Interface Identification 396 15.5 [ ] [ ] Errored Interface Identification 397 15.6 [X] [ ] Link Fault Handling 398 15.7 [ ] [ ] Nodal Fault Handling 400 16. Other specification(s) which apply: 402 16.1 [X] draft-ietf-mpls-diff-ext-09.txt 403 16.2 [X] RFC 2597 Assured Forwarding PHB group 404 16.3 [X] RFC 3246 An Expedited Forwarding PHB 405 16.4 [X] RFC 3036 LDP Specification 406 16.5 [X] RFC 3037 LDP Applicability 407 16.6 [X] RFC 2205 RSVP Protocol Specification 408 16.7 [X] RFC 3032 MPLS Label Stack encoding 409 16.8 [X] RFC 3031 Multiprotocol Label Switching Architecture 411 17. Other features supported: 412 17.1 related to [GMPLS-RSVP] 413 17.2 related to [GMPLS-LDP] 414 17.3 Other: see section 15, 16 and 20. 416 18. Currently-defined GMPLS signaling features not supported: 418 18.1 related to [GMPLS-RSVP]: none 419 18.2 related to [GMPLS-LDP]: none 420 18.3 related to [GMPLS-SONET]: none 421 18.4 Other: FSC interfaces 423 19. Notes (please describe purpose of project, give any information that 424 might be useful to those interested in developing or using GMPLS) 426 The PXS 540 delivers flexible intra AS switched services. The PXS 427 540 services large aggregation and/or metro core/regional 428 applications such as STS-1 grooming, switched SONET/SDH, OCn 429 optical services, Ethernet virtual leased lines, MPLS label 430 switching, cable and/or DSL trunking. 432 The PXS 540 delivers an integrated overlay (hybrid) or peer 433 networking architecture for switched services for the wavelength 434 core.Topology discovery, and layer 3 route interworking are 435 provided with IGPs such as IS-IS and OSPF. Traffic Engineering is 436 intgerated through RSVP-TE with optical extensions. The resulting 437 Photonic Service Switching (PSS) layer aggregates the edge 438 services from elements such as routers, DSLAM, Dial, B-DACS, UPSR 439 SONET ADM, and MPLS LERs to the existing WDM tansmission 440 infrastrucuture. 442 20. If you feel the above categories are not complete, add others which 443 will better describe your project: 444 20.1 [X] OIF Optical UNI 445 20.2 [X] OIF-UNI - GMPLS Interworking 446 20.3 [X] Out of Band Signaling 448 ==================================================================== 450 Person filling out this form: 452 Same as contact person 454 Name: Johnson Kuruvila 455 E-mail: johnson@accelight.com 456 Tel.: 613-596-480 457 Title: Lead Engineer 458 Company: AcceLight Networks 459 Date prepared: April 4, 2002 461 2.2. Agilent Technologies 463 GMPLS Signaling Implementation Survey Form [V 1.0] 465 1. Organization: Agilent Technologies 467 1.1 Organization url(s): www.agilent.com/comms/RouterTester 469 2. Product title(s): 470 Agilent RouterTester System. 471 GMPLS RSVP Conformance Test Suite - E5172A 472 GMPLS, MPLS & OIF UNI RSVP Protocol Software - E5173A 474 2.1 Brief description(s): 476 The Agilent RouterTester platform has 2 software modules for 477 testing GMPLS: 479 E5172A- Automated protocol conformance test suite that tests GMPLS 480 extensions to RSVP and LMP. Operates over in-band or out of band 481 signaling interfaces. 482 http://advanced.comms.agilent.com/RouterTester/datasheets/e5172a.htm 484 E5173A - Provides realistic Internet-scale GMPLS, MPLS, OIF UNI 485 and LMP protocol emulation. This software operates with routing 486 protocol software and traffic generation tools to provide 487 comprehensive multiprotocol verification and stressing of 488 GMPLS-capable devices and networks. Operates over in-band or out 489 of band signaling interfaces. 490 http://advanced.comms.agilent.com/RouterTester/datasheets/e5173a.htm 492 ---------------------------------------------------------------- 494 3. Contact for GMPLS information 495 3.1 Name: Sashi Vyravipillai 497 3.2 Title: Product Marketing Engineer 499 3.3 E-mail: sashi_vyravipillai@agilent.com 501 3.4 Organization/department: 502 Agilent Technologies, 503 Advanced Networks Division 505 3.5 Postal address: 506 Locked Bag 810 507 Blackburn Vic. 3130 508 Australia 510 3.6 Phone: +61-3-9210-5646 512 3.7 Fax: +61-3-9210-5550 514 ---------------------------------------------------------------- 516 4. Status: 517 4.1 [ ] Development 518 4.2 [ ] Alpha 519 4.3 [ ] Beta 520 4.4 [X] Product 521 4.5 [ ] Other (describe): 523 5. Switching capabilities 524 5.1 [X] PSC 525 5.2 [X] TDM 526 5.3 [X] LSC 527 5.4 [X] FSC 529 6. Reference Drafts (please list, include version numbers) 530 6.1 [X] draft-ietf-mpls-generalized-signaling-07 531 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-06 532 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-03 533 6.4 [X] draft-ietf-mpls-rsvp-unnum-04 534 6.5 [X] draft-ietf-mpls-bundle-01 535 6.6 [X] draft-ietf-ccamp-lmp-03 536 6.7 [X] RFC2961 Refresh Reduction 537 6.8 [X] draft-ietf-ccamp-ospf-gmpls-extensions-04 539 7. Interface technologies 540 7.1 [ ] Frame Relay 541 7.2 [X] ATM 542 7.3 [ ] Ethernet V2/DIX 543 7.4 [X] Ethernet 802.3 544 7.5 [X] SDH 545 7.6 [X] SONET 546 7.7 [X] Lambda (photonic) 547 7.8 [X] Fiber 548 7.9 [ ] FiberChannel 549 7.10 [ ] Other (describe): 551 8. Availability 552 8.1 [ ] Public and free 553 8.2 [ ] Only to selected organizations/companies but free 554 8.3 [X] On sale. 555 8.4 [ ] For internal company use only 556 8.5 [ ] Other: 558 9. Implementation based on: (check all that apply) 559 9.1 [ ] Purchased code (please list source if possible) 560 9.2 [ ] Free code (please list source if possible) 561 9.3 [X] Internal implementation (no outside code, just from specs) 562 9.4 [ ] Internal implementation on top of purchased or free code 563 9.4.1 [ ] List portions from external source 564 9.4.2 [ ] List portions developed internally 566 10. Supported Label Types 567 10.1 [X] MPLS Label (when using MPLS software) 568 10.2 [X] Generalized Label 569 10.3 [X] Waveband Label 570 10.4 [X] SONET/SDH Label 572 11. Label Related 573 11.1 [X] Suggested Label 574 11.2 [X] Label Set 576 12. Traffic Parameters 577 12.1 [X] Intserv (Please list which) 578 12.2 [ ] CR-LDP 579 12.3 [X] GMPLS Bandwidth Encoding 580 12.4 [X] SONET/SDH 582 13. [X] Bidirectional LSPs 584 14. Notification 585 14.1 [X] Acceptable Label Set 586 14.2 [X] Notify Request Objects (GMPLS-RSVP) 587 14.3 [X] Notify Message (GMPLS-RSVP) 588 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 590 15 Other features 591 15.1 [X] Explicit Label Control 592 15.2 [X] Protection Information 593 15.3 [X] Administrative Status Information 594 15.4 [X] Interface Identification 595 15.5 [X] Errored Interface Identification 596 15.6 [X] Link Fault Handling 597 15.7 [X] Nodal Fault Handling 599 16. Other specification(s) which apply: 600 [X] Link Management Protocol 602 17. Other features supported: 603 [X] In band control channel on OC48 and OC192 DCC interfaces 605 [X] Out of band control channel on Ethernet/GigE 607 18. Currently-defined GMPLS signaling features not supported: 609 19. Notes (please describe purpose of project, give any information that 610 might be useful to those interested in developing or using GMPLS) 612 20. If you feel the above categories are not complete, add others which 613 will better describe your project: 615 [X] GRE Tunneling Support for control plane transport 616 [X] Unnumbered interface support 617 [X] Bundled interface support 619 ============================================================== 621 Person filling out this form: 623 Name: Cary Wright 624 E-mail: cary_wright@agilent.com 625 Tel.: +61-3-9210-5843 626 Title: R&D Project Manager 627 Company: Agilent Technologies 628 Date prepared: 8 March 2002 630 2.3. Alcatel 632 GMPLS Signaling Implementation Survey Form 634 1. Organization: Alcatel 636 1.1 Organization url(s): www.alcatel.com 638 ------------------------------------------------------------ 640 2. Product title(s): Alcatel Lambda Gate with Generalized 641 Multiprotocol Routing Engine (GMRE) 643 2.1 Brief description(s): The Lambda Gate family, which supports 644 crossconnects on SDH/SONET and OTH, provides with the GMRE the 645 GMPLS functionality in networks. 647 ------------------------------------------------------------ 649 3. Contact for GMPLS information 651 3.1 Name: Gert Grammel 652 Stefan Ansorge 653 Papadimitriou Dimitri 655 3.2 Title: 657 3.3 E-mail: gert.grammel@netit.alcatel.it 658 stefan.ansorge@alcatel.de 659 dimitri.papadimitriou@alcatel.be 661 3.4 Organization/department: Alcatel TND 662 Alcatel Optical NA 664 3.5 Postal address: Via Trento 30, 665 I-20059 Vimercate, Italy 667 Lorenzstrasse, 10 668 70435 Stuttgart, Germany 670 Francis Wellesplein, 1 671 B-2018 Antwerpen, Belgium 673 3.6 Phone: +39 039 686 7060 674 +49 7 11 821 33744 675 +32 3 240 8491 677 3.7 Fax: 679 ------------------------------------------------------------ 681 4. Status: 683 4.1 [ ] Development 684 4.2 [x] Alpha (Supercom 2002 Demo) 685 4.3 [x] Beta (End 2002) 686 4.4 [ ] Product 687 4.5 [ ] Other (describe): 689 ------------------------------------------------------------ 691 5. Switching capabilities 693 5.1 [ ] PSC 694 5.2 [x] TDM 695 5.3 [x] LSC 696 5.4 [x] FSC 698 ------------------------------------------------------------ 699 6. Reference Drafts (please list, include version numbers) 701 6.1 RFC2205 - Resource Reservation Protocol, September 1997 702 6.2 RFC2208 - Resource Reservation Protocol Applicability Statement 703 6.3 RFC2961 - RSVP Summary Refresh and bundling, April 2001 704 6.4 RFC3209 - RSVP extensions for Tunnel Setup, December 2001 705 6.5 RFC3210 - Applicability statement for the extensions to RSVP 706 for LSP Tunnels 707 6.6 Draft-ietf-ccamp-gmpls-architecture-02.txt 708 - Generalized Multi-Protocol Label Switching (GMPLS) 709 Architecture 710 6.7 Draft-ietf-mpls-generalized-signaling-07.txt 711 - Generalized MPLS - Signaling Functional Description 712 6.8 Draft-ietf-mpls-generalized-rsvp-te-06.txt 713 - Generalized MPLS Signaling - RSVP-TE Extensions 714 6.9 Draft-ietf-mpls-rsvp-unnum-04.txt 715 - Signalling Unnumbered Links in RSVP-TE 716 6.10 Draft-ietf-ccamp-gmpls_sonet-sdh-03.txt 717 - Generalized MPLS extensions for SDH/SONET Network Control 718 6.11 Draft-ietf-mpls-bundle-01.txt 719 - Link Bundling in MPLS Traffic Engineering 721 6.12 RFC2328 - OSPF Version 2, April 1998 722 6.13 RFC2370 - Opaque LSA Types, July 1998 723 6.14 Draft-katz-yeung-ospf-traffic-06.txt 724 - Traffic Engineering Extensions to OSPF 725 6.15 Drat-ccamp-opsf-gmpls-extensions-04.txt 726 - OSPF Extensions in Support of Generalized MPLS 727 6.16 Draft-mannie-ccamp-gmpls-sonet-sdh-ospf-isis-00.txt 728 - Extensions to OSPF and IS-IS for GMPLS for SDH/SONET 729 Control 731 ------------------------------------------------------------ 733 7. Interface technologies 735 7.1 [ ] Frame Relay 736 7.2 [ ] ATM 737 7.3 [ ] Ethernet V2/DIX 738 7.4 [ ] Ethernet 802.3 739 7.5 [x] SDH 740 7.6 [x] SONET 741 7.7 [x] Lambda 742 7.8 [x] Fiber (future) 743 7.9 [x] FiberChannel (future) 744 7.10 [ ] Other (describe): 746 ------------------------------------------------------------ 747 8. Availability 749 8.1 [ ] Public and free 750 8.2 [ ] Only to selected organizations/companies but free 751 8.3 [x] On sale. 752 8.4 [x] For internal company use only 753 8.5 [ ] Other: 755 ------------------------------------------------------------ 757 9. Implementation based on: (check all that apply) 759 9.1 [x] Purchased code (please list source if possible) 760 9.2 [x] Free code (please list source if possible) 761 9.3 [x] Internal implementation (no outside code, just from specs) 762 9.4 [x] Internal implementation on top of purchased or free code 763 9.4.1 [ ] List portions from external source 764 9.4.2 [ ] List portions developed internally 766 ------------------------------------------------------------ 768 10. Supported Label Types 770 10.1 [ ] MPLS Label 771 10.2 [x] Generalized Label 772 10.3 [x] Waveband Label (future) 773 10.4 [x] SONET/SDH Label 775 ------------------------------------------------------------ 777 11. Label Related 779 11.1 [x] Suggested Label 780 11.2 [ ] Label Set 782 ------------------------------------------------------------ 784 12. Traffic Parameters 786 12.1 [ ] Intserv (Please list which) 787 12.2 [ ] CR-LDP 788 12.3 [x] GMPLS Bandwidth Encoding 789 12.4 [x] SONET/SDH 791 ------------------------------------------------------------ 793 13. [x] Bidirectional LSPs 794 ------------------------------------------------------------ 796 14. Notification 798 14.1 [x] Acceptable Label Set 799 14.2 [x] Notify Request Objects (GMPLS-RSVP) 800 14.3 [x] Notify Message (GMPLS-RSVP) 801 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 803 ------------------------------------------------------------ 805 15. Other features 807 15.1 [x] Explicit Label Control 808 15.2 [x] Protection Information 809 15.3 [x] Administrative Status Information 810 15.4 [x] Interface Identification 811 15.5 [x] Errored Interface Identification 812 15.6 [x] Link Fault Handling 813 15.7 [x] Nodal Fault Handling 815 ------------------------------------------------------------ 817 16. Other specification(s) which apply: 819 - RSVP COPS - 821 16.1 RFC 2748 - The COPS (Common Open Policy Service) Protocol 822 16.2 RFC 2749 - COPS usage for RSVP 823 16.3 RFC 2753 - A Framework for Policy-based Admission Control 824 16.4 draft-ietf-rap-new-rsvpext-00.txt - RSVP Extension for Policy 825 Control 827 - SNMP - 829 16.5 RFC 2571 - An architecture for Describing SNMP Management 830 Frameworks 831 16.6 RFC 2574 - User-based Security Model (USM) for version 3 of the 832 Simple 833 Network Management Protocol (SNMPv3) 834 16.7 RFC 2575 - Viewer-based Access Control Model (VACM) for the 835 Simple 836 Network Management Protocol (SNMP) 837 16.8 RFC2863 - The Interfaces Group MIB 839 16.9 draft-nadeau-ccamp-gmpls-label-mib-01.txt 840 - Generalized Multiprotocol Label Switching (GMPLS) Label 841 Management 842 Information Base 843 16.10 draft-nadeau-ccamp-gmpls-lsr-mib-01.txt 844 - Generalized Multiprotocol Label Switching (GMPLS) Label 845 Switching 846 Router Management Information Base 847 16.11 draft-nadeau-ccamp-gmpls-tc-mib-01.txt 848 - Definition of Textual Conventions and OBJECT-IDENTITIES 849 for 850 Generalized Multiprotocol Label Switching (GMPLS) 851 Management 852 16.12 draft-nadeau-ccamp-gmpls-te-mib-01.txt 853 - Generalized Multiprotocol Label Switching (GMPLS) Traffic 854 Engineering Management Information Base 855 16.13 draft-ietf-ospf-mib-update-05.txt, November 2000 856 - OSPFv2 Management Information Base 857 16.14 RFC2206, September 1997 858 - RSVP Management Information Base using SMIv2 859 16.15 draft-ietf-mpls-tc-mib-03.txt, December 2001 860 - Definition of Textual Conventions and OBJECT-IDENTITIES 861 for Multi-Protocol Label Switching (MPLS) Management 862 16.16 draft-ietf-mpls-te-mib-08.txt, December 2001 863 - MPLS Traffic Engineering Management Information Base Using 864 SMIv2 865 16.17 draft-ietf-mpls-bundle-mib-00.txt, September 2001. 866 - Link Bundling Management Information Base Using SMIv2 867 16.18 draft-ietf-tewg-mib-01.txt, October 2001 868 - Traffic Engineering MIB 870 - LMP - 872 16.19 draft-ietf-ccamp-lmp-03.txt 873 - Link Management Protocol (v1) 874 16.20 draft-ietf-ccamp-lmp-mib-01.txt 875 - Link Management Protocol Management Information Base 876 Using 877 SMIv2 879 - OIF - 881 16.21 User Network Interface (UNI) 1.0 Signaling Specification - 882 OIF October'01 884 ------------------------------------------------------------ 886 17. Other features supported: 888 17.1 OIF-UNI - GMPLS Interworking 889 17.2 Out of Band Signaling 890 17.3 Graceful Deletion 892 ------------------------------------------------------------ 894 18. Currently-defined GMPLS signaling features not supported: 896 ------------------------------------------------------------ 898 19. Notes (please describe purpose of project, give any information 899 that might be useful to those interested in developing or using 900 GMPLS) 902 ------------------------------------------------------------ 904 20. If you feel the above categories are not complete, add others which 905 will better describe your project: 907 ------------------------------------------------------------ 909 2.4. Calient Networks 911 GMPLS Signaling Implementation Survey Form [V 1.0] 913 1. Organization: Calient Networks 915 1.1 Organization url(s): http://www.calient.net 917 2. Product title(s): DiamondWave Photonic Switch 919 2.1 Brief description(s): MEMS-based photonic switch, leveraging 920 GMPLS to provide dynamic provisioning 921 and mesh-based protection/restoration. 923 ---------------------------------------------------------------- 925 3. Contact for GMPLS information 926 3.1 Name: james scott 928 3.2 Title: s/w arch 930 3.3 E-mail: jscott@calient.net 932 3.4 Organization/department: san jose/engineering 934 3.5 Postal address: 5853 rue ferrari 935 san jose, CA 95138 937 3.6 Phone: 408.972.3709 939 3.7 Fax: 408.972.3800 940 ---------------------------------------------------------------- 942 4. Status: 943 4.1 [ ] Development 944 4.2 [ ] Alpha 945 4.3 [X] Beta 946 4.4 [ ] Product 947 4.5 [ ] Other (describe): 949 5. Switching capabilities 950 5.1 [ ] PSC 951 5.2 [ ] TDM 952 5.3 [X] LSC 953 5.4 [X] FSC 955 6. Reference Drafts (please list, include version numbers) 956 6.1 [X] draft-ietf-ccamp-lmp-03.txt 957 6.2 [X] RFC 2784 : GRE Tunneling 958 6.3 [X] RFC 2205 : RSVP 959 6.4 [X] RFC 3209 : RSVP-TE 960 6.5 [X] draft-ietf-mpls-generalized-rsvp-te-05.txt 961 6.6 [X] RFC 2961 : RSVP Refresh Reduction 962 6.7 [X] draft-ietf-mpls-rsvp-unnum-03.txt 963 6.8 [X] RFC 2328 : OSPFv2 964 6.9 [X] RFC 2370 : OSPF Opaque LSA 965 6.10 [X] draft-katz-yeung-ospf-traffic-06.txt 966 6.11 [X] draft-ietf-ccamp-ospf-gmpls-extensions-00.txt 968 7. Interface technologies 969 7.1 [ ] Frame Relay 970 7.2 [ ] ATM 971 7.3 [X] Ethernet V2/DIX 972 7.4 [X] Ethernet 802.3 973 7.5 [X] SDH 974 7.6 [X] SONET 975 7.7 [X] Lambda (photonic) 976 7.8 [X] Fiber 977 7.9 [ ] FiberChannel 978 7.10 [X] Other (describe): device is transparent. all defined 979 LSP encoding types are supported. 981 8. Availability 982 8.1 [ ] Public and free 983 8.2 [ ] Only to selected organizations/companies but free 984 8.3 [X] On sale. 986 8.4 [ ] For internal company use only 987 8.5 [ ] Other: 989 9. Implementation based on: (check all that apply) 990 9.1 [ ] Purchased code (please list source if possible) 991 9.2 [ ] Free code (please list source if possible) 992 9.3 [ ] Internal implementation (no outside code, just from specs) 993 9.4 [X] Internal implementation on top of purchased or free code 994 9.4.1 [X] List portions from external source 995 OSPFv2 996 RSVP 997 9.4.2 [X] List portions developed internally 998 OSPF-TE 999 distributed RSVP-TE 1000 LMP 1002 10. Supported Label Types 1003 10.1 [ ] MPLS Label 1004 10.2 [X] Generalized Label 1005 10.3 [ ] Waveband Label 1006 10.4 [ ] SONET/SDH Label 1008 11. Label Related 1009 11.1 [X] Suggested Label 1010 11.2 [ ] Label Set 1012 12. Traffic Parameters 1013 12.1 [X] Intserv (Please list which) 1014 PATH 1015 Session 1016 IF_ID RSVP Hop 1017 Time Values 1018 Sender Template 1019 Sender Tspec 1020 Message_ID/Message_ID_ACK/Message_ID_NACK 1021 ERO 1022 RRO 1023 Generalized Label Request (LSC/FSC only) 1024 Suggested Label 1025 Upstream Label 1026 Recovery Label 1027 Protection 1028 Notify Req 1029 AdminStatus 1031 PATHErr 1032 Session 1033 Sender Template 1034 Sender Tspec 1035 Message_ID/Message_ID_ACK/Message_ID_NACK 1036 ErrorSpec 1037 RRO 1039 RESV 1040 Session 1041 Time Values 1042 Message_ID/Message_ID_ACK/Message_ID_NACK 1043 IF_ID RSVP Hop 1044 Resv Confirm 1045 Notify Request 1046 AdminStatus 1047 Style (FF or SE) 1048 Flowspec 1049 Filterspec 1050 RSVP Label 1051 RRO 1052 Generalized Label 1054 RESVErr 1055 Session 1056 IF_ID RSVP Hop 1057 Message_ID/Message_ID_ACK/Message_ID_NACK 1058 ErrorSpec 1059 Style (FF and SE) 1061 NOTIFY 1062 Session 1063 Sender Template 1064 Message_ID/Message_ID_ACK/Message_ID_NACK 1065 AdminStatus 1066 ErrorSpec 1068 HELLO 1069 Hello 1070 Restart Capabilities 1072 Summary Refresh 1073 Session 1074 Message_ID/Message_ID_ACK/Message_ID_NACK 1075 Message ID List 1077 12.2 [ ] CR-LDP 1078 12.3 [X] GMPLS Bandwidth Encoding 1079 12.4 [ ] SONET/SDH 1080 13. [X] Bidirectional LSPs 1082 14. Notification 1083 14.1 [ ] Acceptable Label Set 1084 14.2 [X] Notify Request Objects (GMPLS-RSVP) 1085 14.3 [X] Notify Message (GMPLS-RSVP) 1086 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 1088 15 Other features 1089 15.1 [ ] Explicit Label Control 1090 15.2 [X] Protection Information 1091 15.3 [X] Administrative Status Information 1092 15.4 [X] Interface Identification 1093 15.5 [X] Errored Interface Identification 1094 15.6 [X] Link Fault Handling 1095 15.7 [X] Nodal Fault Handling 1097 16. Other specification(s) which apply: 1099 17. Other features supported: 1101 Resilient GMPLS control channels 1102 LSP hierarchy (static) 1104 18. Currently-defined GMPLS signaling features not supported: 1106 Label Set 1107 Waveband Switching 1108 SONET/SDH extensions 1110 19. Notes (please describe purpose of project, give any information 1111 that might be useful to those interested in developing or using 1112 GMPLS) 1114 20. If you feel the above categories are not complete, add others which 1115 will better describe your project: 1117 ==================================================================== 1119 Person filling out this form: 1121 Name: james scott 1122 E-mail: jscott@calient.net 1123 Tel.: 408.972.3709 1124 Title: s/w arch 1125 Company: calient 1126 Date prepared: 02.03.11 1128 2.5. Ciena Corporation 1130 GMPLS Signaling Implementation Survey Form [V 1.1] 1132 1. Organization: Ciena Corporation 1134 1.1 Organization url(s): www.ciena.com 1136 2. Product title(s): MetroDirector, CoreDirector 1138 2.1 Brief description(s): Metro and core optical switches with STS-1 1139 granularity. GMPLS is implemented using the OIF UNI 1.0 1140 Implementation agreement in order to support interoperability. 1142 ---------------------------------------------------------------- 1144 3. Contact for GMPLS information 1145 3.1 Name: Lyndon Ong 1147 3.2 Title: Dir., Net. Control and Management 1149 3.3 E-mail: lyong@ciena.com 1151 3.4 Organization/department: CTO 1153 3.5 Postal address: 10480 Ridgeview Court, Cupertino, CA 95014 1155 3.6 Phone: 408-366-3358 1157 3.7 Fax: 1158 ---------------------------------------------------------------- 1160 4. Status: 1161 4.1 [ ] Development 1162 4.2 [X] Alpha 1163 4.3 [ ] Beta 1164 4.4 [ ] Product 1165 4.5 [ ] Other (describe): 1167 5. Switching capabilities 1168 [GMPLS- [GMPLS- 1169 RSVP] LDP] 1170 5.1 [ ] [ ] PSC 1171 5.2 [X] [ ] TDM 1172 5.3 [ ] [ ] LSC 1173 5.4 [ ] [ ] FSC 1174 6. Reference Drafts (please list, include version numbers) 1175 6.1 [X] draft-ietf-mpls-generalized-signaling-06.txt 1176 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-05.txt 1177 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-02.txt 1178 6.4 [ ] 1180 7. Interface technologies 1181 7.1 [ ] Frame Relay 1182 7.2 [ ] ATM 1183 7.3 [ ] Ethernet V2/DIX 1184 7.4 [ ] Ethernet 802.3 1185 7.5 [X] SDH 1186 7.6 [X] SONET 1187 7.7 [ ] Lambda (photonic) 1188 7.8 [ ] Fiber 1189 7.9 [ ] FiberChannel 1190 7.10 [ ] Other (describe): 1192 8. Availability 1193 [GMPLS- [GMPLS- 1194 RSVP] LDP] 1195 8.1 [ ] [ ] Public and free 1196 8.2 [ ] [ ] Only to selected organizations/companies but free 1197 8.3 [ ] [ ] On sale. 1198 8.4 [X] [ ] For internal company use only 1199 8.5 [ ] [ ] Other: 1201 9. Implementation based on: (check all that apply) 1202 [GMPLS- [GMPLS- 1203 RSVP] LDP] 1204 9.1 [ ] [ ] Purchased code 1205 (please list source if possible) 1206 9.2 [ ] [ ] Free code 1207 (please list source if possible) 1208 9.3 [ ] [ ] Internal implementation 1209 (no outside code, just from specs) 1210 9.4 [X] [ ] Internal implementation on top of purchased 1211 or free code 1212 9.4.1 List portions from external source: 1213 (Identify protocol if appropriate) 1214 9.4.2 List portions developed internally: 1215 (Identify protocol if appropriate) 1217 10. Supported Label Types 1218 [GMPLS- [GMPLS- 1219 RSVP] LDP] 1220 10.1 [ ] [ ] MPLS Label 1221 10.2 [ ] [ ] Generalized Label 1222 10.3 [ ] [ ] Waveband Label 1223 10.4 [X] [ ] SONET/SDH Label 1225 11. Label Related 1226 [GMPLS- [GMPLS- 1227 RSVP] LDP] 1228 11.1 [ ] [ ] Suggested Label 1229 11.2 [ ] [ ] Label Set 1231 12. Traffic Parameters 1232 [GMPLS- [GMPLS- 1233 RSVP] LDP] 1234 12.1 [ ] Intserv (Please list which) 1235 12.2 [ ] CR-LDP 1236 12.3 [ ] [ ] GMPLS Bandwidth Encoding 1237 12.4 [X] [ ] SONET/SDH 1239 13. Bidirectional LSPs 1240 [GMPLS- [GMPLS- 1241 RSVP] LDP] 1242 [X] [ ] Bidirectional LSPs 1244 14. Notification 1245 [GMPLS- [GMPLS- 1246 RSVP] LDP] 1247 14.1 [ ] [ ] Acceptable Label Set 1248 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 1249 14.3 [ ] Notify Message (GMPLS-RSVP) 1250 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 1252 15 Other features 1253 [GMPLS- [GMPLS- 1254 RSVP] LDP] 1255 15.1 [ ] [ ] Explicit Label Control 1256 15.2 [ ] [ ] Protection Information 1257 15.3 [ ] [ ] Administrative Status Information 1258 15.4 [ ] [ ] Interface Identification 1259 15.5 [ ] [ ] Errored Interface Identification 1260 15.6 [ ] [ ] Link Fault Handling 1261 15.7 [ ] [ ] Nodal Fault Handling 1263 16. Other specification(s) which apply: 1265 17. Other features supported: 1266 17.1 related to [GMPLS-RSVP] 1267 17.2 related to [GMPLS-LDP] 1268 17.3 Other 1269 18. Currently-defined GMPLS signaling features not supported: 1270 18.1 related to [GMPLS-RSVP] 1271 18.2 related to [GMPLS-LDP] 1272 18.3 related to [GMPLS-SONET] 1273 18.4 Other 1275 19. Notes (please describe purpose of project, give any information that 1276 might be useful to those interested in developing or using GMPLS) 1278 Based on OIF UNI 1.0 Implementation Agreement, which is a subset of GMPLS 1279 but includes the most stable and commonly agreed features. The purpose of 1280 the implementation is for interoperability with client devices. 1282 20. If you feel the above categories are not complete, add others which 1283 will better describe your project: 1285 ==================================================================== 1287 Person filling out this form: 1289 Name: as above 1290 E-mail: 1291 Tel.: 1292 Title: 1293 Company: 1294 Date prepared: March 22, 2002 1296 2.6. Data Connection Ltd 1298 GMPLS Signaling Implementation Survey Form [V 1.0] 1300 1. Organization: 1301 Data Connection Ltd 1303 1.1 Organization url(s): 1304 www.dataconnection.com 1306 2. Product title(s): 1307 DC-MPLS 1309 2.1 Brief description(s): 1310 MPLS and GMPLS signaling software product, including RSVP, LDP, CR-LDP and 1311 OIF UNI support. 1313 ---------------------------------------------------------------- 1315 3. Contact for GMPLS information 1316 3.1 Name: 1317 Toby Eccles 1319 3.2 Title: 1320 MPLS Product Manager 1322 3.3 E-mail: 1323 thme@dataconnection.com 1325 3.4 Organization/department: 1326 Network Convergence Group 1328 3.5 Postal address: 1329 Data Connection Ltd 1330 100 Church Street 1331 Enfield 1332 Middlesex 1333 EN2 6BQ 1334 UK 1336 3.6 Phone: 1337 +44 20 8366 1177 1339 3.7 Fax: 1340 +44 20 8363 1468 1341 ---------------------------------------------------------------- 1343 4. Status: 1344 4.1 [ ] Development 1345 4.2 [ ] Alpha 1346 4.3 [ ] Beta 1347 4.4 [X] Product 1348 4.5 [ ] Other (describe): 1350 5. Switching capabilities 1351 5.1 [X] PSC 1352 5.2 [X] TDM 1353 5.3 [X] LSC 1354 5.4 [X] FSC 1355 DC-MPLS software can control all of these switching types. 1357 6. Reference Drafts (please list, include version numbers) 1358 Draft support is constantly being updated to the latest versions. 1360 RFC 2205 Resource ReSerVation Protocol (RSVP) 1361 RFC 2207 RSVP Extensions for IPSEC Data Flows 1362 RFC 2208 Resource ReSerVation Protocol (RSVP) Version 1 Applicability 1363 Statement 1364 RFC 2209 Resource ReSerVation Protocol (RSVP) Version 1 Message 1365 Processing Rules 1366 RFC 2210 The Use of RSVP with IETF Integrated Services 1367 RFC 2547 BGP/MPLS VPNs 1368 RFC 2702 Requirements for Traffic Engineering Over MPLS 1369 RFC 2745 RSVP Diagnostic Messages 1370 RFC 2764 Framework for IP-based Virtual Private Networks 1371 RFC 2961 RSVP Refresh Overhead Reduction Extensions 1372 RFC 3031 Multiprotocol Label Switching Architecture 1373 RFC 3032 MPLS Label Stack Encoding 1374 RFC 3034 Use of Label Switching on Frame Relay Networks Specification 1376 RFC 3035 MPLS using LDP and ATM VC Switching 1377 RFC 3036 LDP specification 1378 RFC 3037 LDP Applicability 1379 RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels 1380 RFC 3210 Applicability statement for the extensions to RSVP for LSP 1381 Tunnels 1382 RFC 3212 Constraint-Based LSP Setup using LDP 1383 RFC 3213 Applicability Statement for CR-LDP 1384 draft-ietf-mpls-ldp-mib Definitions of Managed Objects for the Multiprotocol 1385 Label Switching Label Distribution Protocol (LDP) 1386 draft-ietf-mpls-lsr-mib MPLS Label Switch Router Management Information Base 1387 Using SMIv2 1388 draft-ietf-mpls-te-mib MPLS Traffic Engineering Management Information Base 1389 Using SMIv2 1390 draft-ietf-mpls-generalized-signaling Generalized MPLS - Signaling 1391 Functional Description 1392 draft-ietf-mpls-generalized-rsvp-te Generalized MPLS Signaling - RSVP-TE 1393 Extensions 1394 draft-ietf-mpls-diff-ext MPLS Support of Differentiated Services 1395 draft-ietf-mpls-lsp-hierarchy LSP Hierarchy with MPLS TE 1396 draft-ietf-mpls-rsvp-unnum Signaling Unnumbered Links in RSVP-TE 1397 draft-ietf-mpls-bundle Link Bundling in MPLS Traffic Engineering 1398 draft-ietf-mpls-bundle-mib Link Bundling Management Information Base 1399 Using SMIv2 1400 draft-ietf-mpls-tc-mib Definition of Textual Conventions and 1401 OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management 1402 draft-ietf-mpls-mgmt-overview Multiprotocol Label Switching (MPLS) 1403 Management Overview 1404 draft-ietf-mpls-rsvp-lsp-fastreroute-00.txt Fast Reroute Extensions to 1405 RSVP-TE for LSP Tunnels 1406 draft-ietf-ccamp-gmpls- sonet-sdh GMPLS Extensions for SONET and SDH 1407 Control 1408 draft-ietf-ccamp-gmpls- architecture Generalized Multi-Protocol Label 1409 Switching (GMPLS) Architecture 1410 draft-ietf-ccamp-gmpls- sonet-sdh-extensions GMPLS Extensions to Control 1411 Non-Standard SONET and SDH Features 1412 draft-iwata-mpls-crankback Crankback Routing Extensions for MPLS 1413 Signaling 1414 draft-martini-l2circuit-trans- mpls Transport of Layer 2 Frames Over 1415 MPLS 1416 draft-martini-l2circuit-encap-mpls Encapsulation Methods for Transport 1417 of Layer 2 Frames Over IP 1418 draft-azad-mpls-oam-messaging MPLS user-plane OAM messaging 1420 7. Interface technologies 1421 7.1 [X] Frame Relay 1422 7.2 [X] ATM 1423 7.3 [X] Ethernet V2/DIX 1424 7.4 [X] Ethernet 802.3 1425 7.5 [X] SDH 1426 7.6 [X] SONET 1427 7.7 [X] Lambda (photonic) 1428 7.8 [X] Fiber 1429 7.9 [X] FiberChannel 1430 7.10 [ ] Other (describe): 1431 DC-MPLS software can handle all these interface types. 1433 8. Availability 1434 8.1 [ ] Public and free 1435 8.2 [ ] Only to selected organizations/companies but free 1436 8.3 [X] On sale. 1437 8.4 [ ] For internal company use only 1438 8.5 [ ] Other: 1440 9. Implementation based on: (check all that apply) 1441 9.1 [ ] Purchased code (please list source if possible) 1442 9.2 [ ] Free code (please list source if possible) 1443 9.3 [X] Internal implementation (no outside code, just from specs) 1444 9.4 [X] Internal implementation on top of purchased or free code 1445 9.4.1 [ ] List portions from external source 1446 9.4.2 [ ] List portions developed internally 1447 External code was used as a basis for the very initial development of the 1448 RSVP protocol piece for packet MPLS. All other components have been 1449 developed internally. Since then, all externally-derived code has been 1450 either rewritten or substantially revised and enhanced - it is now 1451 unrecognisable; also, large new components (including all the GMPLS protocol 1452 handling) have been developed purely from the specifications. 1454 10. Supported Label Types 1455 10.1 [X] MPLS Label 1456 10.2 [X] Generalized Label 1457 10.3 [X] Waveband Label 1458 10.4 [X] SONET/SDH Label 1459 11. Label Related 1460 11.1 [X] Suggested Label 1461 11.2 [X] Label Set 1463 12. Traffic Parameters 1464 12.1 [X] Intserv (Controlled load and Guaranteed service) 1465 12.2 [X] CR-LDP 1466 12.3 [X] GMPLS Bandwidth Encoding 1467 12.4 [X] SONET/SDH 1469 13. [X] Bidirectional LSPs 1471 14. Notification 1472 14.1 [ ] Acceptable Label Set 1473 14.2 [X] Notify Request Objects (GMPLS-RSVP) 1474 14.3 [X] Notify Message (GMPLS-RSVP) 1475 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 1477 15 Other features 1478 15.1 [X] Explicit Label Control 1479 15.2 [X] Protection Information 1480 15.3 [X] Administrative Status Information 1481 15.4 [X] Interface Identification 1482 15.5 [ ] Errored Interface Identification 1483 15.6 [X] Link Fault Handling 1484 15.7 [X] Nodal Fault Handling 1486 16. Other specification(s) which apply: 1487 OIF2000.125 User Network Interface (UNI) 1.0 Signaling Specification 1489 17. Other features supported: 1490 Control plane restart (as in both the pan-restart and generalized-rsvp-te 1491 signalling drafts) 1492 Fault tolerance (hot backup and persistent store) 1493 Software distribution across distributed processing architectures 1494 Protection switching 1495 Bundled links 1496 Non-associated (out of band) signaling 1497 Graceful deletion 1498 LSP hierarchy 1499 Reverse LSPs 1500 Diffserv 1501 Resource affinities 1503 18. Currently-defined GMPLS signaling features not supported: 1504 Errored Interface Identification 1505 Acceptable Label Set 1506 19. Notes (please describe purpose of project, give any information that 1507 might be useful to those interested in developing or using GMPLS) 1509 DC-MPLS is a source code implementation of the MPLS, GMPLS, and OIF 1510 UNI protocols that has been architected, designed, coded and tested 1511 for the most demanding environments: high performance, unlimited 1512 scalability, resilience and fault tolerance have been designed in 1513 from the outset. It is in use with a large number of OEMs building 1514 a wide variety of types of switch, many of which are using GMPLS. 1516 DCL also supplies implementations of LMP and IP routing protocols 1517 for implementation of a complete control plane. 1519 20. If you feel the above categories are not complete, add others which 1520 will better describe your project: 1522 ======================================================================= 1524 Person filling out this form: 1526 Name: 1527 Tim Hall 1529 E-mail: 1530 timhall@dataconnection.com 1532 Tel.: 1533 +44 20 8366 1177 1535 Title: 1536 DC-MPLS Development Manager 1538 Company: 1539 Data Connection Ltd. 1541 Date prepared: 1542 13th March 2002 1544 2.7. Equipe Communications Corp. 1546 GMPLS Signaling Implementation Survey Form [V 1.1] 1548 1. Organization: Equipe Communications Corp. 1550 1.1 Organization url(s): www.equipecom.com 1552 2. Product title(s): E3200 1553 2.1 Brief description(s): O-UNI implementation for Multi-service 1554 switch 1556 ---------------------------------------------------------------- 1558 3. Contact for GMPLS information 1559 3.1 Name: Nik Langrind 1561 3.2 Title: Prin SW Eng 1563 3.3 E-mail: nik@equipecom.com 1565 3.4 Organization/department: Engineering 1567 3.5 Postal address: 100 Nagog Park, Acton MA 01720 1569 3.6 Phone: (978) 795 2012 1571 3.7 Fax: (978) 635 0095 1572 ---------------------------------------------------------------- 1574 4. Status: 1575 4.1 [ ] Development 1576 4.2 [x] Alpha 1577 4.3 [ ] Beta 1578 4.4 [ ] Product 1579 4.5 [ ] Other (describe): 1581 5. Switching capabilities 1582 [GMPLS- [GMPLS- 1583 RSVP] LDP] 1584 5.1 [x] [ ] PSC 1585 5.2 [x] [ ] TDM 1586 5.3 [ ] [ ] LSC 1587 5.4 [ ] [ ] FSC 1589 6. Reference Drafts (please list, include version numbers) 1590 6.1 [ ] draft-ietf-mpls-generalized-signaling-08 1591 6.2 [ ] draft-ietf-mpls-generalized-rsvp-te-07 1592 6.3 [ ] draft-ietf-ccamp-gmpls-sonet-sdh-03 1593 6.4 [ ] draft-ietf-ccamp-lmp-03 1594 6.5 [ ] RFC2961 Refresh Reduction 1596 7. Interface technologies 1597 7.1 [ ] Frame Relay 1598 7.2 [ ] ATM 1599 7.3 [ ] Ethernet V2/DIX 1600 7.4 [ ] Ethernet 802.3 1601 7.5 [x] SDH 1602 7.6 [x] SONET 1603 7.7 [ ] Lambda (photonic) 1604 7.8 [ ] Fiber 1605 7.9 [ ] FiberChannel 1606 7.10 [ ] Other (describe): 1608 8. Availability 1609 [GMPLS- [GMPLS- 1610 RSVP] LDP] 1611 8.1 [ ] [ ] Public and free 1612 8.2 [ ] [ ] Only to selected organizations/companies but free 1613 8.3 [ ] [ ] On sale. 1614 8.4 [x] [ ] For internal company use only 1615 8.5 [ ] [ ] Other: 1617 9. Implementation based on: (check all that apply) 1618 [GMPLS- [GMPLS- 1619 RSVP] LDP] 1620 9.1 [ ] [ ] Purchased code 1621 (please list source if possible) 1622 9.2 [ ] [ ] Free code 1623 (please list source if possible) 1624 9.3 [x] [ ] Internal implementation 1625 (no outside code, just from specs) 1626 9.4 [ ] [ ] Internal implementation on top of purchased 1627 or free code 1628 9.4.1 List portions from external source: 1629 (Identify protocol if appropriate) 1630 9.4.2 List portions developed internally: 1631 (Identify protocol if appropriate) 1633 10. Supported Label Types 1634 [GMPLS- [GMPLS- 1635 RSVP] LDP] 1636 10.1 [ ] [ ] MPLS Label 1637 10.2 [x] [ ] Generalized Label 1638 10.3 [ ] [ ] Waveband Label 1639 10.4 [x] [ ] SONET/SDH Label 1641 11. Label Related 1642 [GMPLS- [GMPLS- 1643 RSVP] LDP] 1644 11.1 [ ] [ ] Suggested Label 1645 11.2 [ ] [ ] Label Set 1647 12. Traffic Parameters 1648 [GMPLS- [GMPLS- 1649 RSVP] LDP] 1650 12.1 [ ] Intserv (Please list which) 1651 12.2 [ ] CR-LDP 1652 12.3 [ ] [ ] GMPLS Bandwidth Encoding 1653 12.4 [x] [ ] SONET/SDH 1655 13. Bidirectional LSPs 1656 [GMPLS- [GMPLS- 1657 RSVP] LDP] 1658 [x] [ ] Bidirectional LSPs 1660 14. Notification 1661 [GMPLS- [GMPLS- 1662 RSVP] LDP] 1663 14.1 [ ] [ ] Acceptable Label Set 1664 14.2 [x] Notify Request Objects (GMPLS-RSVP) 1665 14.3 [x] Notify Message (GMPLS-RSVP) 1666 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 1668 15 Other features 1669 [GMPLS- [GMPLS- 1670 RSVP] LDP] 1671 15.1 [ ] [ ] Explicit Label Control 1672 15.2 [ ] [ ] Protection Information 1673 15.3 [ ] [ ] Administrative Status Information 1674 15.4 [ ] [ ] Interface Identification 1675 15.5 [ ] [ ] Errored Interface Identification 1676 15.6 [ ] [ ] Link Fault Handling 1677 15.7 [ ] [ ] Nodal Fault Handling 1679 16. Other specification(s) which apply: 1681 17. Other features supported: 1682 17.1 related to [GMPLS-RSVP] 1683 17.2 related to [GMPLS-LDP] 1684 17.3 Other 1686 18. Currently-defined GMPLS signaling features not supported: 1688 Suggested Label, Label Set etc. 1690 19. Notes (please describe purpose of project, give any information that 1691 might be useful to those interested in developing or using GMPLS) 1693 The goal is to provide OIF O-UNI 1.0, User Side. 1695 20. If you feel the above categories are not complete, add others which 1696 will better describe your project: 1698 ==================================================================== 1700 Person filling out this form: 1702 Name: Nik Langrind 1703 E-mail: nik@equipecom.com 1704 Tel.: (978) 795-2012 1705 Title: Prin SW Eng 1706 Company: Equipe Communications Corp 1707 Date prepared: 5/30/02 1709 2.8. Firstwave Intelligent Optical Networks 1711 GMPLS Signaling Implementation Survey Form [V 1.1] 1713 1. Organization: FirstWave Intelligent Optical Networks 1715 1.1 Organization url(s): http://www.fwion.com 1717 2. Product title(s): 1719 2.1 Brief description(s): 1721 ---------------------------------------------------------------- 1723 3. Contact for GMPLS information 1724 3.1 Name: Michael Mandelberg 1726 3.2 Title: Sr. MTS 1728 3.3 E-mail: mmandelberg@fwion.com 1730 3.4 Organization/department: Control Plane Embedded Software Group 1732 3.5 Postal address: 6301 Ivy Lane, Suite 700, Greenbelt, MD 20770 1734 3.6 Phone: (301) 345-2137 x1008 1736 3.7 Fax: (301) 345-3612 1737 ---------------------------------------------------------------- 1739 4. Status: 1740 4.1 [ ] Development 1741 4.2 [x] Alpha 1742 4.3 [ ] Beta 1743 4.4 [ ] Product 1744 4.5 [ ] Other (describe): 1746 5. Switching capabilities 1747 [GMPLS- [GMPLS- 1748 RSVP] LDP] 1749 5.1 [ ] [ ] PSC 1750 5.2 [ ] [ ] TDM 1751 5.3 [x] [x] LSC 1752 5.4 [x] [x] FSC 1754 6. Reference Drafts (please list, include version numbers) 1755 6.1 [x] [GMPLS-SIG] 1756 6.2 [x] [GMPLS-RSVP] 1757 6.3 [x] [GMPLS-LDP] 1758 6.4 [ ] [GMPLS-SONET] 1759 6.5 [x] draft-ietf-ccamp-lmp-03.txt 1760 6.6 [x] draft-ietf-ccamp-gmpls-architecture-02.txt 1761 6.7 [x] draft-ietf-ccamp-ospf-gmpls-extensions-04.txt 1762 6.8 [x] draft-nadeau-ccamp-gmpls-label-mib-01.txt 1763 6.9 [x] draft-nadeau-ccamp-gmpls-tc-mib-01.txt 1764 6.10 [x] draft-nadeau-ccamp-gmpls-lsr-mib-01.txt 1765 6.11 [x] draft-nadeau-ccamp-gmpls-te-mib-01.txt 1766 6.12 [x] draft-ietf-mpls-lsp-hierarchy-04.txt 1767 6.13 [x] draft-ietf-mpls-bundle-01.txt 1769 7. Interface technologies 1770 7.1 [ ] Frame Relay 1771 7.2 [ ] ATM 1772 7.3 [ ] Ethernet V2/DIX 1773 7.4 [ ] Ethernet 802.3 1774 7.5 [ ] SDH 1775 7.6 [ ] SONET 1776 7.7 [x] Lambda (photonic) 1777 7.8 [ ] Fiber 1778 7.9 [ ] FiberChannel 1779 7.10 [x] Other (describe): All optical and transparent to transport 1780 technology 1782 8. Availability 1783 [GMPLS- [GMPLS- 1784 RSVP] LDP] 1785 8.1 [ ] [ ] Public and free 1786 8.2 [ ] [ ] Only to selected organizations/companies but free 1787 8.3 [ ] [ ] On sale. 1788 8.4 [x] [x] For internal company use only 1789 8.5 [ ] [ ] Other: 1791 9. Implementation based on: (check all that apply) 1792 [GMPLS- [GMPLS- 1793 RSVP] LDP] 1795 9.1 [ ] [ ] Purchased code 1796 (please list source if possible) 1797 9.2 [ ] [ ] Free code 1798 (please list source if possible) 1799 9.3 [x] [x] Internal implementation 1800 (no outside code, just from specs) 1801 9.4 [ ] [ ] Internal implementation on top of purchased 1802 or free code 1803 9.4.1 List portions from external source: 1804 (Identify protocol if appropriate) 1805 9.4.2 List portions developed internally: 1806 (Identify protocol if appropriate) 1808 10. Supported Label Types 1809 [GMPLS- [GMPLS- 1810 RSVP] LDP] 1811 10.1 [ ] [ ] MPLS Label 1812 10.2 [x] [x] Generalized Label 1813 10.3 [x] [x] Waveband Label 1814 10.4 [ ] [ ] SONET/SDH Label 1816 11. Label Related 1817 [GMPLS- [GMPLS- 1818 RSVP] LDP] 1819 11.1 [x] [x] Suggested Label 1820 11.2 [x] [x] Label Set 1822 12. Traffic Parameters 1823 [GMPLS- [GMPLS- 1824 RSVP] LDP] 1825 12.1 [ ] [ ] Intserv (Please list which) 1826 12.2 [x] [x] CR-LDP 1827 12.3 [x] [x] GMPLS Bandwidth Encoding 1828 12.4 [ ] [ ] SONET/SDH 1830 13. Bidirectional LSPs 1831 [GMPLS- [GMPLS- 1832 RSVP] LDP] 1833 [x] [x] Bidirectional LSPs 1835 14. Notification 1836 [GMPLS- [GMPLS- 1837 RSVP] LDP] 1838 14.1 [x] [x] Acceptable Label Set 1839 14.2 [x] Notify Request Objects (GMPLS-RSVP) 1840 14.3 [x] Notify Message (GMPLS-RSVP) 1841 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 1842 15 Other features 1843 [GMPLS- [GMPLS- 1844 RSVP] LDP] 1845 15.1 [x] [x] Explicit Label Control 1846 15.2 [x] [x] Protection Information 1847 15.3 [x] [x] Administrative Status Information 1848 15.4 [x] [x] Interface Identification 1849 15.5 [x] [x] Errored Interface Identification 1850 15.6 [x] [x] Link Fault Handling 1851 15.7 [x] [x] Nodal Fault Handling 1853 16. Other specification(s) which apply: 1855 17. Other features supported: 1856 17.1 related to [GMPLS-RSVP] 1857 17.2 related to [GMPLS-LDP] 1858 17.3 Other 1860 18. Currently-defined GMPLS signaling features not supported: 1861 18.1 related to [GMPLS-RSVP] 1862 18.2 related to [GMPLS-LDP] 1863 18.3 related to [GMPLS-SONET] 1864 18.4 Other 1866 19. Notes (please describe purpose of project, give any information that 1867 might be useful to those interested in developing or using GMPLS) 1869 20. If you feel the above categories are not complete, add others which 1870 will better describe your project: 1872 ==================================================================== 1874 Person filling out this form: 1876 Name: Michael Mandelberg 1877 E-mail: mmandelberg@fwion.com 1878 Tel.: (301) 345-2137 x1008 1879 Title: Sr. MTS 1880 Company: FirstWave Intelligent Optical Networks 1881 Date prepared: 3-15-02 1883 2.9. HCL Technologies Ltd., India 1885 GMPLS Signaling Implementation Survey Form [V 1.0] 1887 1. Organization: HCL TECHNOLOGIES LTD., INDIA 1889 1.1 Organization url(s): www.hcltechnologies.com (Corporate Website) 1891 2. Product title(s): HCL LMP , HCL RSVP-TE 1893 2.1 Brief description(s): 1894 * HCL LMP:- 1895 ++++++++++++ 1897 The design and implementation of the product is as per the 1898 working draft mentioned for Link Management Protocol. This 1899 product includes all the features irrespective of optional 1900 and mandatory procedures. Specific API implementation is 1901 also being done in order to match different possible 1902 environments in which it can be used. 1904 * HCL RSVP-TE:- 1905 ++++++++++++++++ 1906 This product is being developed internally for Signalling 1907 and LSP establishment in GMPLS Environment. The design and 1908 implementation is done on top of existing base RSVP 1909 (RFC 2205 ) implementation, by adding provisions so that 1910 it can be used for Signalling & LSP establishment in GMPLS 1911 scenario. This product can work standalone as GMPLS RSVP TE 1912 stack as well as in regular IP Resource Reservation 1913 environment & in MPLS Label Distribution and LSP 1914 establishment environment. 1916 ---------------------------------------------------------------- 1918 3. Contact for GMPLS information 1919 3.1 Name: S. Shankar 1921 3.2 Title: Project Manager 1923 3.3 E-mail: shanky@npd.hcltech.com 1925 3.4 Organization/department: HCL Technologies Limited, 1926 Networking Products Division 1928 3.5 Postal address: 49-50 Nelson Manickam Road, Chennai - 600029, 1929 India 1931 3.6 Phone: +91-44-3741939 1933 3.7 Fax: +91-44-3741038 1934 ---------------------------------------------------------------- 1936 4. Status: 1937 4.1 [*] Development 1938 4.2 [ ] Alpha 1939 4.3 [ ] Beta 1940 4.4 [ ] Product 1941 4.5 [ ] Other (describe): 1943 5. Switching capabilities 1944 5.1 [ ] PSC 1945 5.2 [*] TDM 1946 5.3 [ ] LSC 1947 5.4 [ ] FSC 1949 6. Reference Drafts (please list, include version numbers) 1950 6.1 [*] draft-ietf-ccamp-lmp-02.txt 1951 6.2 [*] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 1952 6.3 [*] draft-ietf-ccamp-gmpls-architecture-02.txt 1953 6.4 [*] draft-ietf-mpls-generalized-rsvp-te-06.txt 1954 6.5 [*] draft-ietf-mpls-rsvp-unnum-04.txt 1955 6.6 [*] draft-ietf-mpls-bundle-01.txt 1956 6.7 [*] rfc3209.txt 1957 6.9 [*] rfc2205.txt 1958 7.0 [*] rfc2961.txt 1959 7.1 [*] draft-ietf-mpls-generalized-signaling-07 1961 7. Interface technologies 1962 7.1 [ ] Frame Relay 1963 7.2 [ ] ATM 1964 7.3 [ ] Ethernet V2/DIX 1965 7.4 [ ] Ethernet 802.3 1966 7.5 [*] SDH 1967 7.6 [*] SONET 1968 7.7 [ ] Lambda (photonic) 1969 7.8 [ ] Fiber 1970 7.9 [ ] FiberChannel 1971 7.10 [ ] Other (describe): 1973 8. Availability 1974 8.1 [ ] Public and free 1975 8.2 [ ] Only to selected organizations/companies but free 1976 8.3 [ ] On sale. 1977 8.4 [ ] For internal company use only 1978 8.5 [*] Other: 1980 9. Implementation based on: (check all that apply) 1981 9.1 [ ] Purchased code (please list source if possible) 1982 9.2 [ ] Free code (please list source if possible) 1983 9.3 [ ] Internal implementation (no outside code, just from specs) 1984 9.4 [*] Internal implementation on top of purchased or free code 1985 9.4.1 [*] List portions from external source 1986 RSVP base code implemented by ISI. Conformance to RFC 2205 1988 9.4.2 [*] List portions developed internally 1989 GMPLS RSVP TE Extensions ( As per Drafts ) 1990 LMP 1992 10. Supported Label Types 1993 10.1 [ ] MPLS Label 1994 10.2 [*] Generalized Label 1995 10.3 [ ] Waveband Label 1996 10.4 [*] SONET/SDH Label 1998 11. Label Related 1999 11.1 [ ] Suggested Label 2000 11.2 [*] Label Set 2002 12. Traffic Parameters 2003 12.1 [*] Intserv (Please list which) 2004 12.2 [ ] CR-LDP 2005 12.3 [*] GMPLS Bandwidth Encoding 2006 12.4 [*] SONET/SDH 2008 13. [*] Bidirectional LSPs 2010 14. Notification 2011 14.1 [*] Acceptable Label Set 2012 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 2013 14.3 [ ] Notify Message (GMPLS-RSVP) 2014 14.4 [*] Removing State with a PathErr message (GMPLS-RSVP) 2016 15 Other features 2017 15.1 [*] Explicit Label Control 2018 15.2 [ ] Protection Information 2019 15.3 [*] Administrative Status Information 2020 15.4 [*] Interface Identification 2021 15.5 [*] Errored Interface Identification 2022 15.6 [*] Link Fault Handling 2023 15.7 [*] Nodal Fault Handling 2024 16. Other specification(s) which apply: OIF-UNI-01.0 2026 17. Other features supported: 2027 a) RECOVERY_LABEL as per OIF UNI specification 2028 b) Service Discovery as per OIF UNI specification 2030 18. Currently-defined GMPLS signaling features not supported: 2031 a) Channel Status procedure 2033 19. Notes (please describe purpose of project, give any information that 2034 might be useful to those interested in developing or using GMPLS) 2036 20. If you feel the above categories are not complete, add others which 2037 will better describe your project: 2039 ==================================================================== 2041 Person filling out this form: 2043 Name: S. Shankar 2044 E-mail: shanky@npd.hcltech.com 2045 Tel.: +91-44-374-1939 2046 Title: Project Manager 2047 Company: HCL Technologies Limited, 2048 Networking Products Division 2049 Date prepared: 13-March-2002 2051 2.10. Intel Corporation 2053 GMPLS Signaling Implementation Survey Form [V 1.0] 2055 1. Organization: Intel Corporation 2057 1.1 Organization url(s):htp://www.intel.com 2059 2. Product title(s):Intelligent Optical Networking using GMPLS 2061 2.1 Brief description(s): 2063 The product utilizes the benefits of GMPLS to provision smart, 2064 scalable and extensible Optical Networks. 2066 ---------------------------------------------------------------- 2068 3. Contact for GMPLS information 2069 3.1 Name:Christian Maciocco, Manav Mishra 2070 3.2 Title: 2072 3.3 E-mail:christian.maciocco@intel.com;manav.mishra@intel.com 2074 3.4 Organization/department:Intel Labs 2076 3.5 Postal address:2111 NE 25th Avenue, Hillsboro, OR 97124 2078 3.6 Phone:503-712-1843 2080 3.7 Fax:503-264-3483 2081 ---------------------------------------------------------------- 2083 4. Status: 2084 4.1 [X ] Development 2085 4.2 [ ] Alpha 2086 4.3 [ ] Beta 2087 4.4 [ ] Product 2088 4.5 [ ] Other (describe): 2090 5. Switching capabilities 2091 5.1 [X] PSC 2092 5.2 [X] TDM 2093 5.3 [ ] LSC 2094 5.4 [ ] FSC 2096 6. Reference Drafts (please list, include version numbers) 2097 6.1 [http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-rsvp-te-06.txt ] 2098 6.2 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-sonet-sdh-02.txt ] 2099 6.3 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-architecture-01.txt ] 2100 6.4 [http://www.ietf.org/internet-drafts/draft-ietf-mpls-generalized-signaling-07.txt ] 2101 6.5 [http://www.ietf.org/internet-drafts/draft-ietf-ccamp-lmp-02.txt ] 2102 6.6 [ ] 2104 7. Interface technologies 2105 7.1 [ ] Frame Relay 2106 7.2 [X] ATM 2107 7.3 [X] Ethernet V2/DIX 2108 7.4 [X] Ethernet 802.3 2109 7.5 [X] SDH 2110 7.6 [X] SONET 2111 7.7 [ ] Lambda (photonic) 2112 7.8 [ ] Fiber 2113 7.9 [ ] FiberChannel 2114 7.10 [ ] Other (describe): 2116 8. Availability 2117 8.1 [ ] Public and free 2118 8.2 [ ] Only to selected organizations/companies but free 2119 8.3 [ ] On sale. 2120 8.4 [ ] For internal company use only 2121 8.5 [X] Other: 2123 9. Implementation based on: (check all that apply) 2124 9.1 [ ] Purchased code (please list source if possible) 2125 9.2 [ ] Free code (please list source if possible) 2126 9.3 [X] Internal implementation (no outside code, just from specs) 2127 9.4 [ ] Internal implementation on top of purchased or free code 2128 9.4.1 [ ] List portions from external source 2129 9.4.2 [ ] List portions developed internally 2131 10. Supported Label Types 2132 10.1 [X] MPLS Label 2133 10.2 [X] Generalized Label 2134 10.3 [ ] Waveband Label 2135 10.4 [X] SONET/SDH Label 2137 11. Label Related 2138 11.1 [ ] Suggested Label 2139 11.2 [X] Label Set 2141 12. Traffic Parameters 2142 12.1 [X] Intserv (Please list which) RSVP-TE 2143 12.2 [ ] CR-LDP 2144 12.3 [X] GMPLS Bandwidth Encoding 2145 12.4 [X] SONET/SDH 2147 13. [X] Bidirectional LSPs 2149 14. Notification 2150 14.1 [X] Acceptable Label Set 2151 14.2 [X] Notify Request Objects (GMPLS-RSVP) 2152 14.3 [X] Notify Message (GMPLS-RSVP) 2153 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 2155 15 Other features 2156 15.1 [X] Explicit Label Control 2157 15.2 [X] Protection Information 2158 15.3 [X] Administrative Status Information 2159 15.4 [ ] Interface Identification 2160 15.5 [ ] Errored Interface Identification 2161 15.6 [X] Link Fault Handling 2162 15.7 [X] Nodal Fault Handling 2164 16. Other specification(s) which apply: 2166 17. Other features supported: 2168 18. Currently-defined GMPLS signaling features not supported: 2170 Acceptable Label Set, Suggested Label Set, Contention resolution, 2171 non-standard SONET/SDH extensions to GMPLS. 2173 19. Notes (please describe purpose of project, give any information that 2174 might be useful to those interested in developing or using GMPLS) 2176 20. If you feel the above categories are not complete, add others which 2177 will better describe your project: 2179 Real World Deployment scenarios-- To get a fair idea as to how the 2180 real world sees GMPLS deployment to happen. How does GMPLS sees 2181 quick fail-over support to be provided to non-SONET/SDH networks. 2183 ===================================================================== 2185 Person filling out this form: 2187 Name:Manav Mishra 2188 E-mail:manav.mishra@intel.com 2189 Tel.:503-712-1843 2190 Title:Senior Network Software Engineer 2191 Company:Intel Corporation 2192 Date prepared:03/12/2002 2194 2.11. Japan Telecom Co., Ltd. 2196 GMPLS Signaling Implementation Survey Form [V 1.0] 2198 1. Organization: 2200 JAPAN TELECOM CO., LTD. 2202 1.1 Organization url(s): 2204 http://www.icl.japan-telecom.co.jp 2206 2. Product title(s): 2208 JT's virtual GMPLS signaling node 2210 2.1 Brief description(s): 2212 JT's virtual GMPLS signaling node is a GMPLS signaling emulator 2213 running on Linux/UNIX environment in order to do some GMPLS signaling 2214 tests. 2216 ---------------------------------------------------------------- 2218 3. Contact for GMPLS information 2219 3.1 Name: 2221 Hirokazu Ishimatsu 2223 3.2 Title: 2225 Assistant Manager 2227 3.3 E-mail: 2229 hirokazu@japan-telecom.co.jp 2231 3.4 Organization/department: 2233 Information and Communication Laboratories 2235 3.5 Postal address: 2237 Shuwa Higashi Yaesu Bldg., 5F 2238 2-9-1 Hachobori, Chuo-ku, Tokyo, 104-0032 Japan 2240 3.6 Phone: 2242 +81 3 5540 8493 2244 3.7 Fax: 2246 +81 3 5540 8485 2247 ---------------------------------------------------------------- 2249 4. Status: 2250 4.1 [X ] Development 2251 4.2 [ ] Alpha 2252 4.3 [ ] Beta 2253 4.4 [ ] Product 2254 4.5 [ ] Other (describe): 2256 5. Switching capabilities 2257 5.1 [ ] PSC 2258 5.2 [ ] TDM 2259 5.3 [ ] LSC 2260 5.4 [ ] FSC 2262 6. Reference Drafts (please list, include version numbers) 2263 6.1 draft-ietf-ccamp-ospf-gmpls-extentions-00.txt 2264 6.2 draft-ietf-mpls-generalized-signaling-07.txt 2265 6.3 draft-ietf-mpls-generalized-rsvp-te-06.txt 2266 6.4 draft-ietf-ccamp-lmp-02.txt 2267 6.5 [ ] 2268 6.6 [ ] 2270 7. Interface technologies 2271 7.1 [ ] Frame Relay 2272 7.2 [ ] ATM 2273 7.3 [ ] Ethernet V2/DIX 2274 7.4 [X ] Ethernet 802.3 for singaling channel 2275 7.5 [ ] SDH 2276 7.6 [ ] SONET 2277 7.7 [ ] Lambda (photonic) 2278 7.8 [ ] Fiber 2279 7.9 [ ] FiberChannel 2280 7.10 [ ] Other (describe): 2282 8. Availability 2283 8.1 [ ] Public and free 2284 8.2 [ ] Only to selected organizations/companies but free 2285 8.3 [ ] On sale. 2286 8.4 [X ] For internal company use only 2287 8.5 [ ] Other: 2289 9. Implementation based on: (check all that apply) 2290 9.1 [ ] Purchased code (please list source if possible) 2291 9.2 [ ] Free code (please list source if possible) 2292 9.3 [X ] Internal implementation (no outside code, just from specs) 2293 9.4 [ ] Internal implementation on top of purchased or free code 2294 9.4.1 [ ] List portions from external source 2295 9.4.2 [ ] List portions developed internally 2297 10. Supported Label Types 2298 10.1 [ ] MPLS Label 2299 10.2 [X ] Generalized Label 2300 10.3 [ ] Waveband Label 2301 10.4 [ ] SONET/SDH Label 2303 11. Label Related 2304 11.1 [X] Suggested Label 2305 11.2 [ ] Label Set 2306 12. Traffic Parameters 2307 12.1 [X ] Intserv (Please list which) 2309 PATH 2310 Session 2311 IF_ID RSVP Hop 2312 Time Values 2313 Sender Template 2314 Sender Tspec 2315 Message_ID/Message_ID_ACK/Message_ID_NACK 2316 ERO 2317 RRO 2318 Generalized Label Request (LSC/FSC only) 2319 Suggested Label 2320 Upstream Label 2321 Recovery Label 2322 Protection 2323 Notify Req 2324 AdminStatus 2326 PATHErr 2327 Session 2328 Sender Template 2329 Sender Tspec 2330 Message_ID/Message_ID_ACK/Message_ID_NACK 2331 ErrorSpec 2332 RRO 2334 RESV 2335 Session 2336 Time Values 2337 Message_ID/Message_ID_ACK/Message_ID_NACK 2338 IF_ID RSVP Hop 2339 Resv Confirm 2340 Notify Request 2341 AdminStatus 2342 Style (FF or SE) 2343 Flowspec 2344 Filterspec 2345 RSVP Label 2346 RRO 2347 Generalized Label 2349 RESVErr 2350 Session 2351 IF_ID RSVP Hop 2352 Message_ID/Message_ID_ACK/Message_ID_NACK 2353 ErrorSpec 2354 Style (FF and SE) 2356 12.2 [ ] CR-LDP 2357 12.3 [X ] GMPLS Bandwidth Encoding 2358 12.4 [ ] SONET/SDH 2360 13. [X ] Bidirectional LSPs 2362 14. Notification 2363 14.1 [ ] Acceptable Label Set 2364 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 2365 14.3 [ ] Notify Message (GMPLS-RSVP) 2366 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 2368 15 Other features 2369 15.1 [X ] Explicit Label Control 2370 15.2 [X ] Protection Information 2371 15.3 [ ] Administrative Status Information 2372 15.4 [ ] Interface Identification 2373 15.5 [ ] Errored Interface Identification 2374 15.6 [ ] Link Fault Handling 2375 15.7 [ ] Nodal Fault Handling 2377 16. Other specification(s) which apply: 2379 17. Other features supported: 2381 18. Currently-defined GMPLS signaling features not supported: 2383 19. Notes (please describe purpose of project, give any information that 2384 might be useful to those interested in developing or using GMPLS) 2386 GMPLS lab tests & field trial 2388 20. If you feel the above categories are not complete, add others which 2389 will better describe your project: 2391 2.12. Juniper Networks 2393 GMPLS Signaling Implementation Survey Form [V 1.0] 2395 1. Organization: Juniper Networks 2397 1.1 Organization url(s): www.juniper.net 2399 2. Product title(s): GMPLS signaling 2400 2.1 Brief description(s): 2402 This implementation aims at being able to dynamically signal 2403 generalized LSPs initiated by the router, across an optical core. It 2404 uses RSVP for signaling. The initial focus is on the signaling 2405 aspects rather than routing in a GMPLS domain. The purpose is to 2406 come up with an interoperable signaling solution and then move 2407 forward. The attributes for the label-switched path (encoding type, 2408 bandwidth, switching type; etc) will be configurable on the router, 2409 and will be translated into an appropriate RSVP signaling 2410 request. Bidirectional LSP setup is supported and so is control-data 2411 plane separation. Other specifics are listed below. 2413 - ---------------------------------------------------------------- 2415 3. Contact for GMPLS information 2416 3.1 Name: Arthi Ayyangar 2418 3.2 Title: Member of Technical Staff 2420 3.3 E-mail: arthi@juniper.net 2422 3.4 Organization/department: Engineering / Software 2424 3.5 Postal address: 1194 N. Mathilda Ave, Sunnyvale, CA 94089 2426 3.6 Phone: (408) 745 2110 2428 3.7 Fax: (408) 745 8905 2429 - 2430 ---------------------------------------------------------------- 2432 4. Status: 2433 4.1 [ ] Development 2434 4.2 [ ] Alpha 2435 4.3 [*] Beta 2436 4.4 [ ] Product 2437 4.5 [ ] Other (describe): 2439 5. Switching capabilities 2440 5.1 [*] PSC 2441 5.2 [ ] TDM 2442 5.3 [ ] LSC 2443 5.4 [ ] FSC 2445 6. Reference Drafts (please list, include version numbers) 2446 6.1 [*] draft-ietf-mpls-generalized-signaling-07.txt 2447 6.2 [*] draft-ietf-mpls-generalized-rsvp-te-06.txt 2448 6.3 [*] draft-ietf-mpls-lsp-hierarchy-04.txt (portions of this) 2449 6.4 [*] draft-ietf-mpls-bundle-01.txt 2450 6.5 [*] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 2451 6.6 [*] IANA proposed values sent by Lou 2453 7. Interface technologies 2454 7.1 [ ] Frame Relay 2455 7.2 [ ] ATM 2456 7.3 [*] Ethernet V2/DIX 2457 7.4 [*] Ethernet 802.3 2458 7.5 [*] SDH 2459 7.6 [*] SONET 2460 7.7 [ ] Lambda (photonic) 2461 7.8 [ ] Fiber 2462 7.9 [ ] FiberChannel 2463 7.10 [*] Other (describe): Packet 2465 8. Availability 2466 8.1 [ ] Public and free 2467 8.2 [ ] Only to selected organizations/companies but free 2468 8.3 [ ] On sale. 2469 8.4 [*] For internal company use only 2470 8.5 [*] Other: Field trials 2472 9. Implementation based on: (check all that apply) 2473 9.1 [ ] Purchased code (please list source if possible) 2474 9.2 [ ] Free code (please list source if possible) 2475 9.3 [*] Internal implementation (no outside code, just from specs) 2476 9.4 [ ] Internal implementation on top of purchased or free code 2477 9.4.1 [ ] List portions from external source 2478 9.4.2 [ ] List portions developed internally 2480 10. Supported Label Types 2481 10.1 [*] MPLS Label 2482 10.2 [*] Generalized Label 2483 10.3 [ ] Waveband Label 2484 10.4 [*] SONET/SDH Label 2486 11. Label Related 2487 11.1 [*] Suggested Label 2488 11.2 [ ] Label Set 2490 12. Traffic Parameters 2491 12.1 [*] Intserv (Please list which) (Token Bucket) 2492 12.2 [ ] CR-LDP 2493 12.3 [*] GMPLS Bandwidth Encoding 2494 12.4 [*] SONET/SDH 2495 13. [*] Bidirectional LSPs 2497 14. Notification 2498 14.1 [ ] Acceptable Label Set 2499 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 2500 14.3 [ ] Notify Message (GMPLS-RSVP) 2501 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 2503 15 Other features 2504 15.1 [ ] Explicit Label Control 2505 15.2 [*] Protection Information 2506 15.3 [ ] Administrative Status Information 2507 15.4 [*] Interface Identification 2508 15.5 [*] Errored Interface Identification 2509 15.6 [ ] Link Fault Handling 2510 15.7 [ ] Nodal Fault Handling 2512 16. Other specification(s) which apply: 2514 17. Other features supported: 2516 18. Currently-defined GMPLS signaling features not supported: 2517 ** Graceful restart (link and node failures), 2518 ** Notify 2519 ** Admin Status 2521 19. Notes (please describe purpose of project, give any information that 2522 might be useful to those interested in developing or using GMPLS) 2524 20. If you feel the above categories are not complete, add others which 2525 will better describe your project: 2526 ** Control channel separation 2527 ** Refresh reduction 2529 ==================================================================== 2531 Person filling out this form: 2533 Name: Arthi Ayyangar 2534 E-mail: arthi@juniper.net 2535 Tel.: (408) 745 2110 2536 Title: Member of Techical Staff 2537 Company: Juniper Networks 2538 Date prepared: 03/12/02 2540 2.13. Lumentis AB 2542 GMPLS Signaling Implementation Survey Form [V 1.0] 2544 1. Organization: Lumentis AB 2546 1.1 Organization url(s): www.lumentis.se 2548 2. Product title(s): Mentis systems 2550 2.1 Brief description(s): DWDM systems for the metro environment 2552 ---------------------------------------------------------------- 2554 3. Contact for GMPLS information 2555 3.1 Name: Mats Dahlgren 2557 3.2 Title: 2559 3.3 E-mail: Mats.Dahlgren@lumentis.se 2561 3.4 Organization/department: Lumentis AB 2563 3.5 Postal address: Jakobsdalsgatan 17, SE-12653 Hagersten, Sweden 2565 3.6 Phone: +46 8 52 76 75 50 2567 3.7 Fax: +46 8 52 76 75 99 2568 ---------------------------------------------------------------- 2570 4. Status: 2571 4.1 [x] Development 2572 4.2 [ ] Alpha 2573 4.3 [ ] Beta 2574 4.4 [ ] Product 2575 4.5 [ ] Other (describe): 2577 5. Switching capabilities 2578 5.1 [ ] PSC 2579 5.2 [ ] TDM 2580 5.3 [x] LSC 2581 5.4 [ ] FSC 2583 6. Reference Drafts (please list, include version numbers) 2584 6.1 [ ] 2585 6.2 [ ] 2586 6.3 [ ] 2587 6.4 [ ] 2588 6.5 [ ] 2589 6.6 [ ] 2591 7. Interface technologies 2592 7.1 [ ] Frame Relay 2593 7.2 [ ] ATM 2594 7.3 [ ] Ethernet V2/DIX 2595 7.4 [ ] Ethernet 802.3 2596 7.5 [ ] SDH 2597 7.6 [ ] SONET 2598 7.7 [x] Lambda (photonic) 2599 7.8 [ ] Fiber 2600 7.9 [ ] FiberChannel 2601 7.10 [ ] Other (describe): 2603 8. Availability 2604 8.1 [ ] Public and free 2605 8.2 [ ] Only to selected organizations/companies but free 2606 8.3 [ ] On sale. 2607 8.4 [x] For internal company use only 2608 8.5 [ ] Other: 2610 9. Implementation based on: (check all that apply) 2612 9.1 [ ] Purchased code (please list source if possible) 2613 9.2 [ ] Free code (please list source if possible) 2614 9.3 [ ] Internal implementation (no outside code, just from specs) 2615 9.4.1 [X] List portions from external source 2616 OSPFv2 2617 9.4.2 [X] List portions developed internally 2618 OSPF-TE 2619 RSVP-TE 2620 LMP 2622 10. Supported Label Types 2623 10.1 [ ] MPLS Label 2624 10.2 [x] Generalized Label 2625 10.3 [ ] Waveband Label 2626 10.4 [ ] SONET/SDH Label 2628 11. Label Related 2629 11.1 [ ] Suggested Label 2630 11.2 [ ] Label Set 2632 12. Traffic Parameters 2633 12.1 [ ] Intserv (Please list which) 2634 12.2 [ ] CR-LDP 2635 12.3 [x] GMPLS Bandwidth Encoding 2636 12.4 [ ] SONET/SDH 2638 13. [x] Bidirectional LSPs 2640 14. Notification 2641 14.1 [ ] Acceptable Label Set 2642 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 2643 14.3 [ ] Notify Message (GMPLS-RSVP) 2644 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 2646 15 Other features 2647 15.1 [ ] Explicit Label Control 2648 15.2 [ ] Protection Information 2649 15.3 [ ] Administrative Status Information 2650 15.4 [ ] Interface Identification 2651 15.5 [ ] Errored Interface Identification 2652 15.6 [ ] Link Fault Handling 2653 15.7 [ ] Nodal Fault Handling 2655 16. Other specification(s) which apply: 2657 17. Other features supported: 2659 18. Currently-defined GMPLS signaling features not supported: 2661 19. Notes (please describe purpose of project, give any information that 2662 might be useful to those interested in developing or using GMPLS) 2664 20. If you feel the above categories are not complete, add others which 2665 will better describe your project: 2667 ============================================================== 2669 Person filling out this form: 2671 Name: see contact for GMPLS information 2672 E-mail: 2673 Tel.: 2674 Title: 2675 Company: 2676 Date prepared: 03/13/02 2678 2.14. Marconi 2680 GMPLS Signaling Implementation Survey Form [V 1.0] 2682 1. Organization: Marconi. 2684 1.1 Organization url(s): www.marconi.com 2686 2. Product title(s): Transport Network Control Plane 2688 2.1 Brief description(s): 2689 Unified Control Plane for the SDH/SONET/Photonics product family 2691 ---------------------------------------------------------------- 2693 3. Contact for GMPLS information 2694 3.1 Name: Piergiorgio Sessarego 2696 3.2 Title: ASON Strategy Director 2698 3.3 E-mail: piergiorgio.sessarego@marconi.com 2700 3.4 Organization/department: ASON Strategy 2702 3.5 Postal address: Via A. Negrone 1/A 16153 Cornigliano (GE) Italy 2704 3.6 Phone: +390106003902 2706 3.7 Fax: 2708 --------------------------------------------------------------- 2710 4. Status: 2711 4.1 [X] Development 2712 4.2 [ ] Alpha 2713 4.3 [ ] Beta 2714 4.4 [ ] Product 2715 4.5 [X] Other (describe): An early GMPLS development is in place in a photonic ring of Marconi equipment (PMA-32) 2717 5. Switching capabilities 2718 5.1 [ ] PSC 2719 5.2 [X] TDM 2720 5.3 [X] LSC 2721 5.4 [X] FSC 2723 6. Reference Drafts (please list, include version numbers) 2724 6.1 [draft-ietf-ccamp-gmpls-architecture-01] 2725 6.2 [draft-ietf-mpls-generalized-signaling-07] 2726 6.3 [draft-ietf-mpls-generalized-rsvp-te-06] 2727 6.4 [draft-ietf-ccamp-gmpls-sonet-sdh-02] 2728 6.5 [draft-ietf-mpls-rsvp-unnum-03] 2729 6.6 [draft-ietf-mpls-lsp-hierarchy-04] 2730 6.7 [draft-ietf-mpls-bundle-01] 2732 7. Interface technologies 2733 7.1 [ ] Frame Relay 2734 7.2 [ ] ATM 2735 7.3 [ ] Ethernet V2/DIX 2736 7.4 [ ] Ethernet 802.3 2737 7.5 [X] SDH 2738 7.6 [X] SONET 2739 7.7 [X] Lambda (photonic) 2740 7.8 [X] Fiber 2741 7.9 [ ] FiberChannel 2742 7.10 [ ] Other (describe): 2744 8. Availability 2745 8.1 [ ] Public and free 2746 8.2 [ ] Only to selected organizations/companies but free 2747 8.3 [X] On sale. 2748 8.4 [ ] For internal company use only 2749 8.5 [ ] Other: 2751 9. Implementation based on: (check all that apply) 2752 9.1 [ ] Purchased code (please list source if possible) 2753 9.2 [ ] Free code (please list source if possible) 2754 9.3 [X] Internal implementation (no outside code, just from specs) 2755 9.4 [ ] Internal implementation on top of purchased or free code 2756 9.4.1 [ ] List portions from external source 2757 9.4.2 [ ] List portions developed internally 2759 10. Supported Label Types 2760 10.1 [ ] MPLS Label 2761 10.2 [X] Generalized Label 2762 10.3 [X] Waveband Label 2763 10.4 [X] SONET/SDH Label 2765 11. Label Related 2766 11.1 [ ] Suggested Label 2767 11.2 [X] Label Set 2769 12. Traffic Parameters 2770 12.1 [ ] Intserv (Please list which) 2771 12.2 [ ] CR-LDP 2772 12.3 [X] GMPLS Bandwidth Encoding 2773 12.4 [X] SONET/SDH 2775 13. [X] Bidirectional LSPs 2777 14. Notification 2778 14.1 [X] Acceptable Label Set 2779 14.2 [X] Notify Request Objects (GMPLS-RSVP) 2780 14.3 [X] Notify Message (GMPLS-RSVP) 2781 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 2783 15 Other features 2784 15.1 [X] Explicit Label Control 2785 15.2 [X] Protection Information 2786 15.3 [X] Administrative Status Information 2787 15.4 [X] Interface Identification 2788 15.5 [X] Errored Interface Identification 2789 15.6 [X] Link Fault Handling 2790 15.7 [X] Nodal Fault Handling 2792 16. Other specification(s) which apply: 2793 OIF 1.0 2795 17. Other features supported: 2797 18. Currently-defined GMPLS signaling features not supported: 2799 19. Notes (please describe purpose of project, give any information that 2800 might be useful to those interested in developing or using GMPLS) 2802 20. If you feel the above categories are not complete, add others which 2803 will better describe your project: 2805 ======================================================================= 2807 Person filling out this form: 2809 Name: Diego Caviglia 2810 E-mail: diego.caviglia@marconi.com 2811 Tel.: +390106003808 2812 Title: ASON Strategy 2813 Company: Marconi 2814 Date prepared: 11/03/02 2816 2.15. Movaz Networks 2818 GMPLS Signaling Implementation Survey Form [V 1.0] 2820 1. Organization: Movaz Networks. 2822 1.1 Organization url(s): www.movaz.com 2824 2. Product title(s): RAYstar, RAYexpress 2826 2.1 Brief description(s): 2828 RAYstar integrates the values of a very-high-density OADM (optical 2829 add/drop multiplexer) and a compact, distributed optical switching 2830 platform into a single 7 foot bay. 2832 The RAYexpress OADM (optical add/drop multiplexer) provides a versatile, 2833 cost effective, and compact platform for wavelength services in access 2834 and regional applications. 2836 ---------------------------------------------------------------- 2838 3. Contact for GMPLS information 2839 3.1 Name: Adrian Farrel 2841 3.2 Title: Director Protocol Development 2843 3.3 E-mail: afarrel@movaz.com 2845 3.4 Organization/department: 2847 3.5 Postal address: 7926 Jones Branch Drive 2848 Suite 615 2849 McLean, VA 22102 2851 3.6 Phone: 703-847-1867 2853 3.7 Fax: 703-847-3975 2854 ---------------------------------------------------------------- 2856 4. Status: 2857 4.1 [ ] Development 2858 4.2 [ ] Alpha 2859 4.3 [ ] Beta 2860 4.4 [x] Product 2861 Swi [ ] Other (describe): 2863 5. Switching capabilities 2864 5.1 [ ] PSC 2865 5.2 [x] TDM 2866 5.3 [x] LSC 2867 5.4 [x] FSC 2869 6. Reference Drafts (please list, include version numbers) 2870 6.1 draft-ietf-mpls-generalized-signaling-07.txt 2871 6.2 draft-ietf-mpls-generalized-rsvp-te-06.txt 2872 6.3 draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 2873 6.4 RFC3209 2874 6.5 RFC2961 2875 6.6 RFC2205 2876 6.7 draft-nadeau-ccamp-gmpls-tc-mib-01.txt 2877 6.8 draft-nadeau-ccamp-gmpls-te-mib-01.txt 2879 Interface technologies 2880 7.1 [ ] Frame Relay 2881 7.2 [ ] ATM 2882 7.3 [ ] Ethernet V2/DIX 2883 7.4 [ ] Ethernet 802.3 2884 7.5 [x] SDH 2885 7.6 [x] SONET 2886 7.7 [x] Lambda (photonic) 2887 7.8 [x] Fiber 2888 7.9 [ ] FiberChannel 2889 7.10 [x] Other (describe): 2890 GigEthernet 2892 8.1 [ ] Public and free 2893 8.2 [ ] Only to selected organizations/companies but free 2894 8.3 [x] On sale. 2895 8.4 [ ] For internal company use only 2896 8.5 [ ] Other: 2898 9. Implementation based on: (check all that apply) 2899 9.1 [ ] Purchased code (please list source if possible) 2900 9.2 [ ] Free code (please list source if possible) 2901 9.3 [ ] Internal implementation (no outside code, just from specs) 2902 9.4 [x] Internal implementation on top of purchased or free code 2903 9.4.1 [ ] List portions from external source 2904 Base RSVP-TE code from LabN 2905 9.4.2 [ ] List portions developed internally 2906 RSVP-TE for GMPLS 2907 MIB support 2909 10. Supported Label Types 2910 10.1 [ ] MPLS Label 2911 10.2 [x] Generalized Label 2912 10.3 [ ] Waveband Label 2913 10.4 [x] SONET/SDH Label 2915 11. Label Related 2916 11.1 [x] Suggested Label 2917 11.2 [x] Label Set 2919 12. Traffic Parameters 2920 12.1 [ ] Intserv (Please list which) 2921 12.2 [ ] CR-LDP 2922 12.3 [x] GMPLS Bandwidth Encoding 2923 12.4 [x] SONET/SDH 2925 13. [x] Bidirectional LSPs 2927 14. Notification 2928 14.1 [x] Acceptable Label Set 2929 14.2 [x] Notify Request Objects (GMPLS-RSVP) 2930 14.3 [x] Notify Message (GMPLS-RSVP) 2931 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 2933 15 Other features 2934 15.1 [x] Explicit Label Control 2935 15.2 [x] Protection Information 2936 15.3 [x] Administrative Status Information 2937 15.4 [x] Interface Identification 2938 15.5 [x] Errored Interface Identification 2939 15.6 [x] Link Fault Handling 2940 15.7 [x] Nodal Fault Handling 2942 16. Other specification(s) which apply: 2944 17. Other features supported: 2945 OSPF and OSPF extensions for TE and GMPLS 2947 18. Currently-defined GMPLS signaling features not supported: 2948 CR-LDP 2950 19. Notes (please describe purpose of project, give any information that 2951 might be useful to those interested in developing or using GMPLS) 2953 20. If you feel the above categories are not complete, add others which 2954 will better describe your project: 2956 ============================================================== 2958 Person filling out this form: 2960 Name: Adrian Farrel 2961 E-mail: 2962 Tel.: 2963 Title: 2964 Company: 2965 Date prepared: 3/13/02 2967 2.16. NEC Corporation 2969 GMPLS Signaling Implementation Survey Form [V 1.1] 2971 1. Organization: 2973 NEC Corporation 2975 1.1 Organization url(s): 2977 www.nec.com 2979 2. Product title(s): 2980 SpectralWave Networking Software for U-Node, DWDM 2982 2.1 Brief description(s): 2984 SpectralWave family supports crossconnects on SDH/SONET and wavelength 2985 multiplexing for metro and core network with GMPLS/ASON based control 2986 plane. 2988 ---------------------------------------------------------------- 2990 3. Contact for GMPLS information 2991 3.1 Name: 2992 Su-Hun YUN 2994 3.2 Title: 2995 Assistant Manager 2997 3.3 E-mail: 2998 s-yun@bl.jp.nec.com 3000 3.4 Organization/department: 3001 Systems Development Department 3002 First Optical Network Division 3004 3.5 Postal address: 3005 1753 Shimonumabe Nakahara-ku 3006 Kawasaki, 211-8666, Japan 3008 3.6 Phone: 3009 +81 44 396 3247 3011 3.7 Fax: 3012 +81 44 435 5161 3014 ---------------------------------------------------------------- 3016 4. Status: 3017 4.1 [ ] Development 3018 4.2 [ ] Alpha 3019 4.3 [X] Beta 3020 4.4 [X] Product 3021 4.5 [ ] Other (describe): 3023 5. Switching capabilities 3024 [GMPLS- [GMPLS- 3025 RSVP] LDP] 3026 5.1 [ ] [ ] PSC 3027 5.2 [X] [ ] TDM 3028 5.3 [ ] [ ] LSC 3029 5.4 [ ] [ ] FSC 3031 6. Reference Drafts (please list, include version numbers) 3033 6.1 [X] draft-ietf-mpls-generalized-signaling-08.txt 3034 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-07.txt 3035 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-05.txt 3036 6.4 [X] draft-ietf-mpls-rsvp-unnum-02.txt 3037 6.5 [X] draft-ietf-mpls-bundle-03.txt 3039 6.6 [X] draft-ietf-mpls-lmp-02.txt 3041 6.7 [X] draft-ietf-ccamp-gmpls-routing-04.txt 3042 6.8 [X] draft-ietf-ccamp-ospf-gmpls-extensions-07.txt 3044 7. Interface technologies 3045 7.1 [ ] Frame Relay 3046 7.2 [ ] ATM 3047 7.3 [X] Ethernet V2/DIX 3048 7.4 [X] Ethernet 802.3 3049 7.5 [X] SDH 3050 7.6 [X] SONET 3051 7.7 [ ] Lambda (photonic) 3052 7.8 [ ] Fiber 3053 7.9 [ ] FiberChannel 3054 7.10 [ ] Other (describe): 3056 8. Availability 3057 [GMPLS- [GMPLS- 3058 RSVP] LDP] 3059 8.1 [ ] [ ] Public and free 3060 8.2 [ ] [ ] Only to selected organizations/companies but free 3061 8.3 [X] [ ] On sale. 3062 8.4 [ ] [ ] For internal company use only 3063 8.5 [ ] [ ] Other: 3065 9. Implementation based on: (check all that apply) 3066 [GMPLS- [GMPLS- 3067 RSVP] LDP] 3068 9.1 [X] [ ] Purchased code 3069 (please list source if possible) 3070 9.2 [ ] [ ] Free code 3071 (please list source if possible) 3072 9.3 [X] [ ] Internal implementation 3073 (no outside code, just from specs) 3074 9.4 [X] [ ] Internal implementation on top of purchased 3075 or free code 3076 9.4.1 List portions from external source: 3077 (Identify protocol if appropriate) 3078 9.4.2 List portions developed internally: 3079 (Identify protocol if appropriate) 3081 10. Supported Label Types 3082 [GMPLS- [GMPLS- 3083 RSVP] LDP] 3084 10.1 [ ] [ ] MPLS Label 3085 10.2 [ ] [ ] Generalized Label 3086 10.3 [ ] [ ] Waveband Label 3087 10.4 [X] [ ] SONET/SDH Label 3089 11. Label Related 3090 [GMPLS- [GMPLS- 3091 RSVP] LDP] 3092 11.1 [X] [ ] Suggested Label 3093 11.2 [X] [ ] Label Set 3095 12. Traffic Parameters 3096 [GMPLS- [GMPLS- 3097 RSVP] LDP] 3098 12.1 [ ] Intserv (Please list which) 3099 12.2 [ ] CR-LDP 3100 12.3 [X] [ ] GMPLS Bandwidth Encoding 3101 12.4 [X] [ ] SONET/SDH 3103 13. Bidirectional LSPs 3104 [GMPLS- [GMPLS- 3105 RSVP] LDP] 3106 [X] [ ] Bidirectional LSPs 3108 14. Notification 3109 [GMPLS- [GMPLS- 3110 RSVP] LDP] 3111 14.1 [ ] [ ] Acceptable Label Set 3112 14.2 [X] Notify Request Objects (GMPLS-RSVP) 3113 14.3 [X] Notify Message (GMPLS-RSVP) 3114 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 3116 15 Other features 3117 [GMPLS- [GMPLS- 3118 RSVP] LDP] 3119 15.1 [X] [ ] Explicit Label Control 3120 15.2 [X] [ ] Protection Information 3121 15.3 [X] [ ] Administrative Status Information 3122 15.4 [X] [ ] Interface Identification 3123 15.5 [X] [ ] Errored Interface Identification 3124 15.6 [X] [ ] Link Fault Handling 3125 15.7 [X] [ ] Nodal Fault Handling 3127 16. Other specification(s) which apply: 3129 17. Other features supported: 3130 17.1 related to [GMPLS-RSVP] 3132 OIF UNI 1.0 is supported. 3134 17.2 related to [GMPLS-LDP] 3135 17.3 Other 3137 18. Currently-defined GMPLS signaling features not supported: 3138 18.1 related to [GMPLS-RSVP] 3139 18.2 related to [GMPLS-LDP] 3140 18.3 related to [GMPLS-SONET] 3141 18.4 Other 3143 19. Notes (please describe purpose of project, give any information that 3144 might be useful to those interested in developing or using GMPLS) 3146 20. If you feel the above categories are not complete, add others which 3147 will better describe your project: 3149 As a part of SpectralWave Networking Software, SepctralWave Control 3150 Plane fully controls SpectralWave DWDM and U-Node by interacting with 3151 SpectralWave Manager (NMS) and SpectralWave Planning Tool. 3153 ==================================================================== 3155 Person filling out this form: 3157 Name: Su-Hun YUN 3158 E-mail: s-yun@bl.jp.nec.com 3159 Tel.: +81 44 396 3247 3160 Title: Assistant Manager 3161 Company: NEC Corporation 3162 Date prepared: Sep. 20, 2002 3164 2.17. NetPlane Systems 3166 GMPLS Signaling Implementation Survey Form [V 1.0] 3168 1. Organization: NetPlane Systems, a division of Conexant Systems 3170 1.1 Organization url(s): www.netplane.com 3172 2. Product title(s): 3173 LTCS (Label Traffic Control System)- Optical and Classical, LTCS-LMP 3175 2.1 Brief description(s): 3177 3. Portable software protocol products which support multiple ietf 3178 drafts and RFCs, and implementation agreements coming out of the OIF. 3179 MPLS and GMPLS Signaling Products, which includes RSVP, LDP, CR-LDP, 3180 OUNI. Also have LMP to support optical network requirements. 3182 ---------------------------------------------------------------- 3184 3. Contact for GMPLS information 3185 3.1 Name: Sandra Herforth 3187 3.2 Title: Sr. Product Manager 3189 3.3 E-mail: sherforth@netplane.com 3191 3.4 Organization/department: Marketing 3193 3.5 Postal address: 200 Lowder Brook Drive, Westwood, MA 02090 3194 3.6 Phone: 781-251-5363 3196 3.7 Fax: 781-329-6703 3197 ---------------------------------------------------------------- 3199 4. Status: 3200 4.1 [ ] Development 3201 4.2 [ ] Alpha 3202 4.3 [ ] Beta 3203 4.4 [X] Product: All products listed above are released and are generally available. 3204 4.5 [ ] Other (describe): 3206 5. Switching capabilities 3207 5.1 [X] PSC 3208 5.2 [X] TDM 3209 5.3 [X] LSC 3210 5.4 [X] FSC 3212 6. Reference Drafts (please list, include version numbers) 3214 RFC 2205 Resource ReSerVation Protocol (RSVP) 3215 RFC 2206 RSVP Management Information Base using SMIv2 3216 RFC 2208 Resource ReSerVation Protocol (RSVP) Version 1 Applicability Statement 3217 RFC 2209 Resource ReSerVation Protocol (RSVP) Version 1 Message Processing Rules 3218 RFC 2210 The Use of RSVP with IETF Integrated Services 3219 RFC 2547 BGP/MPLS VPNs 3220 RFC 2702 Requirements for Traffic Engineering over MPLS 3221 RFC 2750 RSVP Extensions for Policy Control 3222 RFC 2764 Framework for IP-based Virtual Private Networks 3223 RFC 2961 RSVP Refresh Overhead Reduction Extensions 3224 RFC 2997 Specification of the Null Service Type 3225 RFC 3031 Multiprotocol Label Switching Architecture 3226 RFC 3032 MPLS Label Stack Encoding 3227 RFC 3034 Use of Label Switching on Frame Relay Networks Specification 3228 RFC 3035 MPLS using LDP and ATM VC Switching 3229 RFC 3036 LDP Specification 3230 RFC 3037 LDP Applicability 3231 RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels 3232 RFC 3210 Applicability statement for the extensions to RSVP for LSP Tunnels 3233 RFC 3212 Contraint-Based LSP Setup using LDP 3234 RFC 3213 Applicability Statement for CR-LDP 3236 draft-ietf-ccamp-gmpls-architecture-02 Generalized Multi-Protocol Label Switching (GMPLS) Architecture 3237 draft-ietf-mpls-generalized-signaling-04 Generalized MPLS-Signaling Functional Description 3238 draft-ietf-mpls-generalized-rsvp-te-02 Generalized MPLS Signaling - RSVP-TE Extensions 3239 draft-ietf-ccamp-gmpls-architecture-02 Generalized Multi-Protocol Label Switching (GMPLS) Architecture 3240 draft-many-ccamp-gmpls-framework-00 A Framework for Generalized Multi-protocol Label Switching (GMPLS) 3241 draft-ietf-mpls-rsvp-unnum-04 Signalling Unnumbered Links in RSVP-TE 3242 draft-ietf-mpls-lsp-hierarchy-03 LSP Hierarchy with MPLS TE 3243 draft-ietf-mpls-bundle-01 Link Bundling in MPLS Traffic Engineering 3244 draft-ietf-ccamp-gmpls-sonet-sdh-02 GMPLS Extensions for SONET and SDH Control 3245 draft-oetf-ccamp-gmpls-sonet-sdh-extensions GMPLS Extensions to Control Non-Standard SONET and SDH Features 3246 draft-ietf-mpls-diff-ext-09 MPLS Support of Differentiated Services 3247 draft-ietf-mpls-lsr-mib-07 Multiprotocol Label Switching (MPLS) LSR Management Information Base 3248 draft-ietf-mpls-mpls-te-mib-06 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base 3249 draft-ietf-mpls-ldp-mib-08 Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP) 3250 draft-ietf-mpls-ftn-mib-03 Multiprotocol Label Switching (MPLS) FEC-To-NHLFE (FTN) Management Information Base 3251 draft-ietf-mpls-rsvp-lsp-tunnel-09 RSVP-TE: Extensions to RSVP for LSP Tunnels 3252 draft-ietf-mpls-rsvp-tunnel-applicability-02 Applicability Statement for Extensions to RSVP for LSP-Tunnels 3253 draft-ietf-mpls-cr-ldp-06 Constraint-Based LSP Setup using LDP 3254 draft-ietf-mpls-crisp-modify-03 LSP Modification Using CR-LDP 3255 draft-ietf-mpls-ldp-state-04 LDP State Machine 3256 draft-ietf-mpls-tc-mib-02 Definition of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management 3257 draft-martini-l2circuit-trans-mpls-08 Transport of Layer 2 Frames Over MPLS 3258 draft-martini-l2-encap-mpls-04 Encapsulation Methods for Transport of Layer 2 Frames Over IP and MPLS Networks 3259 draft-ietf-ppvpn-rfc2547bis-01 BGP/MPLS VPNs 3260 draft-ietf-mpls-mgmt-overview Multiprotocol Label Switching (MPLS) Management Overview 3261 draft-ietf-ipo-ason-02 Automatic Switched Optical Network (ASON) Architecture and Its Related Protocols 3262 draft-ietf-ccamp-lmp-02 Link Management Protocol (LMP) 3263 draft-fredette-lmp-wdm-03 Link Management Protocol (LMP) for DWDM Optical Line Systems 3264 draft-ietf-ccamp-lmp-mib-00 Link Management Protocol Management Information Base Using SMIv2 3266 7. Interface technologies 3267 7.1 [X] Frame Relay 3268 7.2 [X] ATM 3269 7.3 [X] Ethernet V2/DIX 3270 7.4 [X] Ethernet 802.3 3271 7.5 [X] SDH 3272 7.6 [X] SONET 3273 7.7 [X] Lambda (photonic) 3274 7.8 [X] Fiber 3275 7.9 [ ] FiberChannel 3276 7.10 [ ] Other (describe): 3278 8. Availability 3279 8.1 [ ] Public and free 3280 8.2 [ ] Only to selected organizations/companies but free 3281 8.3 [X] On sale. 3282 8.4 [ ] For internal company use only 3283 8.5 [ ] Other: 3285 9. Implementation based on: (check all that apply) 3286 9.1 [ ] Purchased code (please list source if possible) 3287 9.2 [ ] Free code (please list source if possible) 3288 9.3 [X] Internal implementation (no outside code, just from specs) 3289 9.4 [ ] Internal implementation on top of purchased or free code 3290 9.4.1 [ ] List portions from external source 3291 9.4.2 [X] List portions developed internally 3293 All of NetPlane Systems' Implementations are based completely on 3294 internally developed code. NetPlane owns all intellectual property 3295 relating to its products and provides full indemnification against 3rd 3296 party claims for possible future royalties, etc. 3298 10. Supported Label Types 3299 10.1 [X] MPLS Label 3300 10.2 [X] Generalized Label 3301 10.3 [X] Waveband Label 3302 10.4 [X] SONET/SDH Label 3304 11. Label Related 3305 11.1 [X] Suggested Label 3306 11.2 [X] Label Set 3308 12. Traffic Parameters 3309 12.1 [X] Intserv (Controlled load, Guaranteed Service, and Null Service Type) 3310 12.2 [X] CR-LDP 3311 12.3 [X] GMPLS Bandwidth Encoding 3312 12.4 [X] SONET/SDH 3314 13. [X] Bidirectional LSPs 3316 14. Notification 3317 14.1 [X] Acceptable Label Set 3318 14.2 [X] Notify Request Objects (GMPLS-RSVP) 3319 14.3 [X] Notify Message (GMPLS-RSVP) 3320 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 3322 15 Other features 3323 15.1 [X] Explicit Label Control 3324 15.2 [X] Protection Information 3325 15.3 [X] Administrative Status Information 3326 15.4 [X] Interface Identification 3327 15.5 [ ] Errored Interface Identification 3328 15.6 [X] Link Fault Handling 3329 15.7 [X] Nodal Fault Handling 3330 - Supported by Redundant and Distributed Product Packages 3332 16. Other specification(s) which apply: 3334 OIF UNI 1.0 Signaling Implementation Agreement, oif2000.125.7 3335 ITU-T G.8080/Y.1304-Architecture and Specifications for Automatically 3336 Switched Optical Network 3338 ITU-T G.7713/Y.1704-Distributed Call and Connection Management 3340 ITU-T G.7712/Y.1703-Architecture and Specification of Data Communication Network 3342 17. Other features supported: 3344 Support of Redundant Architectures to support Nodal and Control Plane Failure 3345 Fault Tolerance (hot backup) 3346 Flexible Software to support multiple types of distributed architectures 3347 Bundled links 3348 Non-associated (out of band) signaling 3349 Graceful deletion 3350 LSP hierarchy 3351 Reverse LSPs 3352 Diffserv 3353 Resource Affinities 3354 Wavelength Conversion Incapable 3356 18. Currently-defined GMPLS signaling features not supported: 3358 Generally support all GMPLS signaling requirements which are adequately 3359 defined in the IETF drafts today. There are a few items like Graceful 3360 Restart and Persistence which have IETF Drafts or industry solutions 3361 which carriers are resistant to deploy in their current networks. 3362 NetPlane is taking a measured approach to support more appropriate and 3363 effective solutions. Fast Restart Link Bundling MIB is currently 3364 supported by an Enterprise MIB which was developed to support an early 3365 version of the Link Bundle MIB. 3367 19. Notes (please describe purpose of project, give any information that 3368 might be useful to those interested in developing or using GMPLS) 3370 NetPlane's LTCS product line supports a unified code base which 3371 (optionally) supports MPLS (RSVP-TE, LDP, CR-LDP), GMPLS (RSVP-TE) and 3372 OIF O-UNI (RSVP-TE).It has been used a majority of OEMs for a wide range 3373 of applications, including core optical network devices, where 3374 scalability and high availability is a critical requirement, a variety 3375 of optical "edge" devices where architectural flexibility, scalability 3376 and performance are key, including support for O-UNI and it has been 3377 field deployed in carrier networks for classical MPLS applications. 3379 To fully support GMPLS applications, NetPlane also offers LMP. 3381 Additionally NetPlane offers a full range of routing protocols, 3382 including OSPF and BGP4. The OSPF implementation is complemented by 3383 Traffic Engineering (TE) extensions and a Constrained Shortest Path 3384 First (CSPF) engine to calculate explicit paths for both IP and optical 3385 applications MPLS/GMPLS. 3387 Provide Software Source code to many types of Network Equipment 3388 Providers, NetPlane Systems has over 200 customers worldwide for all of 3389 their products. 3391 20. If you feel the above categories are not complete, add others which 3392 will better describe your project: 3394 ======================================================================= 3396 Person filling out this form: 3397 Name: Sandra Herforth 3398 E-mail: sherforth@netplane.com 3399 Tel.: 781-251-5363 3400 Title: Sr. Product Manager 3401 Company: NetPlane Systems 3402 Date prepared: April 3, 2002 3404 2.18. Nippon Telegraph and Telephone Corporation 3406 GMPLS Signaling Implementation Survey Form [V 1.1] 3408 1. Organization: Nippon Telegraph and Telephone Corporation 3410 1.1 Organization url(s): http://www.onlab.ntt.co.jp/ 3412 2. Product title(s): HIKARI router 3414 2.1 Brief description(s): 3415 NTT's HIKARI router is an integrated GMPLS router 3416 with L1/L2/L3 switching capabilities. 3418 ---------------------------------------------------------------- 3420 3. Contact for GMPLS information 3421 3.1 Name: Satoru Okamoto 3423 3.2 Title: Senior Research Engineer 3425 3.3 E-mail: okamoto@exa.onlab.ntt.co.jp 3427 3.4 Organization/department: NTT Network Innovation Laboratories 3429 3.5 Postal address: 9-11 Midori-Cho 3-Chome, Musashino-shi, 3430 Tokyo 180-8585 JAPAN 3432 3.6 Phone: +81 422 59 4353 3434 3.7 Fax: +81 422 59 6387 3435 ---------------------------------------------------------------- 3437 4. Status: 3438 4.1 [X] Development 3439 4.2 [ ] Alpha 3440 4.3 [ ] Beta 3441 4.4 [ ] Product 3442 4.5 [ ] Other (describe): 3444 5. Switching capabilities 3445 [GMPLS- [GMPLS- 3446 RSVP] LDP] 3447 5.1 [X] [X] PSC 3448 5.2 [ ] [ ] TDM 3449 5.3 [X] [X] LSC 3450 5.4 [ ] [ ] FSC 3452 6. Reference Drafts (please list, include version numbers) 3453 6.1 [RFC-3212] 3454 6.2 [draft-ietf-mpls-generalized-rsvp-te-06.txt] 3455 6.3 [draft-ietf-mpls-generalized-signaling-07.txt] 3456 6.4 [draft-ietf-ccamp-ospf-gmpls-extensions-05.txt] 3457 6.5 [ ] 3458 6.6 [ ] 3460 7. Interface technologies 3461 7.1 [ ] Frame Relay 3462 7.2 [ ] ATM 3463 7.3 [ ] Ethernet V2/DIX 3464 7.4 [X] Ethernet 802.3 3465 7.5 [X] SDH 3466 7.6 [X] SONET 3467 7.7 [X] Lambda (photonic) 3468 7.8 [ ] Fiber 3469 7.9 [ ] FiberChannel 3470 7.10 [ ] Other (describe): 3472 8. Availability 3473 [GMPLS- [GMPLS- 3474 RSVP] LDP] 3475 8.1 [ ] [ ] Public and free 3476 8.2 [ ] [ ] Only to selected organizations/companies but free 3477 8.3 [ ] [ ] On sale. 3479 8.4 [X] [X] For internal company use only 3480 8.5 [ ] [ ] Other: 3482 9. Implementation based on: (check all that apply) 3483 [GMPLS- [GMPLS- 3484 RSVP] LDP] 3485 9.1 [ ] [ ] Purchased code 3486 (please list source if possible) 3487 9.2 [ ] [ ] Free code 3488 (please list source if possible) 3489 9.3 [ ] [ ] Internal implementation 3490 (no outside code, just from specs) 3491 9.4 [X] [X] Internal implementation on top of purchased 3492 or free code 3493 9.4.1 List portions from external source: 3494 (Identify protocol if appropriate) 3495 9.4.2 List portions developed internally: 3496 (Identify protocol if appropriate) 3498 10. Supported Label Types 3499 [GMPLS- [GMPLS- 3500 RSVP] LDP] 3501 10.1 [X] [X] MPLS Label 3502 10.2 [X] [ ] Generalized Label 3503 10.3 [X] [X] Waveband Label 3504 10.4 [ ] [ ] SONET/SDH Label 3506 11. Label Related 3507 [GMPLS- [GMPLS- 3508 RSVP] LDP] 3509 11.1 [X] [ ] Suggested Label 3510 11.2 [X] [ ] Label Set 3512 12. Traffic Parameters 3513 [GMPLS- [GMPLS- 3514 RSVP] LDP] 3515 12.1 [ ] Intserv (Please list which) 3516 12.2 [X] CR-LDP 3517 12.3 [X] [ ] GMPLS Bandwidth Encoding 3518 12.4 [ ] [ ] SONET/SDH 3520 13. Bidirectional LSPs 3521 [GMPLS- [GMPLS- 3522 RSVP] LDP] 3523 [X] [X] Bidirectional LSPs 3525 14. Notification 3526 [GMPLS- [GMPLS- 3527 RSVP] LDP] 3528 14.1 [ ] [ ] Acceptable Label Set 3529 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 3530 14.3 [X] Notify Message (GMPLS-RSVP) 3531 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 3533 15 Other features 3534 [GMPLS- [GMPLS- 3535 RSVP] LDP] 3536 15.1 [X] [ ] Explicit Label Control 3537 15.2 [X] [ ] Protection Information 3538 15.3 [X] [ ] Administrative Status Information 3539 15.4 [X] [ ] Interface Identification 3540 15.5 [X] [ ] Errored Interface Identification 3541 15.6 [ ] [ ] Link Fault Handling 3542 15.7 [ ] [ ] Nodal Fault Handling 3544 16. Other specification(s) which apply: 3546 17. Other features supported: 3547 17.1 related to [GMPLS-RSVP] 3548 17.2 related to [GMPLS-LDP] 3549 17.3 Other 3551 18. Currently-defined GMPLS signaling features not supported: 3552 18.1 related to [GMPLS-RSVP] 3553 18.2 related to [GMPLS-LDP] 3554 18.3 related to [GMPLS-SONET] 3555 18.4 Other 3557 19. Notes (please describe purpose of project, give any information that 3558 might be useful to those interested in developing or using GMPLS) 3560 20. If you feel the above categories are not complete, add others which 3561 will better describe your project: 3563 ==================================================================== 3565 Person filling out this form: 3567 Name: Satoru Okamoto 3568 E-mail: okamoto@exa.onlab.ntt.co.jp 3569 Tel.: +81 422 59 4353 3570 Title: Senior Research Engineer 3571 Company: Nippon Telegraph and Telephone Corporation 3572 Date prepared: 05/31/2002 3574 2.19. Nortel Networks 3576 GMPLS Signaling Implementation Survey Form [V 1.0] 3578 1. Organization: Nortel Networks 3580 1.1 Organization url(s): www.nortelnetworks.com 3582 2. Product title(s): Automatic Switched Optical Networks (ASON) 3584 2.1 Brief description(s): optical control plane 3586 ---------------------------------------------------------------- 3588 3. Contact for GMPLS information 3590 3.1 Name: Don Fedyk 3592 3.2 Title:Senior Advisor 3594 3.3 E-mail: dwfedyk@nortelnetworks.com 3596 3.4 Organization/department: 3598 3.5 Postal address: 600 Technology Park, Billerica, MA 01450 3600 3.6 Phone:978 288 3041 3602 3.7 Fax: 3603 ---------------------------------------------------------------- 3605 4. Status: 3606 4.1 [ ] Development 3607 4.2 [ ] Alpha 3608 4.3 [ ] Beta 3609 4.4 [ ] Product 3610 4.5 [ ] Other (describe): 3612 5. Switching capabilities 3613 5.1 [ ] PSC 3614 5.2 [ ] TDM 3615 5.3 [ ] LSC 3616 5.4 [ ] FSC 3618 6. Reference Drafts (please list, include version numbers) 3619 6.1 [x] draft-ietf-mpls-generalized-signaling-07.txt 3620 6.2 [x] draft-ietf-mpls-generalized-cr-ldp-05.txt 3621 6.3 [ ] 3622 6.4 [ ] 3623 6.5 [ ] 3624 6.6 [ ] 3626 7. Interface technologies 3627 7.1 [ ] Frame Relay 3628 7.2 [ ] ATM 3629 7.3 [ ] Ethernet V2/DIX 3630 7.4 [ ] Ethernet 802.3 3631 7.5 [ ] SDH 3632 7.6 [ ] SONET 3633 7.7 [ ] Lambda (photonic) 3634 7.8 [ ] Fiber 3635 7.9 [ ] FiberChannel 3636 7.10 [ ] Other (describe): 3638 8. Availability 3639 8.1 [ ] Public and free 3640 8.2 [ ] Only to selected organizations/companies but free 3641 8.3 [ ] On sale. 3642 8.4 [ ] For internal company use only 3643 8.5 [ ] Other: 3645 9. Implementation based on: (check all that apply) 3646 9.1 [ ] Purchased code (please list source if possible) 3647 9.2 [ ] Free code (please list source if possible) 3648 9.3 [ ] Internal implementation (no outside code, just from specs) 3649 9.4 [ ] Internal implementation on top of purchased or free code 3650 9.4.1 [ ] List portions from external source 3651 9.4.2 [ ] List portions developed internally 3653 10. Supported Label Types 3654 10.1 [x] MPLS Label 3655 10.2 [x] Generalized Label 3656 10.3 [x] Waveband Label 3657 10.4 [x] SONET/SDH Label 3659 11. Label Related 3660 11.1 [x] Suggested Label 3661 11.2 [x] Label Set 3663 12. Traffic Parameters 3664 12.1 [ ] Intserv (Please list which) 3665 12.2 [x] CR-LDP 3666 12.3 [x] GMPLS Bandwidth Encoding 3667 12.4 [x] SONET/SDH 3668 13. [x] Bidirectional LSPs 3670 14. Notification 3671 14.1 [x] Acceptable Label Set 3672 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 3673 14.3 [ ] Notify Message (GMPLS-RSVP) 3674 14.4 [ ] Removing State with a PathErr message (GMPLS-RSVP) 3676 15 Other features 3677 15.1 [ ] Explicit Label Control 3678 15.2 [ ] Protection Information 3679 15.3 [ ] Administrative Status Information 3680 15.4 [ ] Interface Identification 3681 15.5 [ ] Errored Interface Identification 3682 15.6 [ ] Link Fault Handling 3683 15.7 [ ] Nodal Fault Handling 3685 16. Other specification(s) which apply: 3687 17. Other features supported: 3689 18. Currently-defined GMPLS signaling features not supported: 3691 19. Notes (please describe purpose of project, give any information that 3692 might be useful to those interested in developing or using GMPLS) 3694 20. If you feel the above categories are not complete, add others which 3695 will better describe your project: 3697 ======================================================================= 3699 Person filling out this form: 3701 Name:Don Fedyk 3702 E-mail:see above 3703 Tel.: 3704 Title: 3705 Company: 3706 Date prepared: 3708 2.20. Polaris Networks Inc 3710 GMPLS Signaling Implementation Survey Form [V 1.1] 3712 1. Organization: Polaris Networks Inc. 3714 1.1 Organization url(s): www.polarisnetworks.com 3716 2. Product title(s): OMX 3718 2.1 Brief description(s): 3720 The OMX is a Terabit-scalable optical transport 3721 switch that combines the functions of SONET ADM 3722 with a Wideband, Broadband and Super-broadband 3723 Digital Cross-connect System (DCS) in a single 3724 consolidated footprint. The control plane on the 3725 OMX is IP and GMPLS based to support the end-to-end 3726 provisioning of services. 3728 ---------------------------------------------------------------- 3730 3. Contact for GMPLS information 3731 3.1 Name: Dean Cheng 3733 3.2 Title: Principal Network Architect 3735 3.3 E-mail: dcheng@polarisnetworks.com 3737 3.4 Organization/department: Architecture 3739 3.5 Postal address: 3741 6810 Santa Teresa Bl., San Jose CA 95119 3743 3.6 Phone: (408) 284-8061 3745 3.7 Fax: (408) 281-7463 3746 --------------------------------------------------------------- 3748 4. Status: 3749 4.1 [x] Development 3750 4.2 [ ] Alpha 3751 4.3 [ ] Beta 3752 4.4 [ ] Product 3753 4.5 [ ] Other (describe): 3755 5. Switching capabilities 3757 [GMPLS- [GMPLS- 3758 RSVP] LDP] 3759 5.1 [ ] [ ] PSC 3760 5.2 [x] [ ] TDM 3761 5.3 [ ] [ ] LSC 3762 5.4 [ ] [ ] FSC 3764 6. Reference Drafts (please list, include version numbers) 3765 6.1 [x] RFC 2328 OSPF v2 3766 6.2 [x] RFC 2370 OSPF Opaque LSA 3767 6.3 [x] draft-katz-yeung-ospf-traffic-06.txt 3768 6.4 [x] draft-ietf-ccamp-gmpls-routing-04.txt 3769 6.5 [x] draft-ietf-ccamp-gmpls-ospf-gmpls-extensions-07.txt 3770 6.6 [x] RFC 2205 RSVP 3771 6.7 [x] RFC 3209 Traffic Engineering Extensions to RSVP 3772 6.8 [x] draft-ietf-mpls-generalized-signaling-07.txt 3773 6.9 [x] draft-ietf-mpls-generalized-rsvp-te-06.txt 3774 6.10 [x] draft-ietf-ccamp-gmpls-sonet-sdh-05.txt 3775 6.11 [x] draft-ietf-mpls-rsvp-unnum-06.txt 3776 6.12 [x] draft-ietf-mpls-bundle-03.txt 3777 6.13 [x] draft-ietf-ccamp-lmp-02.txt 3778 6.14 [x] RFC 2784 GRE 3779 6.14 [x] RFC 1661 PPP in HDLC-like Framing 3780 6.15 [x] RFC 1662 PPP 3781 6.16 [x] RFC 1332 IPCP 3783 7. Interface technologies 3784 7.1 [ ] Frame Relay 3785 7.2 [ ] ATM 3786 7.3 [x] Ethernet V2/DIX 3787 7.4 [x] Ethernet 802.3 3788 7.5 [ ] SDH 3789 7.6 [x] SONET 3790 7.7 [ ] Lambda (photonic) 3791 7.8 [ ] Fiber 3792 7.9 [ ] FiberChannel 3793 7.10 [ ] Other (describe): 3795 8. Availability 3796 [GMPLS- [GMPLS- 3797 RSVP] LDP] 3798 8.1 [ ] [ ] Public and free 3799 8.2 [ ] [ ] Only to selected organizations/companies but free 3800 8.3 [ ] [ ] On sale. 3801 8.4 [x] [ ] For internal company use only 3802 8.5 [ ] [ ] Other: 3804 9. Implementation based on: (check all that apply) 3806 [GMPLS- [GMPLS- 3807 RSVP] LDP] 3808 9.1 [ ] [ ] Purchased code 3809 (please list source if possible) 3810 9.2 [ ] [ ] Free code 3811 (please list source if possible) 3812 9.3 [ ] [ ] Internal implementation 3813 (no outside code, just from specs) 3814 9.4 [x] [ ] Internal implementation on top of purchased 3815 or free code 3816 9.4.1 List portions from external source: 3817 (Identify protocol if appropriate) 3818 9.4.2 List portions developed internally: 3819 (Identify protocol if appropriate) 3821 10. Supported Label Types 3822 [GMPLS- [GMPLS- 3823 RSVP] LDP] 3824 10.1 [ ] [ ] MPLS Label 3825 10.2 [ ] [ ] Generalized Label 3826 10.3 [ ] [ ] Waveband Label 3827 10.4 [x] [ ] SONET/SDH Label 3829 11. Label Related 3830 [GMPLS- [GMPLS- 3831 RSVP] LDP] 3832 11.1 [x] [ ] Suggested Label 3833 11.2 [ ] [ ] Label Set 3835 12. Traffic Parameters 3836 [GMPLS- [GMPLS- 3837 RSVP] LDP] 3838 12.1 [ ] Intserv (Please list which) 3839 12.2 [ ] CR-LDP 3840 12.3 [x] [ ] GMPLS Bandwidth Encoding 3841 12.4 [x] [ ] SONET/SDH 3843 13. Bidirectional LSPs 3844 [GMPLS- [GMPLS- 3845 RSVP] LDP] 3846 [x] [ ] Bidirectional LSPs 3848 14. Notification 3849 [GMPLS- [GMPLS- 3850 RSVP] LDP] 3851 14.1 [ ] [ ] Acceptable Label Set 3852 14.2 [x] Notify Request Objects (GMPLS-RSVP) 3853 14.3 [x] Notify Message (GMPLS-RSVP) 3854 14.4 [x] Removing State with a PathErr message (GMPLS-RSVP) 3856 15 Other features 3857 [GMPLS- [GMPLS- 3858 RSVP] LDP] 3859 15.1 [x] [ ] Explicit Label Control 3860 15.2 [x] [ ] Protection Information 3861 15.3 [x] [ ] Administrative Status Information 3862 15.4 [x] [ ] Interface Identification 3863 15.5 [x] [ ] Errored Interface Identification 3864 15.6 [x] [ ] Link Fault Handling 3865 15.7 [x] [ ] Nodal Fault Handling 3867 16. Other specification(s) which apply: 3869 17. Other features supported: 3870 17.1 related to [GMPLS-RSVP] 3871 17.2 related to [GMPLS-LDP] 3872 17.3 Other 3874 18. Currently-defined GMPLS signaling features not supported: 3875 18.1 related to [GMPLS-RSVP] 3876 18.2 related to [GMPLS-LDP] 3877 18.3 related to [GMPLS-SONET] 3878 18.4 Other 3880 19. Notes (please describe purpose of project, give any information that 3881 might be useful to those interested in developing or using GMPLS) 3883 20. If you feel the above categories are not complete, add others which 3884 will better describe your project: 3886 ==================================================================== 3888 Person filling out this form: 3890 Name: Same as above. 3891 E-mail: 3892 Tel.: 3893 Title: 3894 Company: 3895 Date prepared: 9/16/2002 3897 2.21. Sycamore Networks Inc. 3899 GMPLS Signaling Implementation Survey Form [V 1.1] 3901 1. Organization: Sycamore Networks Inc. 3903 1.1 Organization url(s): www.sycamorenetworks.com 3905 2. Product title(s): SN 3000 optical switch, SN 16000 optical switch 3907 2.1 Brief description(s): 3909 Metro and core optical switches with STS-1 level granularity, integrated 3910 routing, signaling and management software. GMPLS is implemented using 3911 the IETF CCAMP Working Group Internet Drafts in order to support 3912 standards-based compatibility and provide the foundation for 3913 multi-vendor interoperability. Validated multiple GMPLS 3914 interoperability configurations (peer, overlay, hybrid) during the MPLS 3915 Forum-sponsored GMPLS testing activity conducted at University of New 3916 Hampshire InterOperability Lab, September 30 - October 4, 2002. 3917 Testing included signaling (RSVP-TE) and control plane interoperability 3918 with multiple (edge LSR) devices from vendors including Cisco, Juniper, 3919 Agilent, Data Connection Ltd., NetTest, and NetPlane. 3921 ---------------------------------------------------------------- 3923 3. Contact for GMPLS information 3924 3.1 Name: Tom DiMicelli 3926 3.2 Title: Senior Product Manager 3928 3.3 E-mail: tdimicelli@sycamorenet.com 3930 3.4 Organization/department: Product Management/Network Switching 3932 3.5 Postal address: 220 Mill Road, Chelmsford, MA 3934 3.6 Phone: 978-367-7978 3936 3.7 Fax: 978-250-9207 3937 ---------------------------------------------------------------- 3939 4. Status: 3940 4.1 [ ] Development 3941 4.2 [] Alpha 3942 4.3 [X] Beta 3943 4.4 [ ] Product 3944 4.5 [ ] Other (describe): 3946 5. Switching capabilities 3947 [GMPLS- RSVP] [GMPLS-LDP] 3948 5.1 [ ] [ ] PSC 3949 5.2 [X] [ ] TDM 3950 5.3 [X] [ ] LSC 3951 5.4 [X] [ ] FSC 3953 6. Reference Drafts (please list, include version numbers) 3954 6.1 [X] draft-ietf-mpls-generalized-signaling-07.txt 3955 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-06.txt 3956 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-02.txt 3957 6.4 [X] draft-iwata-mpls-crankback-00.txt 3958 6.5 [X] draft-pan-mpls-restart-01.txt 3960 Drafts implemented as part of the October 2002 UNH and NGN GMPLS interoperability testing and demonstration: 3961 . draft-ietf-mpls-generalized-signaling-08.txt 3962 . draft-ietf-mpls-generalized-rsvp-te-07.txt 3964 7. Interface technologies 3965 7.1 [ ] Frame Relay 3966 7.2 [ ] ATM 3967 7.3 [ ] Ethernet V2/DIX 3968 7.4 [ ] Ethernet 802.3 3969 7.5 [X] SDH 3970 7.6 [X] SONET 3971 7.7 [ ] Lambda (photonic) 3972 7.8 [ ] Fiber 3973 7.9 [ ] FiberChannel 3974 7.10 [ ] Other (describe): 3976 8. Availability 3977 [GMPLS-RSVP] [GMPLS- LDP] 3979 8.1 [ ] [ ] Public and free 3980 8.2 [X] [ ] Only to selected organizations/companies but free 3981 8.3 [ ] [ ] On sale. 3982 8.4 [ ] [ ] For internal company use only 3983 8.5 [ ] [ ] Other: 3985 9. Implementation based on: (check all that apply) 3986 [GMPLS-RSVP] [GMPLS-LDP] 3987 9.1 [ ] [ ] Purchased code (please list source if possible) 3988 9.2 [ ] [ ] Free code (please list source if possible) 3989 9.3 [ ] [ ] Internal implementation (no outside code, just from specs) 3990 9.4 [X] [ ] Internal implementation on top of purchased or free code 3991 9.4.1 List portions from external source: (Identify protocol if appropriate) 3992 9.4.2 List portions developed internally: (Identify protocol if appropriate) 3994 10. Supported Label Types 3995 [GMPLS-RSVP] [GMPLS-LDP] 3996 10.1 [ ] [ ] MPLS Label 3997 10.2 [X] [ ] Generalized Label 3998 10.3 [ ] [ ] Waveband Label 3999 10.4 [X] [ ] SONET/SDH Label 4001 11. Label Related 4002 [GMPLS-RSVP] [GMPLS-LDP] 4003 11.1 [X] [ ] Suggested Label 4004 11.2 [X] [ ] Label Set 4006 12. Traffic Parameters 4007 [GMPLS-RSVP] [GMPLS-LDP] 4008 12.1 [X] Intserv (Please list which) 4009 12.2 [ ] CR-LDP 4010 12.3 [ ] [ ] GMPLS Bandwidth Encoding 4011 12.4 [X] [ ] SONET/SDH 4013 13. Bidirectional LSPs 4014 [GMPLS-RSVP] [GMPLS-LDP] 4015 [X] [ ] Bidirectional LSPs 4017 14. Notification 4018 [GMPLS-RSVP] [GMPLS-LDP] 4019 14.1 [ ] [ ] Acceptable Label Set 4020 14.2 [X] Notify Request Objects (GMPLS-RSVP) 4021 14.3 [X] Notify Message (GMPLS-RSVP) 4022 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 4024 15 Other features 4025 [GMPLS-RSVP] [GMPLS-LDP] 4026 15.1 [X] [ ] Explicit Label Control 4027 15.2 [ ] [ ] Protection Information 4028 15.3 [X] [ ] Administrative Status Information 4029 15.4 [X] [ ] Interface Identification 4030 15.5 [X] [ ] Errored Interface Identification 4031 15.6 [X] [ ] Link Fault Handling 4032 15.7 [ ] [ ] Nodal Fault Handling 4034 16. Other specification(s) which apply: 4036 17. Other features supported: 4037 17.1 related to [GMPLS-RSVP] 4038 17.2 related to [GMPLS-LDP] 4039 17.3 Other 4041 18. Currently-defined GMPLS signaling features not supported: 4042 18.1 related to [GMPLS-RSVP] 4043 18.2 related to [GMPLS-LDP] 4044 18.3 related to [GMPLS-SONET] 4045 18.4 Other 4047 19. Notes (please describe purpose of project, give any information that might be useful to those interested in developing or using GMPLS) 4049 20. If you feel the above categories are not complete, add others which will better describe your project: 4051 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. 4053 Parallel to our interoperability activities with GMPLS, Sycamore continues to actively participate in and monitor standards development activities within the OIF and ITU-T. 4055 2.22. Tellium, Inc. 4057 GMPLS Signaling Implementation Survey Form [V 1.0] 4059 1. Organization: Tellium, Inc. 4061 1.1 Organization url(s): www.tellium.com 4063 2. Product title(s): Aurora Optical Switch, Aurora 128 4065 2.1 Brief description(s): 4067 Wavelength optical switch, managing wavelengths which are today 4068 at -48 and -192 levels of granularity 4070 ---------------------------------------------------------------- 4072 3. Contact for GMPLS information 4073 3.1 Name: Dimitrios Pendarakis 4075 3.2 Title: Manager, Internetworking and Applications 4077 3.3 E-mail: dpendarakis@tellium.com 4079 3.4 Organization/department: Tellium, Inc. 4081 3.5 Postal address: 2 Crescent Place, P.O. Box 901, 4082 Oceanport, NJ 07757-0901 4083 3.6 Phone: 732 923-4254 4085 3.7 Fax: 732 728-9862 4086 ---------------------------------------------------------------- 4088 4. Status: 4089 4.1 [ ] Development 4090 4.2 [X] Alpha 4091 4.3 [ ] Beta 4092 4.4 [ ] Product 4093 4.5 [ ] Other (describe): 4095 5. Switching capabilities 4096 5.1 [ ] PSC 4097 5.2 [X] TDM 4098 5.3 [X] LSC 4099 5.4 [X] FSC 4101 6. Reference Drafts (please list, include version numbers) 4102 6.1 [X] draft-ietf-mpls-generalized-signaling-07.txt 4103 6.2 [X] draft-ietf-mpls-generalized-rsvp-te-06.txt 4104 6.3 [X] draft-ietf-ccamp-gmpls-sonet-sdh-03.txt 4105 6.4 [X] draft-ietf-mpls-rsvp-unnum-04.txt 4106 6.5 [X] draft-ietf-mpls-bundle-01.txt 4107 6.6 [ ] 4109 7. Interface technologies 4110 7.1 [ ] Frame Relay 4111 7.2 [ ] ATM 4112 7.3 [ ] Ethernet V2/DIX 4113 7.4 [ ] Ethernet 802.3 4114 7.5 [X] SDH 4115 7.6 [X] SONET 4116 7.7 [X] Lambda (photonic) 4117 7.8 [X] Fiber 4118 7.9 [ ] FiberChannel 4119 7.10 [ ] Other (describe): 4121 8. Availability 4122 8.1 [ ] Public and free 4123 8.2 [ ] Only to selected organizations/companies but free 4124 8.3 [ ] On sale. 4125 8.4 [X] For internal company use only 4126 8.5 [ ] Other: 4128 9. Implementation based on: (check all that apply) 4129 9.1 [ ] Purchased code (please list source if possible) 4130 9.2 [ ] Free code (please list source if possible) 4131 9.3 [ ] Internal implementation (no outside code, just from specs) 4132 9.4 [X] Internal implementation on top of purchased or free code 4133 9.4.1 [ ] List portions from external source 4134 9.4.2 [ ] List portions developed internally 4136 10. Supported Label Types 4137 10.1 [ ] MPLS Label 4138 10.2 [X] Generalized Label 4139 10.3 [ ] Waveband Label 4140 10.4 [X] SONET/SDH Label 4142 11. Label Related 4143 11.1 [X] Suggested Label 4144 11.2 [X] Label Set 4146 12. Traffic Parameters 4147 12.1 [ ] Intserv (Please list which) 4148 12.2 [ ] CR-LDP 4149 12.3 [X] GMPLS Bandwidth Encoding 4150 12.4 [X] SONET/SDH 4152 13. [X] Bidirectional LSPs 4154 14. Notification 4155 14.1 [ ] Acceptable Label Set 4156 14.2 [X] Notify Request Objects (GMPLS-RSVP) 4157 14.3 [X] Notify Message (GMPLS-RSVP) 4158 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 4160 15 Other features 4161 15.1 [X] Explicit Label Control 4162 15.2 [X] Protection Information 4163 15.3 [X] Administrative Status Information 4164 15.4 [X] Interface Identification 4165 15.5 [X] Errored Interface Identification 4166 15.6 [ ] Link Fault Handling 4167 15.7 [ ] Nodal Fault Handling 4169 16. Other specification(s) which apply: 4171 17. Other features supported: 4173 18. Currently-defined GMPLS signaling features not supported: 4175 19. Notes (please describe purpose of project, give any information that 4176 might be useful to those interested in developing or using GMPLS) 4178 20. If you feel the above categories are not complete, add others which 4179 will better describe your project: 4181 ===================================================================== 4183 Person filling out this form: Same as above 4184 Name: 4185 E-mail: 4186 Tel.: 4187 Title: 4188 Company: 4189 Date prepared: March 12, 2002 4191 2.23. Tropic Networks Inc 4193 GMPLS Signaling Implementation Survey Form [V 1.0] 4195 1. Organization: Tropic Networks Inc 4197 1.1 Organization url(s): http://www.tropicnetworks.com 4199 2.1 Brief description(s): 4201 The product is a switching device in the area of 4202 Optical Packet Networking 4204 ---------------------------------------------------------------- 4206 3. Contact for GMPLS information 4208 3.1 Name: Nabil Seddigh 4209 3.3 E-mail: nseddigh@tropicnetworks.com 4210 3.5 Postal address: 135 Michael Cowpland Dr 4211 Kanata, ON K2M 2E9 4212 3.6 Phone: 613-270-6936 4214 ---------------------------------------------------------------- 4216 4. Status: 4217 4.1 [X] Development 4218 4.2 [ ] Alpha 4219 4.3 [ ] Beta 4220 4.4 [ ] Product 4221 4.5 [ ] Other (describe): 4223 5. Switching capabilities 4224 5.1 [X] PSC 4225 5.2 [ ] TDM 4226 5.3 [X] LSC 4227 5.4 [X] FSC 4229 6. Reference Drafts (please list, include version numbers) 4230 6.1 [ ] draft-ietf-mpls-generalized-signaling-07.txt 4231 6.2 [ ] draft-ietf-mpls-generalized-rsvp-te-06.txt 4232 6.3 [ ] draft-ietf-mpls-rsvp-unnum-04.txt 4233 6.4 [ ] draft-ietf-mpls-lsp-hierarchy-04.txt 4234 6.5 [ ] draft-ietf-mpls-bundle-01.txt 4235 6.6 [ ] RFC 3032 4237 7. Interface technologies 4238 7.1 [ ] Frame Relay 4239 7.2 [ ] ATM 4240 7.3 [ ] Ethernet V2/DIX 4241 7.4 [X] Ethernet 802.3 4242 7.5 [ ] SDH 4243 7.6 [ ] SONET 4244 7.7 [X] Lambda (photonic) 4245 7.8 [X] Fiber 4246 7.9 [ ] FiberChannel 4247 7.10 [ ] Other (describe): 4249 8. Availability 4250 8.1 [ ] Public and free 4251 8.2 [ ] Only to selected organizations/companies but free 4252 8.3 [ ] On sale. 4253 8.4 [X] For internal company use only 4254 8.5 [ ] Other: 4256 9. Implementation based on: (check all that apply) 4257 9.1 [ ] Purchased code (please list source if possible) 4258 9.2 [ ] Free code (please list source if possible) 4259 9.3 [ ] Internal implementation (no outside code, just from specs) 4260 9.4 [X] Internal implementation on top of purchased or free code 4261 9.4.1 [ ] List portions from external source 4262 9.4.2 [ ] List portions developed internally 4264 10. Supported Label Types 4265 10.1 [X] MPLS Label 4266 10.2 [X] Generalized Label 4267 10.3 [X] Waveband Label 4268 10.4 [ ] SONET/SDH Label 4270 11. Label Related 4271 11.1 [X] Suggested Label 4272 11.2 [ ] Label Set 4273 12. Traffic Parameters 4274 12.1 [X] Intserv (Please list which) 4275 12.2 [ ] CR-LDP 4276 12.3 [X] GMPLS Bandwidth Encoding 4277 12.4 [ ] SONET/SDH 4279 13. [X] Bidirectional LSPs 4281 14. Notification 4282 14.1 [ ] Acceptable Label Set 4283 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 4284 14.3 [ ] Notify Message (GMPLS-RSVP) 4285 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 4287 15 Other features 4288 15.1 [ ] Explicit Label Control 4289 15.2 [ ] Protection Information 4290 15.3 [ ] Administrative Status Information 4291 15.4 [X] Interface Identification 4292 15.5 [X] Errored Interface Identification 4293 15.6 [X] Link Fault Handling 4294 15.7 [X] Nodal Fault Handling 4296 =============================================================== 4298 Person filling out this form: 4300 Name: Nabil Seddigh 4301 E-mail: nseddigh@tropicnetworks.com 4302 Tel.: 613-270-6936 4303 Company: Tropic Networks 4304 Date prepared: March 13, 2002 4306 2.24. Wipro Technologies 4308 GMPLS Signaling Implementation Survey Form [V 1.1] 4310 1. Organization: Wipro Technologies 4312 1.1 Organization url(s): www.wipro.com 4314 2. Product title(s): Wipro MPLS stacks 4316 2.1 Brief description(s): 4318 WIP-MPLS product line offers GMPLS/MPLS control plane stacks: 4320 GMPLS extension to CRLDP, GMPLS extension to RSVP-TE, LDP, CRLDP, 4321 RSVP-TE and other related stacks. 4322 ---------------------------------------------------------------- 4324 3. Contact for GMPLS information 4325 3.1 Name: Rana Pratap Sircar 4327 3.2 Title: Architect 4329 3.3 E-mail: rana.sircar@wipro.com 4331 3.4 Organization/department: Wipro Technologies/Telecom and 4332 Internetworking Solutions 4334 3.5 Postal address: Wipro Technologies 4335 No. 26, Hosur Main Road, Bomannahalli, 4336 Bangalore - 560068 4338 3.6 Phone: +91-80-5732296/3 ext 1040 4340 3.7 Fax: +91-80-5732696 / 5732441 4341 ---------------------------------------------------------------- 4343 4. Status: 4344 4.1 [X] Development 4345 4.2 [ ] Alpha 4346 4.3 [ ] Beta 4347 4.4 [ ] Product 4348 4.5 [ ] Other (describe): 4350 5. Switching capabilities 4351 [GMPLS- [GMPLS- 4352 RSVP] LDP] 4353 5.1 [X] [X] PSC 4354 5.2 [X] [X] TDM 4355 5.3 [ ] [ ] LSC 4356 5.4 [ ] [ ] FSC 4358 6. Reference Drafts (please list, include version numbers) 4359 6.1 [draft-ietf-mpls-generalized-cr-ldp-05.txt] 4360 6.2 [draft-ietf-mpls-generalized-signaling-07.txt] 4361 6.3 [draft-ietf-ccamp-gmpls-architecture-02.txt] 4362 6.4 [draft-ietf-mpls-generalized-rsvp-te-06.txt] 4363 6.5 [RFC 2205 : RSVP ] 4364 6.6 [RFC 3209 : RSVP-TE ] 4365 6.7 [RFC 3212 : CR-LDP ] 4366 6.8 [RFC 3214 : LSP Modification Using CR-LDP ] 4367 7. Interface technologies 4368 7.1 [X] Frame Relay 4369 7.2 [X] ATM 4370 7.3 [ ] Ethernet V2/DIX 4371 7.4 [X] Ethernet 802.3 4372 7.5 [X] SDH 4373 7.6 [X] SONET 4374 7.7 [ ] Lambda (photonic) 4375 7.8 [ ] Fiber 4376 7.9 [ ] FiberChannel 4377 7.10 [ ] Other (describe): 4379 8. Availability 4380 [GMPLS- [GMPLS- 4381 RSVP] LDP] 4382 8.1 [ ] [ ] Public and free 4383 8.2 [ ] [ ] Only to selected organizations/companies but free 4384 8.3 [X] [X] On sale. 4385 8.4 [ ] [ ] For internal company use only 4386 8.5 [ ] [ ] Other: 4388 9. Implementation based on: (check all that apply) 4389 [GMPLS- [GMPLS- 4390 RSVP] LDP] 4391 9.1 [ ] [ ] Purchased code 4392 (please list source if possible) 4393 9.2 [ ] [ ] Free code 4394 (please list source if possible) 4395 9.3 [X] [X] Internal implementation 4396 (no outside code, just from specs) 4397 9.4 [ ] [ ] Internal implementation on top of purchased 4398 or free code 4399 9.4.1 List portions from external source: 4400 (Identify protocol if appropriate) 4401 9.4.2 List portions developed internally: 4402 (Identify protocol if appropriate) 4404 10. Supported Label Types 4405 [GMPLS- [GMPLS- 4406 RSVP] LDP] 4407 10.1 [X] [X] MPLS Label 4408 10.2 [X] [X] Generalized Label 4409 10.3 [ ] [ ] Waveband Label 4410 10.4 [X] [X] SONET/SDH Label 4412 11. Label Related 4413 [GMPLS- [GMPLS- 4414 RSVP] LDP] 4416 11.1 [X] [X] Suggested Label 4417 11.2 [X] [X] Label Set 4419 12. Traffic Parameters 4420 [GMPLS- [GMPLS- 4421 RSVP] LDP] 4422 12.1 [ ] Intserv (Please list which) 4423 12.2 [X] CR-LDP 4424 12.3 [X] [X] GMPLS Bandwidth Encoding 4425 12.4 [X] [X] SONET/SDH 4427 13. Bidirectional LSPs 4428 [GMPLS- [GMPLS- 4429 RSVP] LDP] 4430 [X] [X] Bidirectional LSPs 4432 14. Notification 4433 [GMPLS- [GMPLS- 4434 RSVP] LDP] 4435 14.1 [X] [X] Acceptable Label Set 4436 14.2 [X] Notify Request Objects (GMPLS-RSVP) 4437 14.3 [X] Notify Message (GMPLS-RSVP) 4438 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 4440 15 Other features 4441 [GMPLS- [GMPLS- 4442 RSVP] LDP] 4443 15.1 [X] [X] Explicit Label Control 4444 15.2 [X] [X] Protection Information 4445 15.3 [X] [X] Administrative Status Information 4446 15.4 [X] [X] Interface Identification 4447 15.5 [X] [X] Errored Interface Identification 4448 15.6 [ ] [ ] Link Fault Handling 4449 15.7 [ ] [ ] Nodal Fault Handling 4451 16. Other specification(s) which apply: Contention Resolution supported 4453 17. Other features supported: 4454 17.1 related to [GMPLS-RSVP] A Node level Admission controller and Resource 4455 Manager. 4456 17.2 related to [GMPLS-LDP] A Node level Admission controller and Resource 4457 Manager. 4458 17.3 Other 4460 18. Currently-defined GMPLS signaling features not supported: 4461 18.1 related to [GMPLS-RSVP] 4462 18.2 related to [GMPLS-LDP] 4463 18.3 related to [GMPLS-SONET] 4464 18.4 Other 4466 19. Notes (please describe purpose of project, give any information that 4467 might be useful to those interested in developing or using GMPLS) 4469 Wipro Technologies offers a carrier-class GMPLS/MPLS protocol 4470 stacks to OEM vendors. Our product line includes source code 4471 architected, developed and tested in a well defined quality 4472 framework. 4474 20. If you feel the above categories are not complete, add others which 4475 will better describe your project: 4477 ==================================================================== 4479 Person filling out this form: 4481 Name: Chetan Kumar S 4482 E-mail: chetan.kumar@wipro.com 4483 Tel.: +91 80 5732296 4484 Title: Protocol Specialist 4485 Company: Wipro Technologies 4486 Date prepared: 28-03-02 (dd-mm-yy) 4488 2.25. Anonymous 1 4490 GMPLS Signaling Implementation Survey Form [V 1.0] 4492 4. Status: 4493 4.1 [X] Development 4494 4.2 [ ] Alpha 4495 4.3 [ ] Beta 4496 4.4 [ ] Product 4497 4.5 [ ] Other (describe): 4499 5. Switching capabilities 4500 5.1 [ ] PSC 4501 5.2 [ ] TDM 4502 5.3 [X] LSC 4503 5.4 [ ] FSC 4505 6. Reference Drafts (please list, include version numbers) 4506 6.1 [ ] 4507 6.2 [ ] 4508 6.3 [ ] 4509 6.4 [ ] 4510 6.5 [ ] 4511 6.6 [ ] 4513 7. Interface technologies 4514 7.1 [ ] Frame Relay 4515 7.2 [ ] ATM 4516 7.3 [ ] Ethernet V2/DIX 4517 7.4 [ ] Ethernet 802.3 4518 7.5 [ ] SDH 4519 7.6 [ ] SONET 4520 7.7 [ ] Lambda (photonic) 4521 7.8 [ ] Fiber 4522 7.9 [ ] FiberChannel 4523 7.10 [X] Other (describe): Lambda O-E-O 4525 8. Availability 4526 8.1 [ ] Public and free 4527 8.2 [ ] Only to selected organizations/companies but free 4528 8.3 [ ] On sale. 4529 8.4 [X] For internal company use only 4530 8.5 [ ] Other: 4532 9. Implementation based on: (check all that apply) 4533 9.1 [ ] Purchased code (please list source if possible) 4534 9.2 [ ] Free code (please list source if possible) 4535 9.3 [ ] Internal implementation (no outside code, just from specs) 4536 9.4 [X] Internal implementation on top of purchased or free code 4537 9.4.1 [ ] List portions from external source 4538 9.4.2 [ ] List portions developed internally 4540 10. Supported Label Types 4541 10.1 [ ] MPLS Label 4542 10.2 [X] Generalized Label 4543 10.3 [ ] Waveband Label 4544 10.4 [ ] SONET/SDH Label 4546 11. Label Related 4547 11.1 [X] Suggested Label 4548 11.2 [ ] Label Set 4550 12. Traffic Parameters 4551 12.1 [ ] Intserv (Please list which) 4552 12.2 [ ] CR-LDP 4553 12.3 [X] GMPLS Bandwidth Encoding 4554 12.4 [ ] SONET/SDH 4556 13. [X] Bidirectional LSPs 4557 14. Notification 4558 14.1 [ ] Acceptable Label Set 4559 14.2 [ ] Notify Request Objects (GMPLS-RSVP) 4560 14.3 [X] Notify Message (GMPLS-RSVP) 4561 14.4 [X] Removing State with a PathErr message (GMPLS-RSVP) 4563 15 Other features 4564 15.1 [ ] Explicit Label Control 4565 15.2 [ ] Protection Information 4566 15.3 [ ] Administrative Status Information 4567 15.4 [ ] Interface Identification 4568 15.5 [ ] Errored Interface Identification 4569 15.6 [X] Link Fault Handling 4570 15.7 [X] Nodal Fault Handling 4572 16. Other specification(s) which apply: 4574 17. Other features supported: 4576 18. Currently-defined GMPLS signaling features not supported: 4578 19. Notes (please describe purpose of project, give any information that 4579 might be useful to those interested in developing or using GMPLS) 4581 20. If you feel the above categories are not complete, add others which 4582 will better describe your project: 4584 3. Acknowledgments 4586 The survey form was derived from V2.2 of the "RSVP and QoS 4587 Implementation Survey Information Form" authored by Gene Gaines 4588 and Marco Festa . See 4589 http://www.iit.nrc.ca/IETF/RSVP_survey/rsvp-qos_quest_980210.txt. 4591 Scott Bradner, sob@harvard.edu, provided the "anonymous submission" 4592 service for this survey. 4594 4. Security Considerations 4596 This document does not address any security issues. 4598 5. IANA Considerations 4600 No parameters are defined in this document. 4602 6. References 4604 [GMPLS-LDP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - 4605 CR-LDP Extensions", Internet Draft, 4606 draft-ietf-mpls-generalized-cr-ldp-07.txt, 4607 August 2002. 4609 [GMPLS-RSVP] Ashwood-Smith, P. et al, "Generalized MPLS Signaling - 4610 RSVP-TE Extensions", Internet Draft, 4611 draft-ietf-mpls-generalized-rsvp-te-09.txt, 4612 October 2002. 4614 [GMPLS-SIG] Ashwood-Smith, P. et al, "Generalized MPLS - 4615 Signaling Functional Description", Internet Draft, 4616 draft-ietf-mpls-generalized-signaling-09.txt, 4617 August 2002. 4619 [GMPLS-SONET] Ashwood-Smith, P. et al, "GMPLS - SONET / SDH Specifics", 4620 Internet Draft, draft-ietf-ccamp-gmpls-sonet-sdh-03.txt, 4621 April, 2001. 4623 7. Editors' Addresses 4625 Lou Berger 4626 Movaz Networks, Inc. 4627 7926 Jones Branch Drive 4628 Suite 615 4629 McLean VA, 22102 4630 Phone: +1 703 847-1801 4631 Email: lberger@movaz.com 4633 Yakov Rekhter 4634 Juniper Networks, Inc. 4635 Email: yakov@juniper.net 4637 Generated on: Mon Oct 28 08:21:34 2002