[ixpmanager] ixpmanager Digest, Vol 79, Issue 6

[Mike Hammett]

I'd say informational for the other participants of the IX. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Haider Ali" <haiderrana45 at gmail.com> 
To: "INEX IXP Manager Users Mailing List" <ixpmanager at inex.ie> 
Sent: Monday, August 5, 2019 7:07:46 AM 
Subject: Re: [ixpmanager] ixpmanager Digest, Vol 79, Issue 6 


Then what is the significance of selecting policy in the IXP manager if IXP manager doesnt interfere for any behavior ISP will do? I mean if ISP is independent then how is the open or selective peering handled? 

Like, If an ISP selects peering policy: open instead of selective and do opposite that is it still use communities for selective advertisements then is it possible for an ISP? 


-Haider 




On Sun, Aug 4, 2019 at 4:00 PM < ixpmanager-request at inex.ie > wrote: 


Send ixpmanager mailing list submissions to 
ixpmanager at inex.ie 

To subscribe or unsubscribe via the World Wide Web, visit 
https://www.inex.ie/mailman/listinfo/ixpmanager 
or, via email, send a message with subject or body 'help' to 
ixpmanager-request at inex.ie 

You can reach the person managing the list at 
ixpmanager-owner at inex.ie 

When replying, please edit your Subject line so it is more specific 
than "Re: Contents of ixpmanager digest..." 


Today's Topics: 

1. How is Peering policy handled in the backend? (Haider Ali) 
2. Re: How is Peering policy handled in the backend? 
(Nick Hilliard (INEX)) 


---------------------------------------------------------------------- 

Message: 1 
Date: Sat, 3 Aug 2019 16:06:29 +0500 
From: Haider Ali < haiderrana45 at gmail.com > 
To: INEX IXP Manager Users Mailing List < ixpmanager at inex.ie > 
Subject: [ixpmanager] How is Peering policy handled in the backend? 
Message-ID: 
<CADKV7BR4aGtmqOEn7DCEtBHhwUwi= To7YyxkNdLYPwOSzxEbrg at mail.gmail.com > 
Content-Type: text/plain; charset="utf-8" 

Dear Community, 
How is the peering policy implemented in the IXP 
manager at the backend? Is it done by route server? If the route server is 
not used then will the selective peering still can occur? If yes then how? 

Also, if the route server is handling all the peering policies such as open 
or selective then how is it handling? Explaining the question through an 
example. Suppose there are two ISPs: ISP A and ISP B. Can an ISP A provide 
the prefixes in selective peering through its customer portal that I want 
these prefixes to go to ISP B and vice versa. If yes, then how is this 
thing implemented? Is it implemented through route server or what? If it is 
implemented through route server then how? Can you share any link for such 
configurations? 

So, the basic question is: 
How is selective peering being handled at the backend? 

----------- 
One more question is that is there any specific application we should use 
for route server? I am using quagga for route server. 

Thanks for always helping the deployment of IXP manager in Pakistan 
Sincerely, 
Haider 
-------------- next part -------------- 
An HTML attachment was scrubbed... 
URL: < https://www.inex.ie/pipermail/ixpmanager/attachments/20190803/09e39f10/attachment-0001.htm > 

------------------------------ 

Message: 2 
Date: Sat, 3 Aug 2019 15:36:05 +0100 
From: "Nick Hilliard (INEX)" < nick at inex.ie > 
To: INEX IXP Manager Users Mailing List < ixpmanager at inex.ie >, Haider 
Ali < haiderrana45 at gmail.com > 
Subject: Re: [ixpmanager] How is Peering policy handled in the 
backend? 
Message-ID: < 8d30b101-3a98-5888-7ecf-8a70d5e64826 at inex.ie > 
Content-Type: text/plain; charset=utf-8; format=flowed 

Haider Ali wrote on 03/08/2019 12:06: 
> How is selective peering being handled at the backend? 

It isn't. The participants at the IXP determine how they want their 
prefixes to be exchanged. 

If they have bilateral BGP sessions, then this is entirely a matter for 
them, and the IXP has no way of interfering with this. If they choose 
to use the route servers, then: 

outgoing prefixes: they can use the standard community tags if they want 
their prefixes to be sent or blocked for other RS clients. 

incoming prefixes: they can use standard BGP as path filters or prefix 
lists to filter out what they don't want to see. 

The IXP doesn't control any of this. The control is solely in the hands 
of the IXP participants because they are better at deciding what's most 
appropriate for their routing policy. 

Nick 


------------------------------ 

Subject: Digest Footer 

_______________________________________________ 
ixpmanager mailing list 
ixpmanager at inex.ie 
https://www.inex.ie/mailman/listinfo/ixpmanager 


------------------------------ 

End of ixpmanager Digest, Vol 79, Issue 6 
***************************************** 



_______________________________________________ 
INEX IXP Manager mailing list 
ixpmanager at inex.ie 
Unsubscribe or change options here: https://www.inex.ie/mailman/listinfo/ixpmanager 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20190805/14de88c3/attachment-0001.htm>