idr...@ietf.org
> Subject: RE: [GROW] IXP Route Server question
>
> Hi Shunwan,
>
> >> 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
Hi Shunwan,
>> 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".
>IMO, the ASPA verification draft regards the relationship between R
Nick,
>Ben Maddison wrote on 11/03/2022 07:23:
>> Essential, I would think: how could a far end relying party know that
>> an AS in the middle of a received AS_PATH is a non-transparent IXP RS
>> in order to apply any other treatment?
>given that they're a shrinking rarity, would it not make se
> given that they're a shrinking rarity, would it not make sense to
> completely exclude non-transparent RSs from the ASPA definition? In
> the short term this would cause problems for ASNs which connect to
> non-transparent RSs, but there are hardly any left, and only one
> sizeable one.
>
> I wo
Ben Maddison wrote on 11/03/2022 07:23:
Essential, I would think: how could a far end relying party know that an
AS in the middle of a received AS_PATH is a non-transparent IXP RS in
order to apply any other treatment?
given that they're a shrinking rarity, would it not make sense to
completel
; Sent: Thursday, March 10, 2022 11:31 AM
> To: Nick Hilliard
> Cc: grow@ietf.org; sidr...@ietf.org
> Subject: Re: [GROW] IXP Route Server question
>
> Nick and all,
>
> Thank you. What you all shared/discussed is very useful info.
>
> >Almost all RS's are transpa
Sounds good. Thank you so much for the discussions and info.
Sriram
-Original Message-
From: Ben Maddison
Sent: Friday, March 11, 2022 2:23 AM
To: Nick Hilliard
Cc: Sriram, Kotikalapudi (Fed) ; grow@ietf.org;
sidr...@ietf.org
Subject: Re: [GROW] IXP Route Server question
Hi Sriram
Hi Sriram,
On 03/10, Nick Hilliard wrote:
> Sriram, Kotikalapudi (Fed) wrote on 10/03/2022 03:31:
[...]
> > 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 it
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 m
e RS's AS in its ASPA as a "Provider".
Sriram
-Original Message-
From: Nick Hilliard
Sent: Tuesday, March 8, 2022 4:28 PM
To: Sriram, Kotikalapudi (Fed)
Cc: grow@ietf.org; sidr...@ietf.org
Subject: Re: [GROW] IXP Route Server question
Sriram, Kotikalapudi (Fed) wr
Sriram, Kotikalapudi (Fed) wrote on 08/03/2022 19:36:
This question has relevance to the ASPA method for route leak
detection.
Is it possible that an ISP AS A peers with a customer AS C via a
non-transparent IXP AS B?
IOW, the AS path in routes propagated by the ISP A for customer C's
prefixes l
11 matches
Mail list logo
