Internet-Draft Indirection-id Redirect for SRv6 July 2022
Van de Velde, et al. Expires 12 January 2023 [Page]
IDR Working Group
Intended Status:
Standards Track
G. Van de Velde
K. Patel
Z. Li
Huawei Technologies
H. Chen

Flowspec Indirection-id Redirect for SRv6


This document defines extensions to "FlowSpec Redirect to indirection-id Extended Community" for SRv6. This extended community can trigger advanced redirection capabilities to flowspec clients for SRv6. When activated, this flowspec extended community is used by a flowspec client to retrieve the corresponding next-hop and encoding information within a localised indirection-id mapping table.

The functionality detailed in this document allows a network controller to decouple the BGP flowspec redirection instruction from the operation of the available paths.

Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [2].

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 12 January 2023.

Table of Contents

1. Introduction

"FlowSpec Redirect to indirection-id Extended Community" for IPv4 is defined in ietf-idr-flowspec-path-redirect [1]. This draft specifies extensions to this community for SRv6.

2. Redirect to indirection-id Community

This document defines a new sub-type value for SRv6 in "FlowSpec Redirect to indirection-id Extended Community". The format of this extended community with the new sub-type value is show below:

 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
| Type          |Sub-Type (TBD) | Flags(1 octet)|    ID-Type    |
|            Generalized indirection_id (16 octets)             |
~                                                               ~


Type: 1 octet, defined in ietf-idr-flowspec-path-redirect [1].

Sub-Type: 1 octet, its value (TBD) will be assigned by IANA.

Flags: Same as that defined in ietf-idr-flowspec-path-redirect [1].

ID-Type: 1 octet value. This draft defines following Context Types:

Generalized indirection_id: 128-bit identifier used as indirection_id

3. Security Considerations

A system using "Redirect to indirection-id" extended community can cause during the redirect mitigation of a DDoS attack overflow of traffic received by the mitigation infrastructure.

4. Acknowledgements

This document received valuable comments and input from IDR working group including Adam Simpson, Mustapha Aissaoui, Jan Mertens, Robert Raszuk, Jeff Haas, Susan Hares and Lucy Yong.

5. Contributor Addresses

Below is a list of other contributing authors in alphabetical order:

Arjun Sreekantiah
Cisco Systems
170 W. Tasman Drive
San Jose, CA  95134


Nan Wu
Huawei Technologies
Huawei Bld., No. 156 Beiquing Rd
Beijing  100095


Shunwan Zhuang
Huawei Technologies
Huawei Bld., No. 156 Beiquing Rd
Beijing  100095

Wim Henderickx


6. IANA Considerations

This document requests a new sub-type value under "FlowSpec Redirect to indirection-id Extended Community Sub-Type" registery.

 Value   Code                                            Reference
 0x01    Flowspec Redirect to 128-bit Path-id for SRv6   [RFC-To-Be]

7. References

7.1. Normative References

Velde, G. V. D., Patel, K., and Z. Li, "Flowspec Indirection-id Redirect", Work in Progress, Internet-Draft, draft-ietf-idr-flowspec-path-redirect-11, , <>.
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, , <>.
Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., and D. McPherson, "Dissemination of Flow Specification Rules", RFC 5575, DOI 10.17487/RFC5575, , <>.

7.2. Informative References

Uttaro, J., Filsfils, C., Alcaide, J., and P. Mohapatra, "Revised Validation Procedure for BGP Flow Specifications", .
Filsfils, C., Previdi, S., Aries, E., Ginsburg, D., and D. Afanasiev, "Segment Routing Centralized Egress Peer Engineering", .
Sreekantiah, A., Filsfils, C., Previdi, S., Sivabalan, S., Mattes, P., and S. Lin, "Segment Routing Traffic Engineering Policy using BGP", .
Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., Shakir, R., Bashandy, A., Horneffer, M., Henderickx, W., Tantsura, J., Crabbe, E., Milojevic, I., and S. Ytti, "Segment Routing Architecture", .
Sivabalan, S., Medved, M., Filsfils, C., Litkowski, S., Raszuk, R., Bashandy, A., Lopez, V., Tantsura, J., Henderickx, W., Hardwick, J., Milojevic, I., and S. Ytti, "PCEP Extensions for Segment Routing", .

Authors' Addresses

Gunter Van de Velde
Keyur Patel
United States of America
Zhenbin Li
Huawei Technologies
Huawei Bld., No. 156 Beiquing Rd
Huaimo Chen
Boston, MA,
United States of America