[1224] in Commercialization & Privatization of the Internet
Re: ANS mid-level agreements [was "Network World "The Vision of..."]
daemon@ATHENA.MIT.EDU (Ittai Hershman)
Tue Aug 27 14:24:30 1991
Date: Tue, 27 Aug 91 14:00:21 EDT
From: Ittai Hershman <ittai@shemesh.ans.net>
To: jbvb@ftp.com
Cc: com-priv@uu.psi.com, lear@turbo.bio.net
In-Reply-To: Your message of Tue, 27 Aug 91 10:00:29 -0400
Discussion of mid-levels which connect to one another, or via other
backbones is conspicuously absent from the 'Gateway Attachment
Agreement'. Does ANS have any policy you're willing to state
concerning this, or is it all supposed to be dealt with through
'Attachment Bandwidth'?
If I understand your question correctly, the answer is that ANS has
no problem with backdoor connections -- i.e. one midlevel connecting
to another to ANS. A site connected to a backdoor midlevel, from
ANS's view, simply looks like a site connected to the ANS connected
midlevel. The technical details which explain this view are explained
in the paper I announced will be made available next week.
In the specific case of FTP Software, a NEARnet customer: at present
you can pass RE-only traffic over NEARnet to the NSFnet, and CO
traffic over NEARNET to ALTERnet. ALTERnet is also attached to the
NSFnet, but again, they can only pass your RE traffic to the NSFnet.
Presumably, NEARnet and ALTERnet have routing mechanisms in place
which keep CO traffic from the NSFnet.
If either:
NEARnet signs a Gateway or Cooperative agreement, and/or
Alternet signs a Gateway or Cooperative agreement, then
FTP Software can send commercial traffic over the ANSnet backbone. If
neither do, then FTP Software is restricted to only sending RE traffic
on the backbone.
-Ittai
