- address-policy-wg - mailman.ripe.net

Draft Agenda RIPE77 - Address Policy
by Erik Bais 01 Oct '18

01 Oct '18

Hi APWG folks, Below you can find a draft for the RIPE address policy WG meeting's agenda, which will take place in Amsterdam in the side-room in the following time slots: Wednesday, Oct 17, 09:00 - 10:30 Wednesday, Oct 17, 11:00 - 12:30 If you have anything else you want to see on the agenda, or if we need to change anything, please let us know. Regards, Gert Döring & Erik Bais, APWG chairs ---------------------------------------------------------------------- Wednesday, 09:00-10:30 ---------------------------------------------------------------------- A. Administrative Matters (welcome, thanking the scribe, approving the minutes, etc.) B. Update on 2018 - 04 - PDP Clarification to the WG. ( discussion was done on RIPE Discussion list ) C. Current Policy Topics - Marco Schmidt, NCC PDO - global policy overview "what's going on?" - common policy topics in all regions (end of IPv4, transfers, ...) - overview over concluded proposals in the RIPE region since RIPE 76 - brief overview of new proposals (if any) D. IPv4 end-game and afterlife - Andrea Cima, RIPE NCC (+ discussion with the group) E. Country codes in the extended delegated statistics and RIPE DB. by Ingrid Wijte, RIPE NCC ---------------------------------------------------------------------- Wednesday, 11:00-12:30 ---------------------------------------------------------------------- Welcome back F. Discussion of open policy proposals 2018-02 Assignment Clarification in IPv6 Policy Jordi Palet Martinez Y. Open Policy Hour The Open Policy Hour is a showcase for your policy ideas. If you have a policy proposal you'd like to debut, prior to formally submitting it, here is your opportunity. Z. AOB

1 0

[CFP] ACM/IEEE IPSN 2019 in CPSWeek
by Vijay Rao 27 Sep '18

27 Sep '18

The 18th ACM/IEEE The International Conference on Information Processing in Sensor Networks (IPSN) =================================================================== April 16-18, 2019, Montreal, Canada IPSN'19 is part of CPS-IoT Week 2019, co-located with HSCC, ICCPS, CPS-IoT, and RTAS. http://ipsn.acm.org/2019 =================================================================== The International Conference on Information Processing in Sensor Networks (IPSN) is a leading annual forum on research in networked sensing and control, broadly defined. IPSN brings together researchers from academia, industry, and government to present and discuss recent advances in both theoretical and experimental research. Its scope includes signal and image processing, information and coding theory, databases and information management, distributed algorithms, networks and protocols, wireless communications, collaborative objects and the Internet of Things, machine learning, mobile and social sensing, and embedded systems design. Of special interest are contributions at the confluence of multiple of these areas. Like prior years, IPSN 2019 will continue its co-location with CPS-IoT WEEK, the premier venue for research and development of Cyberphysical Systems, and its strong focus on algorithms, theory, and systems for information processing using networks of embedded, human-in-the-loop, or social sensors, as well as new hardware and software platforms, design methods, architectures, modelling, implementation, evaluation, deployment experiences, and tools for networked embedded sensor systems and the Internet of Things. Topics of interest include, but are not limited to: - Sensor data storage, retrieval, processing - Streaming sensor system tasking and operation - Coding, compression, and information theory - Theoretical foundation and fundamental bounds - Network and system architectures and protocols - IoT gateway platform architecture and services - Outdoor, wide-area sensing systems - Location, time, and other network services - Programming models, languages, and systems - Programming models for IoT ensembles - Modeling, simulation, and measurement tools - Operating systems and runtime environments - Applications in health, wellness & sustainability - Applications in smart cities and urban health - Experiences, challenges, comparisons of platforms - Discovery, coordination, and use of IoT services - Security and privacy in heterogeneous systems - IoT reliability, adaptability, and dependability - Technical assessment of emerging IoT standards - Wearable systems and data processing algorithms - Sensor-enabled drone platforms and algorithms In addition to IPSN's traditional focus, IPSN 2019 will place a particular emphasis on embedded machine learning and computer vision, with a special track centered on these topics. In this case, topics of interest include but are not limited to: - Machine learning and deep learning on sensor data - New hardware and system design to enable machine learning on sensor data - Novel embedded machine learning algorithms - Data related issues, such as methods, tools, and analysis - Computer vision for resource-constrained and mobile platforms ********Submission Guidelines******** Coming soon. ********Response Process******** As in previous years, IPSN will also elicit a review and response process. After the initial review, the program committee may request a short response from selected papers for additional clarifications. The authors will get a short time window of roughly 24 hours to respond. Participation in the response process is not mandatory. ****Joint statement from IPSN and IoTDI**** The two conferences are collaborating to create new synergies, also exploiting their CPSWEEK bi-annual co-location. Prospective authors are thus strongly encouraged to consider these guidelines: - Contributions of embedded nature and applying to network segments from the IoT gateway to field devices should be submitted to IPSN. Examples include localization, low-power wireless networking, and embedded data processing. - Contributions with an end-to-end perspective or applying to network segments from the IoT gateway to the cloud should be submitted to IoTDI. Examples include cloud data processing, edge computing, and systems covering multiple network segments. The TPC chairs of both conferences may agree to move a submitted paper from one to the other if they see a better fit, subject to the authors’ consent. The final decision about where to submit, and therefore what program committee will review the work, ultimately rests with the authors. ********Key Dates******** Paper Abstract Registration: October 10th, 2018 11:59pm AoE(UTC-12) Paper Submission Deadline: (Firm*): October, 17th 2018 11:59pm AoE(UTC-12) Authors’ rebuttal period December 17th - 19th, 2018 Acceptance Notification: January 16th, 2019 Camera-Ready Deadline: TBD ********Organizers******** General Chair: Rasit Eskicioglu (University of Manitoba) Technical Committee Chairs: Luca Mottola (Politecnico di Milan and RISE SICS) Bodhi Priyantha (Microsoft Research)

