%% You should probably cite draft-ietf-nvo3-encap-12 instead of this revision.
@techreport{ietf-nvo3-encap-08,
    number =    {draft-ietf-nvo3-encap-08},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-nvo3-encap/08/},
    author =    {Sami Boutros and Donald E. Eastlake 3rd},
    title =     {{Network Virtualization Overlays (NVO3) Encapsulation Considerations}},
    pagetotal = 28,
    year =      2022,
    month =     apr,
    day =       1,
    abstract =  {The IETF Network Virtualization Overlays (NVO3) Working Group Chairs and Routing Area Director chartered a design team to take forward the encapsulation discussion and see if there was potential to design a common encapsulation that addresses the various technical concerns. There are implications of having different encapsulations in real environments consisting of both software and hardware implementations and within and spanning multiple data centers. For example, OAM functions such as path MTU discovery become challenging with multiple encapsulations along the data path. The design team recommended Geneve with a few modifications as the common encapsulation. This document provides more details, particularly in Section 7.},
}