deploying and managing ip over wdm networks - Index of

Recommendations

Info

80 Deploying and Managing IP over WDM Networks described in [2], along with the requirements and issues that they impose [3], are summarized next: • The overlay model. The routing algorithm, topology distribution, and connection setup signaling protocols of the IP and the WDM networks are independent. The overlay model is the one that allows an easy migration from the existing situation to the deployment of ONEs for the transport of the IP directly over WDM. However, the implementation complexity of this model is a burden, and it does not promote the integration of the control plane of the IP and the WDM networks. Only a formal request is passed from the client layer to the server layer. • The peer model. The IP network has full topological view of the optical network and just a single routing algorithm instance is running in both the IP and the WDM networks. This model promotes the integration of the control plane of the IP and the WDM networks and is simpler in implementation, but its operation is far more complex than the overlay. In addition, this model can work only in cases where there is a single entity operating and managing the IP and the optical administrative domains. • The augmented model. This is a combination of the previous two models. Each layer has its own protocols; however, routing information exchange is allowed between the two layers. This model can be seen as the golden mean, combining the advantages of the peer and overlay model and minimizing their disadvantages at the same time. Some of the most significant control plane efforts on IP over optical area are reported hereafter, and although such efforts are still under development, their first results are being elaborated. 5.3.1 MPLambdaS–Generalized MPLS The IETF has originally proposed the MPLambdaS framework [4], which extends the MPLS ideas to the optical domain, allowing the reuse of the existing Internet protocols with the appropriate extensions. The OSPF, as well as the IS-IS routing protocols, have been enhanced to disseminate information relevant to the optical domain [5, 6] allowing the route computation and automatic topology discovery. Furthermore, [7] and [8] present the mapping between the signaling messages defined in the existing IP/MPLS signaling protocols, namely RSVP-TE and CR-LDP. This enables the automation of paths setup. MPlambdaS was originally based on the peer model, enabling direct interaction and integrated routing among the IP and the WDM layers. Later on,
the IETF extended the MPLambdaS framework, which was limited to MPLS/WDM interaction, to multiple layers by means of the generalized MPLS (GMPLS). In this sense, LSRs can take forwarding or cross-connection decisions based not only on packets and wavelengths, but also on time slots (SDH layer) and physical ports (fiber layer). In [9], four classes of interfaces on LSRs are defined—the packet-switch capable (PSC), the TDM capable, the Lambdaswitch capable (LSC), and finally the fiber-switch capable (FSC). Using label stacking, it is possible to make a forwarding hierarchy incorporating these classes of interfaces. Figure 5.5 presents the GMPLS hierarchy. MPLambdaS is focused in the provisioning of MPLS electrical LSPs over optical LSPs, and it was extended through GMPLS to multiple layers, offering electrical LSPs over SDH paths over optical LSPs over cross-connected fibers. Thus, it became a superset of ASON (an ITU-T initiative), which focuses only in the optical layer as will be described later. It should be noted that although GMPLS was defined to be generic, it appears that it is being developed as an extension of particular protocols, namely RSVP-TE and CR-LDP. 5.3.2 The ASON/ASTN Framework IP Over WDM Integration Mechanisms 81 ITU-T has followed a formal methodology regarding the integration of the different layers on top of the optical one by first elaborating the requirements for Fine-grain electrical LSP Figure 5.5 GMPLS hierarchy. Coarsegrain electrical LSP Coarsegrain electrical LSP Coarsegrain electrical LSP Coarsegrain electrical LSP Optical LSP (MPLambdaS) Optical LSP (MPLambdaS) Fiber
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: 30 Deploying and Managing IP over W
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 95 and 96: 4.4.4 Management Interfaces Managem
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: Gigabit Ethernet interface GbE prov
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 126 and 127: 100 Deploying and Managing IP over
Page 156 and 157:
130 Deploying and Managing IP over
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
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 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
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 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
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:
Page 265 and 266:
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?