Dear Keessun,

Looks ok.

Best regards,

Nandraj

Nandraj Kisto
Senior Associate Engineer- Strategic Planning

Emtel Ltd, EmtelWorld, 10, Ebene Cybercity, Ebene 72201, Republic of Mauritius. BRN: C06006174
 +230 5 729 5400 (Ext 517),  ,  +230 5 932 5893

www.emtel.com

This email and all contents are subject to the following Disclaimer:“https://www.emtel.com/email-disclaimer.php”

From: mixp-discussion-bounces@mixp.org [mailto:mixp-discussion-bounces@mixp.org] On Behalf Of Keessun Fokeerah
Sent: Tuesday, August 13, 2019 7:53 PM
To: MIXP Steering Committee (private); mixp-discussion
Subject: [MIXP Discussion] Draft Meeting notes - Management meeting 08.08.19

Dear All,

Please validate below draft meeting notes.

MIXP Management Meeting #1

Date: 08.08.19, 15:30 to 18:00

Venue: Emtelworld, Ebene

Agenda:

1. Volunteering: Elect a new neutral management committee, elected by the community
2. Connectivity to MIXP
3. Internet for MIXP management
4. Upcoming AFPIF event
5. Recent updates
6. Discuss on when and how to host an extension of the IX
7. AOB

Present during meeting

1. Kaldera
2. Rogers
3. Emtel
4. Bharat
5. PCH
6. WoodyNet
7. DCL
8. AFRINIC

Discussion items

1. Volunteering: Elect a new neutral management committee, elected by the community
   1. Registration of MIXP as an Association
   2. Was previously incorporated as an association, now defunct
   3. No need to incorporate until and unless there is exchange of funds with/from MIXP
   4. Decision to keep it informal, But members shall check in parallel for how to register the Association
   5. AFRINIC shall remain as the secretariat for MIXP
   6. PCH shared the attached sample policy that IXPs use around the world
   7. Peers and members of the Management committee can decide on whether to adopt the document as is or customise if to our local context
   8. MIXP Management committee
      1. Keessun proposed at least 5 persons to be onboard the mgmt committee as per the sample policy doc.
      2. Ranveer(Rogers) mentioned that it should have more than 5 persons and be a peer at the MIXP, also share some details from his experience at JINX
      3. Nishal(PCH/Woodynet) mentioned that it should not be limited to peers only but instead be someone interested in making the MIXP better. Nishal added that having 5 persons on the management meeting is better but we can allow up to 7 if needed. A small group is better and more manageable.
      4. Nishal mentioned that we should only allow active(connected and exchanging traffic for last 3 months) Peers to elect the management committee
      5. Nandraj(Emtel) requested that peers present vote for the new committee
      6. Ganesh(DCL) agreed that we keep the size of the committee to 7 persons
      7.  It was jointly agreed that 
         1. 7 members shall be on the management committee
         2. Monthly meetings shall happen
         3. Allow 1 vore per active peer shall be considered to elect members of the management committee
      8. Peers present requested for volunteers to form the management committee 2019
         1. It was noted that 5 persons volunteered and were hence appointed as part of the management; with the approval of all peers present.
         2. Persons appointed for the Management committee:
            1. Ranveer Seetaloo(Rogers Capital)
            2. Jason LEONG SON(Kaldera)
            3. Ganesh Ramalingum(DCL)
            4. Nandraj Kisto(Emtel)
            5. Nishal Goburdhan(PCH/Woodynet)
         3. Ranveer Will be presiding the current committee for one year, until 8/8/20
         4. Keessun Fokeerah shall remain as Ex-officio on the Management committee.
         5. We shall reach out for candidates for the 2 remaining vacant seats, who need not be a peer at the MIXP or locally based in Mauritius. Deadline 13th Aug 2019
2. Connectivity to MIXP
   1. Keessun shared the feedback and challenges expressed by some local organisations where they were unaware of how to connect to the MIXP
   2. Ganesh advised that they can connect for free, if
      1. They have an ASN
      2. Have their own connectivity to MIXP
      3. We may need to update same on the website
   3. Nishal mentioned that we could adopt a process for new peer to connect to the MIXP
   4. It was collectively agreed that the management committee may decide, if needed, to change the rule in the future
