%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %% 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.}, }