[118873] in North American Network Operators' Group
Re: Peering in Latin America
daemon@ATHENA.MIT.EDU (Malte von dem Hagen)
Sun Nov 1 09:59:02 2009
Date: Sun, 01 Nov 2009 15:58:01 +0100
From: Malte von dem Hagen <mvh@hosteurope.de>
To: isabel dias <isabeldias1@yahoo.com>
In-Reply-To: <304331.41010.qm@web52603.mail.re2.yahoo.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Reply-To: mvh@hosteurope.de
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE79BEC9816BBA2EA8DF3D7A6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
G'day,
Am 01.11.2009 13:24 Uhr schrieb isabel dias:
> peering in the IX's a.k.a peering -> unless is a payed service =3Dpriva=
te-peering! at the exchange
despite full sentences are clearly better to understand, the term "_priva=
te_
peering" does not necessarily include payments. It just means that the
interconnect is not realized via a _public_ infrastructure as an IX's net=
work
e.g., but via _discrete_ p2p links, for example.
Paid services are often referred to as "transit" or sometimes even "trans=
it
light" (meaning "my network and the ones of my customers", german Telekom=
uses
this) or explicitly "_paid_ peering" (which is a misuse of the word peeri=
ng,
imho, as e.g. used by Arcor/Vodafone).
At least over here the nomenclature is like that ;-)
Kind regards,
=2Em
--------------enigE79BEC9816BBA2EA8DF3D7A6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkrtof4ACgkQLuLG3RMdjsK/ngCdF2YmHVSPp2fTgr1BY1T+yRAV
VLAAoJLMBaZk9cgTbF5l2vVIk8bnfZVz
=2AnT
-----END PGP SIGNATURE-----
--------------enigE79BEC9816BBA2EA8DF3D7A6--
