< draft-wei-rift-applicability-00.txt   draft-wei-rift-applicability-01.txt >
RIFT WG T. Przygienda RIFT WG Yuehua. Wei
Internet-Draft Juniper Networks Internet-Draft Zheng. Zhang
Intended status: Standards Track Yuehua. Wei Intended status: Standards Track ZTE Corporation
Expires: December 13, 2019 Zheng. Zhang Expires: December 21, 2019 Dmitry. Afanasiev
ZTE Corporation
Dmitry. Afanasiev
Yandex Yandex
Tom. Verhaeg Tom. Verhaeg
Interconnect Services B.V. Interconnect Services B.V.
Jaroslaw. Kowalczyk Jaroslaw. Kowalczyk
Orange Polska Orange Polska
June 11, 2019 June 19, 2019
RIFT Applicability RIFT Applicability
draft-wei-rift-applicability-00 draft-wei-rift-applicability-01
Abstract Abstract
This document discusses the properties and applicability of RIFT in This document discusses the properties and applicability of RIFT in
different network topologies. It intends to provide a rough guide different network topologies. It intends to provide a rough guide
how RIFT can be deployed to simplify routing operations in Clos how RIFT can be deployed to simplify routing operations in Clos
topologies and their variations. topologies and their variations.
Status of This Memo Status of This Memo
skipping to change at page 1, line 41 skipping to change at page 1, line 39
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 December 13, 2019. This Internet-Draft will expire on December 21, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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
skipping to change at page 2, line 33 skipping to change at page 2, line 31
3.3.2. Metro Fabrics . . . . . . . . . . . . . . . . . . . . 6 3.3.2. Metro Fabrics . . . . . . . . . . . . . . . . . . . . 6
3.3.3. Building Cabling . . . . . . . . . . . . . . . . . . 6 3.3.3. Building Cabling . . . . . . . . . . . . . . . . . . 6
3.3.4. Internal Router Switching Fabrics . . . . . . . . . . 7 3.3.4. Internal Router Switching Fabrics . . . . . . . . . . 7
3.3.5. CloudCO . . . . . . . . . . . . . . . . . . . . . . . 7 3.3.5. CloudCO . . . . . . . . . . . . . . . . . . . . . . . 7
4. Operational Simplifications and Considerations . . . . . . . 9 4. Operational Simplifications and Considerations . . . . . . . 9
4.1. Automatic Disaggregation . . . . . . . . . . . . . . . . 10 4.1. Automatic Disaggregation . . . . . . . . . . . . . . . . 10
4.1.1. South reflection . . . . . . . . . . . . . . . . . . 10 4.1.1. South reflection . . . . . . . . . . . . . . . . . . 10
4.1.2. Suboptimal routing upon link failure use case . . . . 10 4.1.2. Suboptimal routing upon link failure use case . . . . 10
4.1.3. Black-holing upon link failure use case . . . . . . . 12 4.1.3. Black-holing upon link failure use case . . . . . . . 12
4.2. Usage of ZTP . . . . . . . . . . . . . . . . . . . . . . 13 4.2. Usage of ZTP . . . . . . . . . . . . . . . . . . . . . . 13
5. Normative References . . . . . . . . . . . . . . . . . . . . 13 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13
7. Normative References . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
This document intends to explain the properties and applicability of This document intends to explain the properties and applicability of
RIFT [I-D.ietf-rift-rift] in different deployment scenarios and RIFT [I-D.ietf-rift-rift] in different deployment scenarios and
highlight the operational simplicity of the technology compared to highlight the operational simplicity of the technology compared to
traditional routing solutions. traditional routing solutions.
2. Problem statement of a Fat Tree network in modern IP fabric 2. Problem statement of a Fat Tree network in modern IP fabric
skipping to change at page 13, line 43 skipping to change at page 13, line 43
The derivation of the level of each node happens based on LIEs The derivation of the level of each node happens based on LIEs
received from its neighbors whereas each node (with possibly received from its neighbors whereas each node (with possibly
exceptions of configured leafs) tries to attach at the highest exceptions of configured leafs) tries to attach at the highest
possible point in the fabric. possible point in the fabric.
This guarantees that even if the diffusion front reaches a node from This guarantees that even if the diffusion front reaches a node from
"below" faster than from "above", it will greedily abandon already "below" faster than from "above", it will greedily abandon already
negotiated level derived from nodes topologically below it and negotiated level derived from nodes topologically below it and
properly peers with nodes above. properly peers with nodes above.
5. Normative References 5. Acknowledgements
6. Contributors
The following people (listed in alphabetical order) contributed
significantly to the content of this document and should be
considered co-authors:
Tony Przygienda
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale, CA 94089
US
Email: prz@juniper.net
7. Normative References
[I-D.ietf-rift-rift] [I-D.ietf-rift-rift]
Team, T., "RIFT: Routing in Fat Trees", draft-ietf-rift- Team, T., "RIFT: Routing in Fat Trees", draft-ietf-rift-
rift-05 (work in progress), April 2019. rift-05 (work in progress), April 2019.
[I-D.white-distoptflood] [I-D.white-distoptflood]
White, R. and S. Zandi, "IS-IS Optimal Distributed White, R. and S. Zandi, "IS-IS Optimal Distributed
Flooding for Dense Topologies", draft-white- Flooding for Dense Topologies", draft-white-
distoptflood-00 (work in progress), March 2019. distoptflood-00 (work in progress), March 2019.
skipping to change at page 14, line 42 skipping to change at page 15, line 10
Binderberger, M., Ed., and J. Haas, Ed., "Bidirectional Binderberger, M., Ed., and J. Haas, Ed., "Bidirectional
Forwarding Detection (BFD) on Link Aggregation Group (LAG) Forwarding Detection (BFD) on Link Aggregation Group (LAG)
Interfaces", RFC 7130, DOI 10.17487/RFC7130, February Interfaces", RFC 7130, DOI 10.17487/RFC7130, February
2014, <https://www.rfc-editor.org/info/rfc7130>. 2014, <https://www.rfc-editor.org/info/rfc7130>.
[TR-384] Broadband Forum Technical Report, "TR-384 Cloud Central [TR-384] Broadband Forum Technical Report, "TR-384 Cloud Central
Office Reference Architectural Framework", Jan 2018. Office Reference Architectural Framework", Jan 2018.
Authors' Addresses Authors' Addresses
Tony Przygienda
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale, CA 94089
US
Email: prz@juniper.net
Yuehua Wei Yuehua Wei
ZTE Corporation ZTE Corporation
No.50, Software Avenue No.50, Software Avenue
Nanjing 210012 Nanjing 210012
P. R. China P. R. China
Email: wei.yuehua@zte.com.cn Email: wei.yuehua@zte.com.cn
Zheng Zhang Zheng Zhang
ZTE Corporation ZTE Corporation
 End of changes. 7 change blocks. 
19 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/