draft-ietf-bier-ping-00.txt | draft-ietf-bier-ping-01.txt | |||
---|---|---|---|---|
Network Work group N. Kumar | Network Work group N. Kumar | |||
Internet-Draft C. Pignataro | Internet-Draft C. Pignataro | |||
Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Cisco Systems, Inc. | |||
Expires: January 20, 2017 N. Akiya | Expires: July 21, 2017 N. Akiya | |||
Big Switch Networks | Big Switch Networks | |||
L. Zheng | L. Zheng | |||
M. Chen | M. Chen | |||
Huawei Technologies | Huawei Technologies | |||
G. Mirsky | G. Mirsky | |||
Ericsson | Ericsson | |||
July 19, 2016 | January 17, 2017 | |||
BIER Ping and Trace | BIER Ping and Trace | |||
draft-ietf-bier-ping-00 | draft-ietf-bier-ping-01 | |||
Abstract | Abstract | |||
Bit Index Explicit Replication (BIER) is an architecture that | Bit Index Explicit Replication (BIER) is an architecture that | |||
provides optimal multicast forwarding through a "BIER domain" without | provides optimal multicast forwarding through a "BIER domain" without | |||
requiring intermediate routers to maintain any multicast related per- | requiring intermediate routers to maintain any multicast related per- | |||
flow state. BIER also does not require any explicit tree-building | flow state. BIER also does not require any explicit tree-building | |||
protocol for its operation. A multicast data packet enters a BIER | protocol for its operation. A multicast data packet enters a BIER | |||
domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the | domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the | |||
BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). | BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). | |||
skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
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 January 20, 2017. | This Internet-Draft will expire on July 21, 2017. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2017 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 | |||
skipping to change at page 23, line 46 ¶ | skipping to change at page 23, line 46 ¶ | |||
TBD | TBD | |||
9. References | 9. References | |||
9.1. Normative References | 9.1. Normative References | |||
[I-D.ietf-bier-architecture] | [I-D.ietf-bier-architecture] | |||
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and | Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and | |||
S. Aldrin, "Multicast using Bit Index Explicit | S. Aldrin, "Multicast using Bit Index Explicit | |||
Replication", draft-ietf-bier-architecture-04 (work in | Replication", draft-ietf-bier-architecture-05 (work in | |||
progress), July 2016. | progress), October 2016. | |||
[I-D.ietf-bier-mpls-encapsulation] | [I-D.ietf-bier-mpls-encapsulation] | |||
Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., | Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., | |||
Aldrin, S., and I. Meilik, "Encapsulation for Bit Index | Aldrin, S., and I. Meilik, "Encapsulation for Bit Index | |||
Explicit Replication in MPLS Networks", draft-ietf-bier- | Explicit Replication in MPLS and non-MPLS Networks", | |||
mpls-encapsulation-05 (work in progress), July 2016. | draft-ietf-bier-mpls-encapsulation-06 (work in progress), | |||
December 2016. | ||||
[I-D.ietf-bier-ospf-bier-extensions] | [I-D.ietf-bier-ospf-bier-extensions] | |||
Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., | Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., | |||
Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions | Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions | |||
for BIER", draft-ietf-bier-ospf-bier-extensions-02 (work | for BIER", draft-ietf-bier-ospf-bier-extensions-04 (work | |||
in progress), March 2016. | in progress), September 2016. | |||
[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, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <http://www.rfc-editor.org/info/rfc2119>. | |||
[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol | [RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol | |||
Label Switched (MPLS) Data Plane Failures", RFC 4379, | Label Switched (MPLS) Data Plane Failures", RFC 4379, | |||
DOI 10.17487/RFC4379, February 2006, | DOI 10.17487/RFC4379, February 2006, | |||
<http://www.rfc-editor.org/info/rfc4379>. | <http://www.rfc-editor.org/info/rfc4379>. | |||
End of changes. 8 change blocks. | ||||
11 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |