Home | History | Annotate | Download | only in doc

Lines Matching refs:By

42 \item To assign flow labels to packets sent by user.
58 hop by hop options and all the headers up to and including routing header,
62 There is a hole in specs: some hop-by-hop options can be
77 the label is taken over by another flow.
79 by some application specific methods
80 (f.e.\ in RSVP PATH messages or in some hop-by-hop option).
115 is followed by attempts to patch the hole and more mistakes...
135 By default Linux IPv6 does not read \verb|sin6_flowinfo| field
160 Flowinfo received and latched by a connected TCP socket also may be fetched
289 to lease flow label ordered by user. In this case, it is user task to provide
315 #define IPV6_FL_S_PROCESS 2 /* May be reused by this process */
316 #define IPV6_FL_S_USER 3 /* May be reused by this user */
323 still can be shared by another sockets. Current implementation does not allow
336 This structure is followed by optional extension headers associated