draft-ietf-bier-isis-extensions-10.txt   draft-ietf-bier-isis-extensions-11.txt 
Internet Engineering Task Force L. Ginsberg, Ed. Internet Engineering Task Force L. Ginsberg, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track A. Przygienda Intended status: Standards Track A. Przygienda
Expires: September 12, 2018 Juniper Networks Expires: October 1, 2018 Juniper Networks
S. Aldrin S. Aldrin
Google Google
J. Zhang J. Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
March 11, 2018 March 30, 2018
BIER support via ISIS BIER support via ISIS
draft-ietf-bier-isis-extensions-10 draft-ietf-bier-isis-extensions-11
Abstract Abstract
This document defines ISIS extensions to support multicast forwarding This document defines ISIS extensions to support multicast forwarding
using the Bit Index Explicit Replication (BIER) architecture. using the Bit Index Explicit Replication (BIER) architecture.
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", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 September 12, 2018. This Internet-Draft will expire on October 1, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 38 skipping to change at page 2, line 38
5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Multi Topology and Sub-Domain . . . . . . . . . . . . . . 5 5.1. Multi Topology and Sub-Domain . . . . . . . . . . . . . . 5
5.2. BFR-id Advertisements . . . . . . . . . . . . . . . . . . 6 5.2. BFR-id Advertisements . . . . . . . . . . . . . . . . . . 6
5.3. Logging Misconfiguration . . . . . . . . . . . . . . . . 6 5.3. Logging Misconfiguration . . . . . . . . . . . . . . . . 6
5.4. Flooding Reduction . . . . . . . . . . . . . . . . . . . 6 5.4. Flooding Reduction . . . . . . . . . . . . . . . . . . . 6
6. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 6 6. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. BIER Info sub-TLV . . . . . . . . . . . . . . . . . . . . 7 6.1. BIER Info sub-TLV . . . . . . . . . . . . . . . . . . . . 7
6.2. BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . . 8 6.2. BIER MPLS Encapsulation sub-sub-TLV . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 9 9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 10 9.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Bit Index Explicit Replication (BIER) [RFC8279] defines an Bit Index Explicit Replication (BIER) [RFC8279] defines an
architecture where all intended multicast receivers are encoded as architecture where all intended multicast receivers are encoded as
bitmask in the Multicast packet header within different bitmask in the Multicast packet header within different
encapsulations such as [RFC8296]. A router that receives such a encapsulations such as [RFC8296]. A router that receives such a
packet will forward the packet based on the Bit Position in the packet will forward the packet based on the Bit Position in the
packet header towards the receiver(s), following a precomputed tree packet header towards the receiver(s), following a precomputed tree
skipping to change at page 9, line 11 skipping to change at page 9, line 11
Local BitString Length (BS Len): Encoded bitstring length as per Local BitString Length (BS Len): Encoded bitstring length as per
[RFC8296]. 4 bits. [RFC8296]. 4 bits.
Label: First label of the range, 20 bits. The labels are as defined Label: First label of the range, 20 bits. The labels are as defined
in [RFC8296]. in [RFC8296].
7. Security Considerations 7. Security Considerations
Security concerns for IS-IS are addressed in [RFC5304] and [RFC5310]. Security concerns for IS-IS are addressed in [RFC5304] and [RFC5310].
Advertisement of the additional information defined in this document
introduces no new security concerns.
BIER specific security considerations are discussed in [RFC8279]. The Security Considerations section of [RFC8279] discusses the
possibility of performing a Denial of Service (DoS) attack by setting
too many bits in the BitString of a BIER-encapsulated packet.
However, this sort of DoS attack cannot be initiated by modifying the
ISIS BIER advertisements specified in this document. A BFIR decides
which systems are to receive a BIER-encapsulated packet. In making
this decision, it is not influenced by the ISIS control messages.
When creating the encapsulation, the BFIR sets one bit in the
encapsulation for each destination system. The information in the
ISIS BIER advertisements is used to construct the forwarding tables
that map each bit in the encapsulation into a set of next hops for
the host that is identified by that bit, but is not used by the BFIR
to decide which bits to set. Hence an attack on the ISIS control
plane cannot be used to cause this sort of DoS attack.
While a BIER-encapsulated packet is traversing the network, a BFR
that receives a BIER-encapsulated packet with n bits set in its
BitString may have to replicate the packet and forward multiple
copies. However, a given bit will only be set in one copy of the
packet. That means that each transmitted replica of a received
packet has fewer bits set (i.e., is targeted to fewer destinations)
than the received packet. This is an essential property of the BIER
forwarding process as defined in [RFC8279]. While a failure of this
process might cause a DoS attack (as discussed in the Security
Considerations of [RFC8279]), such a failure cannot be caused by an
attack on the ISIS control plane.
Further discussion of BIER specific security considerations can be
found in [RFC8279].
8. Acknowledgements 8. Acknowledgements
The RFC is aligned with the The RFC is aligned with the [I-D.ietf-bier-ospf-bier-extensions]
[I-D.draft-ietf-bier-ospf-bier-extensions-15] draft as far as the draft as far as the protocol mechanisms overlap.
protocol mechanisms overlap.
Many thanks for comments from (in no particular order) Hannes Many thanks for comments from (in no particular order) Hannes
Gredler, Ijsbrand Wijnands, Peter Psenak and Chris Bowers. Gredler, Ijsbrand Wijnands, Peter Psenak and Chris Bowers.
Special thanks to Eric Rosen.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, DOI 10.17487/RFC1195, dual environments", RFC 1195, DOI 10.17487/RFC1195,
December 1990, <https://www.rfc-editor.org/info/rfc1195>. December 1990, <https://www.rfc-editor.org/info/rfc1195>.
[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,
skipping to change at page 10, line 27 skipping to change at page 11, line 9
[RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and
U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4
and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794,
March 2016, <https://www.rfc-editor.org/info/rfc7794>. March 2016, <https://www.rfc-editor.org/info/rfc7794>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References
[I-D.draft-ietf-bier-ospf-bier-extensions-15]
Psenak et al., P., "OSPF Extension for Bit Index Explicit
Replication", internet-draft draft-ietf-bier-ospf-bier-
extensions-15, February 2018.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Przygienda, T., and S. Aldrin, "Multicast Using Bit Index Przygienda, T., and S. Aldrin, "Multicast Using Bit Index
Explicit Replication (BIER)", RFC 8279, Explicit Replication (BIER)", RFC 8279,
DOI 10.17487/RFC8279, November 2017, DOI 10.17487/RFC8279, November 2017,
<https://www.rfc-editor.org/info/rfc8279>. <https://www.rfc-editor.org/info/rfc8279>.
[RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A.,
Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation
for Bit Index Explicit Replication (BIER) in MPLS and Non- for Bit Index Explicit Replication (BIER) in MPLS and Non-
MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January
2018, <https://www.rfc-editor.org/info/rfc8296>. 2018, <https://www.rfc-editor.org/info/rfc8296>.
9.2. Informative References
[I-D.ietf-bier-ospf-bier-extensions]
Psenak, P., Kumar, N., Wijnands, I., Dolganow, A.,
Przygienda, T., Zhang, Z., and S. Aldrin, "OSPFv2
Extensions for BIER", draft-ietf-bier-ospf-bier-
extensions-16 (work in progress), March 2018.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
Authors' Addresses Authors' Addresses
Les Ginsberg (editor) Les Ginsberg (editor)
Cisco Systems Cisco Systems
510 McCarthy Blvd. 510 McCarthy Blvd.
Milpitas, CA 95035 Milpitas, CA 95035
USA USA
Email: ginsberg@cisco.com Email: ginsberg@cisco.com
 End of changes. 11 change blocks. 
25 lines changed or deleted 53 lines changed or added

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