%% You should probably cite draft-altanai-moq-relay-geocode-02 instead of this revision.
@techreport{altanai-moq-relay-geocode-01,
    number =    {draft-altanai-moq-relay-geocode-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-altanai-moq-relay-geocode/01/},
    author =    {Altanai Bisht and Tim Evens},
    title =     {{Geographic Location for Media over QUIC Relays}},
    pagetotal = 12,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document defines a mechanism for Media over QUIC (MoQ) relays to advertise their geographic location (geocode) and related path metrics. Some clients require their media data to remain locally or geo-fenced within specific jurisdictions for privacy and security compliance (e.g., GDPR, HIPAA, or sector-specific regulations). This mechanism enables service providers to track the geographic path of media packets through the relay mesh and to enforce geo-fencing policies. It supports Geo-Distributed Orchestration and Routing (GDOR), data residency compliance, latency optimization, and relay selection. The specification includes optional IATA airport codes as human-readable geographic identifiers for major relay locations.},
}