> > 5. Patch for ITEM7: TCS currently have no plans to design
> and implement this.
> >
>
> (Datagram labeling)
>
> I guess we'd probably use SCM_SECURITY for this (similar to
> IP_CMSG_PASSEC for receiving the label).
Seems like a logical way to do it.
>
> Is this enough support for user API support at the kernel
> level in terms
> of setting and getting labels?
Actually I missed mentioning the following under User API:
4. iptables contexts
a. Specify labels with iptables rules.
Can't think of anything else being needed at this point in time.
Also, for the sake of the discussion, one "requirement" that some
may have is "Label-based routing", which would basically be a
polyinstantiated routing table. This is something TCS is currently
not interested in pursuing.
So, under USER REQUIREMENTS:
4. Routing support
a. provision for a label-based routing mechanism (aka
polyinstantiated
routing table).
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
