[rpd] Last Call - Resource Reservation for Internet Exchange Points

[Lu Heng]

Hi

On Wed, Jun 17, 2015 at 9:20 PM, Owen DeLong <owen at delong.com> wrote:

>
> > On Jun 17, 2015, at 11:58 , H.Lu <h.lu at anytimechinese.com> wrote:
> >
> >
> >
> > Kind regards
> >
> > Lu
> >
> >> 在 2015年6月17日，下午8:42，Owen DeLong <owen at delong.com> 写道：
> >>
> >> I support the proposal. I question the need for the inclusion of short
> ASNs and believe that it will overall lead to the continuance of bad
> practices that should be phased out.
> >>
> >> The pool of ASNs available ≤65535 is very limited and we really should
> be using solutions that do not depend on ASNs being less than 65536.
> >
> > Partially agree, however reality must faced and unless someone going to
> pay for upgrade for all African ISPs, short ASN makes more sense for
> African Ixp.
>
> This simply isn’t true. There are ways for 16-bit only routers to peer
> with 32-bit ASN routers. No upgrade is required.
>
> The issue as I understand it has to do with the way certain route server
> filtration is being done due to enforced MLPAs rather than use of direct
> peering
> across the IXP with BLPAs.
>
> In discussing this with a variety of people, including the proposal
> authors, most of it boiled down to “we’ve been doing it this way and we
> don’t want to
> change” vs. any real technical issue.
>
> The desire to use inbound tagging on the routes followed by outbound
> filtering on communities which are of the form action:target-AS and/or
> sourceAS:targetAS
> was brought up.
>
> In the case of action:target-AS this is simply that the community has been
> written backwards and should be target-AS:action.
>
> In the other case, it was completely unclear what the exact use case for
> these tags was, but most likely an ASPATH access list or similar could
> actually
> accomplish the equivalent functionality.
>
> Note that this is entirely about the ASN used on the route servers hosted
> by the exchange and not any of the participant’s ASNs.
>
> Owen
>
> I respect your tech expertise, however, from what I understand, any major
change to core router at cooperate level does require a complicated
process. And there are technical and communication cost involved as well.

I would agree make life simpler for IXPs as they are one of very
fundamental part of the internet.


-- 
--
Kind regards.
Lu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20150617/85ed23a4/attachment.html>