Reading through that, there are some definitions I think could be done
better.
In section 4.2 you have:
Downstream:
In a direct relationship between two ASes the one receiving upstream
from the other. (See: [RFC9234], also known as the customer in a
customer-provider relationship.)
Upstream:
Moin,
(Repost to list as my original reply had a wrong From:)
On Thu, 2024-10-03 at 07:57 +0300, Saku Ytti wrote:
> On Thu, 3 Oct 2024 at 07:04, Jeff Behrns via NANOG
> wrote
>
> > This seems like a total misuse of the RFC framework / process and
> > more a grab at publicity, but I'll play alon
On Thu, 3 Oct 2024 at 07:04, Jeff Behrns via NANOG wrote
> This seems like a total misuse of the RFC framework / process and more a grab
> at publicity, but I'll play along...bogon. You should include the term
> "bogon". Someday when I'm done keeping actual production networks alive, I
> may
This seems like a total misuse of the RFC framework / process and more a grab
at publicity, but I'll play along...bogon. You should include the term
"bogon". Someday when I'm done keeping actual production networks alive, I may
wade into the morass of IETF & IEEE and work on trimming the fat..
Moin,
I have been working on a document listing terms & abbreviations used in
the context of BGP/Global Routing Operations (leftovers from the cut-
down of the attempts to update documents in BCP194):
https://datatracker.ietf.org/doc/draft-fiebig-grow-routing-ops-terms/02/
I just setup a web-form
5 matches
Mail list logo
