Re: looking for hostname router identifier validation

[Paul Ebersman]

lg.hadron> And 666 is Nero Caesar :-)

surfer> It's the US Army.

Same same... :)

Re: looking for hostname router identifier validation

[Scott Weeks]

--- large.hadron.colli...@gmx.com wrote:

And 666 is Nero Caesar :-)
--


It's the US Army.

scott

Re: looking for hostname router identifier validation

[Large Hadron Collider]

And 666 is Nero Caesar :-)

On 19-04-29 17 h 38, Chris Adams wrote:

Once upon a time, Valdis Klētnieks  said:

I wonder what year we'll get to a point where less than half of NANOG's
membership was around when UUNet was. We're probably there already.
And likely coming up on when less than half the people know what it
was, other than myth and legend

I still refer to ASes by companies that haven't existed in ages... 701
is UUNet, 3561 is MCI, 1 is BBN, etc. :)  I don't handle name changes
well (I also refer to one of the main roads where I live by a name it
hasn't had in close to 20 years).

Re: looking for hostname router identifier validation

[Large Hadron Collider]

I legit guffawed.

On 19-04-29 13 h 13, Eric Kuhnke wrote:

I would caution against putting much faith in the validity of
geolocation or site ID by reverse DNS PTR records. There are a vast
number of unmaintained, ancient, stale, erroneous or wildly wrong PTR
records out there. I can name at least a half dozen ISPs that have
absorbed other ASes, some of those which also acquired other ASes
earlier in their history, forming a turducken of obsolete PTR records
that has things with ISP domain names last in use in the year 2002.



On Mon, Apr 29, 2019 at 6:15 AM Matthew Luckie mailto:m...@luckie.org.nz>> wrote:

Hi NANOG,

To support Internet topology analysis efforts, I have been working on
an algorithm to automatically detect router names inside hostnames
(PTR records) for router interfaces, and build regular expressions
(regexes) to extract them.  By "router name" inside the hostname, I
mean a substring, or set of non-contiguous substrings, that is common
among interfaces on a router.  For example, suppose we had the
following three routers in the savvis.net 
domain suffix, each with two
interfaces:

das1-v3005.nj2.savvis.net 
das1-v3006.nj2.savvis.net 

das1-v3005.oc2.savvis.net 
das1-v3007.oc2.savvis.net 

das2-v3009.nj2.savvis.net 
das2-v3012.nj2.savvis.net 

We might infer the router names are das1|nj2, das1|oc2, and das2|nj2,
respectively, and captured by the regex:
^([a-z]+\d+)-[^\.]+\.([a-z]+\d+)\.savvis\.net$

After much refinement based on smaller sets of ground truth, I'm
asking for broader feedback from operators.  I've placed a webpage at
https://www.caida.org/~mjl/rnc/ that shows the inferences my algorithm
made for 2523 domains.  If you operate one of the domains in that
list, I would appreciate it if you could comment (private is probably
better but public is fine with me) on whether the regex my algorithm
inferred represents your naming intent.  In the first instance, I am
most interested in feedback for the suffix / date combinations for
suffixes that are colored green, i.e. appear to be reasonable.

Each suffix / date combination links to a page that contains the
naming convention and corresponding inferences.  The colored part of
each hostname is the inferred router name.  The green hostnames appear
to be correct, at least as far as the algorithm determined. Some
suffixes have errors due to either stale hostnames or incorrect
training data, and those hostnames are colored red or orange.

If anyone is interested in sets of hostnames the algorithm may have
inferred as 'stale' for their network, because for some operators it
was an oversight and they were grateful to learn about it, I can
provide that information.

Thanks,

Matthew

Re: looking for hostname router identifier validation

[Chris Adams]

Once upon a time, Valdis Klētnieks  said:
> I wonder what year we'll get to a point where less than half of NANOG's
> membership was around when UUNet was. We're probably there already.
> And likely coming up on when less than half the people know what it
> was, other than myth and legend

I still refer to ASes by companies that haven't existed in ages... 701
is UUNet, 3561 is MCI, 1 is BBN, etc. :)  I don't handle name changes
well (I also refer to one of the main roads where I live by a name it
hasn't had in close to 20 years).
-- 
Chris Adams 

Re: looking for hostname router identifier validation

[Valdis Klētnieks]

On Mon, 29 Apr 2019 16:16:06 -0500, Bryan Holloway said:

> I still see references to UUNet in some reverse PTRs.
>
> So, uh, yeah.

I wonder what year we'll get to a point where less than half of NANOG's
membership was around when UUNet was. We're probably there already.
And likely coming up on when less than half the people know what it
was, other than myth and legend

Re: looking for hostname router identifier validation

[Paul Ebersman]

ekuhnke> I would caution against putting much faith in the validity of
ekuhnke> geolocation or site ID by reverse DNS PTR records. There are a
ekuhnke> vast number of unmaintained, ancient, stale, erroneous or
ekuhnke> wildly wrong PTR records out there. I can name at least a half
ekuhnke> dozen ISPs that have absorbed other ASes, some of those which
ekuhnke> also acquired other ASes earlier in their history, forming a
ekuhnke> turducken of obsolete PTR records that has things with ISP
ekuhnke> domain names last in use in the year 2002.

That's because the version of perl required to run the perl script that
creates the ascii text PTR zone file is 4.x. perhaps? :)

bryan> I still see references to UUNet in some reverse PTRs.

bryan> So, uh, yeah.

The uu.net PTRs should mostly have been service machines, like
ns.uu.net, auth00.ns.uu.net (which horrifyingly do still
resolve). Routers should have been in alter.net, which I do still see in
traceroutes.

Re: looking for hostname router identifier validation

[Bryan Holloway]

On 4/29/19 3:13 PM, Eric Kuhnke wrote:
I would caution against putting much faith in the validity of 
geolocation or site ID by reverse DNS PTR records. There are a vast 
number of unmaintained, ancient, stale, erroneous or wildly wrong PTR 
records out there. I can name at least a half dozen ISPs that have 
absorbed other ASes, some of those which also acquired other ASes 
earlier in their history, forming a turducken of obsolete PTR records 
that has things with ISP domain names last in use in the year 2002.


I still see references to UUNet in some reverse PTRs.

So, uh, yeah.

Re: looking for hostname router identifier validation

[Eric Kuhnke]

I would caution against putting much faith in the validity of geolocation
or site ID by reverse DNS PTR records. There are a vast number of
unmaintained, ancient, stale, erroneous or wildly wrong PTR records out
there. I can name at least a half dozen ISPs that have absorbed other ASes,
some of those which also acquired other ASes earlier in their history,
forming a turducken of obsolete PTR records that has things with ISP domain
names last in use in the year 2002.



On Mon, Apr 29, 2019 at 6:15 AM Matthew Luckie  wrote:

> Hi NANOG,
>
> To support Internet topology analysis efforts, I have been working on
> an algorithm to automatically detect router names inside hostnames
> (PTR records) for router interfaces, and build regular expressions
> (regexes) to extract them.  By "router name" inside the hostname, I
> mean a substring, or set of non-contiguous substrings, that is common
> among interfaces on a router.  For example, suppose we had the
> following three routers in the savvis.net domain suffix, each with two
> interfaces:
>
> das1-v3005.nj2.savvis.net
> das1-v3006.nj2.savvis.net
>
> das1-v3005.oc2.savvis.net
> das1-v3007.oc2.savvis.net
>
> das2-v3009.nj2.savvis.net
> das2-v3012.nj2.savvis.net
>
> We might infer the router names are das1|nj2, das1|oc2, and das2|nj2,
> respectively, and captured by the regex:
> ^([a-z]+\d+)-[^\.]+\.([a-z]+\d+)\.savvis\.net$
>
> After much refinement based on smaller sets of ground truth, I'm
> asking for broader feedback from operators.  I've placed a webpage at
> https://www.caida.org/~mjl/rnc/ that shows the inferences my algorithm
> made for 2523 domains.  If you operate one of the domains in that
> list, I would appreciate it if you could comment (private is probably
> better but public is fine with me) on whether the regex my algorithm
> inferred represents your naming intent.  In the first instance, I am
> most interested in feedback for the suffix / date combinations for
> suffixes that are colored green, i.e. appear to be reasonable.
>
> Each suffix / date combination links to a page that contains the
> naming convention and corresponding inferences.  The colored part of
> each hostname is the inferred router name.  The green hostnames appear
> to be correct, at least as far as the algorithm determined.  Some
> suffixes have errors due to either stale hostnames or incorrect
> training data, and those hostnames are colored red or orange.
>
> If anyone is interested in sets of hostnames the algorithm may have
> inferred as 'stale' for their network, because for some operators it
> was an oversight and they were grateful to learn about it, I can
> provide that information.
>
> Thanks,
>
> Matthew
>

Re: Bing news feeds stale for 5 days (api.cognitive.microsoft.com)

[Valdis Klētnieks]

On Mon, 29 Apr 2019 12:35:23 -0400, John Von Essen said:
> I work with a major search affiliate partner, and starting this morning news 
> feeds from api.cognitive.microsoft.com 
> were coming in stale, nothing new in the past 5 days. 

Wait, what?  So yesterday, it returned news for Sunday, but this morning, it's
only returning news from Wed or before? (It's one thing to fail to have updates,
rolling back already done updates takes a more convoluted failure mode...)

Bing news feeds stale for 5 days (api.cognitive.microsoft.com)

[John Von Essen]

Any Bing engineers on here?

I work with a major search affiliate partner, and starting this morning news 
feeds from api.cognitive.microsoft.com  
were coming in stale, nothing new in the past 5 days. However, this was only 
effecting API calls originating outside the USA.

In the US, api.cognitive.microsoft.com  
returns fresh news, but globally through GeoDNS, that URL resolves to different 
IPs, those IPs (Europe, Singapore, etc.,.) are returning 5 day old news.

Sorry if this is slightly off-topic, but we dont have a good PoC at Bing for 
this… I figure there is a very good chance someone here could escalate.

Thanks
John

Call for Presentations ICANN65 Marrakesh - June 24, 2019

[Jacques Latour]

Hi all!



Call for Presentations ICANN65 Marrakesh



 Call for Presentations

  39th TechDay

  at ICANN 65

 in Marrakesh



The ICANN Tech Working Group is again planning a technical workshop at

the ICANN 65 meeting in Marrakesh on Monday 2019-06-24, Blocks 3-5,

starting 13:30.



The TechDay workshop has been a part of ICANN meetings since 2006 and

has provided a forum for both experienced and new people to meet,

present and discuss technical topics related to registry and DNS work

and security.



We are specially interested in:



1. IDN



2. Disaster Planning and Mitigation



3. Techniques for fighting abuse



4. DNSSEC In particular: Getting Africa signed)



5. RDAP - what is it, implementing, authentication, challenges



6. IDNA2008 - emoji



7. In addition, we welcome suggestions for additional topics.





If you are interested in presenting, please email

ccnso-tech...@icann.org



We hope that you can join us and request that you disseminate this

Request to other lists where it might of interest.



Greetings,

Jacques, on behalf of the TechDay program Committee

looking for hostname router identifier validation

[Matthew Luckie]

Hi NANOG,

To support Internet topology analysis efforts, I have been working on
an algorithm to automatically detect router names inside hostnames
(PTR records) for router interfaces, and build regular expressions
(regexes) to extract them.  By "router name" inside the hostname, I
mean a substring, or set of non-contiguous substrings, that is common
among interfaces on a router.  For example, suppose we had the
following three routers in the savvis.net domain suffix, each with two
interfaces:

das1-v3005.nj2.savvis.net
das1-v3006.nj2.savvis.net

das1-v3005.oc2.savvis.net
das1-v3007.oc2.savvis.net

das2-v3009.nj2.savvis.net
das2-v3012.nj2.savvis.net

We might infer the router names are das1|nj2, das1|oc2, and das2|nj2,
respectively, and captured by the regex:
^([a-z]+\d+)-[^\.]+\.([a-z]+\d+)\.savvis\.net$

After much refinement based on smaller sets of ground truth, I'm
asking for broader feedback from operators.  I've placed a webpage at
https://www.caida.org/~mjl/rnc/ that shows the inferences my algorithm
made for 2523 domains.  If you operate one of the domains in that
list, I would appreciate it if you could comment (private is probably
better but public is fine with me) on whether the regex my algorithm
inferred represents your naming intent.  In the first instance, I am
most interested in feedback for the suffix / date combinations for
suffixes that are colored green, i.e. appear to be reasonable.

Each suffix / date combination links to a page that contains the
naming convention and corresponding inferences.  The colored part of
each hostname is the inferred router name.  The green hostnames appear
to be correct, at least as far as the algorithm determined.  Some
suffixes have errors due to either stale hostnames or incorrect
training data, and those hostnames are colored red or orange.

If anyone is interested in sets of hostnames the algorithm may have
inferred as 'stale' for their network, because for some operators it
was an oversight and they were grateful to learn about it, I can
provide that information.

Thanks,

Matthew


signature.asc
Description: PGP signature