draft-ietf-bier-entropy-staged-dc-clos-01.txt   draft-ietf-bier-entropy-staged-dc-clos-02.txt 
Network Working Group J. Xie Network Working Group J. Xie
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Informational X. Xu Intended status: Informational X. Xu
Expires: November 9, 2019 Alibaba Inc. Expires: May 7, 2020 Alibaba Inc.
G. Yan G. Yan
M. McBride
Huawei Technologies Huawei Technologies
May 8, 2019 M. McBride
Futurewei
November 4, 2019
Use of BIER Entropy for Data Center Clos Networks Use of BIER Entropy for Data Center Clos Networks
draft-ietf-bier-entropy-staged-dc-clos-01 draft-ietf-bier-entropy-staged-dc-clos-02
Abstract Abstract
Bit Index Explicit Replication (BIER) introduces a new multicast- Bit Index Explicit Replication (BIER) introduces a new multicast-
specific BIER Header. BIER can be applied to the Multi Protocol specific BIER Header. BIER can be applied to the Multi Protocol
Label Switching (MPLS) data plane or Non-MPLS data plane. Entropy is Label Switching (MPLS) data plane or Non-MPLS data plane. Entropy is
a technique used in BIER to support load-balancing. This document a technique used in BIER to support load-balancing. This document
examines and describes how BIER Entropy is to be applied to Data examines and describes how BIER Entropy is to be applied to Data
Center Clos networks for path selection. Center Clos networks for path selection.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 November 9, 2019. This Internet-Draft will expire on May 7, 2020.
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 8, line 35 skipping to change at page 8, line 35
DOI 10.17487/RFC8365, March 2018, DOI 10.17487/RFC8365, March 2018,
<https://www.rfc-editor.org/info/rfc8365>. <https://www.rfc-editor.org/info/rfc8365>.
9.2. Informative References 9.2. Informative 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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
Authors' Addresses Authors' Addresses
Jingrong Xie Jingrong Xie
Huawei Technologies Huawei Technologies
Email: xiejingrong@huawei.com Email: xiejingrong@huawei.com
Xiaohu Xu Xiaohu Xu
Alibaba Inc. Alibaba Inc.
skipping to change at page 8, line 46 skipping to change at page 9, line 4
Jingrong Xie Jingrong Xie
Huawei Technologies Huawei Technologies
Email: xiejingrong@huawei.com Email: xiejingrong@huawei.com
Xiaohu Xu Xiaohu Xu
Alibaba Inc. Alibaba Inc.
Email: xiaohu.xxh@alibaba-inc.com Email: xiaohu.xxh@alibaba-inc.com
Gang Yan Gang Yan
Huawei Technologies Huawei Technologies
Email: yangang@huawei.com Email: yangang@huawei.com
Mike McBride Mike McBride
Huawei Technologies Futurewei
Email: mmcbride7@gmail.com Email: mmcbride7@gmail.com
 End of changes. 10 change blocks. 
9 lines changed or deleted 16 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/