[Idr] Validation for BGP Flow-Spec Redirect to IP Action

[PVLR Pavana Murthy <[e-mail]>]

Hello,
  In the draft  draft-ietf-idr-flowspec-redirect-ip-02.txt, the following
procedure is mentioned to validate the extended community of 'Flowspec
redirect to IP'.

   BGP speakers that support the extended communities defined in this
   draft MUST also, by default, enforce the following check when
   receiving a flow-spec route from an EBGP peer: if the received flow-

   spec route has a 'redirect to IP' extended community with a 'target
   address' X (in the global administrator field) and the best matching
   route to X is not a BGP route with *origin AS* matching the peer AS
   then the extended community should be discarded and not propagated
   along with the flow-spec route to other peers.


*I have 2 doubts related to this statement.*


*What is 'origin AS' here? Is it the AS no. that is first added to the
AS_PATH? *
*In the previous version of the draft its mentioned as the last AS in
the AS_PATH.*
*Is it the last AS no. that has been added to the AS_PATH or the last
AS no. from left in AS_PATH? *


*What if the redirect target X is directly connected or reachable by a
static route and its not advertised by EBGP?*

*Do we need to consider that action invalid in that case?*



Thanks,

Pavana.