1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN)...
-
Upload
molly-chambers -
Category
Documents
-
view
215 -
download
0
Transcript of 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN)...
![Page 1: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/1.jpg)
1
Requirements for GMPLS-based multi-region andmulti-layer networks (MRN/MLN)
draft-ietf-ccamp-gmpls-mln-reqs-01.txt
CCAMP WG, IETF 66
Jul. 10, 2006
Kohei Shiomoto (NTT)Dimitri Papadimitriou (Alcatel)
Jean-Louis Le Roux (France Telecom)Martin Vigoureux (Alcatel)Deborah Brungard (AT&T)
Eiji Oki (NTT) Ichiro Inoue (NTT)
Emmanuel Dotaro (Alcatel)
![Page 2: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/2.jpg)
3
Changes since Dallas (1)
• Clarified client/server relationship– Customer network provided on top of a server MRN/MLN
• MLN/MRN services
– The customer network may form part of the MRN/MLN or may be partially separated
• E.g. separate routing instances
• Multiple control plane instances addressed as part of the client/server relationship
• MLN definition kept as is: – "A set of LSR with multiple data plane layers of either the same
ISC or different ISCs, controlled by a single GMPLS control plane instance"
![Page 3: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/3.jpg)
4
Changes since Dallas (2)
• Added some requirements– FA LSP rerouting MUST be possible while the FA
LSP is carrying traffic, with minimal traffic disruption– Virtual TE link creation/deletion MUST be under the
control of operator policy
• Some rewordings for the sake of clarity
![Page 4: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/4.jpg)
5
Next Steps
• Requirements for control plane separation between client and server layers– Support for administrative boundary between client and
server MLN/MRN network , minimizing impact on the customer network design, operation, and administration
– Support for path computation across separated TEDs associated with client and server MLN/MRN network
– Support for association between TE-links in separated TEDs associated with client and server MLN/MRN networks
• Discussion should continue on the list
![Page 5: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/5.jpg)
6
Evaluation of existing GMPLS protocols against MLN requirements
draft-ietf-ccamp-gmpls-mln-eval-01.txt
CCAMP WG, IETF 66
July 10, 2006
Jean-Louis Le Roux (France Telecom) Deborah Brungard (AT&T)
Eiji Oki (NTT)Dimitri Papadimitriou (Alcatel)
Kohei Shiomoto (NTT)Martin Vigoureux (Alcatel)
Ichiro Inoue (NTT) Emmanuel Dotaro (Alcatel)
![Page 6: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/6.jpg)
7
Evaluation Summary
• Four areas, where extensions of GMPLS protocols and procedures are required, have been identified
1. GMPLS signaling extension for the setup/deletion of virtual TE-links
2. GMPLS routing and signaling extension for graceful TE-link deletion
3. GMPLS signaling extension for constrained multi-region signaling (SC inclusion/exclusion)
4. GMPLS routing extension for the advertisement of the internal adaptation capability of hybrid nodes.
![Page 7: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/7.jpg)
8
Changes since Dallas • Aligned client/server relationship with the requirement draft• Clarified analysis of the VNT reconfiguration function
– Clear distinction between elementary functional blocks• Collection of traffic demands of an upper layer• VNT Management (decision to setup/remove FA-LSPs, FA config)• VNT Computation
– There functions can be distributed on networks elements and/or centralized – Anyway, no need for GMPLS protocol extensions here
• Detailed analysis of virtual TE link function– Two approaches
• Soft-FA: LSP signaled but data plane resources not committed => Could rely on procedures similar to secondary LSPs (shared meshed restoration)
• Remote Association: LSP not signaled, TE link ids and parameters exchanged between FA end-points => Could rely on extensions to the Call procedure (with Notify messages)
– Pros and cons are discussed• Soft FA: More admission control capabilities, but scalability limitations• Remote Association: Scales well but less admission control
![Page 8: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/8.jpg)
9
Next Steps
• Analyze requirements for control plane separation between client and server layers– Path computation across separated TEDs– Association of TE-links in separated TEDs– Client/MLN administrative boundaries
• Continue discussion on the list
![Page 9: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/9.jpg)
10
(GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
draft-papadimitriou-ccamp-gmpls-mrn-extensions-02.txt
CCAMP WG, IETF 66
July 10, 2006
Dimitri Papadimitriou (Alcatel)Kohei Shiomoto (NTT)
Martin Vigoureux (Alcatel)Deborah Brungard (AT&T)
Jean-Louis Le Roux (France Telecom) Ichiro Inoue (NTT)
Emmanuel Dotaro (Alcatel)Gert Grammel (Alcatel)
![Page 10: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/10.jpg)
11
Overview
• This draft defines GMPLS protocol extensions for Multi Layer Networks
• Currently two protocol extensions defined– Routing extensions for the advertisement of the Internal
Adaptation Capabilities: • IACD sub-TLV to be carried within the ISIS Extended IS
Reacheability TLV or the OPSF Link TLV
– Signaling extensions for SC inclusion exclusion• A new SC subobject to be carried within the ERO and XRO
![Page 11: 1 Requirements for GMPLS-based multi-region and multi-layer networks (MRN/MLN) draft-ietf-ccamp-gmpls-mln-reqs-01.txt CCAMP WG, IETF 66 Jul. 10, 2006 Kohei.](https://reader036.fdocuments.us/reader036/viewer/2022082613/5697bfef1a28abf838cba26a/html5/thumbnails/11.jpg)
12
Next Steps
• Draft restructuring to focus on GMPLS protocol extensions
• Clarify SC Inclusion/exclusion procedures
• Define solution(s) for virtual TE links
• WG feedback required
• Adopt as WG doc?