Router Naming Convention for ipns.com, 201207

Regular Expressions:

  1. ^[^\.]+\.(core1\.[a-z]+)\.ipns\.com$

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:

core1.portland
66.78.83.6+ve1.core1.portland.ipns.com
216.162.207.60+ve254.core1.portland.ipns.com
208.110.128.52ve255.core1.portland.com
 
core1.saltlakecity
208.110.128.9+ve1.core1.saltlakecity.ipns.com
208.110.128.41+ve254.core1.saltlakecity.ipns.com
208.110.128.49+ve255.core1.saltlakecity.ipns.com
69.22.153.66as12284.ae0.cr1.slc1.us.nlayer.net
 
core1.seattle
216.162.207.65+fe-3-2.core1.seattle.ipns.com
208.110.128.44+ve254.core1.seattle.ipns.com
216.162.207.58+ve255.core1.seattle.ipns.com
 
216.162.207.57oge-1-0-0-888.ebr1.seattle.ipns.com
 
216.162.207.59oge-0-1-0-888.ebr1.portland.ipns.com
 
216.162.207.66ofe-5-7.core1.seattle2.ipns.com
209.95.37.11pdx-pm01.navi.net
216.162.207.129ve4.core1.seattle.sitespecific.net