> On 7/26/16 12:08 PM, Dino Farinacci wrote: >>> Having VXLAN as an Independent Stream RFC gives a document to be used to >>> innovate from. I believe that was the intent of VXLAN-GPE - to provide >>> the ability >>> for needed extensions. >> The only new feature the VXLAN-GPE brings to the table is a way to identify >> that NSH is being encapsulated. > > or any other shim header, NSH just happens to be one.
Which will require a hardware change. Since “another” isn’t specific yet, we don’t know if it is a bug or a feature. ;-) Dino > > Fabio > >> All other flexibility features can be implemented in the options Michael >> outlined. >> >> Dino >> >> _______________________________________________ >> nvo3 mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/nvo3 > > > _______________________________________________ > nvo3 mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/nvo3 _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
