IETF Logo Mail Archive

Re: [Sidrops] [GROW] IXP Route Server question

"Mosher, Rob" <rmosher@amazon.com> Fri, 11 March 2022 02:37 UTC

Return-Path: <prvs=062d6cf8c=rmosher@amazon.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA6D3A1196; Thu, 10 Mar 2022 18:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.608
X-Spam-Level:
X-Spam-Status: No, score=-14.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HqFR5_MUXfnj; Thu, 10 Mar 2022 18:37:40 -0800 (PST)
Received: from smtp-fw-6001.amazon.com (smtp-fw-6001.amazon.com [52.95.48.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3969B3A116C; Thu, 10 Mar 2022 18:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1646966261; x=1678502261; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=WZ+UMD8nBZC4Y32PRLaem7pcJ+iiGd/XrD6hRkuaD14=; b=MMOZzvy/Y4BbyIvAdxJG9/c3dpNUwsN8BiRzcBAHJnNcoQS++8d9e/Gb S/BAgO8UNHHBGP8LmH5J3UteoKhv+bZyLwJ/ruLWdgIFFJ0TOZkt8jIr7 3bAH7+WpW6DIiqEfEMDbb6nQHQTdDjd+xgk4dxxJzPF39X1TgMP7v8AiO k=;
X-IronPort-AV: E=Sophos;i="5.90,172,1643673600"; d="scan'208";a="185113092"
Thread-Topic: [Sidrops] [GROW] IXP Route Server question
Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-iad-1e-8be8ed69.us-east-1.amazon.com) ([10.43.8.6]) by smtp-border-fw-6001.iad6.amazon.com with ESMTP; 11 Mar 2022 02:37:30 +0000
Received: from EX13MTAUEE002.ant.amazon.com (iad12-ws-svc-p26-lb9-vlan3.iad.amazon.com [10.40.163.38]) by email-inbound-relay-iad-1e-8be8ed69.us-east-1.amazon.com (Postfix) with ESMTPS id 69F4AC0A20; Fri, 11 Mar 2022 02:37:28 +0000 (UTC)
Received: from EX13D14UEE003.ant.amazon.com (10.43.62.11) by EX13MTAUEE002.ant.amazon.com (10.43.62.24) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Fri, 11 Mar 2022 02:37:27 +0000
Received: from EX13D14UEE003.ant.amazon.com (10.43.62.11) by EX13D14UEE003.ant.amazon.com (10.43.62.11) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Fri, 11 Mar 2022 02:37:27 +0000
Received: from EX13D14UEE003.ant.amazon.com ([10.43.62.11]) by EX13D14UEE003.ant.amazon.com ([10.43.62.11]) with mapi id 15.00.1497.033; Fri, 11 Mar 2022 02:37:27 +0000
From: "Mosher, Rob" <rmosher@amazon.com>
To: Nick Hilliard <nick@foobar.org>, "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
CC: "grow@ietf.org" <grow@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Index: AQHYMzOTj7J0F5wxK0qmWvLm6zmdXay3+DyAgAFJy4CAADcGgA==
Date: Fri, 11 Mar 2022 02:37:27 +0000
Message-ID: <5665d2c20e4c45f0acfa55fa08987247@EX13D14UEE003.ant.amazon.com>
References: <SA1PR09MB8142093BE50A27A7EED132D884099@SA1PR09MB8142.namprd09.prod.outlook.com> <0db7749f-66fd-5def-a8bb-3ee316cf2ca1@foobar.org> <SA1PR09MB81421BCBA7FB59615A7638A5840B9@SA1PR09MB8142.namprd09.prod.outlook.com> <fa0b5b32-6541-f493-e02b-fe75d44dacd5@foobar.org>
In-Reply-To: <fa0b5b32-6541-f493-e02b-fe75d44dacd5@foobar.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.62.53]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/riNx-JSWZQoiiW5mK1EW1ET3lGI>
X-Mailman-Approved-At: Mon, 14 Mar 2022 08:35:20 -0700
Subject: Re: [Sidrops] [GROW] IXP Route Server question
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2022 02:43:14 -0000

HKIX inserts their ASN 4635 in the path, and they're quite large.  Having connected to route servers on hundreds of exchanges, this is the only one that I can think of that still does this. 

https://www.hkix.net/hkix/route-server.htm

https://bgp.he.net/AS4635


-rm

-----Original Message-----
From: Sidrops <sidrops-bounces@ietf.org> On Behalf Of Nick Hilliard
Sent: Thursday, March 10, 2022 6:12 PM
To: Sriram, Kotikalapudi (Fed) <kotikalapudi.sriram@nist.gov>
Cc: grow@ietf.org; sidrops@ietf.org
Subject: RE: [EXTERNAL] [Sidrops] [GROW] IXP Route Server question

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



Sriram, Kotikalapudi (Fed) wrote on 10/03/2022 03:31:
> Nick and all,
>
> Thank you. What you all shared/discussed is very useful info.

>> Almost all RS's are transparent these days.  Usually IXPs go to 
>> lengths to ensure that the RS ASN doesn't appear in the AS path.

> Good to know that. Well, that means there can be an occasional RS that 
> is non-transparent. When there is a non-transparent RS, could there be 
> big ISPs (Tier-1, Tier-2) present there as RS-clients?

I would seriously doubt it.  There are some "Tier 1" and "Tier 2"
providers who peer using route servers at IXPs, but it's a bit unusual (and entertaining to hear them strenuously denying that this ever happens).

Non-transparent RS's were used until a couple of years ago but I'm not aware of any left at this point. Even when non-transparent RS's were more widespread, I would have expected the intersection of these two groups to be null, and that if there were an intersection, the
Tier1/Tier2 providers would not be upset if those paths were dropped / marked as invalid.

> The ASPA verification draft treats the relationship of RS to RS-client 
> as similar to that of Provider to Customer. Seems reasonable? The AS 
> of an RS client includes the RS's AS in its ASPA as a "Provider".

yes, this is reasonable.

Nick

_______________________________________________
Sidrops mailing list
Sidrops@ietf.org
https://www.ietf.org/mailman/listinfo/sidrops

v2.8.7 | Report a Bug | By Email