deploying and managing ip over wdm networks - Index of

Recommendations

Info

178 Deploying and Managing IP over WDM Networks between members of the scientific community of the Internet. Combined with the HTTP protocol that had the role of the transport mechanism, HTML was widely accepted as an emerging standard for data presentation in the new World Wide Web (WWW) network. Very soon the popularity, ease of usage, and the abundance of HTML authoring tools convinced the users to adopt HTML for performing a wide new range of roles. New roles meant new requirements and most notably the demand for delivering dynamic content to the user. It was clear that for this task, the classic implementation of an HTTP server sending static HTML pages to client devices was no longer adequate. The new applications could no longer be based on the traditional client-server paradigm. This led to the emergence of new architectures that aimed at covering the new needs. One such methodology was the three-tier architecture that is followed for the WINMAN implementation. According to this, the system consists of three layers: the back end, the business layer, and the presentation layer. 9.9.2 Java From the early years, Java provided a rich set of libraries and tools aimed to help programmers in building complex user interfaces. An early implementation of such a library was AWT [6], which was provided with JDK 1.0 and 1.1 platforms. While AWT provided to the user an easy way to utilize a rich set of graphic interface elements, it also suffered from several major disadvantages. Most notably, AWT components were implemented using libraries that were system dependent. This meant that the AWT-based applications were restricted to lowest common denominator of the features provided by the systemdependant libraries. The Java foundation classes (JFC) were introduced in 1997 to overcome this problem. The JFC contained the following: • The swing components. These include everything from buttons to split panes to tables. • Pluggable look and feel support. This gives any program that uses swing components a choice of looks and feels (e.g., the same program can use either the Java look and feel or the Windows look and feel). We expect many more look-and-feel packages—including some that use sound instead of a visual look—to become available from various sources. • Accessibility API. This enables assistive technologies such as screen readers and Braille displays to get information from the user interface. • Java 2D TM API (Java 2 platform only). This enables developers to easily incorporate high-quality two-dimensional graphics, text, and images in applications and in applets.
• Drag and drop support (Java 2 platform only). This provides the ability to drag and drop between a Java application and a native application. The first three JFC features were implemented without any native code, relying only on the API defined in JDK 1.1. As a result, they could and did become available as an extension to JDK 1.1. This extension was released as JFC 1.1, which is sometimes called the swing release. The API in JFC 1.1 is often called the swing API. Although the Java 2 platform still supports the AWT components, programmers are strongly encouraged to use swing components instead. 9.9.3 The WINMAN Implementation For the implementation of the GUI, Java is utilized. The undisputable characteristics that render Java as the programming language of choice are well known: platform portability, underlying technology independence, security, and competence in GUI development. Only pure, open-source Java has been adopted for the graphical interface in order to be compliant with the established Java standards and ensure the portability and interoperability of the GUI application. The version of Java used is the standard edition SDK 1.3. All of the visual objects that comprise the WINMAN GUI are taken from the swing package, which provides lightweight components; that is, they separate the model from the view of a graphic class. In such a manner, the graphical representation of a given class can be altered without affecting the data and the logic of the associated model and there can be multiple views of the same object. For instance, a network element can be depicted either as a node in the network tree or an image on the network topology canvas. Apart from the standard visualization classes of Java SDK, helper classes are introduced that facilitate the integration with the DSC framework described in Section 9.2.2. As such, the GUI is handled as a common DSC component. Its mere difference from the rest of the components is that it does not publish an IDL interface. 9.10 Policy-Based Management Tools Technologies and Tools 179 Policy development tools are intended to create, verify, and implement policies to be used in policy-based management systems. In some respects, these tools are similar to correlation tools, but in this case they are oriented to the most specific aspects of network management. Thus, ILOG Rules, which is a rule-based system, could be used.
Page 3 and 4:
Deploying and Managing IP over WDM
Page 5 and 6:
Deploying and Managing IP over WDM
Page 7 and 8:
Contents Foreword xv Preface xix Ac
Page 9 and 10:
Contents vii 4.2 The WDM Network El
Page 11 and 12:
Contents ix 8 Management System Des
Page 13 and 14:
Contents xi 10.3 The WINMAN Testbed
Page 15:
Contents xiii 13.4.1 Adoption of Op
Page 18 and 19:
xvi Deploying and Managing IP over
Page 21 and 22:
Preface The integration of the Inte
Page 23:
Coauthors of the IST-OPTIMIST proje
Page 27 and 28:
1 Introduction 1.1 The Importance o
Page 29 and 30:
communications. These legacy networ
Page 31:
Within these programs, consortia of
Page 34 and 35:
8 Deploying and Managing IP over WD
Page 36 and 37:
10 Deploying and Managing IP over W
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 81 and 82:
4 Management of the WDM Network Lay
Page 83 and 84:
λ1λ 2 ··· λ w λ1λ 2 ···
Page 85 and 86:
Management of the WDM Network Layer
Page 87 and 88:
• Lightpaths that may be protecte
Page 89 and 90:
• Wavelength continuity. Two conn
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
4.4.4 Management Interfaces Managem
Page 97 and 98:
Page 99 and 100:
5 IP Over WDM Integration Mechanism
Page 101 and 102:
STM1/ATM interface requirements. Fo
Page 103 and 104:
IP router OLA The version of IP ove
Page 105 and 106:
Gigabit Ethernet interface GbE prov
Page 107 and 108:
the IETF extended the MPLambdaS fra
Page 109 and 110:
ASON/ASTN. ITU-T will try to push t
Page 111 and 112:
The proposed management solution is
Page 113:
IP Over WDM Integration Mechanisms
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
100 Deploying and Managing IP over
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155: 128 Deploying and Managing IP over
Page 165 and 166: 8 Management System Design and Impl
Page 167 and 168: Management System Design and Implem
Page 169 and 170: checking is done at the very beginn
Page 171 and 172: 8.4.1 The Inventory Model The inven
Page 173 and 174: for any of the three WINMAN NMSs. T
Page 185: Management System Design and Implem
Page 225 and 226: 11 Evaluation of IP over WDM Manage
Page 227 and 228: Evaluation of IP over WDM Managemen
Page 229 and 230: system will still perform without i
Page 241 and 242: 11.5.3.1 General Remarks The manage
Page 243 and 244: 12 Integration of IP over WDM: The
Page 245 and 246: domains with different management t
Page 247 and 248: Integration of IP over WDM: The LIO
Page 255 and 256:
ClientCTP Integration of IP over WD
Page 257 and 258:
AstnTrail AstnTTP NL resource Integ
Page 259 and 260:
12.4.1.1 TILAB Equipment Integratio
Page 261 and 262:
12.4.1.3 Tellium Equipment Integrat
Page 263 and 264:
Integration of IP over WDM: The LIO
Page 265 and 266:
Integration of IP over WDM: The LIO
Page 267 and 268:
At least two other possible solutio
Page 269 and 270:
13 Future Developments and Challeng
Page 271 and 272:
Future Developments and Challenges
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 303:
About the Editors Joan Serrat recei
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314:
show all

deploying and managing ip over wdm networks - Index of

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?