%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%% Descr:       Vorlage für Berichte der DHBW-Karlsruhe, BibTeX
%% Author:      Prof. Dr. Jürgen Vollmer, vollmer AT dhbw-karlsruhe.de
%% $Id: bericht.bib,v 1.10 2016/03/16 12:27:42 vollmer draft $
%% -*- coding: utf-8 -*-
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%
%%  declararion of abbreviations
%%%%
@STRING{addison		= "Addison-Wesley"}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

@BOOK{knuth.1984a,
AUTHOR		= "Knuth, Donald E.",
TITLE		= "The \TeX{}book",
PUBLISHER	= addison,
YEAR		= 1984
}

@BOOK{lamport.1995a,
AUTHOR		= "Lamport, Leslie",
TITLE		= "Das \LaTeX\ Handbuch",
PUBLISHER	= addison,
YEAR		= 1995
}

@BOOK{beijnum.2002a,
AUTHOR		= "van Beijnum, Iljitsch",
TITLE		= "Building Reliable Networks with the Border Gateway Protocol",
PUBLISHER	= "O'Reilly",
YEAR		= 2002
}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% Referenzieren von URL's
@MISC{dante.2010a,
  AUTHOR	= "Dante",
  TITLE		= "Webseite der \emph{Deutschsprachige Anwendervereinigung TeX e.V.}",
  HOWPUBLISHED 	= "\url{http://www.dante.de}",
  YEAR		= 2010,
  MONTH		= jan
}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

@misc{rfc1997,
  series =    {Request for Comments},
  number =    1997,
  howpublished =  {RFC 1997},
  publisher = {RFC Editor},
  doi =       {10.17487/RFC1997},
  url =       {https://www.rfc-editor.org/info/rfc1997},
  author =    {Tony Li and Ravi Chandra and Paul S. Traina},
  title =     {{BGP Communities Attribute}},
  pagetotal = 5,
  year =      1996,
  month =     aug,
  abstract =  {This document describes an extension to BGP which may be used to pass additional information to both neighboring and remote BGP peers. {[}STANDARDS-TRACK{]}},
}

@misc{rfc8642,
  series =    {Request for Comments},
  number =    8642,
  howpublished =  {RFC 8642},
  publisher = {RFC Editor},
  doi =       {10.17487/RFC8642},
  url =       {https://www.rfc-editor.org/info/rfc8642},
  author =    {Jay Borkenhagen and Randy Bush and Ron Bonica and Serpil Bayraktar},
  title =     {{Policy Behavior for Well-Known BGP Communities}},
  pagetotal = 7,
  year =      2019,
  month =     aug,
  abstract =  {Well-known BGP communities are manipulated differently across various current implementations, resulting in difficulties for operators. Network operators should deploy consistent community handling across their networks while taking the inconsistent behaviors from the various BGP implementations into consideration. This document recommends specific actions to limit future inconsistency: namely, BGP implementors must not create further inconsistencies from this point forward. These behavioral changes, though subtle, actually update RFC 1997.},
}

@misc{rfc1998,
    series =    {Request for Comments},
    number =    1998,
    howpublished =  {RFC 1998},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC1998},
    url =       {https://www.rfc-editor.org/info/rfc1998},
        author =    {Tony J. Bates and Enke Chen},
    title =     {{An Application of the BGP Community Attribute in Multi-home Routing}},
    pagetotal = 9,
    year =      1996,
    month =     aug,
    abstract =  {This document presents an application of the BGP community attribute {[}2{]} in simplifying the implementation and configuration of routing policies in the multi-provider Internet. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.},
}

@misc{rfc4271,
    series =    {Request for Comments},
    number =    4271,
    howpublished =  {RFC 4271},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC4271},
    url =       {https://www.rfc-editor.org/info/rfc4271},
        author =    {Yakov Rekhter and Susan Hares and Tony Li},
    title =     {{A Border Gateway Protocol 4 (BGP-4)}},
    pagetotal = 104,
    year =      2006,
    month =     jan,
    abstract =  {This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced. BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths. This document obsoletes RFC 1771. {[}STANDARDS-TRACK{]}},
}