@misc{internet_society_2018,
 title={State of IPv6 Deployment 2018},
 url={https://www.internetsociety.org/resources/2018/state-of-ipv6-deployment-2018/},
 journal={Internet Society},
 publisher={Internet Society},
 year={2018},
 month={Jun}
} 

@misc{cohen_1980,
 title={ON HOLY WARS AND A PLEA FOR PEACE},
 url={https://www.ietf.org/rfc/ien/ien137.txt},
 journal={IETF},
 publisher={IETF},
 author={Cohen, Danny},
 year={1980},
 month={Apr}
} 

@techreport{RFC1700,
  author = {J. Reynolds and J. Postel},
  title = {Assigned Numbers},
  howpublished = {Internet Requests for Comments},
  type = {RFC},
  number = {1700},
  year = {1994},
  month = {October},
  issn = {2070-1721},
  publisher = {RFC Editor},
  institution = {RFC Editor},
}

@misc{rfc7231,
    series =    {Request for Comments},
    number =    7231,
    howpublished =  {RFC 7231},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC7231},
    url =       {https://rfc-editor.org/rfc/rfc7231.txt},
        author =    {Roy T. Fielding and Julian Reschke},
    title =     {{Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content}},
    pagetotal = 101,
    year =      2014,
    month =     jun,
    abstract =  {The Hypertext Transfer Protocol (HTTP) is a stateless \textbackslash{}\%application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.},
}

@misc{rfc768,
    series =    {Request for Comments},
    number =    768,
    howpublished =  {RFC 768},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC0768},
    url =       {https://rfc-editor.org/rfc/rfc768.txt},
        author =    {},
    title =     {{User Datagram Protocol}},
    pagetotal = 3,
    year =      1980,
    month =     aug,
    abstract =  {},
}
