%% You should probably cite draft-ietf-ecrit-rough-loc-05 instead of this revision.
@techreport{ietf-ecrit-rough-loc-04,
    number =    {draft-ietf-ecrit-rough-loc-04},
    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-ecrit-rough-loc/04/},
    author =    {Richard Barnes and Matt Lepinski},
    title =     {{Using Imprecise Location for Emergency Context Resolution}},
    pagetotal = 18,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {Emergency calling works best when precise location is available for emergency call routing. However, there are situations in which a location provider is unable or unwilling to provide precise location, yet still wishes to enable subscribers to make emergency calls. This document describes the level of location accuracy that providers must provide to enable emergency call routing. In addition, we descibe how emergency services and non-emergency services can be invoked by an endpoint that does not have access to its precise location.},
}