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

recantation
by Randy Bush 11 May '17

11 May '17

at yesterday's address policy statement, i was quite incorrect when i said that updated or obsoleted rfcs were marked. they are not. the index entry is marked. the rfcB obsoliting rfcA is marked as such. but rfcA is not marked as modified. apologies. randy

1 0

2017-01 New Policy Proposal (Publish statistics on Intra-RIR Legacy updates)
by Marco Schmidt 05 May '17

05 May '17

Dear colleagues, A new RIPE Policy proposal, 2017-01, "Publish statistics on Intra-RIR Legacy updates" is now available for discussion. The goal of this proposal is to require the RIPE NCC to publish all changes to the holdership of legacy resources in the existing transfer statistics. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2017-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 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 24 May 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

11 22

APWG meeting agenda 0.2
by Gert Doering 26 Apr '17

26 Apr '17

Hi APWG folks, below you can find a second draft for the RIPE address policy WG meeting's agenda, which will take place in Budapest in the following time slots: Wednesday, May 10, 09:00 - 10:30 Wednesday, May 10, 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. Depending on the amount of "not yet known" things to show up on the agenda, we might only need one time slot. In which case, we can all join the Connect WG for a change :-) Notable changes in the second version: Item "E" added (this was prompted by a reference to an updated-behind-our-back RFC in the AS number policy), and due to "more policy proposals", item "F" moved to second slot. HEADS UP: side room. regards, Gert Doering & Sander Steffann, APWG chairs ---------------------------------------------------------------------- Wednesday, 09:00-10:30 - main room ---------------------------------------------------------------------- A. Administrative Matters 5 min (welcome, thanking the scribe, approving the minutes, etc.) B. WG Chair Selection 10 min - longest-serving chair (Gert Döring) stepping down - willing to be re-appointed and serve another term C. Current Policy Topics - Marco Schmidt, NCC PDO 20 min - 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 72 - brief overview over new proposals (if any) D. Feedback From NCC Registration Service - Andrea Cima 25 min (+ discussion with the group) E. outdated references in policy documents - Marco Schmidt 15 min (+ discussion with the group) ---------------------------------------------------------------------- Wednesday, 12:00-13:30 - side room (HEADS UP!) ---------------------------------------------------------------------- Welcome back F. Discussion of open policy proposals 40 min 2016-04 IPv6 PI Sub-assignment Clarification Maximilian Wilhelm 2017-01 Publish statistics on Intra-RIR Legacy updates Elvis Daniel Velea Y. Open Policy Hour 5 min 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 Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279

1 0

Policy Proposal Implemented: 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies"
by Laurens Hoogendoorn 20 Apr '17

20 Apr '17

Dear colleagues, We are pleased to announce that we have implemented policy proposal 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies". The criteria used to evaluate the size of subsequent IPv6 allocations has been expanded to include: - Hierarchical and geographical structuring of the organisation - Planned longevity of the allocation - Segmentation of infrastructure for security You can find more information about the expanded evaluation criteria here: https://www.ripe.net/manage-ips-and-asns/ipv6/request-ipv6/assessment-crite… The archived policy proposal can be found here: https://www.ripe.net/participate/policies/proposals/2016-05 The RIPE Document, "IPv6 Address Allocation and Assignment Policy", is available here: https://www.ripe.net/publications/docs/ripe-684 -- Kind regards, Laurens Hoogendoorn RIPE NCC Registration Services

1 0

Cleaning up Unused AS Numbers
by Sander Steffann 19 Apr '17

19 Apr '17

Hi working group, After reviewing the discussions on this mailing list about cleaning up unused AS numbers we think that the concerns and questions that came up have been addressed by the RIPE NCC. Therefore the working group chairs have asked the RIPE NCC to take the feedback into account and proceed with the cleanup. Cheers, Sander Steffann APWG co-chair

1 0

FYI: policy proposal in AFRINIC
by Shane Kerr 13 Apr '17

13 Apr '17

All, This just crossed my news feeds: https://www.theregister.co.uk/2017/04/12/no_ip_addresses_for_countries/ Cheers, -- Shane

3 2

Password
by Stephen Balogh 09 Apr '17

09 Apr '17

Need password

5 4

Cleaning up Unused AS Numbers
by Laurens Hoogendoorn 05 Apr '17

05 Apr '17

Dear colleagues, As previously mentioned at RIPE 73, we are planning a project to clean up unused AS Numbers. You can find this presentation here: https://ripe73.ripe.net/archives/video/1456/ According to ripe-679, "Autonomous System (AS) Number Assignment Policies" if an organisation no longer uses as AS Number, it should be returned to the free pool so it can be reassigned: https://www.ripe.net/publications/docs/ripe-679 There are currently around 6,600 ASNs in our service region (held or sponsored by 2,682 LIRs) that are not being advertised in the routing system. This represents around 22% of the ~30,000 ASNs assigned by the RIPE NCC. There are a number of legitimate reasons why an ASN might not be advertised in the routing system. However, it is also possible that the holder doesn't exist anymore or the ASN is no longer needed. Not only should unused ASNs be returned, but it's important to clean up out of date registrations, which affect the quality of data in the RIPE Registry. Our Proposal We plan to email the LIR or sponsoring LIR for each unannounced ASN and ask if the resource is still needed. We will group together ASNs that are sponsored or held by the same LIR to minimise the number of emails. We will ask if the ASN is currently being used or if there are plans to start using the ASN in the coming three months. Organisations can always request a new ASN in the future if they need one. If we do not receive a reply or if the ASN will not be used within three months, we will start the process of returning the ASN to the free pool. The deregistration process will take three months, during which time the LIR can still indicate that the ASN is needed. If the ASN is still needed, the validity of the assignment (such as the multihoming requirement) will not be re-evaluated. We do not expect any significant cost or impact on other services, as most of this process will be automated and we will not need to re-evaluate the assignments. Contacting all relevant LIRs will take less than six months. Please review this proposal and send any comments or other feedback before Thursday 6 April to <address-policy-wg(a)ripe.net>. Regards, Laurens Hoogendoorn Registration Services RIPE NCC

10 11

2016-05 Proposal Accepted (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 30 Mar '17

30 Mar '17

Dear colleagues, Consensus has been reached on 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies". This policy change matches the subsequent IPv6 allocation requirements with the initial allocation requirements. In addition to the existing justification based on past utilisation, it is now also possible to document new needs, including the number of users, the extent of the organisation's infrastructure, the hierarchical and geographical structuring of the organisation, the segmentation of infrastructure for security and the planned longevity of the allocation. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2016-05 The new RIPE Document is ripe-684 and is available at: https://www.ripe.net/publications/docs/ripe-684 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 Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

1 0

2016-05 Last Call for Comments (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
by Marco Schmidt 28 Mar '17

28 Mar '17

Dear colleagues, Proposal 2016-05, "Synchronising the Initial and Subsequent IPv6 Allocation Policies", is now in Concluding Phase. The goal of this proposal is to match the subsequent IPv6 allocation requirements with the initial allocation requirements. 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 28 March 2017 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/2016-05 Please e-mail any final comments about this proposal to <address-policy-wg(a)ripe.net> before 28 March 2017. Regards, Marco Schmidt Policy Development Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1