There have been a number of questions that have been fielded wrt the EP.NET domain and traceroute failures within that domain. For your edification, here is a brief note on the EP.NET domain.
EP.NET operated as a service by the RA for exchange points around the globe. Any exchange point may become part of the EP.NET domain. The default assignment algorithm follows. The next level identifies the specific exchange. The next level identifies the attaching organization.
So, the default for BillsBait&SushiShop (BBSS) at MAE-WEST is:
bbss.mae-west.ep.net
When BBSS attachs to the AADS NAP, the default name is:
bbss.aads.ep.net
Selection of provider specific names is encouraged. So when BBSS gets around to it, they may change the names to something like this:
mae-west.bbss.org aads.bbss.org
Bill, Personally I think that this is actually a value-subtracted service, as the EP.NET organisation does not run the named boxes, or the exchange points. It would be much more helpfull the the interfaces that faces the NAP and another provider where following each providers naming conventions, and had a domain-name that would point the users to the organisation that actually operates the boxes. You can still provide the service of running the nameservice. --Peter
There have been a number of questions that have been fielded wrt the EP.NET domain and traceroute failures within that domain. For your edification, here is a brief note on the EP.NET domain.
Personally I think that this is actually a value-subtracted service, as the EP.NET organisation does not run the named boxes, or the exchange points.
It would be much more helpfull the the interfaces that faces the NAP and another provider where following each providers naming conventions, and had a domain-name that would point the users to the organisation that actually operates the boxes.
You can still provide the service of running the nameservice.
I would tend to agree with this. I've had a number of customers ask me "what the heck is this ep.net?" Dave -- Dave Siegel Director of Engineering, Network 99, Inc. http://www.net99.net/ (602)249-1083 Network Ops http://www.rtd.com/~dsiegel/ (520)318-0696 Tucson Location
It would be much more helpfull the the interfaces that faces the NAP and another provider where following each providers naming conventions, and had a domain-name that would point the users to the organisation that actually operates the boxes.
I would tend to agree with this. I've had a number of customers ask me "what the heck is this ep.net?"
No argument with either of these premises. However, there are some who don't have a clue and are attaching. They don't know what name they want and so this provides a default. The default can be changed at any time. I don't have to make up some arbitrary name, and the link gets identified. The posting was to let others know what was occuring and why. People are encouraged to use FQDN's from thier own zones. If they can't or won't, this is a default. --bill
Bill,
Personally I think that this is actually a value-subtracted service, as the EP.NET organisation does not run the named boxes, or the exchange points.
It would be much more helpfull the the interfaces that faces the NAP and another provider where following each providers naming conventions, and had a domain-name that would point the users to the organisation that actually operates the boxes.
Yes, that is the desired goal, however some sites are not willing or able to do so, so there is a default case where a name is available. (There are some exchange points where no forward is registered, which can be a hassel)
You can still provide the service of running the nameservice.
Thanks.
--Peter
-- --bill
participants (3)
-
bmanning＠ISI.EDU -
Dave Siegel -
Peter Lothberg