%% You should probably cite draft-iannone-ip-addressing-considerations instead of this I-D.
@techreport{iannone-scenarios-problems-addressing-00,
    number =    {draft-iannone-scenarios-problems-addressing-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-iannone-scenarios-problems-addressing/00/},
    author =    {Luigi Iannone and Dirk Trossen and Nirmala Shenoy and Paulo Mendes and Donald E. Eastlake 3rd and Peng Liu and Dino Farinacci and Jens Finkhäuser and Yihao Jia},
    title =     {{Challenging Scenarios and Problems in Internet Addressing}},
    pagetotal = 38,
    year =      2022,
    month =     sep,
    day =       5,
    abstract =  {The Internet Protocol (IP) has been the major technological success in information technology of the last half century. As the Internet becomes pervasive, IP has been replacing communication technology for many domain-specific solutions. However, domains with specific requirements as well as communication behaviors and semantics still exist and represent what {[}RFC8799{]} recognizes as "limited domains". This document describes well-recognized scenarios that showcase possibly different addressing requirements, which are challenging to be accommodated in the IP addressing model. These scenarios highlight issues related to the Internet addressing model and call for starting a discussion on a way to re-think/evolve the addressing model so to better accommodate different domain-specific requirements. The limitations identified in this document are complemented and deepened by a detailed analysis in a separate companion document {[}I-D.iannone-internet-addressing-considerations{]}.},
}