<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.altanai-moq-relay-geocode" target="https://datatracker.ietf.org/doc/html/draft-altanai-moq-relay-geocode-01">
   <front>
      <title>Geographic Location for Media over QUIC Relays</title>
      <author initials="A." surname="Bisht" fullname="Altanai Bisht">
         <organization>Cisco Meraki</organization>
      </author>
      <author initials="T." surname="Evens" fullname="Tim Evens">
         <organization>Cisco</organization>
      </author>
      <date month="July" day="24" year="2026" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-altanai-moq-relay-geocode-01" />
   
</reference>
