On 30 Oct 2012, at 20:22, Vince Fuller <[email protected]> wrote: > Hi Luigi- > > Same comments/concerns about the citations you offer here. Specifically: > >> May I suggest: >> >> http://biblio.info.ucl.ac.be/2007/415406.pdf > > want to make sure that this is a stable document to reference (i.e. it > will be around on that web site for many years to come) >
Bruno Quoitin, Luigi Iannone, Cédric de Launois, and Olivier Bonaventure. 2007. Evaluating the benefits of the locator/identifier separation. In Proceedings of 2nd ACM/IEEE international workshop on Mobility in the evolving internet architecture (MobiArch '07). ACM, New York, NY, USA, , Article 5 , 6 pages. DOI=10.1145/1366919.1366926 http://doi.acm.org/10.1145/1366919.1366926 >> You can cite: >> >> http://www.net.t-labs.tu-berlin.de/papers/IB-CCLIM-07.pdf Luigi Iannone and Olivier Bonaventure. 2007. On the cost of caching locator/ID mappings. InProceedings of the 2007 ACM CoNEXT conference (CoNEXT '07). ACM, New York, NY, USA, , Article 7 , 12 pages. DOI=10.1145/1364654.1364663 http://doi.acm.org/10.1145/1364654.1364663 >> http://www.net.t-labs.tu-berlin.de/papers/KIF-ADDITLCAWISKAI-11.pdf > Juhoon Kim, Luigi Iannone, and Anja Feldmann. 2011. A deep dive into the LISP cache and what ISPs should know about it. In Proceedings of the 10th international IFIP TC 6 conference on Networking - Volume Part I (NETWORKING'11), Jordi Domingo-Pascual, Pietro Manzoni, Ana Pont, Sergio Palazzo, and Caterina Scoglio (Eds.), Vol. Part I. Springer-Verlag, Berlin, Heidelberg, 367-378. > same comment as above. > >> On this point you can cite: >> >> http://www.computer.org/csdl/mags/ic/preprint/mic2012990288-abs.html > > This is the same reference you offered for "lisp-introduction-01". At a > minimum, that abstract needs to be re-written so that it makes sense. > Right now, it says: > > The Internet has been created for interconnecting few hundreds > networks, but is now close to one billion hosts, grouped in 40,000 > Autonomous Systems, using more than 400,000 prefixes. Such a situation > raises scalability issues that have driven both academia and industry > to review the current Internet Architecture in the light of the > Locator/Identifier Split paradigm. In particular, the Internet > Engineering Task Force (IETF) has adopted and is actively designing > and developing the Locator/ID Separation Protocol (LISP). However, > changing the routing and addressing architecture of the Internet in an > incrementally deployable manner Several constraints impact such a > design. We use LISP as reference to describe the different design > choices necessary to achieve deployability, which is the ultimate goal > of any new Future Internet architecture. Furthermore, we showcase > several alternate usages of LISP, which go beyond improving the > Internet scalability. > > I realize that you are not a native English speaker but this text, > especially the sentence fragment that begins "However, changing the > routing...", is so badly written as to be almost unreadable. > As you can see, IEEE website completely screwed up (also the strange characters in the title), the real abstract is The Internet has been created for interconnecting few hundreds networks, but is now close to one billion hosts, grouped in 40,000 Autonomous Systems, using more than 400,000 prefixes. Such situation raises scalability issues that have driven both academia and industry to review the current Internet architecture in the light of the Locator/Identifier Split paradigm. In particular, the Internet Engineering Task Force (IETF) has adopted and is actively designing and developing the Locator/ID Separation Protocol (LISP). However, changing the routing and addressing architecture of the Internet in an incrementally deployable manner imposes several constraints in the new design. For the sake of illustration, we use LISP as reference to describe the different design choices necessary to achieve deployability, which is the ultimate goal of any new Future Internet architecture. Furthermore, we showcase several alternate usages of LISP, which go beyond improving the Internet scalability. is that more readable? As I said in the previous mail, the reference is for a pre-print so we still have to wait to have the final reference. > I also reiterate my concern that a citation that points to this web page > 1) may not be stable and 2) is to an abstract for a document that one needs > to pay to download. > >> You can cite: >> >> http://www.net.t-labs.tu-berlin.de/papers/IB-CCLIM-07.pdf Luigi Iannone and Olivier Bonaventure. 2007. On the cost of caching locator/ID mappings. InProceedings of the 2007 ACM CoNEXT conference (CoNEXT '07). ACM, New York, NY, USA, , Article 7 , 12 pages. DOI=10.1145/1364654.1364663 http://doi.acm.org/10.1145/1364654.1364663 >> http://www.net.t-labs.tu-berlin.de/papers/KIF-ADDITLCAWISKAI-11.pdf > Juhoon Kim, Luigi Iannone, and Anja Feldmann. 2011. A deep dive into the LISP cache and what ISPs should know about it. In Proceedings of the 10th international IFIP TC 6 conference on Networking - Volume Part I (NETWORKING'11), Jordi Domingo-Pascual, Pietro Manzoni, Ana Pont, Sergio Palazzo, and Caterina Scoglio (Eds.), Vol. Part I. Springer-Verlag, Berlin, Heidelberg, 367-378. > same question/comment as my first regarding stability. > >> In this case this paper might be useful: >> >> http://inl.info.ucl.ac.be/system/files/Networking12-CRV.pdf > Damien Saucez, Juhoon Kim, Luigi Iannone, Olivier Bonaventure, and Clarence Filsfils. 2012. A local approach to fast failure recovery of LISP ingress tunnel routers. In Proceedings of the 11th international IFIP TC 6 conference on Networking - Volume Part I (IFIP'12), Robert Bestak, Lukas Kencl, Li Erran Li, Joerg Widmer, and Hao Yin (Eds.), Vol. Part I. Springer-Verlag, Berlin, Heidelberg, 397-408. DOI=10.1007/978-3-642-30045-5_30 http://dx.doi.org/10.1007/978-3-642-30045-5_30 > same question/comment as my first regarding stability. > > I don't doubt that the materials you have reference is valuable; I just want > to make sure that they are likely to be accessible to potential readers when > and long after the LISP intro and architecture documents are published. If you reference the ACM way, you are sure that it will last (assuming ACM will of course). Damien Saucez > > --Vince > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
