Colocation continues to be a challange.
Both AADS and PAC*BELL have a similiar sort of dip around July 24th. Perhaps there needs to be a more holistic traffic analysis.
Curtis asks if there is any word from DEC on the line blocking issue. Steve Feldman says that he has heard nothing.
Curtis asks AADS about egress loading being full being counted as loss. Andy says that there is no egress loading that is high enough to cause loss right now. However, it is possible this might have an impact.
Peter Lothberg asks Is there any support from the NAP operations to keep customer from sending traffic to another connection where no peering agreement exists?
Sprint NAP says that there is a general provision in their documents that permits them to disconnect anyone that is causing a problem for any other customer.
AADS says that there is a requirement for a PVC, which limits this problem. PAC*BELL agrees.
Peter Lothberg says There are cases where folks are setting default to me.
PAC*BELL says that then the situation is no longer mutual and they can take the connection now.
Steve Feldman says that usually getting folks together is adequate. However, he can also insert features into the Gigaswitch to filter this on a special case-by-case basis.
Enke from MCI says that MCI would like to have such filters installed if possible. Steve says that MFS does not like to do this, but can. Steve Schnell says that Sprint can do this as well, but it would have to be investigated before a specific change could be made.
Enke asks what specific remedies exist in contracts to prevent this type of abuse. Sprint does not know if this is the case, but would like to see any proposed language so they could consider it.
Cathy from @HOME has been playing phone tag for months with AADS to get details. AADS will help her after this session.
It has been suggested that port filtering be used instead of MAC filtering. Both Sprint and MFS agree this is probably the best option.