| < draft-ietf-bier-ospf-bier-extensions-00.txt | draft-ietf-bier-ospf-bier-extensions-01.txt > | |||
|---|---|---|---|---|
| OSPF P. Psenak, Ed. | OSPF P. Psenak, Ed. | |||
| Internet-Draft N. Kumar | Internet-Draft N. Kumar | |||
| Intended status: Standards Track IJ. Wijnands | Intended status: Standards Track IJ. Wijnands | |||
| Expires: October 29, 2015 Cisco | Expires: April 21, 2016 Cisco | |||
| A. Dolganow | A. Dolganow | |||
| Alcatel-Lucent | Alcatel-Lucent | |||
| T. Przygienda | T. Przygienda | |||
| Ericsson | Ericsson | |||
| J. Zhang | J. Zhang | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| S. Aldrin | S. Aldrin | |||
| Google, Inc. | Google, Inc. | |||
| April 27, 2015 | October 19, 2015 | |||
| OSPF Extensions For BIER | OSPF Extensions For BIER | |||
| draft-ietf-bier-ospf-bier-extensions-00.txt | draft-ietf-bier-ospf-bier-extensions-01.txt | |||
| 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 October 29, 2015. | This Internet-Draft will expire on April 21, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 | |||
| skipping to change at page 6, line 37 ¶ | skipping to change at page 6, line 37 ¶ | |||
| BIER MPLS Encapsulation Sub-TLV: TBD | BIER MPLS Encapsulation Sub-TLV: TBD | |||
| 5. Acknowledgments | 5. Acknowledgments | |||
| The authors would like to thank Rajiv Asati, Christian Martin, Greg | The authors would like to thank Rajiv Asati, Christian Martin, Greg | |||
| Shepherd and Eric Rosen for their contribution. | Shepherd and Eric Rosen for their contribution. | |||
| 6. Normative References | 6. Normative References | |||
| [I-D.ietf-ospf-prefix-link-attr] | [I-D.ietf-ospf-prefix-link-attr] | |||
| Psenak, P., Gredler, H., Shakir, R., Henderickx, W., | Psenak, P., Gredler, H., rjs@rob.sh, r., Henderickx, W., | |||
| Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute | Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute | |||
| Advertisement", draft-ietf-ospf-prefix-link-attr-04 (work | Advertisement", draft-ietf-ospf-prefix-link-attr-13 (work | |||
| in progress), April 2015. | in progress), August 2015. | |||
| [I-D.wijnands-bier-architecture] | [I-D.wijnands-bier-architecture] | |||
| Wijnands, I., Rosen, E., Dolganow, A., and T. Przygienda, | Wijnands, I., Rosen, E., Dolganow, A., and T. Przygienda, | |||
| "Multicast using Bit Index Explicit Replication", draft- | "Multicast using Bit Index Explicit Replication", draft- | |||
| wijnands-bier-architecture-00 (work in progress), | wijnands-bier-architecture-00 (work in progress), | |||
| September 2014. | September 2014. | |||
| [I-D.wijnands-mpls-bier-encapsulation] | [I-D.wijnands-mpls-bier-encapsulation] | |||
| Wijnands, I., Rosen, E., Dolganow, A., and J. Tantsura, | Wijnands, I., Rosen, E., Dolganow, A., and J. Tantsura, | |||
| "Encapsulation for Bit Index Explicit Replication in MPLS | "Encapsulation for Bit Index Explicit Replication in MPLS | |||
| Networks", draft-wijnands-mpls-bier-encapsulation-00 (work | Networks", draft-wijnands-mpls-bier-encapsulation-00 (work | |||
| in progress), September 2014. | in progress), September 2014. | |||
| [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>. | ||||
| [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. | |||
| Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", RFC | Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", | |||
| 4915, June 2007. | RFC 4915, DOI 10.17487/RFC4915, June 2007, | |||
| <http://www.rfc-editor.org/info/rfc4915>. | ||||
| Authors' Addresses | Authors' Addresses | |||
| Peter Psenak (editor) | Peter Psenak (editor) | |||
| Cisco | Cisco | |||
| Apollo Business Center | Apollo Business Center | |||
| Mlynske nivy 43 | Mlynske nivy 43 | |||
| Bratislava 821 09 | Bratislava 821 09 | |||
| Slovakia | Slovakia | |||
| End of changes. 8 change blocks. | ||||
| 10 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||