deploying and managing ip over wdm networks - Index of

Recommendations

Info

20 Deploying and Managing IP over WDM Networks The next layer is the metropolitan DWDM network, also called the metro or regional network. The metropolitan WDM equipment will be organized in OADM-based shared protection rings, depending on the service provider’s desired degree of bandwidth overbuild and survivability time-scale requirements. It may be connected either directly to an OLS or to a terabit router performing traffic routing at optical (wavelength) or IP layer accordingly. The metropolitan DWDM systems deliver quite a large number of wavelengths, and distribute channels of traffic to more nodes located in the city region. The access WDM network is primarily the same as the metropolitan WDM network, but it is adapted for a smaller number of wavelengths. Its role is to distribute traffic to the access and customer premises network. Various systems can be attached to the access ring (e.g., x-type digital subscriber loop (xDSL) DSLAMs, SDH fiber rings, SDH direct links, and ONUs). In all cases, the edge device can be either connected directly to the optical terminal or a core switch can be utilized to concentrate the traffic. For the enterprise network, many alternatives can be considered. One example is to use an ATM switch or a gigabit router as edge devices. The access interface can vary from 25 to 155 Mbps, or even to 625 Mbps. At the small office home office (SOHO) access, traffic will be normally distributed via an xDSL interface from a modem or a residential gateway. In Chapter 12, we provide a complementary view of the OTN evolution, pointing out the deployment time scale of different technologies in the earlier mentioned network levels. 2.4.2 I2 I2 [15, 16] is a consortium being led by over 180 universities working in partnership with industry and government to develop and deploy advanced network applications and technologies, accelerating the creation of tomorrow’s Internet. I2 is recreating the partnership among academia, industry, and government that fostered today’s Internet in its infancy. The primary goals of I2 are to: • Create a leading-edge network capability for the national research community; • Enable revolutionary Internet applications; • Ensure the rapid transfer of new network services and applications to the broader Internet community. I2 is not a separate physical network and will not replace the Internet. I2 brings together institutions and resources from academia, industry, and
Network and Service Evolution Scenarios 21 government to develop new technologies and capabilities that can then be deployed in the global Internet. Close collaboration with I2 corporate members will ensure that new applications and technologies are rapidly deployed throughout the Internet. Just as e-mail and the World Wide Web are legacies of earlier investments in academic and federal research networks, the legacy of I2 will be to expand the possibilities of the broader Internet. I2 and its members are developing and testing new technologies, such as IPv6, multicasting, and QoS that will enable revolutionary Internet applications. However, these applications require performance not possible on today’s Internet. More than a faster Web or e-mail, these new technologies will enable completely new applications, such as digital libraries, virtual laboratories, distance-independent learning and teleimmersion. A primary goal of I2 is to ensure the transfer of new network technology and applications to the broader education and networking communities. It is expected that the capabilities needed to use new technologies and applications being tested and developed by I2 and its members will be built into upcoming generations of commercial products. I2 corporate partners are working closely with the I2 community to expand the capabilities of their products and services as well as the global Internet. For example, just as most personal computers sold today include the ability to use the Internet, tomorrow’s commercial products will include the ability to use advanced networking capabilities. University research and education missions increasingly require the collaboration of personnel and hardware located at campuses throughout the country in ways not possible over today’s Internet. Moreover, universities are a principal source of both the demand for advanced networking technologies and the talent needed to implement them. Participation in I2 is open to any university that commits to providing on-campus facilities that will allow advanced applications development. The investment this requires may be more than many institutions can manage right now. However, I2 also supports collaboration by I2 universities with nonmember institutions. Fifteen years ago, connecting to the Internet could be as expensive as participating in I2 today. As the technology dropped in price, the entire academic community benefited from the efforts of the initial research participants. Deployment of I2 technology will follow a similar pattern. A key goal of I2 is to accelerate the diffusion of advanced Internet technology, in particular into the commercial sector. I2 will benefit nonuniversity members of the educational community as well, especially schools and public libraries. I2 and its members aim to share their expertise with as wide a range of computer users as possible. This approach characterized the first Internet, and it can work again today.
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 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 97 and 98:
Management of the WDM Network Layer
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:
90 Deploying and Managing IP over W
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:
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

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

Delete template?

Save as template?