Marco Schmidt

New Year, new Policy Developments: While proposal 2019-07, "Default assignment size for #IXP" is withdrawn, proposal 2019-06, "Multiple Editorial Changes in #IPv6 Policy" does need your input to proceed: ripe.net/ripe/mail/arch…

@natural20 @ripencc uuups! It wasn't me 🤫

Today, at 15:35, we made our final /22 IPv4 allocation from the last remaining addresses in our available pool. We have now run out of IPv4 addresses. Read our full announcement here: ripe.net/publications/n… In the picture, the Registration Services team at the RIPE NCC

As result of the #IPv4 runout also the #RIPE IPv4 policy got updated automatically ripe.net/ripe/mail/arch…

With less than 100 IPv4 /22-equivalents remaining in our pool, we expect to run-out early next week. Once that moment is reached, this table and graph (at zero now) showing the the number of /24 requests will become active. Link to the IPv4 waitlist: ripe.net/manage-ips-and…

After 20 years of service to the RIPE NCC, Axel Pawlik will step aside for a new generation of leaders. He announced his resignation today at the RIPE NCC Services Working Group session at #RIPE79. Read the news announcement at: ripe.net/s/Celk

Today at #RIPE79, @MSchmidt_Policy announced that Petrit Hasani will bet he next Policy Officer!

It was my pleasure 🙏

Great to see four experts discussing the past and future of #IPv4 #RIPE79

Very interesting panel discussion about #IPv4 runout and transfers during #RIPE79 Join remotely: ripe79.ripe.net/live/side/

@chaz_6 Thanks for sharing your opinion. To make your input count for the actual Policy Development Process, it is important that you bring it the mailing list of the Anti-Abuse Working Group ripe.net/participate/ri…

@MSchmidt_Policy This has been a hotly debated subject on the mailing list. It seems the good guys don't mind the additional verification. I am in favour of it. It is good stewardship of a non-infinite resource.

Does the abuse contact need more validation? Join the discussion!

@slipowski @ripencc The number of LIR application has skyrocketed in the last weeks. This needs more time. RIPE NCC is ready to ensure the same due diligence checks and applying a first-come-first-serve rule.

@MSchmidt_Policy @ripencc Ready? Really? Do you know how long the LIR application queue is? :-/ :-(

#IPv4 runout will happen soon - @ripencc is ready This proposal is another example how the RIPE community safeguard the future of the #Internet

Both proposals have also reached consensus at the @APNIC Member meeting - prop-131: Editorial changes in #IPv6 Policy - prop-132: #RPKI #ROAs for unallocated and unassigned APNIC address space

#APNIC48 #Policy SIG summary: Out of 5 proposals 2 have reached consensus - Editorial changes in #IPv6 Policy - prop-132 (#RPKI) Will go now to the @APNIC Member Meeting (AMM) to seek there consensus too. The other 3 go back to the community for further discussion.

The #policy meeting has started at #APNIC48 Looking forward to the discussions for 5 proposals about #IPv6, #RPKI, transfers and more. Join here remotely: apnic.zoom.us/j/823798743 Participate here: confer.apnic.net

Can the #RIPE community play a role against #BGPhijacks ? New version of #policyproposal 2019-03 has been published and needs your input.

The @TeamARIN AC has abandoned the proposal "Validation of POCs Referenced as Abuse Contacts" due to a lack of support from the community. arin.net/participate/po… The proposal was similar to ongoing RIPE proposal 2019-04 ripe.net/participate/po…

Another #policyproposal needs your input. Check it out, especially if you are involved in #routing #rpki and the #RIPE Database

Join us @ripencc where we’ll be tweeting about IP resource management, policy implementations and more!