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
For DetNet IP flow identification the IP 6-tuple is used, which consists of SourceIpAddress, DestinationIpAddress, Dscp, Protocol, SourcePort, and DestinationPort, that is, there is no a kind of Flow ID carried for Detnet, but only the 6-tuple is directly used to identify the Detnet flows. While APN uses the APN ID to differentiate the traffic flows. APN can be used together with Detnet, that is, the APN ID is used to steer the traffic into a corresponding Detnet path which can guarantee latency boundary.
The text was updated successfully, but these errors were encountered:
A new subsection on Detnet has been added to the gap analysis draft to especially clarify on the differences between Detnet and APN, https://datatracker.ietf.org/doc/html/draft-peng-apn-scope-gap-analysis-03#section-6.7.
For DetNet IP flow identification the IP 6-tuple is used, which consists of SourceIpAddress, DestinationIpAddress, Dscp, Protocol, SourcePort, and DestinationPort, that is, there is no a kind of Flow ID carried for Detnet, but only the 6-tuple is directly used to identify the Detnet flows. While APN uses the APN ID to differentiate the traffic flows. APN can be used together with Detnet, that is, the APN ID is used to steer the traffic into a corresponding Detnet path which can guarantee latency boundary.
The text was updated successfully, but these errors were encountered: