> > Why not publish RFC8805 Geofeed directly in inetnum remarks section?
>
> for some flat fan out last kilometer providers that could be the
> inetnum: object from hell. there are global providers which segment
> large prefixes over diverse areas. etc.
>
> i doubt the rpsl providers would like
On Fri, 11 Sep 2020, Matt Erculiani wrote:
Linking relevant past thread about devices that don't alert for
emergencies and, of course, a heated debate on if they should:
https://mailman.nanog.org/pipermail/nanog/2019-March/199721.html
Yep. I'm not naive. I keep saying something, because one
On Sat, Sep 12, 2020 at 4:43 PM Randy Bush wrote:
> hi ca
>
>
>
> > I gave your I-D a try in the real world, and it does not work with a
>
> > major player.
>
>
>
> i.e. arin and radb, your region, which does not do rpsl as others do.
>
> we know this, which is why the OP $subjest was
>
>
>
>
hi ca
> I gave your I-D a try in the real world, and it does not work with a
> major player.
i.e. arin and radb, your region, which does not do rpsl as others do.
we know this, which is why the OP $subjest was
"how would draft-ymbk-opsawg-finding-geofeeds work in noam?"
> I thought you might
yang,
> Why not publish RFC8805 Geofeed directly in inetnum remarks section?
for some flat fan out last kilometer providers that could be the
inetnum: object from hell. there are global providers which segment
large prefixes over diverse areas. etc.
i doubt the rpsl providers would like
On Fri, Sep 11, 2020 at 1:48 PM Randy Bush wrote:
>
> would folk familiar with the north american RIR and IRR registries be
> kind enough to suggest how this might adapt? thanks.
>
Hi Randy,
Why not publish RFC8805 Geofeed directly in inetnum remarks section?
Then there is no more need to host
On Sat, Sep 12, 2020 at 1:13 PM Randy Bush wrote:
> hi camron
>
> sad to say, the days of faxing around number assigments have passed.
> the kiddie googlers who wrote the geofeeds rfc probably have not even
> seen a fax machine. they just did not like having a hundred gnomes in
> the basement
hi camron
sad to say, the days of faxing around number assigments have passed.
the kiddie googlers who wrote the geofeeds rfc probably have not even
seen a fax machine. they just did not like having a hundred gnomes in
the basement dealing with everybody's formats. given silicon valley
housing
>> Does anyone know the scope on why we have 2 names for this ?
>
> SPRING is the IETF working group name - Source Packet Routing in Networking
> Segment Routing is under SPRING
Yeah, sorry, this was my fault. Gotta have a catchy name.
As to "SPRINGv4" as others have said, this is not a
Isn’t this a better topic for CNet as opposed to NANOG?
Chuck
From: NANOG On Behalf Of
ITechGeek
Sent: Friday, September 11, 2020 4:12 PM
To: nanog@nanog.org
Subject: Re: Wildfires: Reminder smart devices don't include emergency warnings
while streaming
At least cell phones have a
On Fri, Sep 11, 2020 at 1:49 PM Randy Bush wrote:
> would folk familiar with the north american RIR and IRR registries be
>
> kind enough to suggest how this might adapt? thanks.
>
>
>
> A new version of I-D, draft-ymbk-opsawg-finding-geofeeds-02.txt
>
> has been successfully submitted by Randy
Don, your answer to Eric's valid point is open to broad interpretation -
what is your point, exactly?
On Sat, Sep 12, 2020 at 3:24 AM Don Gould wrote:
> Eric they have the same issues in Australia. You might want to join
> aunog, if you haven't already, I'm sure you'll find endorsement for
12 matches
Mail list logo
