Muutke küpsiste eelistusi

E-raamat: Service Automation and Dynamic Provisioning Techniques in IP/MPLS Environments [Wiley Online]

(France Telecom), (France Telecom), (France Telecom)
  • Wiley Online
  • Hind: 158,59 €*
  • * hind, mis tagab piiramatu üheaegsete kasutajate arvuga ligipääsu piiramatuks ajaks
Jacquenet, Bourdon and Boucadair (France Telecom) explain how IP service offerings such as television broadcasts, videoconferencing and voice over IP are becoming more popular due to automation, and offer this textbook on how to maintain dynamic provisioning techniques on these technologies to guarantee high quality for consumers. The authors describe architectures and protocols for services such as RADIUS, Common Open Policy Service (COPS), Diameter, Simple Network Management Protocol and NETCONF. Aimed at IT personnel, network managers and students of networking systems, this book also addresses the automated production of MLPS-based VPNs. Annotation ©2008 Book News, Inc., Portland, OR (booknews.com)

Save time & resources with this comprehensive guide to automation configuration for the value-added IP services of the future.

As the Internet becomes the medium of choice for value-added IP service offerings such as TV broadcasting, videoconferencing, and Voice over IP, the ability of automating configuration processes has become a key challenge for service providers. In fact, this feature has become crucial with the ever-growing level of expertise required to deploy such services and the scope of the techniques that need to be activated in order to provide such services with a guaranteed level of quality.

Service Automation and Dynamic Provisioning Techniques in IP/MPLS Environments:

  • Discusses architectures and protocols for services information, covering the state-of-the-art in current implementations of Remote Authentication Dial-In User Service (RADIUS), Diameter, Common Open Policy Service (COPS), Simple Network Management Protocol (SNMP) and NETCONF
  • Explains various application examples, covering the dynamic enforcement of QoS, security, and IP Traffic Engineering policies.
  • Covers the automated production of MPLS-based VPNs.

The authors offer an invaluable guide for IT facilitators, network managers, and researchers in industry and academia, as well as students studying advanced IP/MPLS networking communications courses. System designers and architects will also find this book helpful.

