Router Naming Convention for sg.gs, 201702

Regular Expressions:

  1. ^(core)-\d+\.[a-z]+\d+\.([a-z]+\d+)\.sg\.gs$

Statistics:

Legend:

Green

 + Inferred identifier, true positive when evaluated against training data

Orange

 - Inferred identifier, false negative when evaluated against training data

Red

 ! Inferred identifier, false positive when evaluated against training data

Red

 x Inferred identifier, but contains part of IP address literal embedded in hostname
~ False negative, not matched
o No regex matched the interface, but the interface was the only interface in this suffix on the router
* A filter regex matched the interface

Evaluation against training data:

core|hk1
124.6.32.254+core-1.v10.hk1.sg.gs
103.14.244.99+core-1.v52.hk1.sg.gs
103.14.244.102+core-1.v54.hk1.sg.gs
124.6.32.22+core-2.v3.hk1.sg.gs
 
core|lax1
124.6.40.254+core-1.v10.lax1.sg.gs
124.6.40.21+core-1.v3.lax1.sg.gs
103.14.244.103+core-1.v54.lax1.sg.gs
103.14.244.110+core-1.v58.lax1.sg.gs
 
core|nyc1
124.6.44.254+core-1.v10.nyc1.sg.gs
124.6.44.21+core-1.v3.nyc1.sg.gs
103.14.244.111+core-1.v58.nyc1.sg.gs
103.14.244.112+core-1.v59.nyc1.sg.gs
 
core|sg1
203.175.175.128+core-1.v31.sg1.sg.gs
203.175.175.132+core-1.v33.sg1.sg.gs
 
core|sg1
103.14.244.169!core-1.v16.sg1.sg.gs
 
core|sg2
203.175.175.53+core-1.v3.sg2.sg.gs
203.175.175.131+core-1.v32.sg2.sg.gs
 
core|sg3
203.175.175.69+core-1.v3.sg3.sg.gs
203.175.175.130+core-1.v32.sg3.sg.gs
103.14.244.96+core-1.v51.sg3.sg.gs
103.14.244.98+core-1.v52.sg3.sg.gs
 
core|uk1
124.6.36.254+core-1.v10.uk1.sg.gs
124.6.36.21+core-1.v3.uk1.sg.gs
103.14.244.97+core-1.v51.uk1.sg.gs
103.14.244.113+core-1.v59.uk1.sg.gs
 
124.6.36.35~edge-2.uk1.sg.gs
124.6.36.18~edge-2.v3.uk1.sg.gs
 
203.175.175.101~edge-1.sg2.sg.gs
116.51.23.66~ntt-sg.sg.gs
 
103.14.244.165oas23936.v114.sg1.sg.gs
103.16.102.66epsilon.sgix.sg
 
103.14.246.131ooneasiahost.v108.sg1.sg.gs
 
195.66.226.38olinx-juniper.sg.gs
149.14.144.234sg.gs.demarc.cogentco.com
 
203.175.175.105oedge-1.sg3.sg.gs
 
203.175.175.107oedge-2.sg3.sg.gs