%% You should probably cite draft-brw-scone-rate-policy-discovery-01 instead of this revision.
@techreport{brw-scone-rate-policy-discovery-00,
    number =    {draft-brw-scone-rate-policy-discovery-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-brw-scone-rate-policy-discovery/00/},
    author =    {Mohamed Boucadair and Dan Wing and Tirumaleswar Reddy.K and Sridharan Rajagopalan and Gyan Mishra and Markus Amend and Luis M. Contreras},
    title =     {{Discovery of Network Rate-Limit Policies (NRLPs)}},
    pagetotal = 39,
    year =      2024,
    month =     oct,
    day =       8,
    abstract =  {Traffic exchanged over a network attachment may be subject to rate- limit policies. These policies may be intentional policies (e.g., enforced as part of the activation of the network attachment and typically agreed upon service subscription) or be reactive policies (e.g., enforced temporarily to manage an overload or during a DDoS attack mitigation). This document specifies a mechanims for hosts to dynamically discover Network Rate-Limit Policies (NRLPs). This information is then passed to applicaitons that might adjust their behaviors accordingly. Networks already support mechanisms to advertize a set of network properties to hosts using Neighbor Discovery options. Examples of such properties are link MTU (RFC 4861) and PREFIX64 (RFC 8781). This document complements these tools and specifies a Neighbor Discovery option to be used in Router Advertisements (RAs) to communicate these policies to hosts. For address family parity, a new DHCP option is also defined. The document also discusses how Provisioning Domains (PvD) can be used to notify hosts with NRLPs.},
}