Preface xi
Acknowledgements xiii
PART I ARCHITECTURES AND PROTOCOLS FOR SERVICE AUTOMATION
1(186)
Introduction
3(16)
To Begin With
3(10)
On IP Networks in General, and Routers in Particular
3(2)
On the Usefulness of Dynamic Routing Protocols in IP Networks
5(2)
On the Inability of an IGP to Address Interdomain Communication Needs
7(2)
On the BGP-4 Protocol
9(1)
The Rise of MPLS
10(3)
Context and Motivation of this Book
13(3)
Classifying Capabilities
14(1)
Services and Policies
14(1)
The Need for Automation
15(1)
How this Book is Organized
16(1)
What Is and What Should Never Be
16(3)
References
16(3)
Basic Concepts
19(8)
What is a Policy?
19(1)
Deriving Policies into Rules and Configuration Tasks
19(2)
Instantiation
20(1)
Device Identification
20(1)
Translation
21(1)
Storing Policies
21(1)
Policy and Device Configuration
21(1)
Policy-based Management Model
22(5)
Reaching a Policy Decision
24(1)
Requirements for a PEP-PDP Communication Protocol
24(1)
References
25(2)
The RADIUS Protocol and its Extensions
27(34)
Protocol Design
27(17)
Protocol Structure and Messages
28(8)
Forces and Weaknessess
36(3)
Authorization and Provisioning with RADIUS
39(5)
RADIUS Extensions
44(17)
EAP Support with RADIUS
44(3)
Interim Accounting
47(2)
Dynamic Authorization
49(2)
Using RADIUS for Assignment, Prioritization and Filtering with VLANs
51(1)
Filtering IP Traffic
52(1)
Future Extensions
53(2)
RADIUS and its Future
55(4)
References
59(2)
The Diameter Protocol
61(30)
Learning from RADIUS Deficiencies
61(4)
General Requirements
62(1)
Authentication Requirements
63(1)
Authorization Requirements
64(1)
Accounting Requirements
64(1)
Diameter is Born
64(1)
Diameter: Main Characteristics
65(6)
Diameter Network Entities
66(1)
Diameter Applications
67(1)
Sessions and Connections
67(1)
Diameter Routing
68(2)
Peer Discovery
70(1)
Peer Connection Maintenance for Reliable Transmissions
71(1)
Protocol Details
71(5)
Diameter Header
71(2)
AVP Format
73(1)
Command Codes
74(2)
Accounting
76(1)
Diameter Network Access Application (NASREQ)
76(5)
AVP Usage for NASREQ
77(1)
Enhanced Authorization Parameters
78(2)
Enhanced Authorization Examples
80(1)
Diameter Credit Control Application
81(1)
Diameter in NGN/IMS Architecture for QoS Control
82(9)
What is an NGN?
82(3)
QoS Control in ETSI/TISPAN Architecture
85(5)
References
90(1)
The Common Open Policy Service (COPS) Protocol
91(14)
A New Scheme for Policy-based Admission Control
91(1)
A Client-Server Architecture
92(2)
The COPS Protocol
94(3)
The COPS Header
94(1)
The COPS Message Objects
95(2)
COPS Messages
97(3)
Client-Open (OPN)
97(1)
Client-Accept (CAT)
97(1)
Request (REQ)
97(1)
Decision (DEC)
98(1)
Other COPS Messages
99(1)
Summary of COPS Operations
100(1)
Use of COPS in Outsourcing Mode
101(1)
Use of COPS in Provisioning Mode
101(3)
On the Impact of Provisioning Mode on COPS Operations
102(1)
On the Impact of Provisioning Mode on PEP-PDP Exchanges
103(1)
Security of COPS Messages
104(1)
References
104(1)
The NETCONF Protocol
105(70)
NETCONF at a Glance
105(4)
Introduction
105(1)
Motivations for Introducing NETCONF
106(1)
NETCONF, an IETF Initiative
107(1)
Missions of the IETF NETCONF Working Group
107(1)
NETCONF-related Literature
108(1)
What is In? What is Out?
109(1)
NETCONF Protocol Overview
109(22)
Some Words about XML
110(4)
NETCONF Terminology
114(1)
NETCONF Layer Model
114(2)
NETCONF Communication Phases
116(1)
NETCONF Data
117(1)
NETCONF Capability Exchange
118(2)
RPC Layer
120(9)
NETCONF Filtering
129(2)
NETCONF Protocol Operations
131(22)
Retrieve Configuration Data
135(2)
Get
137(1)
Delete Configuration Data
137(1)
Copy Configuration
138(1)
Edit Configuration Data
139(3)
Close a NETCONF Session
142(1)
Kill a Session
143(1)
Lock NETCONF Sessions
144(1)
Unlock NETCONF Sessions
145(1)
Validate Configuration Data
146(2)
Commit Configuration Changes
148(1)
Discard Changes of Configuration Data
149(1)
NETCONF Notification Procedure
149(4)
NETCONF Transport Protocol
153(9)
NETCONF as Transport-independent Protocol
153(1)
Transport Protocol Alternatives
153(9)
NETCONF Capabilities
162(9)
URL Capability
163(2)
XPath Capability
165(1)
Writable-Running Capability
166(1)
Candidate Configuration Capability
167(1)
Confirmed Commit Capability
167(1)
Validate Capability
168(1)
Distinct Startup Capability
169(1)
Rollback on Error Capability
170(1)
Notification Capability
171(1)
Configuring a Network Device
171(2)
NETCONF Content Layer
173(2)
References
173(2)
Control and Provisioning of Wireless Access Points (CAPWAP)
175(12)
CAPWAP to Address Access Point Provisioning Challenges
176(1)
CAPWAP Concepts and Terminology
176(4)
Objectives: What do we Expect from CAPWAP?
180(2)
CAPWAP Candidate Protocols
182(1)
The CAPWAP Protocol
183(3)
CAPWAP Future
186(1)
References
186(1)
PART II APPLICATION EXAMPLES OF SERVICE AUTOMATION AND DYNAMIC RESOURCE PROVISIONING TECHNIQUES
187(64)
Dynamic Enforcement of QoS Policies
189(10)
Introduction
189(4)
What is Quality of Service, Anyway?
189(3)
The Need for Service Level Specifications
192(1)
An Example
193(1)
Enforcing QoS Policies in Heterogeneous Environments
193(6)
SLS-inferred QoS Policy Enforcement Schemes
193(4)
Policy Rules for Configuring DiffServ Elements
197(1)
References
198(1)
Dynamic Enforcement of IP Traffic Engineering Policies
199(12)
Introduction
199(1)
Terminology Considerations
200(1)
Reference Model
201(1)
COPS Message Content
202(2)
Request Messages (REQ)
202(1)
Decision Messages (DEC)
203(1)
Report Messages (RPT)
203(1)
COPS-PR Usage of the IP TE Client-Type
204(1)
Scalability Considerations
205(1)
A Tentative Metric Taxonomy
205(1)
Reporting the Enforcement of an IP Traffic Engineering Policy
206(1)
IP TE PIB Overview
206(1)
COPS Usage for IP TE Accounting Purposes
207(4)
References
208(3)
Automated Production of BGP/MPLS-based VPN Networks
211(16)
Introduction
211(1)
Approach
212(2)
Use of Policies to Define Rules
214(1)
Instantiation of IP VPN Information Model Classes
214(1)
Policy Components of an IP VPN Information Model
215(6)
Physical Components of an IP VPN Information Model
216(1)
Virtual Components of an IP VPN Information Model
217(1)
Inheritance Hierarchy
218(3)
Dynamic Production of IP VPN Services
221(1)
Context of a Multidomain Environment
222(2)
A Bit of Terminology
222(1)
Reference Model
223(1)
Possible Extensions of the VPN Model
224(3)
References
224(3)
Dynamic Enforcement of Security Policies in IP/MPLS Environments
227(12)
Enforcing Security Policies for Web-based Access Control
227(8)
Enforcing Security Policies in Companies with 802.IX
235(4)
References
238(1)
Future Challenges
239(12)
Introduction
239(2)
Current Issues with Configuration Procedures
239(1)
Towards Service-driven Configuration Policies
240(1)
Towards the Standardization of Dynamic Service Subscription and Negotiation Techniques
241(5)
Basic Motivation
241(1)
Commercial Framework
241(1)
A Service-oriented Architecture
242(1)
Publishing and Accessing Services
243(1)
Example of Automated IP VPN Service Composition
244(2)
Introducing Self-organizing Networks
246(5)
What is a Self-organizing Network?
246(1)
Characteristics of SON Networks and Devices
247(1)
On Self-management
248(1)
SON Algorithms and How to Use Them for Enhancing Dynamic Policy Enforcement Schemes
248(1)
SON-inferred Business Opportunities
249(1)
References
249(2)
APPENDICES
251(78)
Appendix 1 XML Schema for NETCONF RPCs and Operations
253(16)
Appendix 2 XML Schema for NETCONF Notifications
269(4)
Appendix 3 Example of an IP Traffic Engineering Policy Information Base (IP TE PIB)
273(24)
Appendix 4 Example of an IP TE Accounting PIB
297(14)
Appendix 5 Description of Classes of an IP VPN Information Model
311(18)
A5.1 Introduction
311(1)
A5.2 Policy Class Definitions
311(18)
Index 329
Christian Jacquenet is Chief Technical Officer within the Long Distance Networks directorate of France Telecom, where he is involved in the specification and the development of France Telecom's IP network design strategies.?He has authored and co-authored several Internet drafts in the field of dynamic routing protocols and provisioning techniques, as well as several papers in the field of traffic engineering and automated production of services.