Router Naming Convention for gpcom.net, 201708

Router Naming Convention for gpcom.net, 201708

Regular Expressions:

^[a-z]+\d+\.(core1\.[a-z]+)\.gpcom\.net$

Statistics:

Training routers with at least two clustered interfaces: 3
Positive Predictive Value: 1.000
True Positives (green): 6
False Positives (red): 0
IP literals extracted (red): 0
False Negatives, identifier extracted (orange): 0
False Negatives, not matched: 2
Training routers with a single interface in suffix: 1

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.blar
208.175.141.250	+	bndl10.core1.blar.gpcom.net
208.175.141.213	+	bndl200.core1.blar.gpcom.net
208.175.141.245	~	gpc-208-175-141-245-ne.gpcom.net
208.175.141.30	~	gpc-208-175-141-30-ne.gpcom.net

		core1.blfd
208.175.141.246	+	bndl100.core1.blfd.gpcom.net
208.175.141.217	+	bndl300.core1.blfd.gpcom.net

		core1.grnt
208.175.141.206	+	bndl10.core1.grnt.gpcom.net
208.175.141.214	+	bndl200.core1.grnt.gpcom.net

72.8.246.174	o	gpc-72.8.246.174-ne.gpcom.net
69.2.15.10		omaha7604-gi3-3-99.pnpt.com