You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A given network flow's 5-tuple will differ depending on whether it's perceived internally, externally, before or after a NAT, etc. Can the Community ID accommodate this?
The short answer is no, since there's an assumption that the ID is based on the observed flow tuple, so presence of a NAT will make a semantically identical flow look like two different ones. However, this relates to #4 in that the ID could be based on other flow properties such as QUIC's connection ID.
This was a talk discussion question at SuriCon 2018.
The text was updated successfully, but these errors were encountered:
A given network flow's 5-tuple will differ depending on whether it's perceived internally, externally, before or after a NAT, etc. Can the Community ID accommodate this?
The short answer is no, since there's an assumption that the ID is based on the observed flow tuple, so presence of a NAT will make a semantically identical flow look like two different ones. However, this relates to #4 in that the ID could be based on other flow properties such as QUIC's connection ID.
This was a talk discussion question at SuriCon 2018.
The text was updated successfully, but these errors were encountered: