sig-policy May 2015

sig-policy@lists.apnic.net

14 participants
7 discussions

Monthly List Reminder
by noreply＠apnic.net 31 May '15

31 May '15

Dear Subscriber, This is the monthly reminder of subscription information for the sig-policy list, hosted at APNIC. For subscription information including how to un-subscribe go to http://mailman.apnic.net/mailman/listinfo/sig-policy Thank you for participating in this discussion. Kind Regards, List administrator

1 0

Idea for 1.2.3.0/24
by David Huberman 26 May '15

26 May '15

Hello Policy SIG, I have an idea for 1.2.3.0/24 I would like to share with you before submitting a policy proposal. Prop-109 properly directed APNIC to use 1.0.0.0/24 and 1.1.1.0/24 for research purposes. That leaves one more significant prefix to deal with: 1.2.3.0/24. It is significant because it contains the IP address 1.2.3.4. 1.2.3.4 is a desirable IP address. It can be used in all sorts of very interesting applications. It also receives an enormous amount of "junk" traffic every day, so it requires a fairly hefty infrastructure just to start routing it. My idea is that APNIC should make this prefix available to all parties who want it. To decide who gets it, I propose an AUCTION where all proceeds go to a charitable endeavor (perhaps a future APNIC Foundation). As the potential author of such a proposal, and as the IP address manager at Microsoft Corporation, I will guarantee that neither I nor my company will participate in any way in such an auction. This proposal is not to benefit me or my company. It is to give the prefix out to a network operator who wants it, in return for money given to charity. This is a new idea, and is not fully thought out. So I wanted to post it, get some reactions, and improve the idea. (Or abandon it if people do not like it.) Thank you. David David R Huberman Principal, Global IP Addressing Microsoft Corporation

2 1

Policy Outcomes from LACNIC 23
by George Odagi 25 May '15

25 May '15

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: godagi(a)apnic.net<mailto:godagi@apnic.net> p: +61 7 3858 3191 f: +61 7 3858 3199 www.apnic.net _______________________________________________________ Join the conversation: https://blog.apnic.net/ _______________________________________________________

1 0

Fwd: Idea for 1.2.3.0/24
by Dean Pemberton 24 May '15

24 May '15

Oops wrong button :) ---------- Forwarded message ---------- From: *Dean Pemberton* <dean(a)internetnz.net.nz> Date: Friday, 22 May 2015 Subject: [sig-policy] Idea for 1.2.3.0/24 To: David Huberman <David.Huberman(a)microsoft.com> Hi David, Everyone If APNIC were to just sell this off then there is no saying that it won't just appear in some large providers NAT pool. I've just visited some providers who wanted address space so much they would probably bid for this just to have 1.2.3.4 as a flag to wave and the rest of the /24 just sits in their CGN. That would be terrible for anyone whose sessions were associated with these addresses. I won't elaborate here but there are even potential security issues related with a malicious actor being able to redirect this about of traffic. Any of these would be a net loss to the Internet community. So how can we turn this into a net win? I'm not that concerned about the money. Good things can be done with auction proceeds, but good ideas can come from people without money too. For example what if an individual has a great idea to use 1.2.3.4 for the common good but would never have an ability to win an auction? They might also have no ability to purchase infrastructure to make the idea happen. Nat Morris for eg runs a great any cast DNS service helping lots of people but I'm pretty sure his wife and dog would notice him going up against large corps in an auction. What about this. We take suggestions for the best 'public good' use of 1.2.3.4. For each of the ideas, let the community show support "a thumbs up/down" if you will. Also for each of them allow organisations to pitch to deliver it. Market it as recycling trash even :) This way the good idea can come from anyone in any part of the world as long as it benefits all internet users. And large corporations can still get some exposure by offering to make it happen. Imagine the photoshoot. Smart up-and-coming engineer from an LDC alongside a large multinational helping APNIC to make a difference to us all. Thoughts? On Friday, 22 May 2015, David Huberman <David.Huberman(a)microsoft.com <javascript:_e(%7B%7D,'cvml','David.Huberman(a)microsoft.com');>> wrote: > Hello Policy SIG, > > > > I have an idea for 1.2.3.0/24 I would like to share with you before > submitting a policy proposal. > > > > Prop-109 properly directed APNIC to use 1.0.0.0/24 and 1.1.1.0/24 for > research purposes. That leaves one more significant prefix to deal with: > 1.2.3.0/24. It is significant because it contains the IP address 1.2.3.4. > > > > 1.2.3.4 is a desirable IP address. It can be used in all sorts of very > interesting applications. It also receives an enormous amount of “junk” > traffic every day, so it requires a fairly hefty infrastructure just to > start routing it. > > > My idea is that APNIC should make this prefix available to all parties who > want it. To decide who gets it, I propose an AUCTION where all proceeds go > to a charitable endeavor (perhaps a future APNIC Foundation). As the > potential author of such a proposal, and as the IP address manager at > Microsoft Corporation, I will guarantee that neither I nor my company will > participate in any way in such an auction. This proposal is not to benefit > me or my company. It is to give the prefix out to a network operator who > wants it, in return for money given to charity. > > > > This is a new idea, and is not fully thought out. So I wanted to post it, > get some reactions, and improve the idea. (Or abandon it if people do not > like it.) > > > > Thank you. > > > > David > > > > *David R Huberman* > Principal, Global IP Addressing > > Microsoft Corporation > > > -- -- Dean Pemberton Technical Policy Advisor InternetNZ +64 21 920 363 (mob) dean(a)internetnz.net.nz <javascript:_e(%7B%7D,'cvml','dean(a)internetnz.net.nz');> To promote the Internet's benefits and uses, and protect its potential. -- -- Dean Pemberton Technical Policy Advisor InternetNZ +64 21 920 363 (mob) dean(a)internetnz.net.nz To promote the Internet's benefits and uses, and protect its potential.

8 13

1.2.3.4
by Andy Linton 22 May '15

22 May '15

Please stop attempting to rearrange the deckchairs on the Titanic.

2 1

Workshop on Internet of Things for Ambient Assisted Living - IEEE GLOBECOM 2015, San Diego, CA, USA, Dec 6 - 10, 2015
by iotaalsam＠gmail.com 05 May '15

05 May '15

CALL FOR PAPERS (apologies for multiple copies) IEEE International Workshop on Internet of Things for Ambient Assisted Living (IoTAAL) In conjunction with IEEE GLOBECOM 2015, San Diego, CA, USA, Dec 6 - 10, 2015. http://www.tlc.dii.univpm.it/iotaal/ *MOTIVATION AND SCOPE* Ambient Assisted Living (AAL) encompasses technical systems, infrastructures, and services to support elderly people in their daily routine, to allow an independent and safe lifestyle, as long as possible, via the seamless integration of information and communication technologies within homes and residences. Effective AAL solutions require appropriate ICT algorithms, architectures and platforms, that cannot leave out of consideration the development of new and innovative approaches, particularly in the area of pervasive and mobile systems. The Internet of Things (IoT) paradigm is leading to smart objects being capable of identifying, locating, sensing and connecting, and thus opening possibilities for new forms of communication between people and things, and things themselves. This workshop aims to investigate the potential benefits gained when specializing the IoT for AAL, to avoid redundancy and leverage the harmonization of the technological approaches towards an increased Quality of Life for the current and future ageing populations. *TOPICS OF INTEREST* The focus of this workshop is on proposals of architectures, methods, techniques, protocols, components and tools addressing the IoT paradigm to support the Ambient Assisted Living requirements. These may include, but are not limited to, the following topics: - IoT communications for AAL and Enhanced Living Environments - Mobile solutions for AAL - IoT enabled signal acquisition, analysis, and processing for activity identification and recognition in AAL - Smart Ad Hoc Networks and Wireless Sensor Networks (WSNs) for AAL - Distributed sensing and alarming technologies for AAL - IoT devices (smart objects) and cyber-physical systems for AAL - E-healthcare, telemedicine and tele-monitoring through IoT in AAL systems - AAL networks and systems architectures - Green networking in IoT for AAL - Security, privacy, and trustworthiness management in IoT for AAL - Information processing for AAL communications - Interoperability among IoT and AAL platforms - Cloud and Mobile Cloud for AAL - Algorithms and techniques for IoT enabled AAL data analytics - Big data management in AAL - IoT applications, systems, and testbeds for AAL - Standardization activities of IoT for AAL - Future directions in IoT for AAL *IMPORTANT DATES* Paper submission deadline: *July 1, 2015 (strict)* Acceptance/rejection announcement: *September 1, 2015* Final workshop papers due: *October 1, 2015* *SUBMISSION OF PAPERS* All final submissions should be written in English with a maximum paper length of six (6) printed pages (10-point font) including figures without incurring additional page charges (maximum 1 additional page with over length page charge of USD100 if accepted). Papers exceeding 7 pages will not be accepted at EDAS. You may also use one of the following templates for Microsoft Word: A4, US letter. Only PDF files will be accepted for the review process, and all submissions must be done through EDAS (link TBA). Standard IEEE conference templates for LaTeX formats are found at here: http://www.ieee.org/conferences_events/conferences/publishing/templates.html If you have any questions regarding the submission of manuscripts, please contact the Workshop Program Chairs. Important IEEE Policy Announcement: The IEEE reserves the right to exclude a paper from distribution after the conference (including its removal from IEEE Explore) if the paper is not presented at the conference. Plagiarism policy: Papers should not contain plagiarized material and have not been submitted to any other conference/workshop at the same time (double submission). These matters are taken very seriously and the IEEE Communications society will take action against any author who engages in either practice. Follow the link to learn more: http://www.ieee.org/publications_standards/publications/rights/Multi_Sub_Gu… *ORGANIZING COMMITTEE* Workshop co-chairs: - Susanna Spinsante (Università Politecnica delle Marche – ITALY) - Joel Rodrigues (Instituto de Telecomunicacoes, University of Beira Interior – PORTUGAL) Technical program co-chairs: - Ennio Gambi (Università Politecnica delle Marche – ITALY) - Chirag Warty (Intelligent Communication Lab – INDIA) - Fa-Long Luo (Element CXI – USA) - Nuno Garcia (University of Beira Interior – PORTUGAL) Publications chair: - Chirag Warty (Intelligent Communication Lab – INDIA) Publicity co-chairs: - Lambros Lambrinos (Cyprus University of Technology – CYPRUS) - Enea Cippitelli, Samuele Gasparrini (Università Politecnica delle Marche – ITALY) For more information please visit the workshop website at http://www.tlc.dii.univpm.it/iotaal/

1 0

Summary of Policy Proposals from ARIN
by George Odagi 05 May '15

05 May '15

Dear Community Members, This email presents a status update of policy proposals in the ARIN region following the ARIN Advisory Council (AC) meeting on Monday, April 27 2015. Two proposals moved to Last Call: -------------------------------- - Recommended Draft Policy ARIN-2014-6: Remove Operational Reverse DNS Text This proposal removes the policy requirement for some LIRs to maintain rDNS for their downstream or delegate that responsibility to them. https://www.arin.net/policy/proposals/2014_6.html - Recommended Draft Policy ARIN-2014-21: Modification to CI Pool Size per Section 4.4 This policy aims to change a section of the existing NRPM policy to double the number of IPv4 addresses reserved for Critical Infrastructure from a /16 equivalent to a /15 equivalent. https://www.arin.net/policy/proposals/2014_21.html Three proposals were abandoned: ------------------------------ - Recommended Draft Policy ARIN-2014-1: Out of Region Use This proposal aimed to clarify the policy ambiguity surrounding out-of-regional use by trans-regional organizations legally located in the ARIN region. ARIN AC members are currently working to craft a new proposal. https://www.arin.net/policy/proposals/2014_1.html - Recommended Draft Policy ARIN-2014-14: Needs Attestation for some IPv4 Transfers This proposal would have removed the requirement to demonstrate need on resource transfers of a /16 or less. The AC abandoned the proposal due to a lack of support. https://www.arin.net/policy/proposals/2014_14.html - Recommended Draft Policy ARIN-2014-22: Removal of Minimum in Section 4.10 This proposal would have changed to modify existing policy 'NRPM 4.10 Dedicated IPv4 block to facilitate IPv6 deployment'. The current policy sets the minimum allocation size as /28 to a maximum of /24. This proposal changes the allocation size to simply be a /24 with no maximum or minimum. https://www.arin.net/policy/proposals/2014_22.html The ARIN AC continues to work on one draft policy: ------------------------------------------------- - Draft Policy ARIN-2015-1: Modification to Criteria for IPv6 Initial End-User Assignments https://www.arin.net/policy/proposals/2015_1.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: godagi(a)apnic.net p: +61 7 3858 3191 f: +61 7 3858 3199 www.apnic.net _______________________________________________________ Join the conversation: https://blog.apnic.net/ _______________________________________________________

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

sig-policy May 2015