flow
Click on the red underlined text to get to the source
... The modeling of IP traffic as 'flows', and optionally using the
existence of a flow as the basis for attempting to set up a
...
... IP traffic as 'flows', and optionally using the
existence of a flow as the basis for attempting to set up a
shortcut link level connection ...
... Link is responsible for detecting the existence of an IP packet
flow through it that might benefit from a shortcut connection.
...
... router then issues a Redirect to the IP
source, identifying the flow's destination as a transient
Neighbor ...
... Host-initiated triggering of shortcut discovery, regardless of the
existence of a packet flow, is also supported through specific
Neighbor Solicitations sent to a source host ...
... address will be the one chosen by the
destination when the flow was originally established through hop-
by-hop processing. This supports the existing ND ability for IPv6 ...
... Link. Appendix C
discusses shortcut suppression and briefly reviews the future
relationships between flow detection and mapping of flows onto SVCs
of differing qualities of service ...
... discusses shortcut suppression and briefly reviews the future
relationships between flow detection and mapping of flows onto SVCs
of differing qualities of service.
...
... Shortcut connections are justified on the grounds that demanding
flows of IP packets may exist between source/destination pairs that
...
...
Section 3.2.1 discusses flow-based triggers, section 3.2.2 discusses
the host initiated trigger, and section 3.2.3 discusses the use of
...
... Flow Triggered Redirection. ...
... The modification of forwarding paths based on the dynamic detection
of IP packet flows is at the core of models such as the Cell Switch
Router ...
... Switch [12]. Responsibility for detecting
flows is placed into the routers, where packets cross the edges of IP
routing ...
... router MAY
choose to initiate the discovery of a better first-hop when it
determines that an identifiable flow of IP packets are passing
through it.
...
... SHALL only consider IPv6 packets with FlowID of zero for the
purposes of flow detection as defined in this section.
...
... SHALL utilize NHRP as described in section 3.2.3 to ascertain a
better first-hop when a suitable flow is detected, and
advertise the information in a Router Redirect.
...
...
IPv6 routers that support the OPTIONAL flow detection behavior
described above SHALL support administrative mechanisms to switch off
...
... described above SHALL support administrative mechanisms to switch off
flow-detection. They MAY provide mechanisms for adding additional
constraints to the categories of IPv6 packets ...
... algorithm(s) for determining what sequence of IPv6 packets
constitute a 'flow' are outside the scope of this document. Appendix
C discusses the rationale behind the use of non-zero FlowID to
...
... Include the shortcut limit option defined in appendix D. The value
of this option should be equal to the hop limit of the data flow
for which this trigger is being sent. This ensures that the router
...
... resulting answer. (Note, in the case where the NHRP Request
originated due to flow detection, there must already be a hop-by-hop
flow ...
... flow detection, there must already be a hop-by-hop
flow of packets going through the last hop router towards the target ...
...
If the discovery process was triggered through flow detection at the
originating router, the return of the NHRP ...
... flow's source (using the
VC on which the flow is arriving at the router, if it is a bi-
directional pt-pt VC ...
... target host when the target host first
accepted the flow of IP traffic. This retains a useful feature of
Neighbor Discovery ...
... NHRP NAK reply or error indication for a flow-
triggered shortcut attempt, no indication is sent to the source of
the flow ...
...
When constructing a NHRP resolution request as a result of flow
detection, the choice of values is configuration dependent.
...
... NBMA level paths are supported either through router based
flow detection, or host originated explicit requests. Neighbor
Discovery is used without modification for all intra-LL control
...
... Multicast Server
tradeoff. Typically a multicast server aggregates traffic flow to a
common multicast group onto a single VC ...
... Appendix C. Flow detection ...
...
The relationship between IPv6 packet flows, Quality of Service
guarantees, and optimal use of underlying IP ...
... IPNG, and ION working groups). This
document currently only describes the use of flow detection as a
means to optimize the use of NBMA network ...
... IPv6 packets that the first hop router is
allowed to perform flow-detection on for the purposes of
triggering shortcut discovery.
...
...
The flow-detection rule specifies that only packets with a zero
FlowID can be considered as flows for which shortcut discovery may be
...
... The flow-detection rule specifies that only packets with a zero
FlowID can be considered as flows for which shortcut discovery may be
triggered. The rationale behind this decision is:
...
... The IPv6 semantics of zero FlowID are consistent with the flow-
detection rule in this document of "if the FlowID is zero, we are
free to optimize the forwarding path using shortcuts"
...
... semantics of non-zero FlowID are consistent with the
flow-detection rule in this document of "if the FlowID is non-
zero, do not attempt to impose a shortcut".
...
... Zero FlowID
Best effort forwarding, with optional shortcut discovery
triggered through flow-detection.
Non-zero ...
... processing rules for
this FlowID/source-address pair. Flow detection relating to
shortcut discovery is suspended.
...
... processing rules for this FlowID/source-address pair,
the flow is handled according to those rules. Flow detection
relating to shortcut discovery is suspended.
...
... address pair,
the flow is handled according to those rules. Flow detection
relating to shortcut discovery is suspended.
...
... C.2. Future directions for Flow Detection ...
... QoS on IPv6 unicast flows will not require further
extensions to the existing MARS protocol. However, future support for
...
... QoS on IPv6 multicast flows may require extensions. MARS control
messages share the same TLV ...
... NS messages sent as a shortcut trigger, a new type of ND option
is needed to pass on the information about the data flow hop limit
from the host ...