Hi Arturo,
> One assumption that we have is that the Peering Database (in this case
> PeeringDB but it could be any) is the canonical source of most of the
> information that you need to set up a peering session.
While I understand the general direction of your remarks, I find the idea of
rely
Dear Job Snijders,
The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request.
grow Session 1 (1:30 requested)
Wednesday, 24 July 2024, Session III 1530-1700 America/Vancouver
Room Name: Plaza B [Breakout 3
Matthias
One assumption that we have is that the Peering Database (in this case
PeeringDB but it could be any) is the canonical source of most of the
information that you need to set up a peering session.
In the case of RS, all that information is already there and there is no
need to add it agai
Hi Jenny, all,
while I understand the theoretical reasoning behind your answer, I would like
to discuss a few practical issues to clarify the way forward for route server
support before adoption.
(1) Integrating route server support requires minimal effort and the changes
are not specific to r
Rather than attempt to spoon-feed a reader with a long list of detailed tasks
that is most likely incomplete and will be quickly overtaken by subsequent
changes in the operational environment, it's more useful to elevate the level
of the document and describe what these operational security meas
> On Jun 28, 2024, at 08:46, Tobias Fiebig
> wrote:
> Nick and I cut down the draft significantly, to focus on the essentials.
Yes, this draft and the prior one are, essentially, very different documents.
I think the prior draft _looked_ more complete, but was, for the reasons cited,
not a
