Hi, Jeff,
Carlos,
This packet loop may not be practical for several encapsulations and thus is
out of scope for such encapsulations. Whether this is practical for vxlan
today, or in the presence of future extensions to vxlan is left out of scope
for the core proposal.
The question remains: for VXLAN encapsulation, this is like a single hop as far as BFD is concerned (single hop VXLAN tunnel).
Since RFC 5881 defines Echo for single hop, can you please elaborate (in the document) why is out of scope or how it can work?
While my suspicion was that vxlan was quite happy to be able to do BFD Echo in the presence of appropriate forwarding machinery, it's still okay for this document to specify only async mode BFD in the vxlan environment.
I suspected as much as well, but...
If you think it's practical to describe such an environment in a reasonable amount of text in the base proposal, it could be incorporated in that document.
…I did not want to assume, and I was simply asking why it was marked out-of-scope; whether that was a deliberate and intentional decision based on technical or code availability reasons, or removing sections just to get the doc out.
Either way is fine — I was asking the rationale for it. Maybe echo as per RFC 5881 would work.
Best,
Carlos.
|
