Dale,
On 7/21/2017 7:15 PM, Dale R. Worley wrote: > When layer 4 is used over Geneve, things are more complicated, because > there's no defined way of representing an IP protocol/next header value > directly as an Ethertype, and few or no protocols that can be > represented as such a value have assigned Ethertypes. That is a good thing, IMO. > It seems to me that it would be useful to embed the IP protocol/next > header value space into the Ethertype space by allocating a block of 256 > Ethertypes, xx00 to xxFF, to IANA, to represent the protocol/next header > values. This is a large allocation, but the Ethertype space is thinly > allocated and ony 60 or so of the possible first-byte values are used, > leaving over 150 choices to allocate. I disagree. As with most codepoints, if you want ONE (e.g., for Geneve as the next protocol after ethernet) then maybe. If you want more, then IMO absolutely not. Joe _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
