all.bib


@TECHREPORT{rfc791,
  AUTHOR = {J. B. Postel},
  TITLE = {{Internet} Protocol},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 791,
  PAGES = 45,
  DAYS = 15,
  MONTH = SEP,
  YEAR = 1981,
  ABSTRACT = {An updated specification of IP. Replaces RFC 760. This
document specifies the DoD Standard Internet Protocol. This document is
based on six earlier editions of the ARPA Internet Protocol
Specification, and the present text draws heavily from them. This
edition revises aspects of addressing, error handling, option codes, and
the security, precedence, compartments, and handling restriction
features of the internet protocol.},
  URL = {http://www.rfc-editor.org/rfc/rfc791.txt}
}


@TECHREPORT{rfc1519,
  AUTHOR = {V. Fuller and T. Li and J. Yu and K. Varadhan},
  TITLE = {Classless Inter-Domain Routing {(CIDR):} an Address Assignment
and Aggregation Strategy},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1519,
  PAGES = 24,
  DAYS = 15,
  MONTH = SEP,
  YEAR = 1993,
  ABSTRACT = {This memo discusses strategies for address assignment of the
existing IP address space with a view to conserve the address space and
stem the explosive growth of routing tables in default-route-free
routers.},
  URL = {http://www.rfc-editor.org/rfc/rfc1519.txt}
}


@TECHREPORT{rfc1631,
  AUTHOR = {K. Egevang and P. Francis},
  TITLE = {The {IP} Network Address Translator {(NAT)}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1631,
  PAGES = 10,
  DAYS = 15,
  MONTH = MAY,
  YEAR = 1994,
  ABSTRACT = {The two most compelling problems facing the IP Internet are IP
address depletion and scaling in routing. Long-term and short-term
solutions to these problems are being developed. The short-term solution
is CIDR (Classless InterDomain Routing). The long-term solutions consist
of various proposals for new internet protocols with larger addresses.
It is possible that CIDR will not be adequate to maintain the IP
Internet until the long-term solutions are in place. This memo proposes
another short-term solution, address reuse, that complements CIDR or
even makes it unnecessary. The address reuse solution is to place
Network Address Translators (NAT) at the borders of stub domains. Each
NAT box has a table consisting of pairs of local IP addresses and
globally unique addresses. The IP addresses inside the stub domain are
not globally unique. They are reused in other domains, thus solving the
address depletion problem. The globally unique IP addresses are assigned
according to current CIDR address allocation schemes. CIDR solves the
scaling problem. The main advantage of NAT is that it can be installed
without changes to routers or hosts. This memo presents a preliminary
design for NAT, and discusses its pros and cons.},
  URL = {http://www.rfc-editor.org/rfc/rfc1631.txt}
}


@TECHREPORT{rfc1771,
  AUTHOR = {Y. Rekhter and T. Li},
  TITLE = {A Border Gateway Protocol 4 {(BGP-4)}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1771,
  PAGES = 57,
  DAYS = 15,
  MONTH = MAR,
  YEAR = 1995,
  ABSTRACT = {This document, together with its companion document,
"Application of the Border Gateway Protocol in the Internet", define an
inter-autonomous system routing protocol for the Internet. This RFC is a
product of the Inter-Domain Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1771.txt}
}


@TECHREPORT{rfc1863,
  AUTHOR = {D. Haskin},
  TITLE = {A {BGP/IDRP} Route Server alternative to a full mesh routing},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1863,
  PAGES = 16,
  DAYS = 15,
  MONTH = OCT,
  YEAR = 1995,
  ABSTRACT = {This document describes the use and detailed design of Route
Servers for dissemination of routing information among BGP/IDRP speaking
routers. The intention of the proposed technique is to reduce overhead
and management complexity of maintaining numerous direct BGP/IDRP
sessions which otherwise might be required or desired among routers
within a single routing domain as well as among routers in different
domains that are connected to a common switched fabric (e.g. an ATM
cloud). This RFC is a product of the Inter-Domain Routing Working Group
of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1863.txt}
}


@TECHREPORT{rfc1878,
  AUTHOR = {T. Pummill and Alantec and B. Manning},
  TITLE = {Variable Length Subnet Table For {IPv4}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1878,
  PAGES = 8,
  MONTH = DEC,
  YEAR = 1995,
  ABSTRACT = {This memo clarifies issues surrounding subnetting IP networks by
providing a standard subnet table.  This table includes subnetting
for Class A, B, and C networks, as well as Network IDs, host ranges
and IP broadcast addresses with emphasis on Class C subnets.},
  URL = {http://www.rfc-editor.org/rfc/rfc1878.txt}
}


@TECHREPORT{rfc1918,
  AUTHOR = {Y. Rekhter and B. Moskowitz and D. Karrenberg and G. J. de and
E. Lear},
  TITLE = {Address Allocation for Private Internets},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1918,
  PAGES = 9,
  DAYS = 15,
  MONTH = FEB,
  YEAR = 1996,
  ABSTRACT = {For the purposes of this document, an enterprise is an entity
autonomously operating a network using TCP/IP and in particular
determining the addressing plan and address assignments within that
network. This document describes address allocation for private
internets. The allocation permits full network layer connectivity among
all hosts inside an enterprise as well as among all public hosts of
different enterprises. The cost of using private internet address space
is the potentially costly effort to renumber hosts and networks between
public and private. This RFC is the product of the CIDR Deployment
Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1918.txt}
}


@TECHREPORT{rfc1930,
  AUTHOR = {J. Hawkinson and T. Bates},
  TITLE = {Guidelines for creation, selection, and registration of an
Autonomous System {(AS)}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1930,
  PAGES = 10,
  DAYS = 15,
  MONTH = MAR,
  YEAR = 1996,
  ABSTRACT = {This memo discusses when it is appropriate to register and
utilize an Autonomous System (AS), and lists criteria for such. ASes are
the unit of routing policy in the modern world of exterior routing, and
are specifically applicable to protocols like EGP (Exterior Gateway
Protocol, now at historical status; see EGP), BGP (Border Gateway
Protocol, the current de facto standard for inter-AS routing, and IDRP
(The OSI Inter-Domain Routing Protocol, which the Internet is expected
to adopt when BGP becomes obsolete. It should be noted that the IDRP
equivalent of an AS is the RDI, or Routing Domain Identifier. This RFC
is the product of the Inter-Domain Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1930.txt}
}


@TECHREPORT{rfc1997,
  AUTHOR = {R. Chandra and P. Traina and T. Li},
  TITLE = {{BGP} Communities Attribute},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1997,
  PAGES = 5,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 1996,
  ABSTRACT = {The Border Gateway Protocol is an inter-autonomous system
routing protocol designed for TCP/IP internets. This document describes
an extension to BGP which may be used to pass additional information to
both neighboring and remote BGP peers. The intention of the proposed
technique is to aid in policy administration and reduce the management
complexity of maintaining the Internet. This RFC is the product of the
Inter-Domain Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1997.txt}
}


@TECHREPORT{rfc1998,
  AUTHOR = {E. H. Chen and T. Bates},
  TITLE = {An Application of the {BGP} Community Attribute in Multi-home
Routing},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 1998,
  PAGES = 9,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 1996,
  ABSTRACT = {This document presents an application of the BGP community
attribute in simplifying the implementation and configuration of routing
policies in the multi-provider Internet. It shows how the community
based configuration can be used to replace the AS-based customization of
the BGP "LOCAL_PREF" attribute, a common method used today. Not only
does the technique presented simplifies configuration and management at
the provider level, it also represents a paradigm shift in that it gives
the potential for the customer to control its own routing policy with
respect to its service provider, as well as providing the ability for
policy configuration to be done at a prefix based granularity rather
than the more common AS based granularity. This RFC is the product of
the Inter-Domain Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc1998.txt}
}


@TECHREPORT{rfc2373,
  AUTHOR = {R. Hinden and S. E. Deering},
  TITLE = {{IP} Version 6 Addressing Architecture},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2373,
  PAGES = 26,
  DAYS = 15,
  MONTH = JUL,
  YEAR = 1998,
  ABSTRACT = {This specification defines the addressing architecture of the
IP Version 6 protocol. The document includes the IPv6 addressing model,
text representations of IPv6 addresses, definition of IPv6 unicast
addresses, anycast addresses, and multicast addresses, and an IPv6
node's required addresses.},
  URL = {http://www.rfc-editor.org/rfc/rfc2373.txt}
}


@TECHREPORT{rfc2391,
  AUTHOR = {P. Srisuresh and D. Gan},
  TITLE = {Load Sharing using {IP} Network Address Translation {(LSNAT)}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2391,
  PAGES = 18,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 1998,
  ABSTRACT = {Network Address Translators (NATs) translate IP addresses in a
datagram, transparent to end nodes, while routing the datagram. NATs
have traditionally been been used to allow private network domains to
connect to Global networks using as few as one globally unique IP
address. In this document, we extend the use of NATs to offer Load share
feature, where session load can be distributed across a pool of servers,
instead of directing to a single server. Load sharing is beneficial to
service providers and system administrators alike in grappling with
scalability of servers with increasing session load.},
  URL = {http://www.rfc-editor.org/rfc/rfc2391.txt}
}


@TECHREPORT{rfc2439,
  AUTHOR = {C. Villamizar and R. Chandra and R. Govindan},
  TITLE = {{BGP} Route Flap Damping},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2439,
  PAGES = 37,
  DAYS = 15,
  MONTH = NOV,
  YEAR = 1998,
  ABSTRACT = {A usage of the BGP routing protocol is described which is
capable of reducing the routing traffic passed on to routing peers and
therefore the load on these peers without adversely affecting route
convergence time for relatively stable routes. This technique has been
implemented in commercial products supporting BGP. The technique is also
applicable to IDRP.},
  URL = {http://www.rfc-editor.org/rfc/rfc2439.txt}
}


@TECHREPORT{rfc2460,
  AUTHOR = {S. E. Deering and R. Hinden},
  TITLE = {{Internet} Protocol, Version 6 (IPv6) Specification},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2460,
  PAGES = 39,
  DAYS = 15,
  MONTH = DEC,
  YEAR = 1998,
  ABSTRACT = {This document specifies version 6 of the Internet Protocol
(IPv6), also sometimes referred to as IP Next Generation or IPng.},
  URL = {http://www.rfc-editor.org/rfc/rfc2460.txt}
}


@TECHREPORT{rfc2519,
  AUTHOR = {E. H. Chen and J. Stewart},
  TITLE = {A Framework for Inter-Domain Route Aggregation},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2519,
  PAGES = 13,
  DAYS = 15,
  MONTH = FEB,
  YEAR = 1999,
  ABSTRACT = {This document presents a framework for inter-domain route
aggregation and shows an example router configuration which 'implements'
this framework. This framework is flexible and scales well as it
emphasizes the philosophy of aggregation by the source, both within
routing domains as well as towards upstream providers, and it also
strongly encourages the use of the 'no-export' BGP community to balance
the provider-subscriber need for more granular routing information with
the Internet's need for scalable inter-domain routing.},
  URL = {http://www.rfc-editor.org/rfc/rfc2519.txt}
}


@TECHREPORT{rfc2702,
  AUTHOR = {Daniel O. Awduche and J. Malcolm and J. Agogbua and M. O'Dell
and J. McManus},
  TITLE = {Requirements for Traffic Engineering Over {MPLS}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2702,
  PAGES = 29,
  DAYS = 15,
  MONTH = SEP,
  YEAR = 1999,
  ABSTRACT = {This document presents a set of requirements for Traffic
Engineering over Multiprotocol Label Switching (MPLS). It identifies the
functional capabilities required to implement policies that facilitate
efficient and reliable network operations in an MPLS domain.},
  URL = {http://www.rfc-editor.org/rfc/rfc2702.txt}
}


@TECHREPORT{rfc2796,
  AUTHOR = {T. Bates and R. Chandra and E. H. Chen},
  TITLE = {{BGP} Route Reflection - An Alternative to Full Mesh {IBGP}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2796,
  PAGES = 11,
  DAYS = 15,
  MONTH = APR,
  YEAR = 2000,
  ABSTRACT = {The Border Gateway Protocol is an inter-autonomous system
routing protocol designed for TCP/IP internets. Currently in the
Internet BGP deployments are configured such that that all BGP speakers
within a single AS must be fully meshed so that any external routing
information must be re-distributed to all other routers within that AS.
This represents a serious scaling problem that has been well documented
with several alternatives proposed. This document describes the use and
design of a method known as "Route Reflection" to alleviate the the need
for "full mesh" IBGP. This document is a product of the Inter-Domain
Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc2796.txt}
}


@TECHREPORT{rfc2893,
  AUTHOR = {R. Gilligan and E. Nordmark},
  TITLE = {Transition Mechanisms for {IPv6} Hosts and Routers},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 2893,
  PAGES = 29,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 2000,
  ABSTRACT = {This document specifies IPv4 compatibility mechanisms that can
be implemented by IPv6 hosts and routers. These mechanisms include
providing complete implementations of both versions of the Internet
Protocol (IPv4 and IPv6), and tunneling IPv6 packets over IPv4 routing
infrastructures. They are designed to allow IPv6 nodes to maintain
complete compatibility with IPv4, which should greatly simplify the
deployment of IPv6 in the Internet, and facilitate the eventual
transition of the entire Internet to IPv6. This document obsoletes RFC
1933. This document is a product of the Next Generation Transition
Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc2893.txt}
}


@TECHREPORT{rfc3031,
  AUTHOR = {E. C. Rosen and A. Viswanathan and R. Callon},
  TITLE = {Multiprotocol Label Switching Architecture},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3031,
  PAGES = 61,
  DAYS = 15,
  MONTH = JAN,
  YEAR = 2001,
  ABSTRACT = {This document specifies the architecture for Multiprotocol
Label Switching (MPLS). This document is a product of the Multiprotocol
Label Switching Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3031.txt}
}


@TECHREPORT{rfc3065,
  AUTHOR = {P. Traina and D. McPherson and J. Scudder},
  TITLE = {Autonomous System Confederations for {BGP}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3065,
  PAGES = 11,
  DAYS = 15,
  MONTH = FEB,
  YEAR = 2001,
  ABSTRACT = {The Border Gateway Protocol (BGP) is an inter-autonomous
system routing protocol designed for Transmission Control
Protocol/Internet Protocol (TCP/IP) networks. BGP requires that all BGP
speakers within a single autonomous system (AS) must be fully meshed.
This represents a serious scaling problem that has been well documented
in a number of proposals. This document describes an extension to BGP
which may be used to create a confederation of autonomous systems that
is represented as a single autonomous system to BGP peers external to
the confederation, thereby removing the "full mesh" requirement. The
intention of this extension is to aid in policy administration and
reduce the management complexity of maintaining a large autonomous
system.},
  URL = {http://www.rfc-editor.org/rfc/rfc3065.txt}
}


@TECHREPORT{rfc3168,
  AUTHOR = {K. G. Ramakrishnan and S. Floyd and D. L. Black},
  TITLE = {The Addition of Explicit Congestion Notification {(ECN)} to
{IP}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3168,
  PAGES = 63,
  DAYS = 15,
  MONTH = SEP,
  YEAR = 2001,
  ABSTRACT = {This memo specifies the incorporation of ECN (Explicit
Congestion Notification) to TCP and IP, including ECN's use of two bits
in the IP header. This document is a product of the Transport Area
Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3168.txt}
}


@TECHREPORT{rfc3272,
  AUTHOR = {Daniel O. Awduche and A. Chiu and A. I. Elwalid and I. Widjaja
and X. Xiao},
  TITLE = {Overview and Principles of {Internet} Traffic Engineering},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3272,
  PAGES = 71,
  DAYS = 15,
  MONTH = MAY,
  YEAR = 2002,
  ABSTRACT = {This memo describes the principles of Traffic Engineering (TE)
in the Internet. The document is intended to promote better
understanding of the issues surrounding traffic engineering in IP
networks, and to provide a common basis for the development of traffic
engineering capabilities for the Internet. The principles,
architectures, and methodologies for performance evaluation and
performance optimization of operational IP networks are discussed
throughout this document. This document is a product of the Internet
Traffic Engineering Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3272.txt}
}


@TECHREPORT{rfc3345,
  AUTHOR = {D. McPherson and V. Gill and D. Walton and A. Retana},
  TITLE = {Border Gateway Protocol {(BGP)} Persistent Route Oscillation
Condition},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3345,
  PAGES = 19,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 2002,
  ABSTRACT = {In particular configurations, the BGP scaling mechanisms
defined in "BGP Route Reflection - An Alternative to Full Mesh IBGP" and
"Autonomous System Confederations for BGP" will introduce persistent BGP
route oscillation. This document discusses the two types of persistent
route oscillation that have been identified, describes when these
conditions will occur, and provides some network design guidelines to
avoid introducing such occurrences. This document is a product of the
Inter-Domain Routing Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3345.txt}
}


@TECHREPORT{rfc3346,
  AUTHOR = {J. Boyle and V. Gill and A. Hannan and D. B. Cooper and Daniel
O. Awduche and B. Christian and W. S. Lai},
  TITLE = {Applicability Statement for Traffic Engineering with {MPLS}},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3346,
  PAGES = 14,
  DAYS = 15,
  MONTH = AUG,
  YEAR = 2002,
  ABSTRACT = {This document describes the applicability of Multiprotocol
Label Switching (MPLS) to traffic engineering in IP networks. Special
considerations for deployment of MPLS for traffic engineering in
operational contexts are discussed and the limitations of the MPLS
approach to traffic engineering are highlighted. This document is a
product of the Internet Traffic Engineering Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3346.txt}
}


@TECHREPORT{rfc3330,
  AUTHOR = {Carla-Fabiana Chiasserini},
  TITLE = {Special-Use {IPv4} Addresses},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3330,
  PAGES = 7,
  DAYS = 15,
  MONTH = SEP,
  YEAR = 2002,
  ABSTRACT = {This document describes the global and other specialized IPv4
address blocks that have been assigned by the Internet Assigned Numbers
Authority (IANA). It does not address IPv4 address space assigned to
operators and users through the Regional Internet Registries. It also
does not address allocations or assignments of IPv6 addresses or
autonomous system numbers.},
  URL = {http://www.rfc-editor.org/rfc/rfc3330.txt}
}


@TECHREPORT{rfc3386,
  TITLE = {Network Hierarchy and Multilayer Survivability},
  EDITOR = {W. S. Lai and D. McDysan+},
  TYPE = {RFC},
  INSTITUTION = {Internet Engineering Task Force},
  NUMBER = 3386,
  PAGES = 27,
  DAYS = 15,
  MONTH = NOV,
  YEAR = 2002,
  ABSTRACT = {This document presents a proposal of the near-term and
practical requirements for network survivability and hierarchy in
current service provider environments. This document is a product of the
Internet Traffic Engineering Working Group of the IETF.},
  URL = {http://www.rfc-editor.org/rfc/rfc3386.txt}
}


@INPROCEEDINGS{andersen01resilient,
  AUTHOR = {David Andersen and Hari Balakrishnan and M. Frans Kaashoek and Robert Morris},
  TITLE = {Resilient Overlay Networks},
  BOOKTITLE = {Proceedings of 18th ACM Symposium on Operating Systems Principles},
  MONTH = {October},
  YEAR = {2001},
  ADDRESS = {Banff, Canada},
  URL = {http://citeseer.nj.nec.com/andersen01resilient.html}
}


@INPROCEEDINGS{awduche98approach,
  AUTHOR = {D. O. Awduche and J. Agogbua and J. McManus},
  TITLE = {An Approach to Optimal Peering between Autonomous Systems in the Internet},
  BOOKTITLE = {Proceedings of International Conference on Computer Communications and Networks},
  YEAR = {1998},
  PAGES = {346--351},
  URL = {http://citeseer.nj.nec.com/awduche98approach.html}
}


@ARTICLE{bauer02performance,
  AUTHOR = {Daniel Bauer and Sean Rooney and Paolo Scotton and Sonja Buchegger and Ilias Iliadis},
  TITLE = {The Performance of Measurement-Based Overlay Networks},
  JOURNAL = {Lecture Notes in Computer Science},
  VOLUME = {2511},
  PAGES = {115--124},
  YEAR = {2002},
  ISSN = {0302-9743},
  PUBLISHER = {Springer-Verlag},
  URL = {http://citeseer.nj.nec.com/bauer02performance.html}
}


@TECHREPORT{bernstein88highly,
  AUTHOR = {Herbert J. Bernstein},
  TITLE = {Some Comments on Highly Dynamic Network Routing},
  INSTITUTION = {New York University},
  NUMBER = {371},
  ADDRESS = {Computer Science Department},
  MONTH = {May},
  YEAR = {1988},
  URL = {http://www.bernstein-plus-sons.com/TMM/Routing/}
}


@TECHREPORT{castro02topologyaware,
  AUTHOR = {Miguel Castro and Peter Druschel and Y. Charlie Hu and Antony Rowstron},
  TITLE = {Topology-aware routing in structured peer-to-peer overlay networks},
  INSTITUTION = {Microsoft Research},
  NUMBER = {82},
  ADDRESS = {One Microsoft Way, Redmond},
  YEAR = {2002},
  URL = {http://citeseer.nj.nec.com/castro02topologyaware.html}
}


@TECHREPORT{dicaro97antnet,
  AUTHOR = {Gianni Di Caro and Marco Dorigo},
  TITLE = {AntNet: A Mobile Agents Approach to Adaptive Routing},
  INSTITUTION = {Universite Libre de Bruxelles},
  NUMBER = {12},
  ADDRESS = {IRIDIA},
  YEAR = 1997,
  URL = {http://citeseer.nj.nec.com/dicaro97antnet.html}
}


@ARTICLE{dommety98route,
  AUTHOR = {Gopal Dommety and Malathi Veeraraghavan and Mukesh Singhal},
  TITLE = {A route optimization algorithm and its application to mobile location management in ATM networks},
  JOURNAL = {IEEE Journal on Selected Areas in Communications},
  VOLUME = {16},
  NUMBER = {6},
  PAGES = {890--908},
  MONTH = {August},
  YEAR = {1998},
  URL = {http://citeseer.nj.nec.com/dommety98route.html}
}


@INPROCEEDINGS{duffield01charging,
  AUTHOR = {Nick Duffield and Carsten Lund and Mikkel Thorup},
  TITLE = {Charging from sampled network usage},
  BOOKTITLE = {Proceedings of SIGCOMM Internet Measurement Workshop},
  MONTH = {November},
  YEAR = {2001},
  URL = {http://citeseer.nj.nec.com/duffield01charging.html}
}


@INPROCEEDINGS{ely01robust,
  AUTHOR = {David Ely and Neil Spring and David Wetherall and Stefan Savage and Tom Anderson},
  BOOKTITLE = {Proceedings of International Conference on Network Protocols},
  ADDRESS = {Riverside, CA},
  MONTH = {November},
  YEAR = {2001},
  TITLE = {Robust Congestion Signaling},
  URL = {http://citeseer.nj.nec.com/ely01robust.html}
}


@INPROCEEDINGS{feigenbaum02bgpbased,
  AUTHOR = {J. Feigenbaum and C. Papadimitriou and R. Sami and S. Shenker},
  TITLE = {A {BGP}-based Mechanism for Lowest-Cost Routing},
  BOOKTITLE = {Proceedings of the 2002 {ACM} Symposium
    on Principles of Distributed Computing},
  PAGES = {173--182},
  MONTH = {July},
  ADDRESS = {New York, NY},
  YEAR = {2002},
  URL = {http://citeseer.nj.nec.com/feigenbaum02bgpbased.html}
}


@ARTICLE{fleischer99universally,
  AUTHOR = {Lisa Fleischer},
  TITLE = {Universally Maximum Flow with Piecewise-Constant Capacities},
  JOURNAL = {Lecture Notes in Computer Science},
  VOLUME = {1610},
  PAGES = {151--165},
  MONTH = {June},
  YEAR = {1999},
  ADDRESS = {Graz, Austria},
  PUBLISHER = {Springer-Verlag},
  URL = {http://citeseer.nj.nec.com/fleischer98universally.html}
}


@ARTICLE{floyd99promoting,
  AUTHOR = {Sally Floyd and Kevin Fall},
  TITLE = {Promoting the use of end-to-end congestion control in the Internet},
  JOURNAL = {IEEE/ACM Transactions on Networking (TON)},
  VOLUME = {7},
  NUMBER = {4},
  MONTH = {August},
  YEAR = {1999},
  ISSN = {1063-6692},
  PAGES = {458--472},
  PUBLISHER = {ACM Press},
  URL = {http://citeseer.nj.nec.com/floyd99promoting.html}
}


@ARTICLE{fortz02traffic,
  AUTHOR = {Bernard Fortz and Jennifer Rexford and Mikkel Thorup},
  TITLE = {Traffic engineering with traditional IP routing protocols},
  JOURNAL = {IEEE Communications Magazine},
  YEAR = {2002},
  MONTH = {October},
  PAGES = {118--124},
  URL = {http://citeseer.nj.nec.com/fortz02traffic.html}
}


@INPROCEEDINGS{gao00stable,
  AUTHOR = {Lixin Gao and Jennifer Rexford},
  TITLE = {Stable Internet routing without global coordination},
  BOOKTITLE = {Proceedings of the 2000 ACM SIGMETRICS international conference on Measurement and modeling of computer systems},
  ISBN = {1-58113-194-1},
  PAGES = {307--317},
  LOCATION = {Santa Clara, California, United States},
  PUBLISHER = {ACM Press},
  MONTH = {June},
  YEAR = {2000},
  URL = {http://citeseer.nj.nec.com/gao00stable.html}
}


@INPROCEEDINGS{goodell03working,
  AUTHOR = {Geoffrey Goodell and William Aiello and Timothy Griffin and John Ioannidis and Patrick McDaniel and Aviel Rubin},
  TITLE = {Working Around BGP: An Incremental Approach to Improving Security and Accuracy of Interdomain Routing},
  BOOKTITLE = {Proceedings of Network and Distributed System Security Symposium},
  ADDRESS = {San Diego, CA},
  MONTH = {February},
  YEAR = {2003},
  URL = {http://citeseer.nj.nec.com/goodell03working.html}
}


@ARTICLE{govindan98route,
  AUTHOR = {Ramesh Govindan and Cengiz Alaettino{g-}lu and Kannan Varadhan and Deborah Estrin},
  TITLE = {Route servers for inter-domain routing},
  JOURNAL = {Computer Networks and ISDN Systems},
  VOLUME = {30},
  NUMBER = {12},
  PAGES = {1157--1174},
  YEAR = {1998},
  URL = {http://citeseer.nj.nec.com/govindan98route.html}
}


@INPROCEEDINGS{griffin99analysis,
  AUTHOR = {Timothy G. Griffin and Gordon T. Wilfong},
  TITLE = {An Analysis of {BGP} Convergence Properties},
  BOOKTITLE = {Proceedings of {SIGCOMM}},
  PAGES = {277--288},
  MONTH = {August},
  YEAR = {1999},
  ADDRESS = {Cambridge, MA},
  URL = {http://citeseer.nj.nec.com/griffin99analysis.html}
}


@INPROCEEDINGS{griffin99policy,
  AUTHOR = {Timothy Griffin and F. Bruce Shepherd and Gordon T. Wilfong},
  TITLE = {Policy Disputes in Path-Vector Protocols},
  BOOKTITLE = {Proceedings of the 7th Annual International Conference on Network Protocols},
  PAGES = {21--30},
  MONTH = {November},
  YEAR = {1999},
  ADDRESS = {Toronto, Canada},
  URL = {http://citeseer.nj.nec.com/griffin99policy.html}
}


@INPROCEEDINGS{holmberg01optimal,
  AUTHOR = {Kaj Holmberg and Di Yuan},
  TITLE = {Optimal Network Design and Routing for IP Traffic},
  EDITOR = {T. Cinkler},
  BOOKTITLE = {Proc. of the Third International Workshop on Design of Reliable Communication Networks},
  MONTH = OCT,
  YEAR = 2001,
  ADDRESS = {Budapest, Hungary}
}


@INPROCEEDINGS{jain02endtoend,
  AUTHOR = {Manish Jain and Constantinos Dovrolis},
  TITLE = {End-to-end available bandwidth: Measurement methodology, dynamics, and relation with TCP throughput},
  BOOKTITLE = {Proceedings of {SIGCOMM}},
  YEAR = {2002},
  MONTH = {August},
  ADDRESS = {Pittsburgh, PA},
  URL = {http://citeseer.nj.nec.com/jain02endtoend.html}
}


@TECHREPORT{javidi02sensitivity,
  AUTHOR = {Tara Javidi and Demosethenis Teneketzis},
  TITLE = {Sensitivity Analysis for an Optimal Routing Policy in an Ad Hoc Wireless Network},
  INSTITUTION = {University of Michigan},
  NUMBER = {332},
  ADDRESS = {Department of Electrical Engineering and Computer Science},
  MONTH = {October},
  YEAR = {2002},
  URL = {http://www.ee.washington.edu/people/faculty/javidi_tara/mainVTC.pdf}
}


@MISC{johari03routing,
  AUTHOR = {Ramesh Johari and John Tsitsiklis},
  TITLE = {Routing and Peering in a Competitive Internet},
  URL = {http://citeseer.nj.nec.com/johari03routing.html}
}


@INPROCEEDINGS{karir98experimental,
  AUTHOR = {Manish Karir and Yongguang Zhang},
  TITLE = {An Experimental Study of Asymmetric Routing},
  BOOKTITLE = {Proceedings of the 3rd International Workshop on Satellite-based Information Services},
  PAGES = {97--103},
  ADDRESS = {Dallas, Texas},
  MONTH = {October},
  YEAR = {1998},
  URL = {http://citeseer.nj.nec.com/karir98experimental.html}
}


@INPROCEEDINGS{labovitz00delayed,
  AUTHOR = {Craig Labovitz and Abha Ahuja and Abhijit Bose and Farnam Jahanian},
  TITLE = {Delayed internet routing convergence},
  BOOKTITLE = {Proceedings of {SIGCOMM}},
  PAGES = {175-187},
  YEAR = {2000},
  MONTH = {September},
  ADDRESS = {Stockholm, Sweden},
  URL = {http://citeseer.nj.nec.com/labovitz00delayed.html}
}


@INPROCEEDINGS{labovitz01impact,
  AUTHOR = {Craig Labovitz and Abha Ahuja and Roger Wattenhofer and Srinivasan Venkatachary},
  TITLE = {The Impact of Internet Policy and Topology on Delayed Routing Convergence},
  PAGES = {537--546},
  BOOKTITLE = {Proceedings of the Twentieth Annual Joint Conference of the {IEEE} Computer and Communications Societies ({INFOCOM}-01)},
  MONTH = {April},
  PUBLISHER = {IEEE Computer Society},
  ADDRESS = {Los Alamitos, CA},
  YEAR = {2001},
  URL = {http://citeseer.nj.nec.com/labovitz01impact.html}
}


@INPROCEEDINGS{mithal98bounds,
  AUTHOR = {S. Mithal},
  TITLE = {Bounds on end-to-end performance via greedy, multi-path routing in integrated services networks},
  BOOKTITLE = {Proceedings of IEEE Infocom},
  ADDRESS = {San Francisco, CA},
  PAGES = {19},
  MONTH = {March/April},
  YEAR = {1998},
  URL = {http://www.ieee-infocom.org/1998/papers/01a_3.pdf}
}


@INPROCEEDINGS{norton00internet,
  AUTHOR = {William B. Norton},
  TITLE = {Internet service providers and peering},
  BOOKTITLE = {Proceedings of NANOG 19},
  ADDRESS = {Albuquerque, New Mexico},
  MONTH = {June},
  YEAR = {2000},
  URL = {http://citeseer.nj.nec.com/norton00internet.html}
}


@INPROCEEDINGS{obradovic02realtime,
  AUTHOR = {Davor Obradovic},
  TITLE = {Real-time Model and Convergence Time of {BGP}},
  PAGES = {893--901},
  BOOKTITLE = {Proceedings of the 21st Annual Joint Conference of the {IEEE} Computer and Communications Society ({INFOCOM}-02)},
  SERIES = {Proceedings IEEE INFOCOM 2002},
  VOLUME = {2},
  PUBLISHER = {IEEE Computer Society},
  ADDRESS = {Piscataway, NJ, USA},
  MONTH = {June},
  YEAR = {2002},
  URL = {http://citeseer.nj.nec.com/obradovic02realtime.html}
}


@ARTICLE{orda94continuous,
  AUTHOR = {Ariel Orda and Raphael Rom},
  TITLE = {On Continuous Network Flows},
  JOURNAL = {Operations Research Letters},
  YEAR = {1995},
  VOLUME = {17},
  NUMBER = {1},
  PAGES = {27--36},
  URL = {http://citeseer.nj.nec.com/orda94continuous.html}
}


@INPROCEEDINGS{paxson96endtoend,
  AUTHOR = {Vern Paxson},
  TITLE = {End-to-end routing behavior in the {Internet}},
  BOOKTITLE = {Proceedings of the {ACM} {SIGCOMM} Conference on Applications, Technologies, Architectures, and Protocols for Computer Communications},
  ISBN = {0-89791-790-1},
  PAGES = {25--38},
  SERIES = {ACM SIGCOMM Computer Communication Review},
  VOLUME = {26,4},
  PUBLISHER = {ACM Press},
  ADDRESS = {New York},
  MONTH = {August},
  YEAR = {1996},
  URL = {http://citeseer.nj.nec.com/article/paxson96endtoend.html}
}


@INPROCEEDINGS{paxson97endtoend,
  AUTHOR = {Vern Paxson},
  TITLE = {End-to-End {Internet} Packet Dynamics},
  PAGES = {139--154},
  BOOKTITLE = {Proceedings of the {ACM} {SIGCOMM} '97 conference on Applications, Technologies, Architectures, and Protocols for Computer Communication},
  SERIES = {Computer Communication Review},
  VOLUME = {27,4},
  MONTH = {September},
  YEAR = {1997},
  PUBLISHER = {ACM Press},
  ADDRESS = {Cannes, France},
  URL = {http://citeseer.nj.nec.com/paxson97endtoend.html}
}


@PHDTHESIS{paxson97measurements,
  AUTHOR = {Vern E. Paxson},
  TITLE = {Measurements and Analysis of End-to-End Internet Dynamics},
  SCHOOL = {University of California},
  TYPE = {{PhD} Dissertation},
  ADDRESS = {Lawrence Berkeley National Laboratory},
  MONTH = {April},
  YEAR = 1997,
  URL = {http://citeseer.nj.nec.com/paxson97measurements.html}
}


@INPROCEEDINGS{pei02improving,
  AUTHOR = {Dan Pei and Xiaoliang Zhao and Lan Wang and Daniel Massey and Allison Mankin and Shyhtsun Felix Wu and Lixia Zhang},
  TITLE = {Improving {BGP} Convergence Through Consistency Assertions},
  PAGES = {902--911},
  BOOKTITLE = {Proceedings of the 21st Annual Joint Conference of the {IEEE} Computer and Communications Society ({INFOCOM}-02)},
  MONTH = {June},
  SERIES = {Proceedings IEEE INFOCOM 2002},
  VOLUME = {2},
  PUBLISHER = {IEEE Computer Society},
  ADDRESS = {Piscataway, NJ},
  YEAR = {2002},
  URL = {http://citeseer.nj.nec.com/pei02improving.html}
}


@INPROCEEDINGS{qiu03selfish,
  AUTHOR = {Lili Qiu and Yang Richard Yang and Yin Zhang and Scott Shenker},
  TITLE = {On Selfish Routing in Internet-Like Environments},
  BOOKTITLE = {Proceedings of the {ACM} {SIGCOMM}},
  SERIES = {All ACM Conferences},
  PAGES = {151--162},
  MONTH = {august},
  YEAR = 2003,
  ADDRESS = {Karlsruhe, Germany},
  URL = {http://citeseer.nj.nec.com/qiu03selfish.html}
}


@ARTICLE{quoitin03interdomain,
  AUTHOR = {Bruno Quoitin and Steve Uhlig and Cristel Pelsser and Louis Swinnen and Olivier Bonaventure},
  TITLE = {Interdomain traffic engineering with BGP},
  JOURNAL = {IEEE Communications Magazine},
  YEAR = {2003},
  MONTH = {may},
  URL = {http://citeseer.nj.nec.com/quoitin03interdomain.html}
}


@ARTICLE{quoitin03interdomaincommunities,
  AUTHOR = {Bruno Quoitin and Sebastien Tandel and Steve Uhlig and Olivier Bonaventure},
  TITLE = {Interdomain Traffic Engineering with Redistribution Communities},
  JOURNAL = {Computer Communications},
  YEAR = 2003,
  URL = {http://citeseer.nj.nec.com/article/quoitin03interdomain.html}
}


@INPROCEEDINGS{roughgarden00how,
  AUTHOR = {Tim Roughgarden and Eva Tardos},
  TITLE = {How Bad is Selfish Routing?},
  BOOKTITLE = {{IEEE} Symposium on Foundations of Computer Science},
  PAGES = {93-102},
  YEAR = {2000},
  URL = {http://citeseer.nj.nec.com/roughgarden00how.html}
}


@INPROCEEDINGS{roughgarden02how,
  AUTHOR = {Tim Roughgarden},
  TITLE = {How unfair is optimal routing?},
  BOOKTITLE = {Proceedings of the 13th annual ACM-SIAM symposium on Discrete algorithms},
  MONTH = {January},
  YEAR = {2002},
  ISBN = {0-89871-513-X},
  PAGES = {203--204},
  LOCATION = {San Francisco, California},
  PUBLISHER = {Society for Industrial and Applied Mathematics},
  URL = {http://citeseer.nj.nec.com/roughgarden02how.html}
}


@PHDTHESIS{roughgarden02selfish,
  AUTHOR = {Tim Roughgarden},
  TITLE = {Selfish Routing},
  SCHOOL = {Cornell University},
  ADDRESS = {Department of Computer Science},
  MONTH = {May},
  YEAR = 2002,
  URL = {http://www.cs.cornell.edu/timr/}
}


@INPROCEEDINGS{savage99endtoend,
  AUTHOR = {Stefan Savage and Andy Collins and Eric Hoffman and John Snell and Thomas E. Anderson},
  TITLE = {The End-to-End Effects of Internet Path Selection},
  BOOKTITLE = {Proceedings of {SIGCOMM}},
  PAGES = {289-299},
  MONTH = {August-September},
  YEAR = {1999},
  ADDRESS = {Boston, MA},
  URL = {http://citeseer.nj.nec.com/savage99endtoend.html}
}


@ARTICLE{schoonderwoerd96antbased,
  AUTHOR = {Ruud Schoonderwoerd and Owen E. Holland and Janet L. Bruten and Leon J. M. Rothkrantz},
  TITLE = {Ant-Based Load Balancing in Telecommunications Networks},
  JOURNAL = {Adaptive Behavior},
  VOLUME = {5},
  NUMBER = {2},
  PUBLISHER = {MIT Press},
  PAGES = {169--207},
  YEAR = {1996},
  URL = {http://citeseer.nj.nec.com/schoonderwoerd96antbased.html}
}


@INPROCEEDINGS{thorup01compact,
  AUTHOR = {Mikkel Thorup and Uri Zwick},
  TITLE = {Compact routing schemes},
  BOOKTITLE = {Proceedings of the 13th annual ACM symposium on Parallel algorithms and architectures},
  YEAR = {2001},
  MONTH = {July},
  ISBN = {1-58113-409-6},
  PAGES = {1--10},
  LOCATION = {Crete Island, Greece},
  PUBLISHER = {ACM Press},
  URL = {http://www.cs.tau.ac.il/~zwick/my-online-papers.html}
}


@ARTICLE{varadhan00persistent,
  AUTHOR = {Kannan Varadhan and Ramesh Govindan and Deborah Estrin},
  TITLE = {Persistent route oscillations in inter-domain routing},
  JOURNAL = {Computer Networks},
  VOLUME = {32},
  NUMBER = {1},
  PAGES = {1--16},
  MONTH = {January},
  YEAR = {2000},
  URL = {http://citeseer.nj.nec.com/varadhan00persistent.html}
}


@INPROCEEDINGS{yilmaz02scalabilityperformance,
  AUTHOR = {Selma Yilmaz and Ibrahim Matta},
  TITLE = {On the Scalability-Performance Tradeoffs in {MPLS} and {IP} Routing},
  BOOKTITLE = {Proceedings of {SPIE ITCOM'2002}: Scalability and Traffic Control in IP Networks},
  ADDRESS = {Boston, MA},
  MONTH = {August},
  YEAR = {2002},
  URL = {http://citeseer.nj.nec.com/yilmaz02scalabilityperformance.html}
}


@MISC{eigrp,
  AUTHOR = {Cisco Systems Inc.},
  TITLE = {Introduction to EIGRP: http://www.cisco.com/warp/public/103/1.html},
  YEAR = {2003},
  URL = {http://www.cisco.com/warp/public/103/1.html}
}


@MISC{eigrp-wp,
  AUTHOR = {Cisco Systems Inc.},
  TITLE = {Enhanced Interior Gateway Routing Protocol -- White paper: {http://www.cisco.com/warp/customer/103/eigrp-toc.html}},
  YEAR = {2003},
  URL = {http://www.cisco.com/warp/customer/103/eigrp-toc.html}
}


@MISC{netflow-wp,
  AUTHOR = {Cisco Systems Inc.},
  TITLE = {NetFlow Ecosystem Solutions -- White paper: {http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/netfl\_wp.htm}},
  YEAR = {2001},
  URL = {http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/netfl_wp.htm}
}


@BOOK{bgp,
  AUTHOR = {Iljitsch van Beijnum},
  TITLE = {BGP - Building Reliable Networks with the Border Gateway Protocol},
  PUBLISHER = {O'Reilly},
  ADDRESS = {Sebastopol, CA},
  EDITION = {First},
  MONTH = {September},
  YEAR = {2002},
  URL = {http://www.oreilly.com/catalog/bgp/}
}


@BOOK{bscn,
  AUTHOR = {Diane Teare and Catherine Paquet},
  PUBLISHER = {Cisco Press},
  TITLE = {Building Scalable Cisco Networks},
  SERIES = {Two volumes},
  YEAR = {2000},
  MONTH = {October},
  ISBN = {1578702283},
  URL = {http://www.ciscopress.com/catalog/product.asp?product_id={5932B4BF-BFE4-4D1B-8B36-1C3B98A67FC0}}
}


@BOOK{cn,
  AUTHOR = {James E. Kurose and Keith W. Ross},
  TITLE = {Computer Networking - A Top-down Approach Featuring the Internet},
  PUBLISHER = {Addison-Wesley},
  ADDRESS = {Reading, Massachusetts},
  EDITION = {Second},
  YEAR = {2001},
  URL = {http://www.aw.com/kurose-ross/}
}


@BOOK{ira,
  AUTHOR = {Bassam Halabi},
  TITLE = {Internet Routing Architectures},
  PUBLISHER = {Cisco Press},
  EDITION = {First},
  YEAR = {1997},
  URL = {http://www.ciscopress.com/catalog/product.asp?product_id={CA81ECA6-C909-4063-ADCC-CE3AB8D6B906}}
}


This file has been generated by bibtex2html 1.61