<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<style>
html {
line-height: 1.2;
font-family: serif;
font-size: 0.9em;
color: black;
background-color: white;
}
body {
margin: 0;
margin-right: auto;
max-width: 36em;
padding: 1em;
hyphens: auto;
overflow-wrap: break-word;
text-rendering: optimizeLegibility;
font-kerning: normal;
}
@media print {
body {
background-color: transparent;
color: black;
font-size: 11pt;
}
p, h2, h3 {
orphans: 3;
widows: 3;
}
h2, h3, h4 {
page-break-after: avoid;
}
}
p {
margin: 1em 0;
}
a {
color: black;
}
a:visited {
color: black;
}
img {
max-width: 100%;
}
h1, h2, h3, h4, h5, h6 {
margin-top: 1.4em;
}
h5, h6 {
font-size: 1em;
font-style: italic;
}
h6 {
font-weight: normal;
}
ol, ul {
padding-left: 1.7em;
margin-top: 1em;
}
li > ol, li > ul {
margin-top: 0;
}
blockquote {
margin: 0.5em;
padding-left: 0.5em;
border-left: 2px solid #e6e6e6;
color: #444;
}
code {
font-family: 'Lucida Console', monospace;
font-size: 95%;
margin: 0;
}
pre {
margin: 1em 0;
overflow: auto;
}
pre code {
padding: 0;
overflow: visible;
overflow-wrap: normal;
}
.sourceCode {
background-color: transparent;
overflow: visible;
}
hr {
background-color: black;
border: none;
height: 1px;
margin: 1em 0;
}
table {
margin: 1em 0;
border-collapse: collapse;
width: 100%;
overflow-x: auto;
display: block;
font-variant-numeric: lining-nums tabular-nums;
}
table caption {
margin-bottom: 0.75em;
}
tbody {
margin-top: 0.5em;
border-top: 1px solid black;
border-bottom: 1px solid black;
}
th {
border-top: 1px solid black;
padding: 0.25em 0.5em 0.25em 0.5em;
}
td {
padding: 0.125em 0.5em 0.25em 0.5em;
}
header {
margin-bottom: 4em;
text-align: center;
}
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
q { quotes: "„" "”" "»" "«"; }
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
</head>
<body>
<p>Hello Douglas,</p>
<p>just a really fast response, we aren’t going to implement BGP over
QUIC at all, at least when TLS is a required part of QUIC.</p>
<p>There are some thoughts about BGP 5 being encoded as CBOR and sent
over something like QUIC, anyway it doesn’t make any sense to introduce
QUIC to BGP now.</p>
<p>Maria</p>
<p>On Thu, May 16, 2024 at 09:45:56AM -0300, Douglas Fischer wrote:</p>
<blockquote>
<p>I’m not a programmer, and I know almost nothing about it…</p>
<p>But reading this thread, I remembered this draft about BGP-over-QUIC.
https://datatracker.ietf.org/doc/draft-retana-idr-bgp-quic/</p>
<p>I’m not sure what I’m going to say, but I have the impression that
the session closure control method that will be chosen may have
something to do with this BoQ idea.</p>
<p>I don’t even know if what I’m saying makes any sense or not. But if
you do, it may be something that you have to take into consideration
when choosing the method.</p>
<p>And besides, there are many other “ifs”… We don’t even know if this
Draft will actually become an RFC. And if it becomes RFC, we don’t even
know if it will have traction. We also don’t know if the IBRD project
will adhere to this protocol, etc…</p>
<p>But, I thought it was opportune to mention.</p>
<p>Em qui., 16 de mai. de 2024 às 07:59, Ondrej Zajicek <a
href="mailto:santiago@crfreenet.org"
class="email">santiago@crfreenet.org</a> escreveu:</p>
<blockquote>
<p>On Wed, May 15, 2024 at 06:37:18PM +0200, Job Snijders via Bird-users
wrote:</p>
<blockquote>
<p>Dear BIRD people,</p>
<p>On most systems RFC 896 TCP congestion control is used, also known as
“Nagle’s algorithm”. This algorithm is intended to help coalesce
consecutive small packets from userland applications (like BIRD) into a
single larger TCP packet. The idea being it reduces bandwidth because
there is less TCP overhead if data is bundled into fewer packets. … I
think using TCP_NODELAY is interesting to consider, because it seems
sensible to try to deliver BGP messages as fast as possible. OpenBGPD
and FRR set the TCP_NODELAY socket option.</p>
</blockquote>
<p>Hi</p>
<p>Yeah, i think that using TCP_NODELAY for BGP makes sense, considering
there is already non-trivial framing and we write individual BGP
messages with one write().</p>
<p>– Elen sila lumenn’ omentielvo</p>
<p>Ondrej ‘Santiago’ Zajicek (email: santiago@crfreenet.org) “To err is
human – to blame it on a computer is even more so.”</p>
</blockquote>
<p>– Douglas Fernando Fischer Engº de Controle e Automação</p>
</blockquote>
<p>– Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.</p>
</body>
</html>