[Mispa-management-l] (Fwd) Direct Google Cache Peering - request from Airtel

Dr P Nyirenda paulos at sdnp.org.mw
Mon Dec 9 11:18:04 CAT 2019


MMC,
MISPA,

Please note this request from Airtel for an additional port connection at the MIX specifically
for the GGC  and send me your comments.

An additional port is available on the MIX switch for this, however, it appears that MISPA
needs to advise Airtel to finalise details with TNM on GGC traffic sharing since it is TNM that
serves this traffic at the MIX.

Victor, can you confirm if this is also in the interest of TNM ?

Does TNM have any objections?

Finally, I will advise Airtel that as MISPA considers port charges, MISPA will charge Airtel an
additional port fee for the extra port when this is implemented.

Regards,

Paulos
======================
Dr Paulos B Nyirenda
NIC.MW & .mw ccTLD
http://www.registrar.mw
Tel:  +265-(0)-882 089 166
Cell: +265-(0)-888-824787
WhatsApp: +265-(0)-887386433


------- Forwarded message follows -------
From:	Wakisa Kaula <wakisa.kaula at mw.airtel.com>
To:	"paulos at sdnp.org.mw" <paulos at sdnp.org.mw>
Copies to:	Bruce Massamba <Bruce.MASSAMBA at mw.airtel.com>
Subject:	Direct Google Cache Peering
Date sent:	Thu, 5 Dec 2019 14:51:53 +0000


    Dear  Paulos,
     
    We intend to establish direct peering between Airtel and the Google cache.
    This is for purposes of separating the google cache traffic from the normal MIX traffic.
    Kindly advice on the requirements for the GCC direct peering in terms of the following:
     
·        Peering IPs  and prefix routing
·        If there will be need for any additional hardware(router) - considering that
    we already have a physical connection at the MIX
     
     
    Regards
     
    Wakisa

 
***********************************************************************************************************
************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of
the individual or entity to whom they are addressed. If you have received this email in error
please notify the system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if
you have received this e-mail by mistake and delete this e-mail from your system. If you are
not the intended recipient you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly prohibited . The information
contained in this mail is propriety and strictly confidential.
***********************************************************************************************************
************************************************************

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
------- End of forwarded message -------


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://chambo3.sdnp.org.mw/pipermail/mispa-management-l/attachments/20191209/53b8b425/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: -
Type: application/octet-stream
Size: 1756 bytes
Desc: not available
URL: <http://chambo3.sdnp.org.mw/pipermail/mispa-management-l/attachments/20191209/53b8b425/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: -
Type: application/octet-stream
Size: 7027 bytes
Desc: not available
URL: <http://chambo3.sdnp.org.mw/pipermail/mispa-management-l/attachments/20191209/53b8b425/attachment-0001.obj>


More information about the Mispa-management-l mailing list