Subject: [Idr] Progressing draft-litkowski-idr-flowspec-interfaceset-01

From: <[email-masked]>
Date: Mon, 3 Aug 2015 12:43:42 +0000

Hi,

In Dallas, we presented an update of draft-litkowski-idr-flowspec-interfaceset which allow to push flowspec rules to a specific set of interfaces identified by a group ID.
We took into account the comment we had in Toronto but there was no new comment. Last discussion was about putting the interface group within the NLRI which is causing some issue, especially for interAS, so keeping it as community looks better even if we need to use ADDPATH in some specific cases.

I would like to restart the discussion on this draft.

Do you think the technical proposal is right ?
Do you think that the group ID space is large enough ?

One concern I have (not a big one), is that all routers will receive all the flowspec routes even if they do not need it. I would be good to reuse some RT based solution (and RT filtering), but RT may conflict with Flowspec VPN, so special care are required, and I would like to hear from implementors about having RTs identifying VPNs and RTs identifying interfaces groups on the same route.

Do we need to enlarge the application of this mechanism to a "SDN" API, like Openflow ? Programming flows on a specific node, or specific group of node.

Brgds,

Stephane

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.