draft-ietf-i2rs-usecase-reqs-summary-01.txt | draft-ietf-i2rs-usecase-reqs-summary-02.txt | |||
---|---|---|---|---|
i2rs S. Hares | i2rs S. Hares | |||
Internet-Draft Huawei | Internet-Draft Huawei | |||
Intended status: Informational M. Chen | Intended status: Informational M. Chen | |||
Expires: November 20, 2015 Huawei Technologies | Expires: September 16, 2016 Huawei Technologies | |||
May 19, 2015 | March 15, 2016 | |||
Summary of I2RS Use Case Requirements | Summary of I2RS Use Case Requirements | |||
draft-ietf-i2rs-usecase-reqs-summary-01 | draft-ietf-i2rs-usecase-reqs-summary-02 | |||
Abstract | Abstract | |||
The I2RS Working Group (WG) has described a set of use cases that the | The I2RS Working Group (WG) has described a set of use cases that the | |||
I2RS systems could fulfil. This document summarizes these use cases. | I2RS systems could fulfil. This document summarizes these use cases. | |||
It is designed to provide requirements that will aid the design of | It is designed to provide requirements that will aid the design of | |||
the I2RS architecture, Information Models, Data Models, Security, and | the I2RS architecture, Information Models, Data Models, Security, and | |||
protocols. | protocols. | |||
Status of This Memo | Status of This Memo | |||
skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on November 20, 2015. | This Internet-Draft will expire on September 16, 2016. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2016 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
2. Protocol Independent Use Case Requirements . . . . . . . . . 4 | 2. Protocol Independent Use Case Requirements . . . . . . . . . 4 | |||
3. BGP Use Case Requirements . . . . . . . . . . . . . . . . . . 6 | 3. BGP Use Case Requirements . . . . . . . . . . . . . . . . . . 6 | |||
4. IGP Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 8 | 4. IGP Use Cases . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
5. CCNE Use Cases . . . . . . . . . . . . . . . . . . . . . . . 10 | 5. CCNE Use Cases . . . . . . . . . . . . . . . . . . . . . . . 10 | |||
6. Topology Related Use Cases . . . . . . . . . . . . . . . . . 10 | 6. Topology Related Use Cases . . . . . . . . . . . . . . . . . 11 | |||
6.1. Virtual Connection Use Case Requirements . . . . . . . . 11 | 6.1. Virtual Connection Use Case Requirements . . . . . . . . 11 | |||
6.2. Virtual Network Use Case Requirements . . . . . . . . . . 11 | 6.2. Virtual Network Use Case Requirements . . . . . . . . . . 11 | |||
6.3. Topology Use Case . . . . . . . . . . . . . . . . . . . . 12 | 6.3. Topology Use Case . . . . . . . . . . . . . . . . . . . . 13 | |||
6.4. Virtual Topology Data Model . . . . . . . . . . . . . . . 17 | 6.4. Virtual Topology Data Model . . . . . . . . . . . . . . . 17 | |||
6.5. Virtual Topology IP Data Model . . . . . . . . . . . . . 18 | 6.5. Virtual Topology IP Data Model . . . . . . . . . . . . . 19 | |||
6.6. Virtual Topology Network Element . . . . . . . . . . . . 19 | 6.6. Virtual Topology Network Element . . . . . . . . . . . . 19 | |||
7. Requirements from SFC Use Cases . . . . . . . . . . . . . . . 20 | 7. Requirements from SFC Use Cases . . . . . . . . . . . . . . . 20 | |||
8. Requirements from Traffic Steering Use Cases . . . . . . . . 21 | 8. Requirements from Traffic Steering Use Cases . . . . . . . . 22 | |||
9. Requirements from MPLS TE Networks Use Cases . . . . . . . . 22 | 9. Requirements from MPLS TE Networks Use Cases . . . . . . . . 22 | |||
10. Requirements from MPLS LDP Networks Use Cases . . . . . . . . 24 | 10. Requirements from MPLS LDP Networks Use Cases . . . . . . . . 24 | |||
11. Requirements from Mobile Backhaul Ues Cases . . . . . . . . . 25 | 11. Requirements from Mobile Backhaul Ues Cases . . . . . . . . . 25 | |||
12. Requirements from Large Data Flows are . . . . . . . . . . . 27 | 12. Requirements from Large Data Flows are . . . . . . . . . . . 27 | |||
13. Large Data Collection Systems . . . . . . . . . . . . . . . . 28 | 13. Large Data Collection Systems . . . . . . . . . . . . . . . . 28 | |||
14. CDNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 | 14. CDNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 | |||
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 | 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 | |||
16. Security Considerations . . . . . . . . . . . . . . . . . . . 31 | 16. Security Considerations . . . . . . . . . . . . . . . . . . . 31 | |||
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 | 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 31 | |||
17.1. Normative References . . . . . . . . . . . . . . . . . . 31 | 17.1. Normative References . . . . . . . . . . . . . . . . . . 31 | |||
skipping to change at page 6, line 24 ¶ | skipping to change at page 6, line 24 ¶ | |||
o PI-REQ10 (OC): The ability to interact with policies and | o PI-REQ10 (OC): The ability to interact with policies and | |||
configurations on the forwarding devices using time based | configurations on the forwarding devices using time based | |||
processing, either through timed auto-rollback or some other | processing, either through timed auto-rollback or some other | |||
mechanism. This interaction should be through existing | mechanism. This interaction should be through existing | |||
configuration mechanisms, such as NETCONF, and should be recorded | configuration mechanisms, such as NETCONF, and should be recorded | |||
in the configuration of the local device so operators are aware of | in the configuration of the local device so operators are aware of | |||
the full policy implemented in the network from the running | the full policy implemented in the network from the running | |||
configuration. | configuration. | |||
o PI-REQ-11 (IC) The ability to update the Local RIB with varying | ||||
levels of checks on the route. These checks can be simply minimal | ||||
reception checks (TLVs align corrrectly), all non-referential | ||||
checks (do not do leafref, MUST, instance identifiers), do | ||||
referential checks. | ||||
3. BGP Use Case Requirements | 3. BGP Use Case Requirements | |||
This is a summary of the requirements listed in | This is a summary of the requirements listed in | |||
[I-D.keyupate-i2rs-bgp-usecases] are (IC): | [I-D.keyupate-i2rs-bgp-usecases] are (IC): | |||
o BGP-REQ01 (IC): I2RS client/agent exchange SHOULD support the | o BGP-REQ01 (IC): I2RS client/agent exchange SHOULD support the | |||
read, write and quick notification of status of the BGP peer | read, write and quick notification of status of the BGP peer | |||
operational state on each router within a given Autonomous System | operational state on each router within a given Autonomous System | |||
(AS). This operational status includes the quick notification of | (AS). This operational status includes the quick notification of | |||
protocol events that proceed a destructive tear-down of BGP | protocol events that proceed a destructive tear-down of BGP | |||
skipping to change at page 31, line 22 ¶ | skipping to change at page 31, line 27 ¶ | |||
the operators. I2RS should provide strong security mechanism to | the operators. I2RS should provide strong security mechanism to | |||
protect the routing information that it could not be accessed by the | protect the routing information that it could not be accessed by the | |||
un-authorised users. It should also protect the security and | un-authorised users. It should also protect the security and | |||
integrity protection of the routing data. | integrity protection of the routing data. | |||
17. References | 17. References | |||
17.1. Normative References | 17.1. Normative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | ||||
<http://www.rfc-editor.org/info/rfc2119>. | ||||
[RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, | [RFC3746] Yang, L., Dantu, R., Anderson, T., and R. Gopal, | |||
"Forwarding and Control Element Separation (ForCES) | "Forwarding and Control Element Separation (ForCES) | |||
Framework", RFC 3746, April 2004. | Framework", RFC 3746, DOI 10.17487/RFC3746, April 2004, | |||
<http://www.rfc-editor.org/info/rfc3746>. | ||||
17.2. Informative References | 17.2. Informative References | |||
[I-D.amante-i2rs-topology-use-cases] | [I-D.amante-i2rs-topology-use-cases] | |||
Medved, J., Previdi, S., Lopez, V., and S. Amante, | Medved, J., Previdi, S., Lopez, V., and S. Amante, | |||
"Topology API Use Cases", draft-amante-i2rs-topology-use- | "Topology API Use Cases", draft-amante-i2rs-topology-use- | |||
cases-01 (work in progress), October 2013. | cases-01 (work in progress), October 2013. | |||
[I-D.bitar-i2rs-service-chaining] | [I-D.bitar-i2rs-service-chaining] | |||
Bitar, N., Heron, G., Fang, L., ramki, r., Leymann, N., | Bitar, N., Heron, G., Fang, L., ramki, r., Leymann, N., | |||
skipping to change at page 32, line 19 ¶ | skipping to change at page 32, line 29 ¶ | |||
case-vn-vc-03 (work in progress), July 2014. | case-vn-vc-03 (work in progress), July 2014. | |||
[I-D.huang-i2rs-mpls-te-usecases] | [I-D.huang-i2rs-mpls-te-usecases] | |||
Huang, T., Li, Z., and S. Hares, "Use Cases for an | Huang, T., Li, Z., and S. Hares, "Use Cases for an | |||
Interface to MPLS TE", draft-huang-i2rs-mpls-te- | Interface to MPLS TE", draft-huang-i2rs-mpls-te- | |||
usecases-02 (work in progress), July 2014. | usecases-02 (work in progress), July 2014. | |||
[I-D.ietf-i2rs-architecture] | [I-D.ietf-i2rs-architecture] | |||
Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | Atlas, A., Halpern, J., Hares, S., Ward, D., and T. | |||
Nadeau, "An Architecture for the Interface to the Routing | Nadeau, "An Architecture for the Interface to the Routing | |||
System", draft-ietf-i2rs-architecture-09 (work in | System", draft-ietf-i2rs-architecture-13 (work in | |||
progress), March 2015. | progress), February 2016. | |||
[I-D.ietf-i2rs-problem-statement] | [I-D.ietf-i2rs-problem-statement] | |||
Atlas, A., Nadeau, T., and D. Ward, "Interface to the | Atlas, A., Nadeau, T., and D. Ward, "Interface to the | |||
Routing System Problem Statement", draft-ietf-i2rs- | Routing System Problem Statement", draft-ietf-i2rs- | |||
problem-statement-06 (work in progress), January 2015. | problem-statement-10 (work in progress), February 2016. | |||
[I-D.ietf-i2rs-rib-info-model] | [I-D.ietf-i2rs-rib-info-model] | |||
Bahadur, N., Folkes, R., Kini, S., and J. Medved, "Routing | Bahadur, N., Kini, S., and J. Medved, "Routing Information | |||
Information Base Info Model", draft-ietf-i2rs-rib-info- | Base Info Model", draft-ietf-i2rs-rib-info-model-08 (work | |||
model-06 (work in progress), March 2015. | in progress), October 2015. | |||
[I-D.ietf-sfc-problem-statement] | [I-D.ietf-sfc-problem-statement] | |||
Quinn, P. and T. Nadeau, "Service Function Chaining | Quinn, P. and T. Nadeau, "Service Function Chaining | |||
Problem Statement", draft-ietf-sfc-problem-statement-13 | Problem Statement", draft-ietf-sfc-problem-statement-13 | |||
(work in progress), February 2015. | (work in progress), February 2015. | |||
[I-D.ji-i2rs-usecases-ccne-service] | [I-D.ji-i2rs-usecases-ccne-service] | |||
Ji, X., Zhuang, S., Huang, T., and S. Hares, "I2RS Use | Ji, X., Zhuang, S., Huang, T., and S. Hares, "I2RS Use | |||
Cases for Control of Forwarding Path by Central Control | Cases for Control of Forwarding Path by Central Control | |||
Network Element (CCNE)", draft-ji-i2rs-usecases-ccne- | Network Element (CCNE)", draft-ji-i2rs-usecases-ccne- | |||
skipping to change at page 33, line 43 ¶ | skipping to change at page 33, line 49 ¶ | |||
White, R., Hares, S., and A. Retana, "Protocol Independent | White, R., Hares, S., and A. Retana, "Protocol Independent | |||
Use Cases for an Interface to the Routing System", draft- | Use Cases for an Interface to the Routing System", draft- | |||
white-i2rs-use-case-06 (work in progress), July 2014. | white-i2rs-use-case-06 (work in progress), July 2014. | |||
[I-D.zhang-i2rs-mbb-usecases] | [I-D.zhang-i2rs-mbb-usecases] | |||
Zhang, L., Li, Z., Liu, D., and S. Hares, "Use Cases of | Zhang, L., Li, Z., Liu, D., and S. Hares, "Use Cases of | |||
I2RS in Mobile Backhaul Network", draft-zhang-i2rs-mbb- | I2RS in Mobile Backhaul Network", draft-zhang-i2rs-mbb- | |||
usecases-01 (work in progress), February 2014. | usecases-01 (work in progress), February 2014. | |||
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | |||
Element (PCE)-Based Architecture", RFC 4655, August 2006. | Element (PCE)-Based Architecture", RFC 4655, | |||
DOI 10.17487/RFC4655, August 2006, | ||||
<http://www.rfc-editor.org/info/rfc4655>. | ||||
[RFC5212] Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, | [RFC5212] Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, | |||
M., and D. Brungard, "Requirements for GMPLS-Based Multi- | M., and D. Brungard, "Requirements for GMPLS-Based Multi- | |||
Region and Multi-Layer Networks (MRN/MLN)", RFC 5212, July | Region and Multi-Layer Networks (MRN/MLN)", RFC 5212, | |||
2008. | DOI 10.17487/RFC5212, July 2008, | |||
<http://www.rfc-editor.org/info/rfc5212>. | ||||
[RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast | [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for | |||
Reroute: Loop-Free Alternates", RFC 5286, September 2008. | IP Fast Reroute: Loop-Free Alternates", RFC 5286, | |||
DOI 10.17487/RFC5286, September 2008, | ||||
<http://www.rfc-editor.org/info/rfc5286>. | ||||
[RFC5623] Oki, E., Takeda, T., Le Roux, JL., and A. Farrel, | [RFC5623] Oki, E., Takeda, T., Le Roux, JL., and A. Farrel, | |||
"Framework for PCE-Based Inter-Layer MPLS and GMPLS | "Framework for PCE-Based Inter-Layer MPLS and GMPLS | |||
Traffic Engineering", RFC 5623, September 2009. | Traffic Engineering", RFC 5623, DOI 10.17487/RFC5623, | |||
September 2009, <http://www.rfc-editor.org/info/rfc5623>. | ||||
[RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic | [RFC5693] Seedorf, J. and E. Burger, "Application-Layer Traffic | |||
Optimization (ALTO) Problem Statement", RFC 5693, October | Optimization (ALTO) Problem Statement", RFC 5693, | |||
2009. | DOI 10.17487/RFC5693, October 2009, | |||
<http://www.rfc-editor.org/info/rfc5693>. | ||||
Authors' Addresses | Authors' Addresses | |||
Susan Hares | Susan Hares | |||
Huawei | Huawei | |||
Email: shares@ndzh.com | Email: shares@ndzh.com | |||
Mach Chen | Mach Chen | |||
Huawei Technologies | Huawei Technologies | |||
End of changes. 19 change blocks. | ||||
25 lines changed or deleted | 41 lines changed or added | |||
This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |