[sig-policy] REMINDER: Nominations for SIG Chair/Co-Chair elections close on 1 September 2023

[George Odagi]

Dear Community Members,

This serves as a final reminder that the deadline for submitting 
nominations for the positions outlined below is 17:30 (UTC +10) on 
Friday, 1 September 2023:

- Policy SIG Chair (one position)
- Policy SIG Co-Chair (one position)
- Cooperation SIG Chair (one position)
- NIR SIG Chair (one position)
- Routing Security SIG Chair (one position)
- Routing Security SIG Co-Chair (one position)


How to nominate


Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/56/elections/sigs/nominations 
<https://conference.apnic.net/56/elections/sigs/nominations>


Who can be nominated


Any individual residing within the Asia Pacific region may be nominated,
with the exception of staff members of any Regional Internet Registry
(RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered and attending the current conference in person. The
attendee must be checked-in at the registration desk at any time
from the start of the conference until 10:00 (UTC +9), Thursday,
14 September 2023.

- Registered and attended at least one of the past eight APRICOT or
APNIC standalone conferences (not including the current
conference):

- APNIC 55 with APRICOT 2023 in Manila, Philippines
- APNIC 54 in Singapore
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand


More information


For more information about the role and the SIGs, please see:

https://conference.apnic.net/56/elections/sigs/about 
<https://conference.apnic.net/56/elections/sigs/about>

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Services Team Lead (East Asia), APNIC
e: helpd...@apnic.net <mailto:helpd...@apnic.net>
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net <http://www.apnic.net>
___
Join the conversation: https://blog.apnic.net/ <https://blog.apnic.net/>



smime.p7s
Description: S/MIME cryptographic signature
___
SIG-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] REMINDER: Nominations for IANA Numbering Services Review Committee (IANA RC) election closes 1 September 2023

[George Odagi]

Dear Community Members,

This serves as a final reminder that the deadline for submitting 
nominations for the IANA Numbering Services Review Committee (IANA RC) 
election is 17:30 (UTC +10) on Friday, 1 September 2023:


How to nominate

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/56/elections/iana-rc/nominations 
<https://conference.apnic.net/56/elections/iana-rc/nominations>


Who can be nominated


Any individual residing within the Asia Pacific region may be nominated,
with the exception of staff members of any Regional Internet Registry
(RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered and attending the current conference in person. The
attendee must be checked-in at the registration desk at any time
from the start of the conference until 10:00 (UTC +9), Thursday,
14 September 2023.

- Registered and attended at least one of the past eight APRICOT or
APNIC standalone conferences (not including the current
conference):

- APNIC 55 with APRICOT 2023 in Manila, Philippines
- APNIC 54 in Singapore
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand


More information

For more information about the role, please see:

https://conference.apnic.net/56/elections/iana-rc/about 
<https://conference.apnic.net/56/elections/iana-rc/about>

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Services Team Lead (East Asia), APNIC
e: helpd...@apnic.net <mailto:helpd...@apnic.net>
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net <http://www.apnic.net>
___
Join the conversation: https://blog.apnic.net/ <https://blog.apnic.net/>



smime.p7s
Description: S/MIME cryptographic signature
___
SIG-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] Nominations now open for SIG Chair/Co-Chair positions

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve for the positions 
below:

- Policy SIG Chair (one position)
- Policy SIG Co-Chair (one position)
- Cooperation SIG Chair (one position)
- Routing Security SIG Chair (one position)
- Routing Security SIG Co-Chair (one position)

The successful nominee will be elected to serve as a SIG Chair or Co-Chair 
for two years from the end of the conference (APNIC 56) in 2023 to end 
of the conference (APNIC 60) in 2025.

Individuals cannot hold more than one elected position (EC, SIG, IANA RC 
or NRO NC). 

Those who are elected to a new position must resign from any other 
currently held EC, SIG, IANA RC or NRO NC position as soon as practicable 
but no later than 30 days following the election.

Nominees will be invited to provide a recorded video candidate statement, 
which will be published on the APNIC 56 conference website.


Nomination deadline
---

Friday, 1 September 2023 at 17:30 (UTC +10)


Who can be nominated


Any individual residing within the Asia Pacific region may be nominated, 
with the exception of staff members of any Regional Internet Registry 
(RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered and attending the current conference in person. The 
attendee must be checked-in at the registration desk at any time 
from the start of the conference until 10:00 (UTC +9), Thursday, 
14 September 2023.

- Registered and attended at least one of the past eight APRICOT or 
APNIC standalone conferences (not including the current 
conference):

- APNIC 55 with APRICOT 2023 in Manila, Philippines
- APNIC 54 in Singapore
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand


How to nominate
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/56/elections/sigs/nominations 
<https://conference.apnic.net/56/elections/sigs/nominations>


More information


For more information about the role and the SIGs, please see:

https://conference.apnic.net/56/elections/sigs/about 
<https://conference.apnic.net/56/elections/sigs/about>

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Services Team Lead (East Asia)
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation: https://blog.apnic.net/



smime.p7s
Description: S/MIME cryptographic signature
___
SIG-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] Nominations now open for IANA Numbering Services Review Committee (IANA RC)

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking a volunteer to serve on the IANA 
Numbering Services Review Committee (IANA RC) from the APNIC region.

The successful nominee will be elected to serve on the IANA RC for two 
years from 1 January 2024 to 31 December 2025.

Individuals cannot hold more than one elected position (EC, SIG, IANA RC 
or NRO NC). 

Those who are elected to a new position must resign from any other 
currently held EC, SIG, IANA RC or NRO NC position as soon as practicable 
but no later than 30 days following the election.

Nominees will be invited to provide a recorded video candidate statement, 
which will be published on the APNIC 56 conference website.


Nomination deadline
---

Friday, 1 September 2023 at 17:30 (UTC +10)


Who can be nominated


Any individual residing within the Asia Pacific region may be nominated, 
with the exception of staff members of any Regional Internet Registry 
(RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered and attending the current conference in person. The 
attendee must be checked-in at the registration desk at any time 
from the start of the conference until 10:00 (UTC +9), Thursday, 
14 September 2023.

- Registered and attended at least one of the past eight APRICOT or 
APNIC standalone conferences (not including the current 
conference):

- APNIC 55 with APRICOT 2023 in Manila, Philippines
- APNIC 54 in Singapore
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand


How to nominate
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/56/elections/iana-rc/nominations 
<https://conference.apnic.net/56/elections/iana-rc/nominations>


More information


For more information about the role, please see:

https://conference.apnic.net/56/elections/iana-rc/about 
<https://conference.apnic.net/56/elections/iana-rc/about>

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Services Team Lead (East Asia)
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation: https://blog.apnic.net/



smime.p7s
Description: S/MIME cryptographic signature
___
SIG-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] Re: Join the APNIC 55 Policy Proposals Webinar

[George Odagi]

Hi Jordi and Aftab,

Some interesting questions were asked for the authors during the webinar 
session. You can watch the Zoom video recording below and respond back in the 
mailing list if you wish.

https://apnic.zoom.us/rec/share/VvO45SZ60cDAe0g96Yq6iGDHbUX5EZBi0IoileJJgX8Q6OtaHwPcX6arRwH1LfHL.SOyI1tdwPjgjU9Is
 

 

Thanks!

Regards,


George O

From: jordi.palet--- via sig-policy 
Date: Thursday, 16 February 2023 at 8:49 pm
To: Bertrand Cherrier 
Cc: mailman_SIG-policy 
Subject: [sig-policy] Re: Join the APNIC 55 Policy Proposals Webinar

Same problem here, without organizing with the authors of the proposals in 
advance, it is almost impossible that we can participate!






El 13 feb 2023, a las 3:23, Aftab Siddiqui  escribió:


Accept my apologies, I won't be joining the webinar due to other prior 
commitments. If anyone would like to understand more about prop-150 
 and prop-151 
 proposals please 
let me know via mailing list or you can send an email to me for any 
questions/concerns you have. 


prop-150: ROA/whois object with Private, Reserved and Unallocated 
(reserved/available) Origin ASN

prop-151: Restricting non-hierarchical as-set



Regards,

Aftab A. Siddiqui








On Sat, 11 Feb 2023 at 14:36, Bertrand Cherrier mailto:b.cherr...@mynet.nc>> wrote:

Dear Colleagues,


Policy SIG is organizing an open webinar for the authors of the policy 
proposals to be discussed at the APNIC 55 Open Policy Meeting (OPM).


The purpose of the webinar is to provide an opportunity for the authors 
to share their policy proposals with the community and for the community 
to provide feedback to the authors, if any.


We invite you to join this webinar on:


Date: Thursday, 16 February 2023
Time: 14:00 (UTC +10)
Duration: 1 hour


The webinar is open to anyone who wishes to participate. If you are 
interested, please register here to join.
https://apnic.zoom.us/webinar/register/WN_9P4bLuskRhOUvdxN132CEw 

After registering, you will receive a confirmation email containing 
information about joining the session.


Useful links for reference:


- APNIC 55 Policy Proposals
https://conference.apnic.net/55/policy/proposals/ 

- APNIC Policy SIG
https://www.apnic.net/community/policy/policy-sig/ 

We look forward to seeing you online.


Regards,
Bertrand, Shaila, and Anupam
APNIC Policy SIG Chairs 

___
sig-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/ 

To unsubscribe send an email to sig-policy-le...@lists.apnic.net 


___
sig-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net





**
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the exclusive use of the 
individual(s) named above and further non-explicilty authorized disclosure, 
copying, distribution or use of the contents of this information, even if 
partially, including attached files, is strictly prohibited and will be 
considered a criminal offense. If you are not the intended recipient be aware 
that any disclosure, copying, distribution or use of the contents of this 
information, even if partially, including attached files, is strictly 
prohibited, will be considered a criminal offense, so you must reply to the 
original sender to inform about this communication and delete it.



smime.p7s
Description: S/MIME cryptographic signature
___
sig-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] Re: Nominations now open for SIG Chair/Co-Chair positions

[George Odagi]

Hi all,,
 
My sincerest apologies for the error in my previous email, the correct deadline 
for nominations is:

17:30 (UTC +10), Monday, 8 August 2022

 
Regards,
___
George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/





 

On 8/8/22, 2:19 pm, "George Odagi"  wrote:

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve for the below
positions:

Policy SIG Co-Chair (one position)
NIR SIG Co-Chair (one position)
Cooperation SIG Co-Chair (one position)
Routing Security SIG Chair (one position)

The successful nominee will be elected to serve as a SIG Chair/Co-Chair
for 2 years from the end of the APNIC 54 conference in 2022 to end of the 
APNIC 58 conference in 2024.

The deadline for nominations is:
---

09:30 (UTC +8), Tuesday, 13 September 2022.

Who can be nominated:
---

Any individual residing within the Asia Pacific region may be nominated,
with the exception of staff members of any Regional Internet Registry (RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered for the current conference (APNIC 54) with the registration 
form submitted before the start of the current conference.
-Registered and attended at least one of the past eight APRICOT or APNIC 
standalone conferences (not including the current conference):
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand
- APNIC 47 with APRICOT 2019 in Daejeon, South Korea
- APNIC 46 in Noumea, New Caledonia


How to nominate:
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/54/elections/sigs/nominations/

More information
---

For more information about the role and the SIGs, please see:

https://conference.apnic.net/54/elections/sigs/about/

Please contact the APNIC Helpdesk if you have any questions.


Regards,
_______
    George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

___
sig-policy - sig-policy@lists.apnic.net <https://mailman.apnic.net//">https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net


smime.p7s
Description: S/MIME cryptographic signature
___
sig-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] Nominations now open for SIG Chair/Co-Chair positions

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve for the below
positions:

Policy SIG Co-Chair (one position)
NIR SIG Co-Chair (one position)
Cooperation SIG Co-Chair (one position)
Routing Security SIG Chair (one position)

The successful nominee will be elected to serve as a SIG Chair/Co-Chair
for 2 years from the end of the APNIC 54 conference in 2022 to end of the 
APNIC 58 conference in 2024.

The deadline for nominations is:
---

09:30 (UTC +8), Tuesday, 13 September 2022.

Who can be nominated:
---