5 4

New on RIPE Labs: 20, 000 LIRs - A Peek Into the Future
by Mirjam Kühne 26 Sep '18

26 Sep '18

Dear all, The RIPE NCC today hit 20,000 LIR accounts, and my colleague Rene Wilhelm has written an article that looks at how we came to this milestone and what the future holds for membership development. https://labs.ripe.net/Members/wilhelm/20000-local-internet-registries Kind regards, Mirjam Kühne RIPE NCC

1 0

RIPE77 AP-WG Agenda topics in mind ?
by Erik Bais 24 Sep '18

24 Sep '18

Dear Working Group, As we are in the process of sorting out the topics for the AP-WG agenda. We would like to ask if there are people who like to see certain topics or discuss something that would require some time on the agenda for RIPE77 during Address Policy. If you are wondering about certain things (Address Policy related) or like to present something, please let us know and we will see if and where we can reserve some time for it on the agenda. We hope that we can put out the agenda itself on this ML before this Friday. Kind regards, Gert Döring & Erik Bais APWG chairs

2 1

2018-02 New Version Policy Proposal (Assignment Clarification in IPv6 Policy)
by Marco Schmidt 24 Sep '18

24 Sep '18

Dear colleagues, RIPE Policy proposal, 2018-02, "Assignment Clarification in IPv6 Policy" is now available for discussion again. This proposal aims to clarify the definition of "Assign" in ripe-707 (section 2.6). This proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Adjusting the scope of what is considered a sub-assignment You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-02 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 27 September 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

ACM/IEEE IPSN 2019: Call for Papers
by shijiapan＠cmu.edu 16 Sep '18

16 Sep '18

1 0

Call for Paper: SenSys 2018 Doctoral Colloquium
by shijiapan＠cmu.edu 05 Sep '18

05 Sep '18

1 0

2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy)
by Marco Schmidt 30 Aug '18

30 Aug '18

Dear colleagues, Proposal 2018-03, "Fixing Outdated Information in the IPv4 Policy", is now in Concluding Phase. This proposal aims to fix outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". The WG co-chair has declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 22 August 2018 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 22 August 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

4 7

2018-03 Proposal Accepted and Implemented (Fixing Outdated Information in the IPv4 Policy)
by Marco Schmidt 30 Aug '18

