I confess that I have only skimmed this thread, but as far as I can see no one has mentioned OAM. If we are designing a general purpose encapsulation there really needs to be an OAM indicator so that OAM can fate share with the data that it is monitoring.
I don't think it is a factor in this discussion unless people think that we will be doing super DPI, but RFC4928 notes an issue when using the first nibble of a packet as a type identifier in an IP/MPLS environment. In a nutshell this says avoid 0 and 1 as well as 4 and 6. - Stewart _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
