Dear All!
I have some marvelous news from Emtel!
Our operators are gradually willing to open up!
We sincerely hope that everyone joins the party!
Happy reading!
Regards,
--
Keessun Fokeerah
MIXP team
--
Mauritius Internet Exchange Point(MIXP)
w: http://www.mixp.org/
-------- Forwarded Message --------
Subject: RE: MIXP Committee
Date: Thu, 17 May 2018 05:27:05 +0000
From: Yanesh Goburdhone <Yanesh.Goburdhone(a)emtel.com>
To: keessun(a)mixp.org <keessun(a)mixp.org>, Ganesh Ramalingum
<ganesh.ramalingum(a)dcl.mu>, daniel(a)afrinic.net <daniel(a)afrinic.net>,
atma.narasiah(a)continuitymauritius.com
<atma.narasiah(a)continuitymauritius.com>, jlim(a)mauritiustelecom.com
<jlim(a)mauritiustelecom.com>, rhosenkhan(a)udm.ac.mu
<rhosenkhan(a)udm.ac.mu>, sewkumar.dhoomon(a)mauritiustelecom.com
<sewkumar.dhoomon(a)mauritiustelecom.com>, Shameem MOHUR <sm(a)btl.mu>, VIK
BHOYROO <vbhoyroo(a)ncb.mu>, Vyankoj Sawant Mulloo <vmulloo(a)ncb.mu>,
Vishaal Ramessur <vishaal.ramessur(a)dcl.mu>, MIXP Steering Committee
(private) <mixp-steering(a)mixp.org>, peering <peering(a)emtel.com>,
Shivendra Nautiyal <Shivendra.Nautiyal(a)emtel.com>, Avinash V.Chettiar
<Avinash.Chettiar(a)emtel.com>, jayprakash bundhoo <jay.bundhoo(a)telecom.mu>
CC: Sandrina Rasen <srasen(a)mcci.org>
Dear All,
We believe that the meeting was a good start for new and existing members.
As stated yesterday, Emtel is ready for Open Peering with ALL MIXP
members. However it should be a fair game where all players should agree
to peer with each other to the benefit of all members .i.e*. No
Selective Peering *
* *
In case some members continue with their selective peering strategy,
Emtel will have the obligation of doing same.
We would like the committee to present a status on all peering in the
upcoming meetings.
We shall get in touch with you for the pending requests and Emtel shall
remain available on peering(a)emtel.com <mailto:peering@emtel.com> for
future peering.
*Org*
*ASN*
*Peering*
Atlas Communications International
328019
Pending
Bharat Telecom Limited
37455
Pending
Data Communications Ltd
36882
Yes
Enterprise Information Solutions
36868
Pending
National Computer Board
36894
Yes
Kaldera Ltd
51110
Yes
Mauritius Telecom
23889
Pending
MIXP Administration
327821
Yes
Mahanagar Telephone Mauritius Ltd
37622
Pending
WoodyNet
42
Yes
Regards
Yanesh *Goburdhone
*Lead -TX & Datacom
Emtel Ltd, EmtelWorld, 10, Ebene Cybercity, Ebene 72201, Republic of
Mauritius. BRN: C06006174
+230 5 729 5400 (Ext 500), +230 4540400, +230 5 499 6669
*www.emtel.com* <http://www.emtel.com>
*<https://www.emtel.com/airbox%20%09%20%20%20>
This email and all contents are subject to the following
Disclaimer:“**https://www.emtel.com/email-disclaimer.php**” *
**
*From:*keessun.fokeerah@afrinic.net
[mailto:keessun.fokeerah@afrinic.net] *On Behalf Of *Keessun Fokeerah
*Sent:* Friday, April 20, 2018 3:21 PM
*To:* Ganesh Ramalingum; daniel(a)afrinic.net;
atma.narasiah(a)continuitymauritius.com; jlim(a)mauritiustelecom.com;
rhosenkhan(a)udm.ac.mu; sewkumar.dhoomon(a)mauritiustelecom.com; Shameem
MOHUR; VIK BHOYROO; Vyankoj Sawant Mulloo; Yanesh Goburdhone; Vishaal
Ramessur; MIXP Steering Committee (private)
*Cc:* Sandrina Rasen
*Subject:* Re: MIXP Committee
Dear Ganesh,
Thank you for the response and interest on this matter.
We shall wait for your final confirmation concerning the meeting.
Regards,
--
Keessun Fokeerah
MIXP team
--
Mauritius Internet Exchange Point(MIXP)
w: http://www.mixp.org/
On 19/04/2018 19:02, Ganesh Ramalingum wrote:
Dear Keessun,
Thank you very much for your mail.
I have asked Sandrina who is in copy in this mail to set up a
meeting on the 15^th May. (this gives ample time to all ISP to make
arrangements)
She will be calling all ISP’s to get their commitment for the meeting.
I totally agree that we need to get everyone on board as this is in
the interest of the community.
Regards
DCL Logo 2.jpg <http://www.dcl.mu/>*Ganesh Ramalingum*
*Executive Chairman *l* Data Communications Ltd *l* 1^st
Floor *Corner Mgr. Gonin & Lislet Geoffroy Streets,* *Port Louis,
Republic of Mauritius
*Head Office*(230) 210-1327 * *l * **Customer Support*(230)
203-6090* *l * **Fax* (230) 2119467 l *Website** *www.dcl.mu
*BRN *C07018379* *l* ** VAT *20164050* *l* ** EORI* GB015227063000
fb.jpg <https://www.facebook.com/dclmauritius/>Linkedin.jpg
<https://www.linkedin.com/company/dcl-mu>Twitter.jpg
<https://twitter.com/DCLmauritius>Googleplus.jpg
<https://plus.google.com/+dclmauritius>
imap://keessun%2Efokeerah@imap.afrinic.net:143/fetch%3EUID%3E.INBOX%3E261542?part=1.7&filename=image006.jpg
*DISCLAIMER*: This email and any attachments may be confidential and
are solely intended for the use of the individual to whom it is
addressed. Any views or opinions expressed are exclusively those of
the author, and do not necessarily represent the views of Data
Communications Ltd,
else or otherwise stated by the individual sender to be the views of
Data Communications Ltd. In case you are not the intended recipient
of this e-mail, you must not take any action based upon its
contents, distribute, copy or show it to anyone. Please contact the
sender, if you believe you
have received this email in error.
*WARNING*: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage
caused for any damage caused by any virus transmitted by this email.
*INFORMATION LEGALE* : Cet e-mail et ses pièces jointes peuvent être
confidentiels et sont uniquement destinées à l’usage de l’individu à
qui ils sont adressés. Les idées et opinions exprimées sont
strictement ceux de l’auteur et ne représentent pas nécessairement
ceux de Data Communications Ltd,
sauf explicitement mentionné comme étant les vues de Data
Communications Ltd par l’auteur. Au cas où vous n’êtes pas le
destinataire initialement prévu de cet e-mail, vous ne devez pas
agir en conséquence de son contenu, distribuer, copier ou le montrer
à qui que ce soit. Veuillez, s’il vous plait,
contacter l’expéditeur, si vous pensez avoir reçu cet e-mail par
erreur.
*AVERTISSEMENT *: Les virus informatiques peuvent être transmis par
courrier électronique. Le destinataire devrait vérifier cet e-mail
et les pièces jointes pour la présence de virus. La société décline
toute responsabilité pour tout dommage causé par un quelconque virus
transmis via cet e-mail.
* *
*P***Before printing, think about the Environment!
*From:*keessun.fokeerah@afrinic.net
<mailto:keessun.fokeerah@afrinic.net><keessun.fokeerah(a)afrinic.net>
<mailto:keessun.fokeerah@afrinic.net>*On Behalf Of *Keessun Fokeerah
*Sent:* Thursday, April 19, 2018 10:29 AM
*To:* Ganesh Ramalingum <ganesh.ramalingum(a)dcl.mu>
<mailto:ganesh.ramalingum@dcl.mu>; daniel(a)afrinic.net
<mailto:daniel@afrinic.net>; atma.narasiah(a)continuitymauritius.com
<mailto:atma.narasiah@continuitymauritius.com>;
jlim(a)mauritiustelecom.com <mailto:jlim@mauritiustelecom.com>;
rhosenkhan(a)udm.ac.mu <mailto:rhosenkhan@udm.ac.mu>;
sewkumar.dhoomon(a)mauritiustelecom.com
<mailto:sewkumar.dhoomon@mauritiustelecom.com>; Shameem MOHUR
<sm(a)btl.mu> <mailto:sm@btl.mu>; VIK BHOYROO <vbhoyroo(a)ncb.mu>
<mailto:vbhoyroo@ncb.mu>; Vyankoj Sawant Mulloo <vmulloo(a)ncb.mu>
<mailto:vmulloo@ncb.mu>; Yanesh Goburdhone
<Yanesh.Goburdhone(a)emtel.com> <mailto:Yanesh.Goburdhone@emtel.com>;
Vishaal Ramessur <vishaal.ramessur(a)dcl.mu>
<mailto:vishaal.ramessur@dcl.mu>; MIXP Steering Committee (private)
<mixp-steering(a)mixp.org> <mailto:mixp-steering@mixp.org>
*Subject:* Re: MIXP Committee
Dear Ganesh & all,
I would suggest that we plan quick committee meeting since we need
to re-activate this committee.
@Ganesh, can you propose a schedule and venue?
Regards,
--
Keessun Fokeerah
MIXP team
--
Mauritius Internet Exchange Point(MIXP)
w: http://www.mixp.org/
On 05/04/2018 18:46, Ganesh Ramalingum wrote:
Dear All,
It has been quite some time since the MIXP committee met. Can we
meet to discuss on the committee members for the steering
committee and the technical committee?
I believe ISP’s should meet regularly at least once every two
months if possible and on an adhoc basis when there is any
special agreement.
For all those who are new, we can organise a technical training
on the Internet Exchange.
Let me have you thoughts to call for a meeting. If I have missed
anyone in the mail, please feel free to include them.
Regards
DCL Logo 2.jpg <http://www.dcl.mu/>*Ganesh Ramalingum*
*Executive Chairman *l* Data Communications Ltd *l* 1^st
Floor *Corner Mgr. Gonin & Lislet Geoffroy Streets,* *Port
Louis, Republic of Mauritius
*Head Office*(230) 210-1327 * *l * **Customer Support*(230)
203-6090* *l * **Fax* (230) 2119467 l *Website** *www.dcl.mu
*BRN *C07018379* *l* ** VAT *20164050* *l* ** EORI* GB015227063000
fb.jpg <https://www.facebook.com/dclmauritius/>Linkedin.jpg
<https://www.linkedin.com/company/dcl-mu>Twitter.jpg
<https://twitter.com/DCLmauritius>Googleplus.jpg
<https://plus.google.com/+dclmauritius>
imap://keessun%2Efokeerah@imap.afrinic.net:143/fetch%3EUID%3E.INBOX%3E261542?part=1.8&filename=image007.jpg
*DISCLAIMER*: This email and any attachments may be confidential
and are solely intended for the use of the individual to whom it
is addressed. Any views or opinions expressed are exclusively
those of the author, and do not necessarily represent the views
of Data Communications Ltd,
else or otherwise stated by the individual sender to be the
views of Data Communications Ltd. In case you are not the
intended recipient of this e-mail, you must not take any action
based upon its contents, distribute, copy or show it to anyone.
Please contact the sender, if you believe you
have received this email in error.
*WARNING*: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any
damage caused for any damage caused by any virus transmitted by
this email.
*INFORMATION LEGALE* : Cet e-mail et ses pièces jointes peuvent
être confidentiels et sont uniquement destinées à l’usage de
l’individu à qui ils sont adressés. Les idées et opinions
exprimées sont strictement ceux de l’auteur et ne représentent
pas nécessairement ceux de Data Communications Ltd,
sauf explicitement mentionné comme étant les vues de Data
Communications Ltd par l’auteur. Au cas où vous n’êtes pas le
destinataire initialement prévu de cet e-mail, vous ne devez pas
agir en conséquence de son contenu, distribuer, copier ou le
montrer à qui que ce soit. Veuillez, s’il vous plait,
contacter l’expéditeur, si vous pensez avoir reçu cet e-mail par
erreur.
*AVERTISSEMENT *: Les virus informatiques peuvent être transmis
par courrier électronique. Le destinataire devrait vérifier cet
e-mail et les pièces jointes pour la présence de virus. La
société décline toute responsabilité pour tout dommage causé par
un quelconque virus transmis via cet e-mail.
* *
*P***Before printing, think about the Environment!
Dear All,
Trust you are doing great!
We have noted that some of the local players in Mauritius are still
hesitant to have an open bilateral peering via the MIXP and some even
prefer to have direct "paid" local peering links instead of going
through the existing IXP.
What are your challenges?
What is your internal policy on peering on the MIXP?
Did you try sensitising your superiors on the benefits of peering over
an IXP?
--
Keessun Fokeerah
MIXP team
--
Mauritius Internet Exchange Point(MIXP)
w: http://www.mixp.org/
Dear All,
Please take some time to go through this survey which shall help us
contribute towards the development of IXPs in the AFRICAN region :)
Regards,
Keessun
-------- Forwarded Message --------
Subject: [af-ix] Fwd: PCH peering survey 2016
Date: Thu, 15 Sep 2016 09:37:38 +0200
From: Nishal Goburdhan <nishal(a)ispa.org.za>
To: af-ix <af-ix(a)af-ix.net>
hi there af-ix.
could you help circulate this survey request within your respective IX
communities please.
the results of the last survey are still used as reference matter (i
know that both michuki and i use “the 99% don’t need a peering
agreement statistic all the time) and we’d really like to update the
data.
thanks in advance,
—n.
Forwarded message:
> From: Bill Woodcock <woody(a)pch.net>
> To: afnog(a)afnog.org
> Subject: [afnog] PCH peering survey 2016
> Date: Wed, 14 Sep 2016 17:04:16 -0700
>
> Background:
>
> Five years ago PCH conducted the first, and to date only,
> comprehensive survey characterizing Internet peering agreements.
>
> The document that resulted can be found here:
> https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011…
> <https://www.pch.net/resources/Papers/peering-survey/PCH-Peering-Survey-2011…>
>
> That document was one of the principal inputs to an important document
> that the OECD publishes every five years, one that recommends
> communications regulatory policy to OECD member nations:
> http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I…
> <http://www.oecd.org/officialdocuments/publicdisplaydocumentpdf/?cote=DSTI/I…>
>
> The survey had several useful findings which hadn’t previously been
> established as fact—most notably the portion of peering
> relationships that are “handshake” agreements, without written
> contract. These findings have improved the regulatory environments in
> which many of us operate our networks.
>
> At the time of the 2011 survey, we committed to repeating the survey
> every five years, so as to provide an ongoing indication of the
> direction peering trends take. It’s now five years later, so we’re
> repeating the survey.
>
> The survey is global in scope, and our goal is to reflect the
> diversity of peering agreements in the world; we’re interested in
> large ISPs and small ISPs, ISPs in Afghanistan and in Zimbabwe,
> bilateral agreements and multilateral, private and public. Our intent
> is to be as comprehensive as possible. In 2011, the responses we
> received represented 86% of all of the world’s ISPs and 96
> countries. We would like to be at least as inclusive this time.
>
> Privacy:
>
> In 2011, we promised to collect the smallest set of data necessary to
> answer the questions, to perform the analysis immediately, and not to
> retain the data after the analysis was accomplished. In that way, we
> ensured that the privacy of respondents was fully protected. We did as
> we said, no data was leaked, and the whole community benefited from
> the trust that was extended to us. We ask for your trust again now as
> we make the same commitment to protect the privacy of all respondents,
> using the same process as last time. We are asking for no more data
> than is absolutely necessary. We will perform the analysis immediately
> upon receiving all of the data. We will delete the data once the
> analysis has been performed.
>
> The Survey:
>
> We would like to know the following five pieces of information
> relative to each Autonomous System you peer with:
>
> • Your ASN
> • Your peer’s ASN (peers only, not upstream transit providers or
> downstream customers)
> • Whether a written and signed peering agreement exists (the
> alternative being a less formal arrangement, such as a "handshake
> agreement")
> • Whether the terms are roughly symmetric (the alternative being
> that they describe an agreement with different terms for each of the
> two parties, such as one compensating the other, or one receiving more
> or fewer than full customer routes)
> • Whether a jurisdiction of governing law is defined
> • Whether IPv6 routes are being exchanged (this year, we’ll still
> assume that IPv4 are)
>
> The easiest way for us to receive the information is as a tab-text or
> CSV file or an Excel spreadsheet, consisting of rows with the
> following columns:
>
> Your ASN: Integer
> Peer ASN: Integer
> Written agreement: Boolean
> Symmetric: Boolean
> Governing Law: ISO 3166 two-digit country-code, or empty
> IPv6 Routes: Boolean
>
> For instance:
>
> 42 <tab> 715 <tab> false <tab> true <tab> us <tab> true <cr>
> 42 <tab> 3856 <tab> true <tab> true <tab> us <tab> true <cr>
>
> We are asking for the ASNs only so we can avoid double-counting a
> single pair of peers when we hear from both of them, and so that when
> we hear about a relationship in responses from both peers we can see
> how closely the two responses match, an important check on the quality
> of the survey. As soon as we've collated the data, we'll strip the
> ASNs to protect privacy, and only the final aggregate statistics will
> be published. We will never disclose any ASN or any information about
> any ASN. We already have more than 8,000 ASN-pair relationships
> documented, and we hope to receive as many more as possible. We'd like
> to finish collecting data by the end of September, about two weeks
> from now.
>
> If you’re peering with an MLPA route-server, you’re welcome to
> include just the route-server’s ASN, if that’s easiest, rather
> than trying to include each of the peer ASNs on the other side of the
> route-server. Either way is fine.
>
> If all of your sessions have the same characteristics, you can just
> tell us what those characteristics are once, your own ASN once, and
> give us a simple list of your peer ASNs.
>
> If your number of peers is small enough to be pasted or typed into an
> email, rather than attached as a file, and that’s simpler, just go
> ahead and do that.
>
> If you have written peering agreements that are covered by
> non-disclosure agreements, or if your organizational policy precludes
> disclosing your peers, but you’d still like to participate in the
> survey, please let us know, and we’ll work with whatever information
> you’re able to give us and try to ensure that your practices are
> statistically represented in our results.
>
> If you're able to help us, please email me the data in whatever form
> you can. If you need a non-disclosure, we're happy to sign one.
>
> Finally, if there are any other questions you’d like to see answered
> in the future, please let us know so that we can consider addressing
> them in the 2021 survey. The question about IPv6 routing in this
> year’s survey is there because quite a few of the 2011 respondents
> asked us to include it this time.
>
> Please respond by replying to this email, before the end of September.
>
> Thank you for considering participating. We very much appreciate it,
> and we look forward to returning the results to the community.
>
> -Bill Woodcock
> Executive Director
> Packet Clearing House
_______________________________________________
af-ix mailing list
af-ix(a)af-ix.net
http://af-ix.net/mailman/listinfo/af-ix_af-ix.net
As most of you probably don’t follow the AFRINIC Resource Policy discussion mailing list, just to let you know there’s been some mention of the MIXP.
But it’s not necessarily easy to spot in the archives as it’s in between into a longer unrelated thread about IPv6 statistics.
If you’re interested, the mention of the MIXP is in these messages:
https://lists.afrinic.net/pipermail/rpd/2016/005894.htmlhttps://lists.afrinic.net/pipermail/rpd/2016/005898.htmlhttps://lists.afrinic.net/pipermail/rpd/2016/005899.html
What I mostly wanted to address was that there was mention of our IX being “down” and have a /22 of IPv4 space reserved, neither of which are I can assure are at all accurate or true.
Do note that the transit kindly donated by one of our participants was out for a short while, and that did affected *global* access to the web site. But as this is separate from the actual switch, the IX always keeps exchanging traffic!
But this allows me to remind everyone of a few thing:
- Don’t forget that the administrative and management services of the MIXP also *peer* at the IX! So in cases like this, if *your* ASN peers to the MIXP’s management ASN, you won’t see the outage. If you are reading this and are able to set up peering for your AS and don’t have a session to AS327821, please please get in touch with peering(a)mixp.org to configure.
- We have https://lg.mixp.org/ to showcase the participants ASN’s and the associated number of prefixes - but we need folks to peer to the route collector to show up here.
Having good data here is a way to attract possible future content providers!
And peering to the route collector does *not* cause any actual traffic to be exchanged with anyone - so is therefore zero risk and cannot affect your policies or business. But it helps the MIXP hugely!
Please also contact peering(a)mixp.org asap to get this up.
- And don’t forget we also have live route-servers. (Sometimes called route-reflectors). These allow you to set up one single eBGP session and immediately exchange traffic with all others also talking to them. Much less work, but exponentially more traffic changed over time.
Anyone that is open to peering with the maximum of others and does’t yet have a session here is just lazy!
Same contact to get connected: peering(a)mixp.org.
Again, we understand that not everyone has an open policy and so not everyone will find the RS useful. But please use the RC even if you don't operate an open peering policy.
Finally, as always, IXPs work most effectively when they're used by all participants. We encourage peering where practical across the public fabric as it is still a free-to-use IX.
All the best
Daniel
As most of you probably don’t follow the AFRINIC Resource Policy discussion mailing list, just to let you know there’s been some mention of the MIXP.
But it’s not necessarily easy to spot in the archives as it’s in between into a longer unrelated thread about IPv6 statistics.
If you’re interested, the mention of the MIXP is in these messages:
https://lists.afrinic.net/pipermail/rpd/2016/005894.htmlhttps://lists.afrinic.net/pipermail/rpd/2016/005898.htmlhttps://lists.afrinic.net/pipermail/rpd/2016/005899.html
What I mostly wanted to address was that there was mention of our IX being “down” and have a /22 of IPv4 space reserved, neither of which are I can assure are at all accurate or true.
Do note that the transit kindly donated by one of our participants was out for a short while, and that did affected *global* access to the web site. But as this is separate from the actual switch, the IX always keeps exchanging traffic!
But this allows me to remind everyone of a few thing:
- Don’t forget that the administrative and management services of the MIXP also *peer* at the IX! So in cases like this, if *your* ASN peers to the MIXP’s management ASN, you won’t see the outage. If you are reading this and are able to set up peering for your AS and don’t have a session to AS327821, please please get in touch with peering(a)mixp.org to configure.
- We have https://lg.mixp.org/ to showcase the participants ASN’s and the associated number of prefixes - but we need folks to peer to the route collector to show up here.
Having good data here is a way to attract possible future content providers!
And peering to the route collector does *not* cause any actual traffic to be exchanged with anyone - so is therefore zero risk and cannot affect your policies or business. But it helps the MIXP hugely!
Please also contact peering(a)mixp.org asap to get this up.
- And don’t forget we also have live route-servers. (Sometimes called route-reflectors). These allow you to set up one single eBGP session and immediately exchange traffic with all others also talking to them. Much less work, but exponentially more traffic changed over time.
Anyone that is open to peering with the maximum of others and does’t yet have a session here is just lazy!
Same contact to get connected: peering(a)mixp.org.
Again, we understand that not everyone has an open policy and so not everyone will find the RS useful. But please use the RC even if you don't operate an open peering policy.
Finally, as always, IXPs work most effectively when they're used by all participants. We encourage peering where practical across the public fabric as it is still a free-to-use IX.
All the best
Daniel
VERSION FRANCAISE CI-DESSOUS
Dear all,
Registration for AfPIF-2016 is open!
Join us in Dar es Salaam, Tanzania for the 7th AfPIF Conference 30th August-1st September 2016. Don't miss the premier peering event in Africa.
AfPIF attracts ISP's, content providers, governments an IXP's for three days of learning, sharing and building business in Africa.
Why should you attend AfPIF-2016? Have a look through AfPIF-2015 report that contains briefs of presentations, emerging discussions, speakers and sponsors at: http://www.internetsociety.org/afpif-2015/meeting-summary
Sponsorship opportunities are available to promote your business to these key audiences - find out about the opportunities here: http://www.internetsociety.org/afpif-2016/sponsor-opportunities
Register now to secure your place - and remember to check your visa requirements for travel to Tanzania. http://www.internetsociety.org/afpif-2016/register
==================
L’inscription à la Conférence d’AfPIF-2016 est ouverte!
Rejoignez-nous à Dar es Salamm Tanzanie, pour la 7ème édition de la Conférence d’AfPIF du 30 août au 1er septembre 2016. Ne manquez pas le premier évènement de peering en Afrique.
AfPIF attire les FAI, les fournisseurs de contenu, les décideurs politiques et les points d’échange Internet au cours des trois jours d’apprentissage, de partage et de formation de réseau d’affaires en Afrique.
Pourquoi y participer? Jetez un coup d'œil au rapport d’AfPIF-2015 qui contient un résume sur les présentations, les discussions émergeantes, les présentateurs et les sponsors: https://www.internetsociety.org/afpif-2015-fr/résumé de la réunion
Les opportunités de parrainages sont disponibles pour promouvoir votre société à ces publiques cibles – plus de renseignements sur les parrainages sont disponibles ici: https://www.internetsociety.org/afpif-2016-fr/sponsor-opportunities
Inscrivez-vous maintenant pour garantir votre participation – et merci de penser à vérifier votre besoin de visa pour la Tanzanie. https://www.internetsociety.org/afpif-2016-fr/register
Dear colleagues, associates, and others,
You are receiving this email because at some time in the past you have been involved with or have shown interest in the Mauritius Internet Exchange Point (MIXP).
As such you have been subscribed to this mailing list as we hope that your interest and/or involvement will continue.
However, should you wish to opt out and unsubscribe, just visit https://lists.mixp.org/mailman/listinfo/mixp-discussion, scroll down to the “Unsubscribe” form and submit your email address.
Likewise, if you would prefer to subscribe under a different contact, or know anyone else that would like to subscribe that can be done through the same URL.
What is this list for? This mailing list is intended for any discussion related to the MIXP community. That is any topic related to peering and IXPs in general, the MIXP specifically, the network operator community and eco-system in Mauritius, network management and technology, and so on.
Note that posting to the list is limited to being subscribed to the list, mainly to keep out random spam. However, subscription to the list is open. This is not a closed and private list, but one to foster discussion and build a community. All posts are also archived, and the archives are public, so keep this in mind when posting.
We hope that most of you will stay subscribed and raise some interesting topics going forward, and that the list even grow. However we do not expect it to be very high traffic.
That’s all for the time being.
Happy peering and networking!
hi daniel,
thanks for your earlier message about IPv6.
the DNS services that PCH provides, are available to all participants
across both IPv4 and IPv6.
speaking on behalf of PCH, we would be delighted to setup IPv6 sessions
to all participants.
please feel free to contact our peering team to setup sessions at:
peering(a)pch.net.
(of course, if we are not already directly peering with you across IPv4,
we would be delighted to fix that as well)
best,
—
Nishal Goburdhan
Packet Clearing House