30 Aug '18

Dear colleagues, Consensus has been reached on 2018-03, "Fixing Outdated Information in the IPv4 Policy". This proposal fixed outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 The new RIPE Document is called ripe-708 and is available at: https://www.ripe.net/publications/docs/ripe-708 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

CFP IPSN 2019
by Vijay Rao 30 Aug '18

30 Aug '18

The 18th ACM/IEEE The International Conference on Information Processing in Sensor Networks (IPSN) =================================================================== April 16-18, 2019, Montreal, Canada IPSN'19 is part of CPS-IoT Week 2019, co-located with HSCC, ICCPS, CPS-IoT, and RTAS. http://ipsn.acm.org/2019 =================================================================== The International Conference on Information Processing in Sensor Networks (IPSN) is a leading annual forum on research in networked sensing and control, broadly defined. IPSN brings together researchers from academia, industry, and government to present and discuss recent advances in both theoretical and experimental research. Its scope includes signal and image processing, information and coding theory, databases and information management, distributed algorithms, networks and protocols, wireless communications, collaborative objects and the Internet of Things, machine learning, mobile and social sensing, and embedded systems design. Of special interest are contributions at the confluence of multiple of these areas. Like prior years, IPSN 2019 will continue its co-location with CPS-IoT WEEK, the premier venue for research and development of Cyberphysical Systems, and its strong focus on algorithms, theory, and systems for information processing using networks of embedded, human-in-the-loop, or social sensors, as well as new hardware and software platforms, design methods, architectures, modelling, implementation, evaluation, deployment experiences, and tools for networked embedded sensor systems and the Internet of Things. Topics of interest include, but are not limited to: - Sensor data storage, retrieval, processing - Streaming sensor system tasking and operation - Coding, compression, and information theory - Theoretical foundation and fundamental bounds - Network and system architectures and protocols - IoT gateway platform architecture and services - Outdoor, wide-area sensing systems - Location, time, and other network services - Programming models, languages, and systems - Programming models for IoT ensembles - Modeling, simulation, and measurement tools - Operating systems and runtime environments - Applications in health, wellness & sustainability - Applications in smart cities and urban health - Experiences, challenges, comparisons of platforms - Discovery, coordination, and use of IoT services - Security and privacy in heterogeneous systems - IoT reliability, adaptability, and dependability - Technical assessment of emerging IoT standards - Wearable systems and data processing algorithms - Sensor-enabled drone platforms and algorithms In addition to IPSN's traditional focus, IPSN 2019 will place a particular emphasis on embedded machine learning and computer vision, with a special track centered on these topics. In this case, topics of interest include but are not limited to: - Machine learning and deep learning on sensor data - New hardware and system design to enable machine learning on sensor data - Novel embedded machine learning algorithms - Data related issues, such as methods, tools, and analysis - Computer vision for resource-constrained and mobile platforms ********Submission Guidelines******** Coming soon. ********Response Process******** As in previous years, IPSN will also elicit a review and response process. After the initial review, the program committee may request a short response from selected papers for additional clarifications. The authors will get a short time window of roughly 24 hours to respond. Participation in the response process is not mandatory. ****Joint statement from IPSN and IoTDI**** The two conferences are collaborating to create new synergies, also exploiting their CPSWEEK bi-annual co-location. Prospective authors are thus strongly encouraged to consider these guidelines: - Contributions of embedded nature and applying to network segments from the IoT gateway to field devices should be submitted to IPSN. Examples include localization, low-power wireless networking, and embedded data processing. - Contributions with an end-to-end perspective or applying to network segments from the IoT gateway to the cloud should be submitted to IoTDI. Examples include cloud data processing, edge computing, and systems covering multiple network segments. The TPC chairs of both conferences may agree to move a submitted paper from one to the other if they see a better fit, subject to the authors’ consent. The final decision about where to submit, and therefore what program committee will review the work, ultimately rests with the authors. ********Key Dates******** Paper Abstract Registration: October 10th, 2018 11:59pm AoE(UTC-12) Paper Submission Deadline: (Firm*): October, 17th 2018 11:59pm AoE(UTC-12) Authors’ rebuttal period December 17th - 19th, 2018 Acceptance Notification: January 16th, 2019 Camera-Ready Deadline: TBD ********Organizers******** General Chair: Rasit Eskicioglu (University of Manitoba) Technical Committee Chairs: Luca Mottola (Politecnico di Milan and RISE SICS) Bodhi Priyantha (Microsoft Research)

1 0

Proposal Implemented: 2018-01, "Organisation-LIR Clarification in IPv6 Policy"
by Marco Schmidt 27 Aug '18

27 Aug '18

Dear colleagues, We are pleased to announce that we have implemented the policy proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy". This proposal clarified the wording used in the RIPE IPv6 Policy regarding terms such as "organisation" and "LIR". The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2018-01 The RIPE Document, "IPv6 Address Allocation and Assignment Policy", is available at: https://www.ripe.net/publications/docs/ripe-707 Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

New AS Number Block allocated to the RIPE NCC
by Ingrid Wijte 21 Aug '18

21 Aug '18

Dear Colleagues, The RIPE NCC has received the following AS Number Blocks from the IANA on 20 August 2018: 207260-208283 208284-209307 209308-210331 You may want to update your records accordingly. Best regards, Ingrid Wijte Registration Services Assistant Manager and Policy Development RIPE NCC

1 0

[Deadline Extended] SenSys 2018 Poster/Demo
by shijiapan＠cmu.edu 18 Aug '18

18 Aug '18

1 0

[Deadline Extended] SenSys 2018 Workshop DATA -- Data: Acquisition To Analysis
by shijiapan＠cmu.edu 16 Aug '18

16 Aug '18

1 0

2018-01 Proposal Accepted (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 23 Jul '18

23 Jul '18

Dear colleagues, Consensus has been reached on 2018-01, "Organisation-LIR Clarification in IPv6 Policy". The goal of this proposal was to clarify the wording used in RIPE-699 regarding terms such as "organisation" and "LIR". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 The new RIPE Document is ripe-707 and is available at: https://www.ripe.net/publications/docs/ripe-707 We estimate that this proposal will take around two weeks to fully implement. We will send another announcement once the implementation is complete and the new procedures are in place. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy)
by Erik Bais 23 Jul '18

23 Jul '18

Dear WG. While we are still getting used to switching hats/roles between Sander and myself, we are currently at the time of seeing the first official ML post in my new role as WG chair. With Sander stating his support on the 2018-03 policy and showing his ‘renewed’ community role again (and the support of : Mike, Piotr, Dominik and Nikolay), the review phase has come to an end. There were no objections or outstanding questions on the ML regarding the policy proposal and with that result we (The WG chairs) agree that we move the policy to Last Call. If there are specific questions that you might have regarding this policy proposal, please ask them on the ML. And if you (still) agree with the policy moving forward, please state your support here on our ML. Kind regards, Erik Bais APWG Chair

1 0

2018-01 Last Call for Comments (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 19 Jul '18

19 Jul '18

Dear colleagues, Proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy", is now in Concluding Phase. This proposal aims to clarify the wording used in ripe-699 regarding terms such as "organisation" and "LIR". The WG Chair has declared that rough consensus has been reached and the proposal will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of this four week Concluding Phase is to give an opportunity to present well-justified objections for those who missed the previous two phases and wish to oppose the proposal. Any objection must be made by 12 July 2018 and must be supported by an explanation. If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 <https://www.ripe.net/participate/policies/proposals/2018-01> Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net <mailto:address-policy-wg@ripe.net>> before 12 July 2018. Regards, Marco Schmidt Policy Officer RIPE NCC

2 1

Feedback needed for 2018-03 (Fixing Outdated Information in the IPv4 Policy)
by Andrea Cima 18 Jul '18

18 Jul '18

Dear All, Policy proposal 2018-03 aims at fixing outdated information in IPv4 Policy, like outdated references or values of inetnum objects in the RIPE Database. While I am aware this is not the most exciting of the current policy proposals, it is important to keep the content of the IPv4 policy up-to-date. The review phase for this proposed policy change will end this week, and in order to proceed with the PDP this proposal needs your input, whether you support or oppose the changes. You can find the full proposal here: https://www.ripe.net/participate/policies/proposals/2018-03 Thank you in advance for your support and best regards, Andrea Cima RIPE NCC

6 7

2018-03 Review Phase (Fixing Outdated Information in the IPv4 Policy)
by Marco Schmidt 21 Jun '18

21 Jun '18

Dear colleagues, Policy proposal 2018-03, "Fixing Outdated Information in the IPv4 Policy" is now in the Review Phase. This proposal aims to fix outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". The proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Adding a direct reference to the "IANA IPv4 Special-Purpose Address Registry" The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-03 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-03/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to <address-policy-wg(a)ripe.net> before 19 July 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

2018-01 Review Phase (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 12 Jun '18

12 Jun '18

Dear colleagues, Policy proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is now in the Review Phase. This proposal aims to clarify the wording used in ripe-699 regarding terms such as "organisation" and "LIR". The proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Clarifies when the subsequent allocation policy applies - Fixing some typos The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-01 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-01/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussing the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the WG Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to <address-policy-wg(a)ripe.net> before 1 June 2018. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

9 10

proposal to remove IPv6 PI
by JORDI PALET MARTINEZ 21 May '18

21 May '18

Hi all, For those that haven't been in the meeting, the slides are available at https://ripe76.ripe.net/presentations/97-RIPE-2018-05-v1.pdf I believe we have several problems that my proposal is trying to fix. 1) See my previous email on the clarification of IPv6 PI sub-assignments. Is not just a matter of IPv6, but also IPv4. This is an alternative solution (at least of the IPv6 part - we could do the same for IPv4 of course and also remove IPv4 PI). 2) It was clear in the meeting, as we *all* know, that many folks in the community (and not only in this region) are abusing the policy and they actually use end-user space (PI policies) to *assign* (call it sub-assign if you prefer it), to third parties. 3) It may be the case that this happens because the fee structure. An LIR, currently, pays 1.400 Euros per year (plus one-time setup-fee of 2.000 Euros). And end-user just pay 50 Euros per resource assignment. So, it makes sense to just pay for 50 Euros, and then you may be providing services using NAT+CGN (in the case of IPv4) or a single /64 to each subscriber in the case of IPv6. It is broken, of course, but people do that. 4) The fee scheme is somehow responsible of that as well, as there is in my opinion, unfairness. A big ISP having an IPv6 /20, or /24 or /29 or /32 is paying always the same. This is the only region that have a "flat" rate. 5) We could fix the point above, auditing every end-user. But we could also fix it in a better way by: a) A policy change in the line the one I've proposed (see the slides and the links for a diff) b) Having a single LIR contract, instead of LIR and end-user c) This may be (as an option), also become a way to make a price scheme which is proportional to the amount of resources allocated. Note that we don't need to change the fee scheme, but it is an opportunity for taking a look into that. It may be perfectly possible to keep the cost of end-users as 50 Euros (for a single /48, for example), but having a single contract. I know perfectly that fees are not "policy", however only if we address that we can do correctly the policy. A demonstration of that: When I proposed the IPv6 PI and it reached consensus, it was needed to create the "end-user" contract and the corresponding fee, so is something that we have done before. I know that the proposed text may be very imperfect, for example the usage of "ISPs", but this is not the key now, there are for sure several alternatives to that. For example, we could just differentiate both cases with "LIR that do subsequent distributions initially qualify for /32 up to /29 etc. LIRs that do not do subsequent distributions initially qualify for a /48 for each end-site". So please, don't consider specific text at this point of the discussion. And last, but not least, repeating myself, we could do this just for IPv6, or also work in parallel in a policy proposal for IPv4 PI removal as well. This will be probably the best choice, so we can let the NCC to have a simplified policy, a single contract and consequently less overhead: Simplification for everyone. Thoughts? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es 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.

16 50

2018-02 Assignment Clarification in IPv6 Policy - comments from today meeting
by JORDI PALET MARTINEZ 18 May '18

18 May '18

Hi all, I've been asked to state what is the problem. I think it was clear in my slides, but anyway, here we go with all the problems I see: 1) The current policy text says "Providing another entity with separate addresses (not prefixes)". To me this is inconsistent addresses instead of an address vs not-prefixes. 2) If the end-device need a /64 instead of a single address, as per RFC8273, then it is breaking the actual policy. 3) If we allow sub-assignments, what is then the difference in between IPv6 PA and PI ? So, I think it is clear we have not just one problem? Now, if we want to go further. Do we have the same problem with IPv4 if, for example a university, instead of using NAT, they also sub-assign public IPv4 addresses to students? Inputs? Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es 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.

2 4

2018-01 New Policy Proposal (Organisation-LIR Clarification in IPv6 Policy)
by Marco Schmidt 16 May '18

16 May '18

Dear colleagues, A new RIPE Policy proposal, 2018-01, "Organisation-LIR Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the wording used in ripe-684 regarding terms such as "organisation" and "LIR". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-01 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 23 March 2018. Regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

11 11

2018-01 Organisation-LIR Clarification in IPv6 Policy - comments from today meeting
by JORDI PALET MARTINEZ 16 May '18

16 May '18

Hi all, I tried to find the "mismatch" that Peter mention today in the meeting about this proposal text, however was unable to. So, if Peter or somebody else can point to anything more specific, the authors will be happy to provide thougths for alternatives to the mismatching text. Thanks! Regards, Jordi ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es 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.

1 0

FW: WG chair change
by Erik Bais 12 May '18

12 May '18

Hi Gert, Sander & AP-WG members, Thank you for the email and I would like to formally put my name in the hat. For those that don't know me personally, my name is Erik Bais, Dutch, I'm 45, married for 16 year with my wife Wilhelmina and we have 2 sons. I'm the owner of a Dutch ISP named A2B Internet and I'm one of the co-founders of the IPv4 broker : Prefix Broker. I've lived most of my life in The Netherlands and as a family, we lived for almost a year in the UAE (Dubai) in 2008/2009, when I worked for a US based system integrator and I've worked in Germany for a US based company in the 90's for a year. I have a been working in the ISP community since the 2000. And started A2B Internet in 2010 in The Netherlands. In our work as a connectivity ISP, we started to request AS numbers and IP space for customers in order to get them migrated to our network and while doing so, we noticed some things that needed improvement in the AP policies. That is how it all got started ... I've been the author of the following proposals that have been accepted by the community: https://www.ripe.net/participate/policies/proposals/2011-02 : Removal of multihomed requirement for IPv6 PI # co-author together with Jordi https://www.ripe.net/participate/policies/proposals/2013-04 : Resource Certification for non-RIPE NCC Members # Services WG - allowing PI space holders and Legacy space holders the option for RPKI certification. https://www.ripe.net/participate/policies/proposals/2014-02 : Allow IPv4 PI transfer https://www.ripe.net/participate/policies/proposals/2014-12 : Allow IPv6 Transfers https://www.ripe.net/participate/policies/proposals/2014-13 : Allow AS Number Transfers https://www.ripe.net/participate/policies/proposals/2015-04 : RIPE Resource Transfer Policies And I've been quite active on the discussions on the mailinglist and in the GM's. Besides the various presentations about the policies, I've also done some presentations in the plenary of the RIPE meetings and different WG's about various topics.. Examples are: https://ripe72.ripe.net/archives/video/116/ : Naughty Port project about a different way of making a peering decision based on Network Naughty-ness using a rating system against DDOS's. https://ripe74.ripe.net/archives/video/119/ : IRR Filtering at IXP Route Servers https://ripe75.ripe.net/archives/video/165/ : Pre-Transfer Clean-Up of Abused Prefixes I really like the RIPE community and as an active policy proposer, I think I can say that I have been around the block on the PDP and can work with the sometimes harsh way of communication that a co-chair role has need to deal with in the heat of some discussions. I understand what it requires in effort from time to time and as I'm living in the Netherlands, it makes it easy to visit the Amsterdam RIPE office for me if needed. I hope that the community appreciates the transparent way of communicating and knowledge sharing that I like and that I will be selected as the co-chair for the AP-WG. Regards, Erik Bais

2 1