Any individual residing within the Asia Pacific region may be nominated,
with the exception of staff members of any Regional Internet Registry (RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered for the current conference (APNIC 54) with the registration 
form submitted before the start of the current conference.
-Registered and attended at least one of the past eight APRICOT or APNIC 
standalone conferences (not including the current conference):
- APNIC 53 Online
- APNIC 52 Online
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand
- APNIC 47 with APRICOT 2019 in Daejeon, South Korea
- APNIC 46 in Noumea, New Caledonia


How to nominate:
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/54/elections/sigs/nominations/

More information
---

For more information about the role and the SIGs, please see:

https://conference.apnic.net/54/elections/sigs/about/

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

___
sig-policy - https://mailman.apnic.net/sig-policy@lists.apnic.net/
To unsubscribe send an email to sig-policy-le...@lists.apnic.net

[sig-policy] REMINDER: Nominations for Policy SIG Chair/Co-Chair deadline 6 September 2021

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve as Chair and
Co-Chair of the Policy SIG.

The successful nominee will be elected to serve as a SIG Chair/Co-Chair 
for 2 years from the end of the APNIC 52 conference in 2021 to end of the 
APNIC 56 conference in 2023.

The deadline for nominations is:
---

17:30 (UTC +10) on Monday, 6 September 2021.

Who can be nominated:
---

Any individual residing within the Asia Pacific region may be nominated, 
with the exception of staff members of any Regional Internet Registry (RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered for the current conference (APNIC 52) with the registration 
form submitted before the start of the current conference.
- Registered and attended at least one of the past eight APRICOT or APNIC 
standalone conferences (not including the current conference):
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand
- APNIC 47 with APRICOT 2019 in Daejeon, South Korea
- APNIC 46 in Noumea, New Caledonia
- APNIC 45 with APRICOT 2018 in Kathmandu, Nepal
- APNIC 44 in Taichung, Taiwan

How to nominate:
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/52/elections/sigs/nominations/

More information
---

For more information about the role and the SIGs, please see:

https://conference.apnic.net/52/elections/sigs/about/

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Nominations now open for IANA Numbering Services Review Committee (IANA RC)

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking a volunteer to serve on the IANA 
Numbering Services Review Committee (IANA RC) from the APNIC region.

The successful nominee will be elected to serve on the IANA RC for 
2 years from 1 January 2022 to 31 December 2023.

The deadline for nominations is:
---

17:30 (UTC +10) on Monday, 6 September 2021.

Who can be nominated:
---

Any individual residing within the Asia Pacific region may be nominated, 
with the exception of staff members of any Regional Internet Registry (RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered for the current conference (APNIC 52) with the registration 
form submitted before the start of the current conference.
- Registered and attended at least one of the past eight APRICOT or APNIC 
standalone conferences (not including the current conference):
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand
- APNIC 47 with APRICOT 2019 in Daejeon, South Korea
- APNIC 46 in Noumea, New Caledonia
- APNIC 45 with APRICOT 2018 in Kathmandu, Nepal
- APNIC 44 in Taichung, Taiwan

How to nominate:
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/52/elections/iana-rc/nominations/

More information
---

For more information about the role and the SIGs, please see:

https://conference.apnic.net/52/elections/iana-rc/about/

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Nominations now open for Policy SIG Chair/Co-Chair

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve as Chair and
Co-Chair of the Policy SIG.

The successful nominee will be elected to serve as a SIG Chair/Co-Chair 
for 2 years from the end of the APNIC 52 conference in 2021 to end of the 
APNIC 56 conference in 2023.

The deadline for nominations is:
---

17:30 (UTC +10) on Monday, 6 September 2021.

Who can be nominated:
---

Any individual residing within the Asia Pacific region may be nominated, 
with the exception of staff members of any Regional Internet Registry (RIR).

Self-nominations are permitted.

The nominee must meet the following two eligibility criteria:

- Registered for the current conference (APNIC 52) with the registration 
form submitted before the start of the current conference.
- Registered and attended at least one of the past eight APRICOT or APNIC 
standalone conferences (not including the current conference):
- APNIC 51 Online
- APNIC 50 Online
- APNIC 49 with APRICOT 2020 in Melbourne, Australia
- APNIC 48 in Chiang Mai, Thailand
- APNIC 47 with APRICOT 2019 in Daejeon, South Korea
- APNIC 46 in Noumea, New Caledonia
- APNIC 45 with APRICOT 2018 in Kathmandu, Nepal
- APNIC 44 in Taichung, Taiwan

How to nominate:
---

Nominations and self-nominations may be submitted using the online
form:

https://conference.apnic.net/52/elections/sigs/nominations/

More information
---

For more information about the role and the SIGs, please see:

https://conference.apnic.net/52/elections/sigs/about/

Please contact the APNIC Helpdesk if you have any questions.


Regards,
___
George Odagi
Senior Internet Resource & Policy Analyst, APNIC
e: helpd...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

Re: [sig-policy] APNIC Whois role object - Proposed changes

[George Odagi]

Hi Anupam, Thanks again for your comments. Just firstly want to clarify that the role and IRT are two different whois objects with different purposes and we are not proposing to make them the same. You can read more about each object here: https://www.apnic.net/manage-ip/using-whois/guide/role/https://www.apnic.net/manage-ip/using-whois/guide/irt/ To accommodate the requirements in prop-125 to implement 'abuse-c', the role object was used to mirror the contact information published in the IRT object. We will be presenting more details about the proposed change at APNIC 52 to gather wider community feedback and will also share an impact assessment outlining any system changes required (if any). However we believe this is a simple change and should not affect our current systems.  Regards, ___George OdagiSenior Internet Resource & Policy Analyst, APNICe: helpd...@apnic.netp: +61 7 3858 3188f: +61 7 3858 3199www.apnic.net___Join the conversation:   https://blog.apnic.net/ From: Anupam Agrawal Date: Friday, 4 June 2021 at 4:30 amTo: George Odagi Cc: sig-policy@lists.apnic.net Subject: RE: [sig-policy] APNIC Whois role object - Proposed changesDear George,  Once the proposed change is done, there will be no difference between the role object & irt object. Assuming, its okay with everyone to move head, is a dependency analysis available with you? I mean by dependency analysis an exercise to confirm whether or not there is something else which is dependent on role object (being changed) and if there are dependents, whether or not there is an impact of the proposed change.  RegardsAnupam  From: George OdagiSent: Wednesday, June 2, 2021 8:30 AMTo: Anupam AgrawalCc: sig-policy@lists.apnic.netSubject: Re: [sig-policy] APNIC Whois role object - Proposed changes Hi Anupam, Thanks for your feedback. The country information is already published in other whois attributes such as in the resource records and organization object when querying an IP address or AS number. Regarding the phone number - once it becomes optional, there is no need to populate with '+0' if a phone number has not been published in the IRT object itself. Currently it is forced to include the number as the attribute is mandatory in the role object. To give you an example of the issue at hand, please see example of IRT and abuse role objects below: irt:    IRT-APNICRANDNET-AUaddress:    PO Box 3646address:    South Brisbane, QLD 4101address:    Australiae-mail: helpd...@apnic.netabuse-mailbox:  helpd...@apnic.netadmin-c:    AR302-APtech-c: AR302-APauth:   # Filteredremarks:    helpd...@apnic.net was validated on 2021-02-09mnt-by: MAINT-AU-APNIC-GM85-APlast-modified:  2021-03-09T01:10:21Zsource: APNIC role:   ABUSE APNICRANDNETAUaddress:    PO Box 3646address:    South Brisbane, QLD 4101address:    Australiacountry:    ZZphone:  +0e-mail: helpd...@apnic.netadmin-c:    AR302-APtech-c: AR302-APnic-hdl:    AA1412-APremarks:    Generated from irt object IRT-APNICRANDNET-AUabuse-mailbox:  helpd...@apnic.netmnt-by: APNIC-ABUSElast-modified:  2021-03-09T01:10:22Zsource: APNIC  Regards, ___George OdagiSenior Internet Resource & Policy Analyst, APNICe: helpd...@apnic.netp: +61 7 3858 3188f: +61 7 3858 3199www.apnic.net___Join the conversation:   https://blog.apnic.net/ From: Anupam Agrawal Date: Tuesday, 1 June 2021 at 11:13 pmTo: George Odagi Cc: sig-policy@lists.apnic.net Subject: Re: [sig-policy] APNIC Whois role object - Proposed changesDear George, Having the country information is definitely an advantage. If the phone number is made optional, then the issue of phone field getting populated with + will still be there if the phone number is not given.  Pardon my ignorance but the current APNIC model - it is causing an issue exactly where? Regards--Anupam Agrawal | India Internet Foundation - Chair | 91 990 399 2838 On 01-Jun-2021, at 10:23 AM, George Odagi <god...@apnic.net> wrote: Dear Community Members, In light of the recent discussion about abuse role objects that were created as a result of prop-125, we would like to share background information about this implementation and consult with the community. APNIC acknowledges this is a known issue caused by a limitation in whois – which requires the phone number and country attributes to be mandatory in role objects. The abuse role objects are auto-generated from IRT objects, where the phone number attribute is optional and the country attribute which does not exist. This resulted in populating the phone number with '+0' in the event no phone number was p

Re: [sig-policy] about prop-125 Implementation update

[George Odagi]

Hi Jordi,

Thanks for watching the presentation and for your comments.

Based on our recommendations, we are suggesting the following changes:



Example of new validation procedure

1) APNIC initiates the validation automatically ONCE a year, sending ONE email 
to the 'abuse-mailbox' address. 
(We will consider deprecating the 'email' attribute so only one email address 
requires validation)

2) The email will be sent containing plain text only.

3) The email will contain the unique code required for the validation and may 
contain information about the procedure, a brief summary of this policy, etc.

4) The person in charge of the mailbox will be instructed to visit the APNIC 
website (eg. www.apnic.net/irt-validation) and paste the code received in their 
email. (MyAPNIC cannot be used since many abuse mailboxes are either customers 
of members or company staff who do not have MyAPNIC access).

5) The IRT validation page on the APNIC website will be designed in a way that 
it prevents the use of an automated process (for example, "CAPTCHA"). In 
addition, it will contain a text that confirms that the person performing the 
validation understands the procedure and the policy, that they regularly 
monitor the mailboxes, that measures are taken to solve reported cases of 
abuse, and that the abuse report receives a response, with a "checkbox" that 
must be accepted in order to proceed.

6) If the code is not entered within 15 days, the system will mark the IRT as 
"Invalid” in the APNIC Whois Database and an automatic reminder will be sent. 
If validation is still not completed after 30 days, MyAPNIC access will be 
restricted and APNIC staff will follow-up with the member using all contact 
methods available.

7) Once the validation has been resolved, the IRT will be marked as "Valid" and 
MyAPNIC access will be reinstated.



From the Secretariat's point of view - the intention is to make minor tweaks to 
the existing process to simplify the validation and reduce burden that we are 
putting on members. Most of the changes can be made as operational procedure; 
however the current policy text specifies that validation occurs every 6 
months, so we would need an amended proposal to change this timeframe. We want 
to keep this simple by using a fixed timeframe of once yearly as we are already 
starting to reach the goals that we have set out to achieve in this policy. 

Regarding the NIRs, they have reported the following statuses:

- CNNIC is almost ready to implement
- IDNIC have implemented but still tweaking
- JPNIC is working with JPOPF on the implementation
- TWNIC and VNNIC will implement by Q1 2021

We are currently in discussion with IRINN and KRNIC about their implementation 
plan.

We would love to hear from the rest of the community about these changes and 
work together in amending this policy.

Any questions or concerns, please let us know.


Regards,

_______
George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/


 









On 10/9/20, 5:57 pm, "sig-policy-boun...@lists.apnic.net on behalf of JORDI 
PALET MARTINEZ"  wrote:

Hi George, all,

I just looked at the presentation that you have done earlier today and have 
some inputs about possible ways to improve it.

1. Slides 9-10
1.1. About receiving spam
The abuse mailbox should receive *all* the emails to be able to receive 
abuse reports about spam. If you filter emails that contain headers from spam, 
then you are ruining the purpose of the abuse-c. Clearly this could be 
improved, as an operational decision, by making some kind of automation, but in 
such way that ensures that only real spam is dropped. Note that the other RIRs 
are also using (at some point), validation links via the abuse-c email.

1.2. About clicking links
I provided an example procedure in the policy proposal to avoid this. I've 
copied this below my signature. See points 1-5. If that procedure is followed, 
I think it is obvious that you will avoid this problem. I missed to ensure 
during the previous implementation presentations, that you are following a 
procedure that avoids this problem. Of course, you can even avoid needing to 
send the validation link if you just say in the email with the code "you need 
to go to your MyAPNIC account to use this code" ... Maybe also an alternative 
is to use email certificates from APNIC.

2. Slide 11
2.1. About the validation cycle.
In more recent versions of this policy, in other RIRs, I have included 
specific text so APNIC can 

Re: [sig-policy] prop-133: Clarification on Sub-Assignments

[George Odagi]

Hi Jordi,

Thanks for your patience with this.

We have some stats (from the last 15 years) for members with ISP industry type 
who have received at least one portable IPv4 allocation and IPv6 assignment:

2005: 1
2008: 2
2011: 2
2012: 1
2013: 4
2014: 8
2015: 3
2016: 13
2017: 12
2018: 13
2019: 102
2020: 28

Total: 189

For most multihoming IPv4/PI IPv6 assignments, we mainly assess the policy 
criteria and don't always ask what they will use the assignment for. Members 
who have both allocation and assignment could have taken the 'one-click' IPv6 
assignment via MyAPNIC and again we won't know for sure why they took the 
assignment option.

I hope this helps.

Regards,

___
George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

 







On 4/3/20, 4:19 pm, "sig-policy-boun...@lists.apnic.net on behalf of George 
Odagi"  wrote:

Hi Jordi,

Generally speaking - when a LIR (such as an ISP) receives an allocation, 
they can use those IPs for their infrastructure as well as for their customers. 
While most LIRs do this, we have received IP assignment requests for reasons 
such as multihoming their new POPs. 

Once we make an IP assignment to an LIR or an end-user, we expect them to 
use that assignment for the purpose it was delegated. Provided those IPs are 
being routed, we consider them being used for the purpose it was delegated.

The data you have requested is not readily available and we will need more 
time to look into it. APNIC Secretariat will share this soon.


Regards,

___
    George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/








On 26/2/20, 5:35 pm, "sig-policy-boun...@lists.apnic.net on behalf of JORDI 
PALET MARTINEZ"  wrote:

Hi Sunny,

I'm mainly interested in the assignments to ISP infrastructure, as the 
others are different cases, and clearly are "end-users". The point is to 
understand if there is really a need for ISPs to get additional assignments, 
why they can't do it already from their own allocation. 

Any indication of the tendency for those cases (assignments for ISP 
infrastructure), I mean if this was in an early stage and the is going up or 
going down?

What specific text of the policy or guidelines is "being" used to do 
that?

Regards,
Jordi
@jordipalet
 
 



El 26/2/20 4:18, "Srinivas Chendi"  escribió:

Hi Jordi,

On 24/02/2020 1:39 pm, Srinivas (Sunny) Chendi wrote:
>>
>> One more request for the secretariat. Could you please provide 
stats 
>> on the number of ISP (not end-users) assignments, for example in 
the 
>> last 12-15 years, in order to understand if this is a real 
requirement?
> 
> Noted! Secretariat will provide the stats soon.
> 
> Regards
> Sunny

To date we have delegated portable assignments to 547 ISPs. Some 
common 
reasons for this include:

- Assignment to operate IXP
- Historical Resource assignments
- M of members who held assignments
- Assignment for ISP infrastructure

Regards
Sunny




**
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the exclusive use of the 
individual(s) named above and further non-explicilty authorized disclosure, 
copying, distribution or use of the contents of this information, even if 
partially, including attached files, is strictly prohibited and will be 
considered a criminal offense. If you are not the intended recipient be aware 
that any disclosure, copying, distribution or use of the contents of this 
information, even if partially, including attached files, is strictly 
prohibited, will be considered a criminal offense, so you must reply to the 
original sender to inform about this communication and delete

Re: [sig-policy] prop-133: Clarification on Sub-Assignments

[George Odagi]

Hi Jordi,

Generally speaking - when a LIR (such as an ISP) receives an allocation, they 
can use those IPs for their infrastructure as well as for their customers. 
While most LIRs do this, we have received IP assignment requests for reasons 
such as multihoming their new POPs. 

Once we make an IP assignment to an LIR or an end-user, we expect them to use 
that assignment for the purpose it was delegated. Provided those IPs are being 
routed, we consider them being used for the purpose it was delegated.

The data you have requested is not readily available and we will need more time 
to look into it. APNIC Secretariat will share this soon.


Regards,

___
George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/








On 26/2/20, 5:35 pm, "sig-policy-boun...@lists.apnic.net on behalf of JORDI 
PALET MARTINEZ"  wrote:

Hi Sunny,

I'm mainly interested in the assignments to ISP infrastructure, as the 
others are different cases, and clearly are "end-users". The point is to 
understand if there is really a need for ISPs to get additional assignments, 
why they can't do it already from their own allocation. 

Any indication of the tendency for those cases (assignments for ISP 
infrastructure), I mean if this was in an early stage and the is going up or 
going down?

What specific text of the policy or guidelines is "being" used to do that?

Regards,
Jordi
@jordipalet
 
 



El 26/2/20 4:18, "Srinivas Chendi"  escribió:

Hi Jordi,

On 24/02/2020 1:39 pm, Srinivas (Sunny) Chendi wrote:
>>
>> One more request for the secretariat. Could you please provide stats 
>> on the number of ISP (not end-users) assignments, for example in the 
>> last 12-15 years, in order to understand if this is a real 
requirement?
> 
> Noted! Secretariat will provide the stats soon.
> 
> Regards
> Sunny

To date we have delegated portable assignments to 547 ISPs. Some common 
reasons for this include:

- Assignment to operate IXP
- Historical Resource assignments
- M of members who held assignments
- Assignment for ISP infrastructure

Regards
Sunny




**
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or 
confidential. The information is intended to be for the exclusive use of the 
individual(s) named above and further non-explicilty authorized disclosure, 
copying, distribution or use of the contents of this information, even if 
partially, including attached files, is strictly prohibited and will be 
considered a criminal offense. If you are not the intended recipient be aware 
that any disclosure, copying, distribution or use of the contents of this 
information, even if partially, including attached files, is strictly 
prohibited, will be considered a criminal offense, so you must reply to the 
original sender to inform about this communication and delete it.



*  sig-policy:  APNIC SIG on resource management policy 
  *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy SIG Co-Chair Nominations now open

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking two volunteers to serve as Co-Chairs of
the Policy SIG for a two-year term period.

If you would like to nominate yourself or somebody else, please do so
before the deadline. Nominations will be accepted only by using the
online form:

https://2020.apricot.net/apnic-sigs/elections/

The deadline for nominations is:

23:59 (UTC +10)
Sunday, 16 February 2020

Nominees must confirm they are able to fulfil the responsibilities of
Co-Chair as outlined in the APNIC SIG Guidelines:

https://www.apnic.net/sig-guidelines

The election will be the first agenda item of the Policy SIG session on
Thursday, 20 February 2020.


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___ 


smime.p7s
Description: S/MIME cryptographic signature
*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

Re: [sig-policy] Hello SIG-policy team

[George Odagi]

Hi Bromand,

 

You can participate in person at APNIC 48 in Chiang Mai, Thailand by attending 
the Policy SIG sessions on Thursday, 12 September. 

 

See the link below for more information:

 

https://conference.apnic.net/48/policy/participating/

 

If this is your first time at an APNIC conference, I recommend that you attend 
the Newcomers session on Tuesday, 10 September. In this session you will learn 
about APNIC and APNIC Services, the conference program and how to engage in the 
Policy Development Process (PDP).

 

Hope to see you there!

 

 

Regards,

___

George Odagi

Internet Resource Analyst/Policy Support, APNIC

e: god...@apnic.net

p: +61 7 3858 3188

f: +61 7 3858 3199

www.apnic.net

___

Join the conversation:   https://blog.apnic.net/

 

 

From:  on behalf of Sadeq bromand 

Date: Thursday, 29 August 2019 at 11:58 pm
To: "sig-policy@lists.apnic.net" 
Subject: [sig-policy] Hello SIG-policy team

 

Thanks for your email and inviting me in SIG-policy 48: could you please clear 
me about how to participate person not remotely in SIG-policy meeting? 

 

Regards 

Bromand

-- 




smime.p7s
Description: S/MIME cryptographic signature
*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy SIG Chair Nominations now open

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve as Chair of
the Policy SIG for a two-year term period.

If you would like to nominate yourself or somebody else, please do so
before the deadline. Nominations will be accepted only by using the 
online form:

https://2019.apricot.net/apnic-sigs/elections/

The deadline for nominations is:
--
23:59 (UTC +10)
Friday, 22 February 2019

The responsibilities are outlined in Section 2.3 of the APNIC SIG
Guidelines.

https://www.apnic.net/sig-guidelines

The election will be the first agenda item of the APNIC Policy SIG
meeting on Wednesday, 27 February 2019.


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___


smime.p7s
Description: S/MIME cryptographic signature
*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy SIG Co-Chair Nominations now open

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve as Co-Chair of 
the APNIC Policy SIG.

The SIG Guidelines prefer that Chair and Co-Chair terms end in alternate
years to provide continuity if there is a change in leadership. If a new 
Co-Chair is needed they will serve a one-year term.

The deadline for nominations is:
--
23:59 (UTC +10)
Friday, 23 February 2018

The responsibilities are outlined in Section 2.3 of the APNIC SIG
Guidelines.

https://www.apnic.net/sig-guidelines

Nominations will be accepted only by using the following form:

https://www.apnic.net/policy-sig/nominate

The election will be the first agenda item of the APNIC Policy SIG
meeting on Tuesday, 27 February 2018.


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___



*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Final editorial comments on draft document

[George Odagi]

___

Final editorial comments on draft document
___

APNIC seeks final editorial comments on the following draft changes to the
APNIC Internet Number Resource Policies document.

The document has been updated to implement one policy proposal reaching
consensus at APNIC 43 in Ho Chi Minh City during February 2017.

The proposal is:
- prop-117: Returned IPv4 address management and Final /8 exhaustion
https://www.apnic.net/community/policy/proposals/prop-117/


Nature of the document review

This is an editorial review only. Consensus has already been reached on
these policy changes.

Therefore, during the comment period, interested parties may:
- Object to the wording provided by the Secretariat
- Suggest improvements to any aspect of the document
- Request that an additional call for comment be made if substantial
  revisions are required

To view all draft documents, please see:

http://www.apnic.net/community/policy/drafts


Implementation date
--
Following the editorial comment period, the new policies will be
implemented on 24 July 2017.


Deadline for comments
-
Your comments are requested before 24 July 2017.
Please send your comments to: pol...@apnic.net


Kind regards,
 
___
George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: hostmas...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from LACNIC 27

[George Odagi]

Dear Community Members,

Last week in Foz do Iguaçu, Brazil, the LACNIC 27 meeting considered
7 policy proposals.

Four proposal reached consensus and were moved to the 45-day final
comment period. Two proposals did not reach consensus and continue to 
be under discussion. One proposal was abandoned, while another proposal 
was abandoned shortly before the meeting.

Please see below for more detail.


Proposals reaching consensus


- LAC-2017-4: Modify the minimum size of initial allocations to ISPs
  This would reduce the minimum IPv4 allocation from /22 to a /24 to
  assist with exhaustion management.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-4?language=en

- LAC-2017-5: Addenda − Resource revocation
  Allows the LACNIC Board of Directors to extend the period for
  operators to meet policy requirements before the addresses
  recovery process in cases where the recourses form critical
  infrastructure, or in exceptional situations such as natural
  disasters or political instability.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-5?language=en

- LAC-2017-1: Rectifying the size of initial allocations
  Allows ISPs who have underestimated their initial IPv6 request due
  to inexperience, to obtain an additional prefix rather than return
  and renumber.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-1?language=en

- LAC-2016-7: Modify the size of initial IPv6 allocations
  Allows for large IPv6 allocations to organizations that are not
  traditional ISPs.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2016-7?language=en


Proposals not reaching consensus


- LAC-2017-6: Modify the Resource Recovery Process
  This would require LACNIC to publish the details of resources to
  be recovered for a period of three months, to accommodate cases
  where the resource holder cannot be contacted.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-6?language=en

- LAC-2017-2: One-way interregional transfers to LACNIC
  This proposal would allow inter-RIR transfers, but only in cases
  where the recipient was in th eLACNIC region. Resources could not
  be trasnferred out of the Region.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-2?language=en


Proposals abandoned
---

- LAC-2017-3: Modify the minimum size of IPv4 assignments to
  Internet Service Providers
  This was a competing proposal to LAC-2017-4, which reached
  consensus.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2017-3?language=en

- LAC-2016-5: Modify the size of initial IPv6 allocations
  This was a competing proposal to LAC-2016-7, which reached
  consensus.
  https://politicas.lacnic.net/politicas/detail/id/LAC-2016-5?language=en


An overview of LACNIC´s policy proposals can be found here:

  https://politicas.lacnic.net/politicas/list


Read about the LACNIC Policy Development Process here:

  http://www.lacnic.net/en/web/lacnic/proceso-de-desarrollo-de-politicas


Kind regards,

___
George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: hostmas...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Register for CONFER now

[George Odagi]

Dear Community Members,

The APNIC Policy SIG meeting will be held on Wednesday, 1 March 2017.
Three policy proposals will be discussed. We encourage you to take part 
in consensus calls by logging on to CONFER.

CONFER stands for CONsensus FEedback in Realtime and is an electronic 
system to replace the traditional “show of hands” used in APNIC SIG 
sessions.

Register for CONFER to be able to participate in the Consensus Call:

https://consensus.apnic.net

Instructions for using CONFER can be found here:

https://www.apnic.net/using-confer


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy SIG Chair and Co-Chair Nominations now open

[George Odagi]

Dear Community Members,

The APNIC Secretariat is now seeking volunteers to serve as Chair and 
Co-Chair of the APNIC Policy SIG. 

The SIG Guidelines prefer that Chair and Co-Chair terms end in alternate 
years to provide continuity if there is a change in leadership. We 
propose the Chair be elected for a two-year term. If a new Co-Chair is 
needed they will serve a one-year term.

The deadline for nominations is:
--
23:59 (UTC +10)
Wednesday, 22 February 2017

The responsibilities are outlined in Section 2.3 of the APNIC SIG
Guidelines.

https://www.apnic.net/sig-guidelines

Nominations will be accepted only by using the following form:

https://www.apnic.net/policy-sig/nominate

The election will be the first agenda item of the APNIC Policy SIG
meeting on Wednesday, 1 March 2017.


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199 
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from AFRINIC 25

[George Odagi]

Dear Community Members,

Following the AFRINIC 25 meeting in Mauritius, the proposals under
discussions during the Policy Development Working Group (PDWG) session
on Tuesday, 29 November 2016 reached the following statuses:


Reached Consensus and moved to Final Call
-

 - AFPUB-2016-V4-003-DRAFT02: IPv4 Resources Transfer within the
 AFRINIC region
 
http://afrinic.net/en/library/policies/archive/1813-ipv4-resources-transfer-within-the-afrinic-region

 This proposal aims to solve the issue around enabling African
 organisations to receive IPv4 addresses even after IPv4 pool
 exhaustion or when AFRINIC can no longer satisfy the needs of
 such organisations.

Returned to the Mailing List for further discussion
---

 - AFPUB-2016-GEN-002-DRAFT-01: Inbound Transfers Policy
 
http://afrinic.net/en/community/policy-development/policy-proposals/1803-inbound-transfer-policy

 This proposal covers the inbound transfer of all resources from
 other RIRs to the AFRINIC service region. While the community has
 voiced concerns that enacting a transfer policy will result in the
 flow of resources off the continent, this policy addresses that by
 purely catering for inbound transfers.

 - AFPUB-2016-GEN-001-DRAFT02: Internet Number Resources review by
 AFRINIC
 
http://afrinic.net/en/community/policy-development/policy-proposals/1827-internet-number-resources-review-by-afrinic

 This proposal gives AFRINIC authority to conduct regular reviews/
 audits of resource utilisation to ensure efficient and appropriate
 use of resources. It allows for recovery of any type of resource
 where usage is not in compliance with the RSA or policy.

 - AFPUB-2016-V4-001-DRAFT03: IPv4 Soft Landing – BIS
 
http://afrinic.net/en/community/policy-development/policy-proposals/1815-ipv4-soft-landing-bis

 This proposal aims at introducing some provisions to the current
 soft landing policy to cater for reserving space to critical
 infrastructure, making a provision for late requesters and
 stipulating an IPv6 requirement for any company that requests space
 from the last /8.

 - AFPUB-2016-V4-002-DRAFT01: Proposal: IPv4 Soft Landing Overhaul
 
http://afrinic.net/en/community/policy-development/policy-proposals/1623-soft-landing-overhaul

 This proposal aims at maintaining the needs-based approach to
 issuing IPv4 space (by completely removing the current IPv4 Soft
 Landing Policy).


An overview of AFRINIC´s policy proposals can be found here:

 http://afrinic.net/en/community/policy-development/policy-proposals

Find more information about the AFRINIC Policy Development Process here:

 http://afrinic.net/en/community/policy-development


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___








*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] FINAL REMINDER: APNIC Policy Proposal Deadline is Friday, 26 August 2016

[George Odagi]

Dear Community Members,

This is a final reminder that the APNIC Policy SIG Chairs have
previously announced (see below) that new proposals to be considered
at the APNIC 42 Policy SIG must be submitted before the deadline.

Proposal Deadline
---
Friday, 26 August @ 23:59 (UTC+10)

Submissions

Please use the online form at
   http://www.apnic.net/community/policy/proposals/submit

Assistance
--
If you need help please contact us at
pol...@apnic.net

Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199 
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___



On 25/07/2016, 15:10, "sig-policy-boun...@lists.apnic.net on behalf of
Masato Yamanishi" <sig-policy-boun...@lists.apnic.net on behalf of
myama...@gmail.com> wrote:

Dear Colleagues,

The APNIC 42 Policy SIG session and Open Policy Meeting will be held in
Colombo, Sri Lanka on Wednesday, 5 October 2016.

http://conference.apnic.net/42/policy

If you have any ideas to improve policy, or wish to make an informational
presentation about an aspect of resource management, please follow the
instructions below.

The submission deadline for APNIC 42 is 26 August 2016.

Submit a Policy Proposal
--
Complete the online form at:
   http://www.apnic.net/community/policy/proposals/submit

Proposal a presentation

Send your synopsis to:
pol...@apnic.net


We look forward to and encourage your participation in the APNIC 42 OPM.

Kind regards

Masato and Sumon
APNIC Policy SIG Chairs




smime.p7s
Description: S/MIME cryptographic signature
*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from LACNIC 25

[George Odagi]

Dear Community Members,

Following the LACNIC 25 meeting in La Habana, Cuba from 2 - 6 May 2016,
the proposals under discussion during the Open Policy Forum reached the
following statuses:


Two proposals reached consensus and sent to mailing list for 45 day
comment period:


- LAC-2016-4 "Modify direct IPv6 address assignment to end users"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-4?language=en

The proposal removes some of the criteria to justify an IPv6
assignment to end-user organizations. According to the author there
was no justification to request information such as number of hosts
in each subnet and details of routing plan or protocols to be used.

- LAC-2016-6 "Modify the initial assignment size and the requirements
for subsequent direct IPv6 assignments to end sites"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-6?language=en

This proposal aims to remove the maximum limit of /32 for IPv6
assignments to end-user organizations and to modify the text related
to subsequent assignments which would give the interpretation that
a contiguous block would always be granted.


Three proposals sent back to mailing list:


- LAC-2016-2 "IPv4 reserve pool for critical infrastructure in the
Region"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-2?language=en

This proposal seems to create a /15 IPv4 address pool to facilitate
the deployment of critical infrastructure in the region and would
create a reserve that is not subject to the current IPv4 depletion
phases.

- LAC-2016-3 "Remove the reference to a provider's multihomed or
non-multihomed status"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-3?language=en

This proposal eases the multihoming requirement by eliminating the
reference to a provider's "multihomed or non-multihomed status".
It also reduces the utilization requirement from "at least
50% of the requested address space" to "25% of the requested address
space".

- LAC-2016-5 "Modify the size of initial IPv6 allocation"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-5?language=en

This proposal aims to create a new section in the policy manual where
governmental organizations providing Internet access to other
internal organizations could justify their needs for an allocation
larger than a /32.


One proposal was abandoned:


- LAC-2016-1 "IPv4-IPv6 connectivity disputes when only one of the
protocols is supported"
https://politicas.lacnic.net/politicas/detail/id/LAC-2016-1?language=en

This proposal aimed to establish a recommendation or rule for settling
cases of IPv4-IPv6 connectivity disputes when a network or carrier
only supports IPv4 and wants to communicate with another network
which only supports IPv6.


An overview of LACNIC´s policy proposals can be found here:

https://politicas.lacnic.net/politicas/list

Find more information about the LACNIC Policy Development Process here:

    http://www.lacnic.net/en/web/lacnic/proceso-de-desarrollo-de-politicas


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3188
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___


*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
https://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] FINAL REMINDER: APNIC Policy SIG Deadline in 1 week

[George Odagi]

Dear Colleagues,

The Policy SIG Chairs have set a deadline for the submission of
proposals to be considered for consensus at the APNIC 41 Open Policy
Meeting in Auckland, New Zealand.

If you have a proposal for a policy change that would improve IP address
and ASN management in the region, please follow the instructions below
to submit your proposal before Friday, 15 January 2016.

How to submit your Policy Proposal
-

There are two ways to submit a policy proposal:

1. Use the online form at:
https://www.apnic.net/community/policy/proposals/submit-a-policy-proposal

2. Send your proposal in TEXT format to .
https://www.apnic.net/community/policy/proposals/proposal_template.txt

If you have identified an issue, but do not know the solution, you are
able to complete the Problem Statement part of the proposal submission
form and ask the community to help develop the best solution.


More information
-

Learn more about the APNIC 41 OPM:

http://conference.apnic.net/41/policy

Guideline for proposal authors

https://www.apnic.net/community/policy/guidelines/authors

APNIC's PDP is explained at:

http://www.apnic.net/community/policy/process

View current and past policy proposals at:

http://www.apnic.net/policy/proposals


We look forward to and encourage your participation in the APNIC PDP.


Kind regards

APNIC Secretariat



*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] REMINDER: APNIC Policy SIG Deadline in 4 weeks

[George Odagi]

Dear Colleagues,

The Policy SIG Chairs have set a deadline for the submission of
proposals to be considered for consensus at the APNIC 41 Open Policy
Meeting in Auckland, New Zealand.

If you have a proposal for a policy change that would improve IP address
and ASN management in the region, please follow the instructions below
to submit your proposal before Friday, 15 January 2016.

How to submit your Policy Proposal
-

There are two ways to submit a policy proposal:

1. Use the online form at:
https://www.apnic.net/community/policy/proposals/submit-a-policy-proposal

2. Send your proposal in TEXT format to .
https://www.apnic.net/community/policy/proposals/proposal_template.txt

If you have identified an issue, but do not know the solution, you are
able to complete the Problem Statement part of the proposal submission
form and ask the community to help develop the best solution.


More information
-

Learn more about the APNIC 41 OPM:

http://conference.apnic.net/41/policy

Guideline for proposal authors

https://www.apnic.net/community/policy/guidelines/authors

APNIC's PDP is explained at:

http://www.apnic.net/community/policy/process

View current and past policy proposals at:

http://www.apnic.net/policy/proposals


We look forward to and encourage your participation in the APNIC PDP.


Kind regards

APNIC Secretariat

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from ARIN 36

[George Odagi]

Dear Community Members,

This email presents a status update of policy proposals in the ARIN
region following the ARIN Advisory Council (AC) meeting on 9 October
2015.


Two drafts moved to Last Call:


- Recommended Draft Policy ARIN-2015-1: Modification to Criteria for
IPv6 Initial End-User Assignments
https://www.arin.net/policy/proposals/2015_1.html

- Recommended Draft Policy ARIN-2015-4: Modify 8.2 section to better
reflect how ARIN handles reorganizations
https://www.arin.net/policy/proposals/2015_4.html

One draft adopted as a Recommended Draft Policy:
--

- Draft Policy ARIN-2015-5: Out of region use
https://www.arin.net/policy/proposals/2015_5.html

One draft was abandoned:
--

- Draft Policy ARIN-2015-10: Minimum IPv6 Assignments
https://www.arin.net/policy/proposals/2015_10.html

The ARIN AC continues to work on seven draft policies:
-

- Draft Policy ARIN-2015-2: Modify 8.4 (Inter-RIR Transfers to
Specified Recipients)
https://www.arin.net/policy/proposals/2015_2.html

- Draft Policy ARIN-2015-3: Remove 30 day utilization requirement in
end-user IPv4 policy
https://www.arin.net/policy/proposals/2015_3.html

- Draft Policy ARIN-2015-6: Transfers and Multi-national Networks
https://www.arin.net/policy/proposals/2015_6.html

- Draft Policy ARIN-2015-7: Simplified requirements for demonstrated
need for IPv4 transfers
https://www.arin.net/policy/proposals/2015_7.html

- Draft Policy ARIN-2015-8: Reassignment records for IPv4 End-Users
https://www.arin.net/policy/proposals/2015_8.html

- Draft Policy ARIN-2015-9: Eliminating needs-based evaluation for
Section 8.2, 8.3, and 8.4 transfers of IPv4 netblocks
https://www.arin.net/policy/proposals/2015_9.html

- Draft Policy ARIN-2015-11: Remove transfer language which only
applied pre-exhaustion of IPv4 pool
https://www.arin.net/policy/proposals/2015_11.html


An overview of ARIN´s policy proposals can be found here:

https://www.arin.net/policy/proposals/index.html

Find more information about the ARIN Policy Development Process here:

https://www.arin.net/policy/pdp.html


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from LACNIC 24

[George Odagi]

Dear Community Members,

Following the LACNIC 24 meeting in Bogotá, Colombia; the proposals under
discussions during the Public Policy Forum on Wednesday, 30 September
2015 reached the following statuses:


Reached Consensus and moved to Final Call
-

-LAC-2015-1: Trigger 2.3.2.18 when a justified request larger than
/22 is received which can not be allocated from any remaining pool
of addresses at LACNIC.
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-1?language=en

This proposal seeks to trigger IPv4 transfers among members in
the LACNIC region.

   - LAC-2015-4: Resource Recovery Timeline
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-4?language=en

This proposal seeks to reduce the period of time needed to
recover Internet number resources that are not being "properly
utilized" from 6 to 3 months.

- LAC-2015-5: Increase the minimum period of time required before a
block can be transferred under section 2.3.2.18
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-5?language=en

This proposal seeks to modify section 2.3.2.18, increasing the
period of time required before an assigned block can be transfered
to 3 years, from the one-year period currently in force.


Returned to the Mailing List for further discussion
---

- LAC-2015-6: Modify the scope of IPv4 Exhaustion Phase 2 for the
region
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-6?language=en

The proposal seeks to modify the text in sections 11.1 and 11.2,
doubling the space assigned to Phase 2, from a /11 to a /10.

- LAC-2015-3: IPv4 exhaustion policy with a scheduled termination
date and the scheduled return of large users' blocks.
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-3?language=en

This proposal sets 2030 as the date of IPv4 exhaustion, and
suggests that large IPv4 block users return 1/15 of their blocks
each year.


Abandoned
-

- LAC-2015-2: Inter-RIR Transfers
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-2?language=en

This proposal seeks to allow organizations to transfer IPv4
resources into LACNIC from another RIR.


An overview of LACNIC´s policy proposals can be found here:

http://www.lacnic.net/en/web/lacnic/politicas

Find more information about the LACNIC Policy Development Process here:

http://www.lacnic.net/web/lacnic/proceso-de-desarrollo-de-politicas


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___


*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Summary of Policy Proposals from LACNIC

[George Odagi]

Dear Community Members,

This email presents a summary of the policy proposals currently in
discussion and will be presented during the upcoming LACNIC 25 meeting
in Bogotá, Colombia:


Six proposals under discussion, in chronological order:


- LAC-2015-1: Trigger 2.3.2.18 when a justified request larger than
/22 is received which can not be allocated from any remaining pool
of addresses at LACNIC.
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-1?language=en

This proposal seeks to trigger IPv4 transfers among members in
the LACNIC region.

- LAC-2015-2: Inter-RIR Transfers
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-2?language=en

This proposal seeks to allow organizations to transfer IPv4
resources into LACNIC from another RIR.

- LAC-2015-3: IPv4 exhaustion policy with a scheduled termination
date and the scheduled return of large users' blocks.
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-3?language=en

This proposal sets 2030 as the date of IPv4 exhaustion, and
suggests that large IPv4 block users return 1/15 of their blocks
each year.

- LAC-2015-4: Resource Recovery Timeline
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-4?language=en

This proposal seeks to reduce the period of time needed to
recover Internet number resources that are not being "properly
utilized" from 6 to 3 months.

- LAC-2015-5: Increase the minimum period of time required before a
block can be transferred under section 2.3.2.18
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-5?language=en

This proposal seeks to modify section 2.3.2.18, increasing the
period of time required before an assigned block can be transfered
to 3 years, from the one-year period currently in force.

- LAC-2015-6: Modify the scope of IPv4 Exhaustion Phase 2 for the
region
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-6?language=en

The proposal seeks to modify the text in sections 11.1 and 11.2,
doubling the space assigned to Phase 2, from a /11 to a /10.


An overview of LACNIC´s policy proposals can be found here:

http://www.lacnic.net/en/web/lacnic/politicas

Find more information about the LACNIC Policy Development Process here:

http://www.lacnic.net/web/lacnic/proceso-de-desarrollo-de-politicas


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___






*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Implementation at RIPE NCC

[George Odagi]

Dear Community Members,

This email is to inform you that consensus has been reached and the
proposal for a change to ripe-643, IPv4 Address Allocation and
Assignment Policies for the RIPE NCC Service Region has been accepted
by the RIPE community. This proposal has been implemented with immediate
effect.

   - 2015-01: IPv4 Address Allocation and Assignment Policies for the
   RIPE NCC Service Region
   https://www.ripe.net/participate/policies/proposals/2015-01

This policy change aligns the transfer requirements for all IPv4
allocations. LIRs that receive an IPv4 allocation from the RIPE NCC or
via a transfer cannot subsequently transfer this allocation to another
party within 24 months.

The new RIPE Document is called ripe-649 and is available at:

https://www.ripe.net/publications/docs/ripe-649


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___

*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy

[sig-policy] Policy Outcomes from LACNIC 23

[George Odagi]

Dear Community Members,

Following the LACNIC 23 meeting in Lima, Peru, the proposals under
discussions during the Public Policy Forum on Wednesday, 20 May 2015
reached the following statuses:

One proposal was approved by LACNIC community:


- LAC-2014-3: Update to the Policy Development Process
https://politicas.lacnic.net/politicas/detail/id/LAC-2014-3?language=en
This proposal seeks to modify the LACNIC Policy Development Process -
as the existing one lacks clarity and definition in certain points
such as the direct responsibilities of LACNIC, LACNIC chairs and
those of the organization's directors.

Two proposals were returned to the mailing list:


- LAC-2015-2: Inter-RIR Transfers
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-2?language=en
This proposal aims to allow organisations to transfer space into
LACNIC from another RIR so they can build more networks in the
LACNIC region.
- LAC-2015-1: Trigger 2.3.2.18 when a justified request larger than
/22 is received which can not be allocated from any remaining pool
of addresses at LACNIC
https://politicas.lacnic.net/politicas/detail/id/LAC-2015-1?language=en

This proposal would remove the trigger for implementation of LACNIC's
in-region IPv4 transfer policy. Currently, transfers are not
permitted until LACNIC reaches absolute exhaustion. This change
would permit transfers immediately.

The recap of the meeting is available at the following link:

http://www.lacnic.net/web/eventos/lacnic23-recap3

An overview of LACNIC´s policy proposals can be found here:

http://www.lacnic.net/en/web/lacnic/politicas

Find more information about the LACNIC Policy Development Process here:

http://www.lacnic.net/web/lacnic/proceso-de-desarrollo-de-politicas


Kind regards,

George Odagi
Internet Resource Analyst/Policy Support, APNIC
e: god...@apnic.netmailto:god...@apnic.net
p: +61 7 3858 3191
f: +61 7 3858 3199
www.apnic.net
___
Join the conversation:   https://blog.apnic.net/
___
*  sig-policy:  APNIC SIG on resource management policy   *
___
sig-policy mailing list
sig-policy@lists.apnic.net
http://mailman.apnic.net/mailman/listinfo/sig-policy