Router Naming Convention for lilynet.work

Router Naming Convention for lilynet.work

Regular Expressions:

1.

^[a-z]+\.([a-z]{3})\d+\.([a-z]{2})\.[a-z]{4}\.routes\.lilynet\.work$

-- iata, cc

-- 4 TPs

Statistics:

Unique Geocodes: 4
Positive Predictive Value: 1.000
True Positives (green): 4
False Positives (red): 0
IP literals extracted (red): 0
False Negatives, unmatched (orange): 0
Interfaces with an unknown location (purple): 1

Legend:

Bold		Apparent custom geocode
Green	+	Extracted apparent geocode, true positive when evaluated against training data
Orange	~	False negative, apparent geocode unmatched
Purple	?	Extracted geocode, but not in dictionary
Red	!	Extracted apparent geocode, false positive when evaluated against training data

Geocodes:

Hint	Location	Closest VP
prc\|ap		abz	180ms
par\|fr	Paris, IDF, FR	ory	3ms
lon\|uk	London, ENG, GB	ams	7ms
las\|us	Las Vegas, NV, US	san	11ms
sea\|us	Seattle, WA, US	san	43ms

Evaluation against training data:

			par\|fr: ory 3ms, id 256149
2a12:3fc2:aa10::2	+	[1]	axium.par1.fr.core.routes.lilynet.work

			lon\|uk: ams 7ms, id 480775
2a12:3fc2:aa10::1	+	[1]	hikari.lon1.uk.core.routes.lilynet.work

			las\|us: san 11ms, id 98384
2a12:3fc2:aa11::1	+	[1]	iris.las1.us.core.routes.lilynet.work

			sea\|us: san 43ms, id 315021
2a12:3fc2:aa11::2	+	[1]	moeix.sea1.us.edge.routes.lilynet.work

			abz 180ms, id 278379
2a12:3fc2:aa10:cafe::1	?	[1]	reunion.prc1.ap.core.routes.lilynet.work

			san 11ms, id 54273
2605:6400:20:1c27::1			iris.lilynet.work