Lines Matching defs:flow
22 Every IPv6 packet carries 28 bits of flow information. RFC2460 splits
24 prefer this term) and 20 bits of flow label. Currently there exist
25 no well-defined API to manage IPv6 flow information. In this document
42 \item To assign flow labels to packets sent by user.
44 \item To get flow labels of received packets. I do not know
46 want to use flow labels to distinguish sub-flows.
48 \item To allocate flow labels in the way, compliant to RFC2460. Namely:
56 Flows with coinciding source address and flow label must have identical
65 with flow labels.
75 flow label for another flow within the maximal lifetime has expired,
76 so that intermediate nodes will be able to invalidate flow state before
77 the label is taken over by another flow.
87 \section{Sending/receiving flow information.}
106 if \verb|recvmsg()| initializes \verb|sin6_flowinfo| to flow info
120 support flow labels, this field is not zero, but a random number.
149 message to user space, though the kernels which support flow labels
170 If \verb|sin6_flowinfo| does contain not zero flow label,
173 cached at flow setup (see below). However, for connected sockets
224 storage, so that the full implementation necessarily includes user space flow
228 \item {\bf ``Cooperative''. } We could leave flow label allocation wholly
233 One idea is to disallow not privileged user to allocate flow
250 flow label space.
255 for implementor (i.e.\ me), and taking into account that flow labels
264 request flow label manager to allocate new flow label, to reuse
265 already allocated one or to delete old flow label.
287 \item \verb|label| is flow label value in network byte order. If it is zero,
289 to lease flow label ordered by user. In this case, it is user task to provide
290 necessary flow label randomness.
296 #define IPV6_FL_A_GET 0 /* Get flow label */
297 #define IPV6_FL_A_PUT 1 /* Release flow label */
310 \item \verb|share| defines who is allowed to reuse the same flow label.
320 \item \verb|linger| is time in seconds. After the last user releases flow
332 application allocates new flow.
337 with this flow label in format of \verb|IPV6_PKTOPTIONS|. Only
344 private flow label.
382 \paragraph{Listing flow labels.}
383 \addcontentsline{toc}{subsection}{Listing flow labels}
385 flow labels may be read from \verb|/proc/net/ip6_flowlabel|.
393 \item \verb|Label| is hexadecimal flow label value.
409 RSVP daemon supports IPv6 flow labels
411 flow label, fill corresponding sender template and submit it to local rsvp
413 messages. Rsvpd on sender node will renew the flow label, so that it will not
415 routers and receiver purge flow state.
417 \verb|rtap| utility is modified to parse flow labels. F.e.\ if user allocated
418 flow label \verb|0xA1234|, he may write: