*NANOG 83 Kicks-Off on Monday *
Register now to Connect Virtually +/or In-Person!
*Connecting with us virtually for NANOG 83? *
*WHERE TO WATCH:* Go to nanog.org/nanog83 to watch incredible
presentations by industry leaders, participate in real-time Q + A sessions,
networking events, expo,
*NANOG 83 Kicks-Off on Monday *
Register now to Connect Virtually +/or In-Person!
*Connecting with us virtually for NANOG 83? *
*WHERE TO WATCH:* Go to nanog.org/nanog83 to watch incredible
presentations by industry leaders, participate in real-time Q + A sessions,
networking events, expo,
> On Oct 26, 2021, at 9:25 AM, Bryan Fields wrote:
>
> Can you explain how it would work? Say you have a root server operator who
> starts messing up, is there any ability to remove them?
You might look at
https://www.icann.org/en/system/files/files/rssac-037-15jun18-en.pdf. Yes,
there is
On Tue, Oct 26, 2021 at 04:58:20PM -0700, Randy Bush wrote:
> i run a FORT RPKI relying party instance. i am looking for some
> visibility into its operation.
>
> is it up: both ways, fetching and serving routers?
>
> from what CAs has it pulled, how recently and frequently with
> what
> On Oct 21, 2021, at 12:47 PM, William Herrin wrote:
>
> On Thu, Oct 21, 2021 at 12:15 PM John Levine wrote:
>> But it's definitely worth a visit, particularly if Len Kleinrock is around
>> to give his spiel about "LO" the first message.
>>
>> https://uclaconnectionlab.org/internet-museum/
Dear nanog members,
We hope this message finds you safe and well.
Japan Network Information Center (JPNIC) is conducting a survey about the
situation of the implementation of security technologies.
The Internet is spreading in a coordinated manner thanks to its openness and
autonomous,
‐‐‐ Original Message ‐‐‐
On Tuesday, October 26th, 2021 at 21:17, Shawn
wrote:
> Is it standard practice to accept more specifics (append IPv4 "le /24" and
> IPv6 "le /48")?
There was an blog post written somewhere (unfortunately I cannot locate it)
that urged caution as to how you
Thanks, i'm happy that my RIR is RIPE. I hope other RIRs will make
auto-renew as well.
On Tue, Oct 26, 2021 at 4:30 PM Dale W. Carder wrote:
> Thus spake Edvinas Kairys (edvinas.em...@gmail.com) on Tue, Oct 26, 2021
> at 10:11:14AM +0300:
> >
> > Also, about ROA expirations is it possible to
> On 20211027, at 09:26, Lukas Tribus wrote:
>
> On Wed, 27 Oct 2021 at 08:47, Mark Tinka wrote:
>>
>> On 10/27/21 01:58, Randy Bush wrote:
>>> my old DRL RP instances produce MRTG graphs etc of the CA
>>> fetching side, though nothing on the rpki-
On Wed, 27 Oct 2021 at 08:47, Mark Tinka wrote:
>
> On 10/27/21 01:58, Randy Bush wrote:
> > my old DRL RP instances produce MRTG graphs etc of the CA
> > fetching side, though nothing on the rpki-rtr side.
>
> Randy, I actually have an ongoing discussion with the Fort developers
> about this
On 10/27/21 01:58, Randy Bush wrote:
i run a FORT RPKI relying party instance. i am looking for some
visibility into its operation.
is it up: both ways, fetching and serving routers?
from what CAs has it pulled, how recently and frequently with
what success?
what routers is it
Hi Shawn,
On 10/26, Shawn wrote:
>
>
> IRR questions:
> How do most large networks maintain (automate) their IRR records?
> Is it standard practice to accept more specifics (append IPv4 "le /24" and
> IPv6 "le /48")?
> Or is it expected to have one IRR route per BGP announcement?
>
We (37271)
12 matches
Mail list logo
