deploying and managing ip over wdm networks - Index of

Recommendations

Info

78 Deploying and Managing IP over WDM Networks SDL uses a 4-octet header, which includes the packet length, as shown in Figure 5.3. The packet can be up to 65,535 octets long. Additional error checking codes (CRC-16 or CRC-32) can optionally be used for the packet and may be placed after the packet. All bits except for the header are scrambled using an x48 scrambler. The sender and receiver scramblers are kept synchronized by occasional transmission of special packets. SDL does not include any extra bytes dedicated to protection switching protocols (like the K1 and K2 bytes of SDH). The use of the optional payload CRCs could enable BER monitoring. 5.2.5 IP Over GbE Over WDM The new GbE standard can be used to extend high-capacity LANs to MANs and maybe even WANs, using gigabit line cards on IP routers, which can cost five times less than SDH line cards with similar capacity. For this reason, GbE could be a very attractive means to transport IP over metropolitan WDM rings, for example, or even over longer WDM links. Furthermore, 10-Gbps Ethernet ports are likely to be standardized in the near future. Figure 5.4 shows an example of an IP network based on GbE interfaces. The GbE line cards may be used on IP routers only, or fast layer 2 Ethernet switches may also be used to network several IP routers together. Lower bit rate Ethernet networks (e.g., 10Base-T or 100Base-T) have been used a lot in a half-duplex mode, where the bandwidth available for transmission is shared between all users and between both directions of transmission. To policy access to the shared bandwidth, CSMA-CD is used. This imposes limits on the physical size of the network, where the transit time cannot exceed the slot time, which is the minimum frame length (512 bits for 10Base-T and 100Base-T). For a bit rate of 1 Gbps, using a minimum frame length of 512 bits would imply an Ethernet network only roughly 10m long. For this reason, the minimum frame length has been redefined to be 4,096 bits for GbE. However, this still limits the network size to 100m, so full-duplex mode is more attractive when using GbE. When GbE (1000Base-X) is used in full-duplex mode, it becomes simply an encapsulation and framing method for IP packets, and the CSMA-CD functionality is not used. Ethernet switches can also be used to extend the network topology beyond a point-to-point link. Packet Figure 5.3 SDL header structure. Packet length CRC-16 Packet
Gigabit Ethernet interface GbE provides some support of CoS as defined in the standards IEEE 802.1Q and 802.1p. These standards facilitate CoS over Ethernet by providing a means for tagging packets with an indication of the priority or class of service desired for the packet. These tags allow applications to communicate the priority of packets to internetworking devices. RSVP or DiffServ support may also be achieved by mapping into 802.1p service classes. 5.3 Control Plane Integration IP Over WDM Integration Mechanisms 79 OADM OADM GbE 32 λ WDM ring OADM OADM Gigabit Ethernet interfaces GbE Gigabit Ethernet switch Gigabit Ethernet interface Gigabit Ethernet interface Figure 5.4 Example of IP being transported over a WDM ring with GbE framing. Control plane (CP) is used in the literature to refer to the set of real-time mechanisms and algorithms needed for call or connection control. It deals mainly with the signaling to set up, supervise, and release calls and connections [1]. Although a detailed decomposition of the control plane and a description of each component is not the purpose of this book, we can safely assume that the signaling protocols for connection setup, the routing protocols supporting network discovery, and the protection/recovery mechanisms are the most significant features of the control plane. In this way, it is easier to track all of the recent control plane advances and proposals about the integration of multiple layers such as IP, ATM, SDH, and WDM. A significant element in the IP and optical integration is the corresponding business model proposed by each framework. The three basic business models
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: 28 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: IP router OLA The version of IP ove
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 126 and 127: 100 Deploying and Managing IP over
Page 154 and 155:
128 Deploying and Managing IP over
Page 156 and 157:
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

Create successful ePaper yourself

Delete template?

Save as template?