@techreport{ubillos-name-based-sockets-03,
    number =    {draft-ubillos-name-based-sockets-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ubillos-name-based-sockets/03/},
    author =    {Javier Ubillos and Mingwei Xu and Zhongxing Ming and Christian Vogt},
    title =     {{Name-Based Sockets Architecture}},
    pagetotal = 10,
    year =      2010,
    month =     sep,
    day =       17,
    abstract =  {This memo defines Name-based sockets. name-based sockets allow application developers to refer to remote hosts (and it self) by name only, passing on all IP (locator) management to the operating system. Applications are thus relieved of re-implementing features such as multi-homing, mobility, NAT traversal, IPv6/IPv4 interoperability and address management in general. The operating system can in turn re- use the same solutions for a whole set of guest applications. name- based sockets aims to provide a whole set of features without adding new indirection layers, new delays or other dependences while maintaining transparent backwards compatibility.},
}