[169331] in North American Network Operators' Group

home	help	back	first	fref	pref	prev	next	nref	lref	last	post

Re: question about AS relationship

daemon@ATHENA.MIT.EDU (Mark Tinka)
Fri Feb 21 00:51:30 2014

From: Mark Tinka <mark.tinka@seacom.mu>
To: refresh.lsong@gmail.com
Date: Fri, 21 Feb 2014 07:50:38 +0200
In-Reply-To: <5306E630.3090604@gmail.com>
Cc: nanog@nanog.org
Reply-To: mark.tinka@seacom.mu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

--nextPart2461294.ccW0HjgLSo
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Friday, February 21, 2014 07:37:52 AM Song Li wrote:

> Thanks. In order to prevent route leaking, this
> imformation should be provided to providers.

Route leaking is not only from customers-to-providers. It=20
can also be from providers-to-providers (and from peers-to-
peers).

The majority of leaks I've seen in the past have been=20
possible because some inter-provider links have not been=20
filtered correctly, i.e., they are providing (unknown)=20
transit where they would only be peering.

It is not uncommon to see more relaxed filtering between=20
providers/peers, e.g., AS_PATH-based only, max-prefix-based=20
only, e.t.c., but please don't send these out to anyone else=20
besides your customers unless the ultimate relationship=20
calls for it. Of course, one can't guarantee that the=20
customers you send this to won't leak it to their own=20
transit providers.

Bottom line, chasing route leaks can be a full time job.

> but another question, should the AS relationships between
> customer and its other neighbors (downstrem/peer/another
> provider)  be private?

What do you mean, in terms of how they connect or in terms=20
of the business relationship?

I don't think it matters either way. The common peering,=20
filtering and re-announcement rules apply.

Mark.

--nextPart2461294.ccW0HjgLSo
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iQIcBAABAgAGBQJTBukzAAoJEGcZuYTeKm+GX7AQAIWAt9rImVgCbOkPPbzXBVE7
CqkDL8CIBV/2L0uoMfIPrFhTqzY00d1CmLh/BWl9Py0g5J3Ug/ijmU75NbjxqscS
supX65KZvQRyks07UcNZDHXX0L8zIgikWSPRWzmJOQvCCcn2ARSfEeXAYp1ggD9G
fNIRFzONY7V7Eetvsi9I9vsuoFMqpmoRqDWqc6btyEO4+iJR5oJM13s3vCYRg75j
8U4T8Ktok9TNQpKOUv1SwWxCWz8fvJ2sWY98D68KVywK7hZq7vQ0bJysqzVT//pk
MGeQVETy2oHYIMTrli+oLeatD4zL4pab3hYSglg6OrM71PeA6OWMGWSPKrEyuXFP
fam4ZY1wk7lHSqm9hKCFhI0cAX18vccez0Ap/tR3MSmpPPGMhracw9Nx5ZRGHBex
bP3ueHgtXPyP0Ufh9iLSVES7hWy5+OUclGKFzK0K4ubxZl17pkZRJ9nJfQ27MVlm
it/X13b9UxVRvpUSl03R7QFZphPwHAeK4Di/7SjTy6sS7RA2+dJm50KhTRYJxaes
mDQUfvggM0xDN4GzneIfgrO4VbJxRDv1FbflKkF/eLOAP9WxeQGrOLAyAwOl6ANY
ch9a+qwtt0ndn4puN8q+w4VrdN7ybaQvwISsicG7tDBnox9mAauxIv72QuoV9PYM
w7OBia/fCuRSN9LaRF1M
=0jlR
-----END PGP SIGNATURE-----

--nextPart2461294.ccW0HjgLSo--

home	help	back	first	fref	pref	prev	next	nref	lref	last	post