I vote for a semantics where you have MPLS or intserv style semantics and I
would also like a bit telling if the packet is encrypted or not.
[EMAIL PROTECTED]
-PS: Intserv is not 100% dead because there is an environment (wireless)
-where to get more bandwidth is really expensive (in Europe at least :-).
-PPS: there is another usage: flow-based switching for fast routing
-but I don't believe this really helps (petabit router vendors?)
--> No there is no need in term of a flow based switching fast routing since
the memory where you store the routing tables are so huge today. 512 K IPv4
prefixes could be stored in one CAM memory and usually you can use several
to obtain larger tables - all the CAM vendors support between 1 - 4 M IPv4
prefixes to be stored in their CAM and do one look up in a clock cycle.
But many people are using flow to do traffic engneering and that's where I
belive the "mpls" op by hop semantic is needed. for the flow label. It would
also be easier to signal up to the routing protocls like IS-IS, OSPF. BGP
etc when a change occured.
-- thomas
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
