From amelnaud at gmail.com Thu May 5 08:38:58 2016 From: amelnaud at gmail.com (Arnaud AMELINA) Date: Thu, 5 May 2016 08:38:58 +0000 Subject: [Community-Discuss] About NRO NC discuss In-Reply-To: References: Message-ID: Hi community, I have a question that bothers me since our return from Pointe-Noire. We had many discussions about the selection of representatives for NRO NC ... What were the outcomes of those discussions and what were the terms set for their term. I do not remember that we got concensus ? Thank you to whoever wants to answer me . Best regards Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: From alan.barrett at afrinic.net Thu May 5 21:09:31 2016 From: alan.barrett at afrinic.net (Alan Barrett) Date: Thu, 5 May 2016 17:09:31 -0400 Subject: [Community-Discuss] About NRO NC discuss In-Reply-To: References: Message-ID: <0ED81EDB-C4C9-4610-9FB1-1A9F17DFF213@afrinic.net> > On 5 May 2016, at 04:38, Arnaud AMELINA wrote: > I have a question that bothers me since our return from Pointe-Noire. We had many discussions about the selection of representatives for NRO NC ... What were the outcomes of those discussions and what were the terms set for their term. I do not remember that we got concensus ? Thank you to whoever wants to answer me . I think you may be thinking the IANA Numbering Services Review Committee, which is something new. In terms of Board resolution 201511.255 , the Board recommended to the community that the same two people elected to the NRO NC should also automatically serve on the Review Committee. There was a discussion about that at the public meeting in Pointe Noire, and the community supported the Board?s recommendation. Alan Barrett From Serge.Ilunga at vodacom.cd Thu May 5 21:10:13 2016 From: Serge.Ilunga at vodacom.cd (Ilunga, Serge, Vodacom DRC) Date: Thu, 5 May 2016 21:10:13 +0000 Subject: [Community-Discuss] BOD and Management of Conflict of Interest Message-ID: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> Dear Members and Community, It has been raised here and there that Conflict Of Interest shall be well managed inside the board to avoid certain things. The board meeting of February 2016 was dedicated to NOMCOM matters. I'm surprised to see that the Chair did not check Conflict of Interest at the opening. Surprisedly the minutes[under http://www.afrinic.net/en/about/bod/meeting/2016/1699-minutes-20162402 ] do not tell how all the resolutions were passed at that meeting. One could want to know who voted on and for what if the kind of transparency we are calling for is effective. Some of the board members may be running for elections this year. With Regards. [cid:image7bf990.JPG at 0f8fabf3.409c1262] Ilunga, Serge, Vodacom DRC Transmission Optimization Manager Landline: +243814443160 Mobile: +243814443160 Email: Serge.Ilunga at vodacom.cd Address: 3157, Blvd du 30 juin, Building Mobil - Oil, Kinshasa - Gombe, Republique Democratique du Congo www.vodacom.cd MEILLEUR RESEAU INTERNET EN RDC [cid:imagecd0eb6.GIF at eedc0653.459e173e] [cid:image6f6728.GIF at ed088b3f.4d8c36b3] [cid:imageba1322.GIF at fb5d44bd.4490627f] [cid:imagef06403.PNG at f5f756e0.4b8b38b0] This e-mail is classified C2 - Vodacom Restricted - Information to be used inside Vodacom but it may be shared with authorised partners. Ce courriel est classifi? C2 ? Vodacom Restreint. Ce sont des informations dont la divulgation non autoris?e, en particulier en dehors de l'organisation, serait inappropri?e et inopportune -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image7bf990.JPG Type: image/jpeg Size: 29356 bytes Desc: image7bf990.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagecd0eb6.GIF Type: image/gif Size: 413 bytes Desc: imagecd0eb6.GIF URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image6f6728.GIF Type: image/gif Size: 1004 bytes Desc: image6f6728.GIF URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imageba1322.GIF Type: image/gif Size: 638 bytes Desc: imageba1322.GIF URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: imagef06403.PNG Type: image/png Size: 193597 bytes Desc: imagef06403.PNG URL: From owen at delong.com Fri May 6 06:53:30 2016 From: owen at delong.com (Owen DeLong) Date: Thu, 5 May 2016 23:53:30 -0700 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> Message-ID: <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> I agree? Mr. Chair, is there any reason not to disclose the voting records for each board resolution? Owen > On May 5, 2016, at 14:10 , Ilunga, Serge, Vodacom DRC wrote: > > > > > Dear Members and Community, > > It has been raised here and there that Conflict Of Interest shall be well managed inside the board to avoid certain things. > The board meeting of February 2016 was dedicated to NOMCOM matters. > I'm surprised to see that the Chair did not check Conflict of Interest at the opening. > Surprisedly the minutes[under http://www.afrinic.net/en/about/bod/meeting/2016/1699-minutes-20162402 ] do not tell how all the resolutions were passed at that meeting. > One could want to know who voted on and for what if the kind of transparency we are calling for is effective. > Some of the board members may be running for elections this year. > > With Regards. > > > > > > > > > Ilunga, Serge, Vodacom DRC > > Transmission Optimization Manager > > Landline: +243814443160 > > Mobile: +243814443160 > > Email: Serge.Ilunga at vodacom.cd > Address: 3157, Blvd du 30 juin, Building Mobil - Oil, > > Kinshasa - Gombe, Republique Democratique du Congo > > > www.vodacom.cd > > > MEILLEUR RESEAU INTERNET EN RDC > > > > > > > > This e-mail is classified C2 - Vodacom Restricted - Information to be used inside Vodacom but it may be shared with authorised partners. > > Ce courriel est classifi? C2 ? Vodacom Restreint. Ce sont des informations dont la divulgation non autoris?e, en particulier en dehors de l'organisation, serait inappropri?e et inopportune > > > > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From seun.ojedeji at gmail.com Fri May 6 07:29:08 2016 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Fri, 6 May 2016 08:29:08 +0100 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: Based on Alan's response that it was unanimous, then it will be good to have recorded on the minutes. While this could be seen as an editorial oversight, it's important to avoid this minor editorial error from happening in future. Regards Sent from my LG G4 Kindly excuse brevity and typos On 6 May 2016 7:55 a.m., "Owen DeLong" wrote: > I agree? Mr. Chair, is there any reason not to disclose the voting records > for each board resolution? > > Owen > > On May 5, 2016, at 14:10 , Ilunga, Serge, Vodacom DRC < > Serge.Ilunga at vodacom.cd> wrote: > > > > > Dear Members and Community, > > It has been raised here and there that Conflict Of Interest shall be well > managed inside the board to avoid certain things. > The board meeting of February 2016 was dedicated to NOMCOM matters. > I'm surprised to see that the Chair did not check Conflict of Interest at > the opening. > Surprisedly the minutes[under > http://www.afrinic.net/en/about/bod/meeting/2016/1699-minutes-20162402 ] > do not tell how all the resolutions were passed at that meeting. > One could want to know who voted on and for what if the kind of > transparency we are calling for is effective. > Some of the board members may be running for elections this year. > > With Regards. > > > > > > > > > Ilunga, Serge, Vodacom DRC > > Transmission Optimization Manager > > Landline: +243814443160 > > Mobile: +243814443160 > > Email: Serge.Ilunga at vodacom.cd > > Address: 3157, Blvd du 30 juin, Building Mobil - Oil, > > Kinshasa - Gombe, Republique Democratique du Congo > > www.vodacom.cd > > > > *MEILLEUR RESEAU INTERNET EN RDC* > > > > > > > > > *This e-mail is classified C2 - Vodacom Restricted - Information to be > used inside Vodacom but it may be shared with authorised partners.* > > *Ce courriel est classifi? C2 ? Vodacom Restreint. Ce sont des > informations dont la divulgation non autoris?e, en particulier en dehors de > l'organisation, serait inappropri?e et inopportune* > > > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > > > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy at psg.com Fri May 6 09:46:31 2016 From: randy at psg.com (Randy Bush) Date: Fri, 06 May 2016 18:46:31 +0900 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: > Based on Alan's response that it was unanimous, then it will be good to > have recorded on the minutes. > While this could be seen as an editorial oversight, it's important to avoid > this minor editorial error from happening in future. let's put the requirement in the bylaws! :) randy From seun.ojedeji at gmail.com Fri May 6 11:23:40 2016 From: seun.ojedeji at gmail.com (Seun Ojedeji) Date: Fri, 6 May 2016 12:23:40 +0100 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: Actually I don't think it's necessary, as I assume this was just an oversight (as I observed that the votes were recorded in a few previous minutes I checked). Nevertheless, if engraving in the bylaw is what will make us not forget in future then that will be fine. One of the ways we can keep the board accountable is through the minutes, as it could help them to always think deeply before they act (since they know the community is watching their individual actions). More importantly that the community will have facts to challenge the (entire/individual) board as applicable will be a positive step forward on transparency path. Regards Sent from my LG G4 Kindly excuse brevity and typos On 6 May 2016 10:46, "Randy Bush" wrote: > > Based on Alan's response that it was unanimous, then it will be good to > > have recorded on the minutes. > > While this could be seen as an editorial oversight, it's important to > avoid > > this minor editorial error from happening in future. > > let's put the requirement in the bylaws! :) > > randy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah at neo.co.tz Fri May 6 11:41:32 2016 From: noah at neo.co.tz (Noah) Date: Fri, 6 May 2016 14:41:32 +0300 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: On 6 May 2016 14:24, "Seun Ojedeji" wrote: > > Nevertheless, if engraving in the bylaw is what will make us not forget in future then that will be fine. One of the ways we can keep the board accountable is through the minutes, as it could help them to always think deeply before they act (since they know the community is watching their individual actions). More importantly that the community will have facts to challenge the (entire/individual) board as applicable will be a positive step forward on transparency path. > Yes, engraving would remove the room for excusses , let's us add it to the bylawys..[1] Noah > [1] Transparency cant be compromised. -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy at psg.com Fri May 6 11:46:12 2016 From: randy at psg.com (Randy Bush) Date: Fri, 06 May 2016 20:46:12 +0900 Subject: [Community-Discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: > Yes, engraving would remove the room for excusses , let's us add > it to the bylawys..[1] unbelievable! did you not see the smiley? i was being sarcastic. don't folk have networks to run? randy From mainanoa at gmail.com Fri May 6 11:53:27 2016 From: mainanoa at gmail.com (Noah) Date: Fri, 6 May 2016 14:53:27 +0300 Subject: [Community-Discuss] [members-discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: On 6 May 2016 14:46, "Randy Bush" wrote: > > > Yes, engraving would remove the room for excusses , let's us add > > it to the bylawys..[1] > > unbelievable! did you not see the smiley? i was being sarcastic. > What makes you think i was not also being sarcastic :-) > don't folk have networks to run? No, everyone is idle... > > randy > Noah -------------- next part -------------- An HTML attachment was scrubbed... URL: From amelnaud at gmail.com Fri May 6 12:49:14 2016 From: amelnaud at gmail.com (Arnaud AMELINA) Date: Fri, 6 May 2016 12:49:14 +0000 Subject: [Community-Discuss] About NRO NC discuss In-Reply-To: <0ED81EDB-C4C9-4610-9FB1-1A9F17DFF213@afrinic.net> References: <0ED81EDB-C4C9-4610-9FB1-1A9F17DFF213@afrinic.net> Message-ID: If I refer to the resolution 201511-255, it was stated that the Board would make a recommendation to the community. This was done at Pointe-Noire, but the discussion continued online until December 2015. One could expect final decision from the Board after the online various discussions, thus my confusion. Regards. Arnaud 2016-05-05 21:09 GMT+00:00 Alan Barrett : > > > On 5 May 2016, at 04:38, Arnaud AMELINA wrote: > > I have a question that bothers me since our return from Pointe-Noire. We > had many discussions about the selection of representatives for NRO NC ... > What were the outcomes of those discussions and what were the terms set > for their term. I do not remember that we got concensus ? Thank you to > whoever wants to answer me . > > I think you may be thinking the IANA Numbering Services Review Committee, > which is something new. In terms of Board resolution 201511.255 < > http://afrinic.net/en/about/bod/meeting/2015#r255>, the Board recommended > to the community that the same two people elected to the NRO NC should also > automatically serve on the Review Committee. There was a discussion about > that at the public meeting in Pointe Noire, and the community supported the > Board?s recommendation. > > Alan Barrett > > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alan.barrett at afrinic.net Fri May 6 13:53:25 2016 From: alan.barrett at afrinic.net (Alan Barrett) Date: Fri, 6 May 2016 09:53:25 -0400 Subject: [Community-Discuss] About NRO NC discuss In-Reply-To: References: <0ED81EDB-C4C9-4610-9FB1-1A9F17DFF213@afrinic.net> Message-ID: <3718D389-C85C-400E-9C4A-DB340CDB131F@afrinic.net> > On 6 May 2016, at 08:49, Arnaud AMELINA wrote: > > If I refer to the resolution 201511-255, it was stated that the Board would make a recommendation to the community. This was done at Pointe-Noire, but the discussion continued online until December 2015. One could expect final decision from the Board after the online various discussions, thus my confusion. Oh, I see. I think that the Board should pass another resolution to finalise the matter. Alan Barrett From sergekbk at gmail.com Fri May 6 21:02:32 2016 From: sergekbk at gmail.com (serge ilunga) Date: Fri, 6 May 2016 22:02:32 +0100 Subject: [Community-Discuss] [members-discuss] BOD and Management of Conflict of Interest In-Reply-To: References: <16500F9AAE4A5F40A1A13DC12CD8CA47F4B351B0@CDKINJSSPMMB01.vodacom.cd> <931F6273-A188-4E66-9078-E9B0663D8228@delong.com> Message-ID: Hello Allan, The only board member who sits on the 2016 NomCom is not reaching the end of his term, and so is not running for election. If your question about ?how the resolutions were passed? refers to who voted YES and who voted NO, then it?s true that the minutes are silent about that. My memory is that the resolutions at that meeting were all passed unanimously, as is very common. Alan Barrett Wisdom and Good Practices would require that in a meeting around constitution of a committee that will play a role in elections in which some BOD members can be candidates: 1. Start by a Declaration of possible Conflict of Interest. 2. Manage Meeting resolution adoption taking into account COI.. With Regards. On Fri, May 6, 2016 at 12:53 PM, Noah wrote: > > On 6 May 2016 14:46, "Randy Bush" wrote: > > > > > Yes, engraving would remove the room for excusses , let's us add > > > it to the bylawys..[1] > > > > unbelievable! did you not see the smiley? i was being sarcastic. > > > > What makes you think i was not also being sarcastic :-) > > > don't folk have networks to run? > > No, everyone is idle... > > > > > randy > > > > Noah > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > > -- *Serge ILUNGA KABWIKA* *Skype: sergekbk* *Cell: +243814443160 <%2B243814443160>* -------------- next part -------------- An HTML attachment was scrubbed... URL: From kumalop at afri-com.net Mon May 9 10:01:52 2016 From: kumalop at afri-com.net (Promise Kumalo) Date: Mon, 9 May 2016 12:01:52 +0200 Subject: [Community-Discuss] SAFNOG-3: Registration Now Open! In-Reply-To: <55a0aa46-e6e6-bcc7-be45-8cb99bf43545@seacom.mu> References: <55a0aa46-e6e6-bcc7-be45-8cb99bf43545@seacom.mu> Message-ID: <00ae01d1a9d9$cfa8ab30$6efa0190$@afri-com.net> Is there going to be Remote participation option for SAFNOG-3? Regards Promise -----Original Message----- From: Mark Tinka [mailto:mark.tinka at seacom.mu] Sent: Friday, April 29, 2016 10:48 AM To: community-discuss at afrinic.net >> General Discussions of AFRINIC Subject: [Community-Discuss] SAFNOG-3: Registration Now Open! Hello all. Pleased to inform you that registration for the SAFNOG-3 meeting, to be held in Windhoek, Namibia, 8th - 10th August, 2016, is now open. To register your participation for SAFNOG-3, please visit the link below: http://www.safnog.org/ Please note that you will be able to view who else is attending SAFNOG-3 at the bottom of the registration web site. We look forward to seeing you all in Windhoek. Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee _______________________________________________ Community-Discuss mailing list Community-Discuss at afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss From mark.tinka at seacom.mu Mon May 9 14:55:19 2016 From: mark.tinka at seacom.mu (Mark Tinka) Date: Mon, 9 May 2016 16:55:19 +0200 Subject: [Community-Discuss] SAFNOG-3: Registration Now Open! In-Reply-To: <00ae01d1a9d9$cfa8ab30$6efa0190$@afri-com.net> References: <55a0aa46-e6e6-bcc7-be45-8cb99bf43545@seacom.mu> <00ae01d1a9d9$cfa8ab30$6efa0190$@afri-com.net> Message-ID: <9cf289dc-50f0-44af-814e-14014fd992dd@seacom.mu> Hi Promise. Thanks for your e-mail. We are looking into this and will be able to advise in the coming weeks. Mark. On 9/May/16 12:01, Promise Kumalo wrote: > Is there going to be Remote participation option for SAFNOG-3? > > Regards > > Promise > > > > > > > -----Original Message----- > From: Mark Tinka [mailto:mark.tinka at seacom.mu] > Sent: Friday, April 29, 2016 10:48 AM > To: community-discuss at afrinic.net >> General Discussions of AFRINIC > > Subject: [Community-Discuss] SAFNOG-3: Registration Now Open! > > Hello all. > > Pleased to inform you that registration for the SAFNOG-3 meeting, to be held > in Windhoek, Namibia, 8th - 10th August, 2016, is now open. > > To register your participation for SAFNOG-3, please visit the link below: > > http://www.safnog.org/ > > Please note that you will be able to view who else is attending SAFNOG-3 at > the bottom of the registration web site. > > We look forward to seeing you all in Windhoek. > > Cheers, > > Mark Tinka > On Behalf of the SAFNOG Management Committee > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > . > From arbogast.fabian at aku.edu Fri May 13 04:52:16 2016 From: arbogast.fabian at aku.edu (arbogast fabian) Date: Fri, 13 May 2016 04:52:16 +0000 Subject: [Community-Discuss] NAT64 Message-ID: Folks? We are looking into way we can gradually deploy IPv6 in our network? Already we have it running and we have one Test Machine??. The challenge we are facing is that from that machine with IPv6 and from other Machines with IPv4 we can?t communicate in either direction.. IPv6 Machine just communicate with IPv6 only machines like wise IPv4 Machines just communicate with IPv4 machines ?. A work around is to do NAT64 between the two subnets?. It seems the hardware (Cisco 2921 router with IOS Version 15.0) can?t do NAT64??.. >From the internet it seems NAT64 runs on IOS-XE and IOS-CGSE which are Hardware dependent??..seems that we can?t upgrade IOS Version 15.0 to any the two which supports NAT64. Before committing any expenses to acquire new router we want to reach out to the community for comments and advises?. Pls. review and advise. Thank you? -- Arbogast Fabian, IT Manager, Aga Khan Development Network, Aga Khan University - Tanzania 10 Urambo Street ? Upanga, P.o Box 125, 11102 Dar Es Salaam. Tel:+255-22-2150051 Fax:+255-2150875 Cell:+255-78-447-8387 From jnoulaye at yahoo.fr Fri May 13 09:45:34 2016 From: jnoulaye at yahoo.fr (jnoulaye at yahoo.fr) Date: Fri, 13 May 2016 09:45:34 +0000 (UTC) Subject: [Community-Discuss] NAT64 In-Reply-To: References: Message-ID: <482820335.2727617.1463132734378.JavaMail.yahoo@mail.yahoo.com> Dear Fabian,You will be comfortable using the Cisco ASR 1000 Series routers, which includes the stateful NAT64 technology.?In the other hand this mailing list is not appropriate for a quick answer or comment on this issue. Rather move ?this point to the AFNOG mailing list, this one regroups the operators and ISP engineers who can quickly send some suitable comments or best pratices on NAT64 with Cisco2921. I copied ?here the afnog mailing list. Warm regards?Janvier NgnoulayeCisco NetAcad InstructorYaounde - Cameroon De?: arbogast fabian ??: "community-discuss at afrinic.net" Envoy? le : Vendredi 13 mai 2016 5h52 Objet?: [Community-Discuss] NAT64 Folks? We are looking into way we can gradually deploy IPv6 in our network? Already we have it running and we have one Test Machine??. The challenge we are facing is that from that machine with IPv6 and from other Machines with IPv4 we can?t communicate in either direction.. IPv6 Machine just communicate with IPv6 only machines like wise IPv4 Machines just communicate with IPv4 machines ?. A work around is to do NAT64 between the two subnets?. It seems the hardware (Cisco 2921 router with IOS Version 15.0) can?t do NAT64??.. >From the internet it seems NAT64 runs on IOS-XE and IOS-CGSE which are Hardware dependent??..seems that we can?t upgrade IOS Version 15.0 to any the two which supports NAT64. Before committing any expenses to acquire new router we want to reach out to the community for comments and advises?. Pls. review and advise. Thank you? -- Arbogast Fabian, IT Manager, Aga Khan Development Network, Aga Khan University - Tanzania 10 Urambo Street ? Upanga, P.o Box 125, 11102 Dar Es Salaam. Tel:+255-22-2150051 Fax:+255-2150875 Cell:+255-78-447-8387 _______________________________________________ Community-Discuss mailing list Community-Discuss at afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From adam at varud.com Fri May 13 14:02:01 2016 From: adam at varud.com (Adam Nelson) Date: Fri, 13 May 2016 10:02:01 -0400 Subject: [Community-Discuss] NAT64 In-Reply-To: References: Message-ID: Arbogast, I think you'll get better answers on Afrinog or Eanog ... and I'm just a server guy :-) But anyway, it seems like IOS 15.4 supports NAT64: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/15-mt/nat-15-mt-book/iadnat64-stateless.html No need to use XE or CGSE. But I could be totally wrong. -Adam -- About Adam: www.linkedin.com/in/adamcnelson On Fri, May 13, 2016 at 12:52 AM, arbogast fabian wrote: > Folks? > > We are looking into way we can gradually deploy IPv6 in our network? > > Already we have it running and we have one Test Machine??. The challenge > we are facing is that from that machine with IPv6 and from other Machines > with IPv4 we can?t communicate in either direction.. > > IPv6 Machine just communicate with IPv6 only machines like wise IPv4 > Machines just communicate with IPv4 machines ?. > > A work around is to do NAT64 between the two subnets?. > > It seems the hardware (Cisco 2921 router with IOS Version 15.0) can?t do > NAT64??.. > > From the internet it seems NAT64 runs on IOS-XE and IOS-CGSE which are > Hardware dependent??..seems that we can?t upgrade IOS Version 15.0 to any > the two which supports NAT64. > > Before committing any expenses to acquire new router we want to reach out > to the community for comments and advises?. > > Pls. review and advise. > > Thank you? > > > -- > > Arbogast Fabian, > IT Manager, > Aga Khan Development Network, > Aga Khan University - Tanzania > 10 Urambo Street ? Upanga, > P.o Box 125, > 11102 Dar Es Salaam. > Tel:+255-22-2150051 > Fax:+255-2150875 > Cell:+255-78-447-8387 > > _______________________________________________ > Community-Discuss mailing list > Community-Discuss at afrinic.net > https://lists.afrinic.net/mailman/listinfo/community-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From owen at delong.com Fri May 13 17:37:13 2016 From: owen at delong.com (Owen DeLong) Date: Fri, 13 May 2016 10:37:13 -0700 Subject: [Community-Discuss] NAT64 In-Reply-To: References: Message-ID: > On May 12, 2016, at 21:52 , arbogast fabian wrote: > > Folks? > > We are looking into way we can gradually deploy IPv6 in our network? > > Already we have it running and we have one Test Machine??. The challenge we are facing is that from that machine with IPv6 and from other Machines with IPv4 we can?t communicate in either direction.. Why not put both IPv6 _AND_ IPv4 on both sets of machines? > IPv6 Machine just communicate with IPv6 only machines like wise IPv4 Machines just communicate with IPv4 machines ?. If you put IPv4 on the IPv6 machine, it will be able to talk to both. If you put IPv6 on the IPv4 machines, they will be able to talk to the IPv6 only machine. > A work around is to do NAT64 between the two subnets?. Ick, but yes, if you must. > It seems the hardware (Cisco 2921 router with IOS Version 15.0) can?t do NAT64??.. Stand up a cheap Linux box or VM to do the NAT64 and DNS64 (you will need both). >> From the internet it seems NAT64 runs on IOS-XE and IOS-CGSE which are Hardware dependent??..seems that we can?t upgrade IOS Version 15.0 to any the two which supports NAT64. > > Before committing any expenses to acquire new router we want to reach out to the community for comments and advises?. First, if possible, avoid NAT64 and use native dual-stack. If you don?t have sufficient IPv4 resources to do so, you can still acquire additional resources from AfriNIC at this time. Owen From mark.tinka at seacom.mu Mon May 16 14:01:29 2016 From: mark.tinka at seacom.mu (Mark Tinka) Date: Mon, 16 May 2016 16:01:29 +0200 Subject: [Community-Discuss] SAFNOG-3: Call for Papers! Message-ID: <4ddf638f-f87b-c673-4c04-12a2b87cd5df@seacom.mu> Hello all. This is just to remind you that the Call for Papers (CfP) for SAFNOG-3 is open. If you are interested in participating in SAFNOG-3 as a speaker or panelist in Windhoek, Namibia, kindly review the details of the CfP and submit your talk at the link below: http://www.safnog.org/#callforpapers We look forward to receiving your submission, and working with you to develop it into a topic that the community will find interesting and informative. Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee From mangawilly at gmail.com Tue May 31 17:27:35 2016 From: mangawilly at gmail.com (Willy MANGA) Date: Tue, 31 May 2016 18:27:35 +0100 Subject: [Community-Discuss] =?utf-8?q?Tout_est_l=C3=A0_pour_impl=C3=A9men?= =?utf-8?q?ter_IPv6_svp?= In-Reply-To: References: Message-ID: <574DC987.1000105@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bonjour, [j'ai d?plac? mon propos pour la liste community] I have sum up in english at the end... Le 30/05/2016 17:07, Honest Ornella GANKPA a ?crit : > 2016-05-30 16:34 GMT+01:00 GH.-GNONKOTO Serges PATRICK < > gnonkoto.patrick at artci.ci>: > >> Hi Owen, En quoi est-ce d?gradant d'utiliser encore IPv4 ou ses >> capacit?s d?gradantes ? > > > Je pense que Owen parlait des performances de IPv4 en utilisant le > terme *ever progressive degradation of its capabilities. *Avec > l'adoption trop lente de IPv6 en Afrique, nous risquons vraiment de > rater le train du IoT > > Encourager les uns ? migrer ? IPv6 est une chose et donner la > possibilit? ? >> d'autres de le faire progressivement est une autre. > > > Par contre peut ?tre faudrait-il encourager les nouveaux op?rateurs > et ing?nieurs a d?ployer des r?seaux IPv6 de pr?f?rence. Let us not > be ipv4 addicts enablers :-) Je pense tr?s humblement qu'il faut encourager TOUT le monde ? avoir un r?seau double-pile au moins en sortie et dans son r?seau interne ? disposer d'un r?seau g?r? exclusivement en v6 . Tout le monde ici dans cette liste a d?j? ?t? form?/impr?gn? en v6 (j'en suis presque sur) et connait plusieurs autres personnes qui l'ont ?t?. Il n y a AUCUNE raison si ce n'est un peu de volont? et du travail personnel/communautaire qui peut faire progresser les choses. >> Nous voulons donner plus de chances ? ces autres de poss?der IPv4 >> quand on sait que le d?ploiement sera dual stack et que ce ne >> sera pas aussi brutal au risque de se mettre un couteau sous la >> gorge. >> A l'?chelle d'un end-user ? l'heure actuelle qui dispose au moins d'une IPv4 fixe, il est tout ? fait possible d'avoir un r?seau en double-pile. C'est le cas de mon organisation en tout cas [1]. Les plus gros peuvent au moins faire l'effort sur leurs routeurs de bordure et AU MOINS avoir quelques r?seaux d?di?s pour v6. Il n y a pas de raison pour ne pas en avoir, je suis d?sol?. Je redis ici ce que certains veulent faire transparaitre sur la liste RPD: la priorit? doit ?tre d'aller vers l'avant et encourager l'impl?mentation de v6 car RIEN, absolument RIEN n'emp?che d'avoir des r?seaux v6. C'est plut?t parce qu'on se concentre sur v4 et sur ce qu'on doit faire avec qu'on encourage l'existence du march? noir. > Toujours dans le m?me ordre d?id?e Nat64 serait peut ?tre plus > appropri?. Mais encore nous utilisons dans nos infrastructures > beaucoup d'applications non compatibles v6. IPv4 sera encore utile > pour longtemps en Afrique Donc un travail de fond doit se faire a > ce niveau A mon humble avis, le premier travail de fond est d'enlever le NAT (v4) de l'esprit des gens. C'est une plaie. Je vois des op?rateurs avec 4,5 couches de NAT; excusez moi mais c'est du n'importe quoi. Il y eu des pr?sentations int?ressantes lors du RIPE72 [2] sur des cas pratiques: que ce soit en dual-stack ou v6-only . Encore une fois, il n y a pas d'excuses pour ne pas faire le moindre effort svp. Je vais m?me aller plus loin. J'entends certains ?conomistes (africains) dirent qu'on devrait encourager l'?conomie sous-r?gionale. Entre nous: si on d?cidait d'avoir tous nos r?seaux en v6 et mettre place des services pour communiquer entre nous; vous croyez vraiment qu'on aurait trop besoin de v4 ? (Non, Facebook, Google et consort ont des serveurs chez nous et en v6, donc pas d'excuse) :) - ---------------------------------- I will sum up a bit in english below ... I move my comment from rpd list to community-discuss because it's not related to a specific policy. We have no excuse to not use IPv6 today . NO EXCUSE. We have to remove NAT off our mind and in practice. Even an end-user can proceed at least with a dual-stack network [3] . We shall not focus on what should be fair with IPv4 because we are giving more time to black market. Is that what we want ? I don't think so. Most (if not all) suscriber of this list know how to implement IPv6. And most have enough power to make IPv6 a reality in their organisation,country. Have a look on ripe72 presentations [2], they were many use-cases : Dual-stack, IPv6-only and they all work. Let's move forward guy :) 1. http://ongola.blogspot.com/2016/05/utiliser-ipv6-au-cameroun-en-tant.html 2. https://ripe72.ripe.net/archives 3. https://lists.afrinic.net/pipermail/afripv6-discuss/2016/002047.html - -- Willy Manga freenode: ongolaBoy Ubuntu Cameroonian Loco Team https://launchpad.net/~manga-willy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXTcmHAAoJELJWcwZanTJqlFsP+gPeWwN1Pi5tQO3LTBcFCsXr MMmDg9vbcZKw/zqV1StHZUlDxcJrkp9RpV+OcFExb0+CS08DvGU0/o90CF1lQItD ZC5JnEYuyK7H0QL6L/h6xyFYVSeg1kqw1e+MzId64rcyKwX6eANs4CxyXS0SB/z4 nwekl2dzokV7llNe6jPU5HKAtfSdng8j9uR52gk1L4sh4lAXFkLKKmgnpSEZ1B5M /Cmjts0GUFyUDkJUahNezSknC+CoSwFQLw76UCPdED6VK8GMk3CpckeV4pKfIsPh YKzhVexulejwWEzZg3N2S6YnWLvV4LThLqnw8qykya+o46HIXGUq51bVyKDdF04G 30F9Aud5yuso+ln1KUv+achWSoNt12U79X+mg+PJoVXkCwFQuYCHZ4yUTD4CEVuT tZDGOUDzB+FOHSiz63JJiEmIuTSyG38CwB6Z7Ycc4ym7/ydT2VUByESnJzjg+yUd bJ9e4WK9/HB5146rUrARLOcBRww6+DNLmxgGao45lEuYCts851BqU8aCbsbsS1sl K6BwWjJG2xeWtQ5VDJVlzQnW9okcrs69Y1JN8zqktyG/EWcYj3oP/oycnEbieNtU cAa47VRT+wg5E82I2jLN1geYLHpK/43VZBf6uRdeD3WCstssQL/leHyEsF62ffRz co/R6JTECm5vw+MZe6qd =YDIa -----END PGP SIGNATURE-----