Subject: [Idr] Questions to draft-ietf-idr-flowspec-path-redirect-11

From: Linda Dunbar <[email-masked]>
Date: Fri, 25 Jun 2021 20:36:59 +0000

Gunter, Keyur, Zhenbin,

The term "flowspec client" is used in multiple places of the document, which seems to refer to the router that receives the "flowspec" requests, correct?

But the term "Client" usually refers to the entity that makes the requests, which should be the one issuing the "flowspec". Is it possible to use another term?  Such as  "flowspec receiving router"  or "flowspec target router", etc.

Page 4: Section 3.1 Requirement:

  *   the first bullet:  0 (localized ID) is to use a localized Indirection-id table. Can the node  have multiple  "localized Indirection-id table"?
  *   the second bullet: 1 or 2 (Node ID's): what does Node ID here mean? What is "1" for? "2" for? Respectively?

Page 5: the three bullets under the Example: what is the difference between "ID-Type=0 (localized ID)" and "ID-Type =5 (Tunnel ID)? The description is the same: "use the 32-but Indirection-id as global anchor point on the local flowspec client".

Page 5: Section 3.3: does the "sequence ID (S-ID)" represent the priority of the multiple flowspec rules received?

Page 6: First paragraph: is the "pre-identified interface/peer" represented by the second "Redirect to indirection-id" locally significant on the egress node?

Page 8: Section 6: is it too much risk allowing any eBGP peers that advertise the best path for the matching unicast route? Maybe only allowing authorized eBGP peers?

Thank you,

Linda Dunbar