3. Internet for MIXP management
   1. Yanesh mentioned that emtel can contribute 10 Mbps
   2. Ganesh mentioned that the DLC link currently down will be fixed within a week
   3. Keessun specified that we shall hence have 4 links available in the future namely
      1. Bharat(Existing)
      2. DC(Existing)
      3. Emtel(New)
      4. Rogers Capital(New)
   4. Keessun mentioned that the tech team shall work on how to best utilise these links for the MIXP
4. AfPIF
   1. Ranveer mentioned that few locals have registered
   2. All peers agreed to further publicise the event with their collaborators
5. MIXP updates(Keessun)
   1. Website review is in progress
   2. List of services shall be updated as per feedback of the current meeting
   3. Need to confirm and encourage peering with Route collector at least as mandatory and Route server.
   4. We can work on RPKI with all peers
   5. More best practices can be implemented such as more secured routing
6. How to host an Extension of the IX
   1. Rogers Capital wants to host an extension of the IX
      1. Initially wanted to host a new IXP
      2. Nishal and Keessun advised that Mauritius is too small for a second IXP
      3. Rogers Capital is already connected to GOC site
      4. As per the equipments and details shared with Ranveer, they are almost 90% ready to have the extension up and running, infrastructure is ready such as
         1. Fiber
         2. Firewall
         3. SFPs
         4. Router
         5. Switch
         6. Servers
         7. etc
      5. However, Rogers wants to have the blessing and approval of the management committee
   2. Nishal and Keessun mentioned that we could have a minimum requirement for any organisation wanting to host an extension of the IX. A sample MoU was shared, also attached
   3. Members and eventually the Management committee should agree on the terms of the MoU
   4. Keessun mentioned that after a requester is able to meet the minimum requirements, final decision shall be for the management committee to proceed with the extension of the IX
   5. Kaldera has also expressed their wish to host an extension of the IX, but are not technically ready
   6. After discussions, Ranveer proposed and put the proposal to have the extension at Rogers be approved while the rules and MoU are refined
   7. Keessun advised that if a new extension is approved, the internet connection available for management can be used at each location
   8. It was jointly agreed by the management committee that
      1. Not having the final MoU ready is not a show-stopper and hence the new site is approved and shall be
         1. an Extension to the current MIXP switch hosted at GOC
         2. adhering to the MoU when same is finalised and any gaps shall be filled by Rogers Capital to ensure compliance to MoU
7. AOB
   1. MUNOG
      1. Keessun mentioned that independently from MIXP, the MUNOG has been formed
      2. The MUNOG shall bring network operators and IT personnels/engineers etc without any affiliation to the company they work for
      3. MUNOG shall live to "We compete commercially and collaborate technically"
      4. Keessun proposed that we could have a first MUNOG workshop during AfPIF, if we have an available room.
   2. Ranveer proposed that we appoint an IXP manager
      1. Nishal mentioned that we can wait for some time before appointing someone as this will certainly impact on the financials
   3. Technical committee
      1. Will be elected later, further discussions in the next management meeting
8. Next meeting will be on 6th Sept 2019 at 16:00 at Rogers Capital's office

 Action items:

1.  1. Keessun to send details of the new mgmt committee and request for volunteers for the 2 available seats
2.   Update the website:
   1.   Nishal volunteer to manage the website content, backend stuffs
   2.   Front end stuff by other two/three persons
3. Keessun to get a list of service that shall be publicised on the revised site
4. Keessun to work with the tech team to get the approved IX extension ready
5. Keessun &Nishal to work out a draft process for new peers to connect  
6. under connectivity:
   # how to get people to peer with the BGP-RS.   
   # how to get the management committee to get their networks to peer (no excuses)

-- 
Keessun Fokeerah
MIXP team
--
Mauritius Internet Exchange Point(MIXP)
w: http://www.mixp.org/