|
(Sponsors Only) |
| Cutting-edge technology validation in next generation Internet and wireless networking | |
|
Isonotes MPLS 2002, a premier annual conference focused on emerging Internetworking technologies, was held October 27-29, 2002. This was the fifth conference in a series that started with MPLS 98 - the very first International conference held on MPLS. MPLS 2002 was hosted by Isocore in association with leading Internet Service Providers Cable & Wireless, France Telecom, NTT, and Worldcom. The conference was sponsored by Alcatel, Avici Systems, Cisco Systems, Cosine Communications, Extreme Networks, Ixia, Juniper Networks, Laurel Networks, Lucent Technologies, NetTest, NEC, Nortel Networks, Redback Networks, Spirent Communications, and other leading network equipment suppliers. The technical program covered a wide array of MPLS topics such as Layer 2 and Layer 3 VPNs, Internetworking, Network Management, Security, Traffic Engineering, QoS, Resiliency, and GMPLS/Optical Networks. The technical session on Layer 2 VPNs covered VPN architectures such as Pseudowires, Virtual Private Wire Service (VPWS), and Virtual Private LAN Service (VPLS). Presenters shared their views on how signaling of Layer 2 VPNS should be done - the two primary camps being for targeted LDP and BGP. Service providers participating in the the Service & Internetworking Issues Panel shared the view that MPLS may be used to converge different legacy networks onto one network to reduce operating expenses. One migration strategy would be to keeping existing customers and sites in the legacy networks while using MPLS for new customers and sites. One of the talks in the Layer 3 VPNs session compared the Virtual Router based Layer 3 VPNs with RFC 2547bis based Layer 3 VPNs and proposed an approach that combines both to take advantage of the enhanced management capabilities of the Virtual Router with the scalability advantages of RFC 2547bis model. Another speaker proposed to add hierarchy to RFC 2547bis based VPNs by extending MPLS to an aggregation router between the PE router and CE router to increase scalability. In the Network Management Session the approaches developed by the IETF (LSP Ping) and ITU (Y.1711) were compared. The Security Session included a talk that integrated BGP/MPLS VPNs, IPSec, and NAT in one PE, an approach that relied on use of IPSec for PE-PE communication. Several discussions on the ways and means to protect the control, data, and management planes from abuse by VPN customers were presented. The presentations in the Protection and Recovery session described different resiliency mechanisms such as Fast ReRoute (FRR), dynamic routing, and backup LSPs. Numerical comparisons of restoration times with FRR and dynamic routing were provided for different network topologies. The session on Optical Networks provided views on inherent impairment characteristics of optical networks and how they can be taken into account in routing, interoperability of the Optical UNI and GMPLS Protocols, techniques for routing and wavelength assignment, integration of packet and optical networks, and how GMPLS can be used for building photonic, hierarchical, and hybrid optical networks. Integrating Differentiated Services and MPLS TE, its advantages, required IGP signaling extensions, and its applications was one of the topics in the Traffic Engineering session. This session also included an interesting approach for determining LSP routes on-line while using a global traffic distribution matrix. The conference was followed by the 3rd Public Interoperability Demonstration that took place at Isocore's state-of-the-art Internetworking Lab facility in McLean, Virginia. - Dr. Ferit Yegenoglu One of the important outcomes of the Isocore Internetworking Lab’s October 2002 TAC meeting was the announcement of Isocore’s new interoperability testing program, “IP-Based Control and Management of Optical Networks (IPCMON)”. The scope of the program was discussed with service providers and equipment vendors during the TAC meeting, and a phased approach with initial focus on optical connection control was adopted. Tests will also cover new protocols for management of optical networks and IP routing protocol enhancements for advertising optical network parameters. The Isocore IPCMON program is driven by three main objectives: i) to foster rapid adoption of the IPCMON technology in the commercial market, ii) to validate the technology for deployment by carriers through demonstrating interoperability between products from different vendors, and iii) to help in progressing standardization process relating to IPCMON. Protocols and architectures for IP-based control and management of optical networks that will be tested at Isocore are being developed by the IETF, OIF, and the ITU-T. In the IETF, the architecture for IP-based control and management of optical networks was seen as a generalization of MPLS and hence referred to as GMPLS. GMPLS extends MPLS to encompass time division switching (e.g. SONET/SDH), wavelength switching (optical lambdas), and spatial switching (e.g. incoming port or fiber to outgoing port or fiber). Label Switched Paths (LSPs) are no longer limited to paths where forwarding is based on the MPLS packet header, but also cover TDM connections, wavelength-switched optical connections, and fiber switched optical connections. In GMPLS, an IP-based control channel that may or may not be associated with a particular data channel is used for LSP setup and teardown, routing, and link management. IETF has developed a GMPLS Control plane based on extensions to RSVP-TE as well as CR-LDP; and GMPLS routing protocols based on extensions to OSPF-TE and ISIS-TE. IETF is also developing a Link Management Protocol (LMP) to control channel management, link property correlation, link connectivity verification, and fault management. GMPLS introduces the following enhancements to MPLS signaling that are important from the point of view of interoperability testing: The OIF architecture for control and management of optical networks is based on the separation of user domain (IP network) and service provider domain (Optical Transport Network). In this architecture, signaling between the user domain and the service provider domain is based on the OIF UNI 1.0 Specification whereas signaling between two service provider domains is based on OIF NNI Specification currently being developed (see Figure 1). This separation hides the details of the optical transport network from the user domain, for example by limiting the scope of optical routing protocols to the optical transport domain. In this case, a connection request to a particular destination is made by a user node, however the path to the destination is determined by the optical transport network. In the GMPLS architecture, no such separation exists. The OIF signaling and management protocols are heavily based on their GMPLS counterparts. ![]() Figure 1:OIF Separation of User and Service Provider Domains The optical network control and management standardization work that is being conducted by the ITU-T falls under the umbrella of Architecture for Automatically Switched Optical Networks (ASON). ASON is not a set of protocols, but an architecture that defines network boundaries, different types of network equipment, and the interactions between different domains. The requirements defined in ASON can be met by GMPLS and OIF-UNI protocols or enhancements to them. As in OIF, ASON defines a number of reference points to indicate where in the network different protocols need to be defined. In ASON, these are UNI, E-NNI, and I-NNI. The Isocore IPCMON program will cover the protocols developed by all three standards organizations. Current plan is to start with the GMPLS and OIF connection control signaling protocols and continue with routing and management protocols based on guidance from service providers and equipment vendors. - Loa Andersson, Co-chair, IETF MPLS-WG The first generation of the MPLS RFCs and drafts today constitutes a fairly solid and coherent set of implementable specifications. The missing parts are some tools, e.g. "mpls ping" and possibly an equivalent to traceroute. A wider OAM framework has been discussed, but is still for further study. The MPLS MIBs were extensively reviewed in Atlanta, prior to the IETF meeting. We are in a situation that the better part of the MIBs compile together, but further attention needs to be given to the MIB consistency. The MIB-doctor still has a sizeable number of comments on the MIBs that will be addressed over the period up to the San Francisco meeting. The MPLS working group made a number of drafts ready for publication. They are currently on the RFC Editors queue and will shortly appear as RFCs. As a result of more or less completing the first generation of the MPLS standards, the working group will update the working group charter and its milestones. During this period, based on a discussion started in Yokohama, the working group has come to a consensus on not taking on new work based on CR-LDP, and that further traffic engineering work will be based on RSVP-TE. The existing set of CR-LDP related drafts will however be progressed by the working group to their intended RFC status. For the future the MPLS WG needs to look into topics such as security aspects of MPLS based VPN solutions and the issues around MPLS based multicast. A multicast framework exists and will be a good basis for this work. The list found via the link below indicates the state of the IETF MPLS working group documents. The headings are comparatively high-level and the list is intended to give a quick overview of the situation. The headings indicate the state of the draft, possibly with some explanatory notes. The notes are useful for example in a situation where a document has been submitted to IESG and a quick update has been requested. IETF MPLS WG Documents can be found at:http://urax.utfors.net/~loa/MPLS_WG_Drafts.htm Isocore successfully hosted the 3rd Public MPLS Interoperability Demonstration that followed the MPLS 2002 International Conference. The demonstration included CE and PE edge devices running L3-BGP and L2-Martini VPNs over a resilient core running Fast ReRoute Link Bypass Protection and Standby LSPs. With a goal of demonstrating a test scenario that closely resembles a typical Service Provider Network, the topology included several vendors and multiple interfaces—including OC-192 POS links in the core. Vendors included Cisco, Juniper, Avici, and Marconi in the core; with Cisco, Lucent, Extreme, Redback, CoSine, and Foundry as the edge. Test equipment from IXIA, Spirent, and NetTest was used for edge functions, as well as for MPLS/IP traffic generation. Multiple demonstrations of link failovers resulted in restoration times of under 50 milliseconds, values that are well below SONET restoration mechanisms. This certainly bode good news for the future of the technology. On the flip side, the Internetworking Lab’s LEC testing held over previous months has illustrated that the FRR standards are far from mature - interoperability issues still have to be resolved for Next-Next Hop (NNHOP) protection, and for certain specialized failover scenarios. There are several new programs being launched at Isocore to promote MPLS/GMPLS standards and protocol development from an interoperability perspective. The Internetworking Lab is launching a program for testing IP based Control and Management of Optical Networks. We look forward to your continued support and participation in these new programs. - Kavita Khanna |
© 2002 ISOCORE Corporation
Contact the Webmaster