1
0
Fork 0

Bibliography, bad.

master
LEdoian 1 year ago
parent 4104e99f00
commit fbb39dafea

@ -74,6 +74,51 @@
abstract = {This memo documents version 2 of the OSPF protocol. OSPF is a link- state routing protocol. {[}STANDARDS-TRACK{]}},
}
@misc{rfc3101,
series = {Request for Comments},
number = 3101,
howpublished = {RFC 3101},
publisher = {RFC Editor},
doi = {10.17487/RFC3101},
url = {https://www.rfc-editor.org/info/rfc3101},
author = {Dr. Patrick W. Murphy},
title = {{The OSPF Not-So-Stubby Area (NSSA) Option}},
pagetotal = 33,
year = 2003,
month = jan,
abstract = {This memo documents an optional type of Open Shortest Path First (OSPF) area that is somewhat humorously referred to as a "not-so-stubby" area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion. The OSPF NSSA Option was originally defined in RFC 1587. The functional differences between this memo and RFC 1587 are explained in Appendix F. All differences, while expanding capability, are backward-compatible in nature. Implementations of this memo and of RFC 1587 will interoperate. {[}STANDARDS-TRACK{]}},
}
@misc{rfc6549,
series = {Request for Comments},
number = 6549,
howpublished = {RFC 6549},
publisher = {RFC Editor},
doi = {10.17487/RFC6549},
url = {https://www.rfc-editor.org/info/rfc6549},
author = {Acee Lindem and Abhay Roy and Sina Mirtorabi},
title = {{OSPFv2 Multi-Instance Extensions}},
pagetotal = 9,
year = 2012,
month = mar,
abstract = {OSPFv3 includes a mechanism to support multiple instances of the protocol running on the same interface. OSPFv2 can utilize such a mechanism in order to support multiple routing domains on the same subnet. This document defines the OSPFv2 Instance ID to enable separate OSPFv2 protocol instances on the same interface. Unlike OSPFv3 where the Instance ID can be used for multiple purposes, such as putting the same interface in multiple areas, the OSPFv2 Instance ID is reserved for identifying protocol instances. This document updates RFC 2328. {[}STANDARDS-TRACK{]}},
}
@misc{rfc5709,
series = {Request for Comments},
number = 5709,
howpublished = {RFC 5709},
publisher = {RFC Editor},
doi = {10.17487/RFC5709},
url = {https://www.rfc-editor.org/info/rfc5709},
author = {M Fanto and Randall Atkinson and Michael Barnes and Vishwas Manral and Russ White and Tony Li and Manav Bhatia},
title = {{OSPFv2 HMAC-SHA Cryptographic Authentication}},
pagetotal = 14,
year = 2009,
month = oct,
abstract = {This document describes how the National Institute of Standards and Technology (NIST) Secure Hash Standard family of algorithms can be used with OSPF version 2's built-in, cryptographic authentication mechanism. This updates, but does not supercede, the cryptographic authentication mechanism specified in RFC 2328. {[}STANDARDS-TRACK{]}},
}
@misc{rfc5340,
series = {Request for Comments},
number = 5340,
@ -138,6 +183,38 @@
howpublished={Available at \url{https://grafana.com/grafana/}},
note={Accessed: 2023-07-17}
}
@misc{python,
url={https://www.python.org/},
urldate={2023-07-20},
author={Python Software Foundation},
title={Python},
howpublished={Available at \url{https://www.python.org/}},
note={Accessed: 2023-07-20}
}
@misc{qt6,
url={https://www.qt.io/product/qt6},
urldate={2023-07-20},
author={The Qt Company},
title={{Qt} 6},
howpublished={Available at \url{https://www.qt.io/product/qt6}},
note={Accessed: 2023-07-20}
}
@misc{graphviz,
url={https://graphviz.org/},
urldate={2023-07-20},
author={The Graphviz Authors},
title={Graphviz},
howpublished={Available at \url{https://graphviz.org/}},
note={Accessed: 2023-07-20}
}
@misc{czelanet,
url={https://www.czela.net/},
urldate={2023-07-20},
author={czela.net z.s.},
title={{czela.net}: Metropolitní síť v {Č}elákovicích a okolí},
howpublished={Available at \url{https://www.czela.net/}},
note={Accessed: 2023-07-20}
}
@misc{cacti,
url={https://www.cacti.net/},
urldate={2023-07-17},

Loading…
Cancel
Save