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

Language clarification proposal
by Nick Hilliard 15 Dec '14

15 Dec '14

2014-07: support 2014-08: support 2014-10: support 2014-11: support Nick

3 2

2014-11 New Draft Document and Impact Analysis Published (Language Clarification for "Allocating/Assigning Resources to the RIPE NCC")
by Marco Schmidt 11 Dec '14

11 Dec '14

Dear colleagues, The proposal described in 2014-11, "Language Clarification for "Allocating/Assigning Resources to the RIPE NCC"", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-11 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-11/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 9 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-10 New Draft Document and Impact Analysis Published (Language Clarification in "IPv6 Addresses for Internet Root Servers In The RIPE Region")
by Marco Schmidt 11 Dec '14

11 Dec '14

Dear colleagues, The proposal described in 2014-10, "Language Clarification in "IPv6 Addresses for Internet Root Servers In The RIPE Region"", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-10 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-10/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 9 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

2014-08 New Draft Document and Impact Analysis Published (Language Clarification in "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region")
by Marco Schmidt 11 Dec '14

11 Dec '14

Dear colleagues, The proposal described in 2014-08, "Language Clarification in "Contractual Requirements for Provider Independent Resource Holders in the RIPE NCC Service Region"", is now in its Review Phase. The draft document has been published, along with an impact analysis conducted by the RIPE NCC. You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2014-08 The draft document is available at: https://www.ripe.net/ripe/policies/proposals/2014-08/draft We encourage you to read the draft document and send any comments to address-policy-wg(a)ripe.net before 9 January 2015. Regards, Marco Schmidt Policy Development Officer RIPE NCC

1 0

Re: [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Removing IPv6 Requirement for Receiving Space from the Final /8)
by Hamed Shafaghi 10 Dec '14

10 Dec '14

+1 Support -- -------------------------------------------- I Hamed Shafaghi I I Managing Director I I Skydsl® Telecom I hamed(a)skydsl.ir I www.skydsl.ir I

1 0

Policy Proposal Implemented: 2014-02, "Allow PI transfer"
by Ioanna Spyroulia 03 Dec '14

03 Dec '14

Dear colleagues, We are pleased to announce that we have implemented policy proposal 2014-02, "Allow IPv4 PI transfer”. In accordance with the new policy, End Users can transfer complete or partial blocks of Provider Independent (PI) IPv4 address space that were previously assigned to them by the RIPE NCC. To initiate a PI transfer, the sponsoring LIR of either the transferring or receiving End User should open a ticket with the RIPE NCC by sending an email to lir-help(a)ripe.net. The procedure describing the requirements for PI transfers can be found at: https://www.ripe.net/lir-services/resource-management/ipv4-transfers/transf… The list of all PI assignments transferred under this policy can be found at: https://www.ripe.net/lir-services/resource-management/ipv4-transfers/table-… The archived policy proposal can be found at: https://www.ripe.net/ripe/policies/proposals/2014-02 The updated RIPE Document, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", is available at: https://www.ripe.net/ripe/docs/ripe-623 Kind regards, Ioanna Spyroulia RIPE NCC Registration Services

3 3

Policy Proposal Implemented: 2014-02, "Allow PI transfer"
by Sakun Alexey 01 Dec '14

01 Dec '14

Hi! My question is: is it possible in accordance with a new policy to transfer PI-block from End User to LIR, not to another End User? So LIR becomes valid owner of PI-block and then convertes this PI block to PA in accordance with this procedure: http://www.ripe.net/lir-services/resource-management/converting-pi-to-pa. Here, https://www.ripe.net/lir-services/resource-management/ipv4-transfers/transf… it is written : ... Any legitimate holder of IPv4 PI space can transfer this to another End User or _*MEMBER*_ in the RIPE NCC service region, provided:.. As i understand - it is possible? Thank you. -- Best regards, Alexey

2 1

Re: [address-policy-wg] 2014-04 New Draft Document and Impact Analysis Published (Relaxing IPv6 Requirement for Receiving Space from the Final /8)
by Gert Doering 01 Dec '14

01 Dec '14

Dear Address Policy WG, while I can understand that beaches and drinks are more attractive than policy work, we have a proposal here that needs a bit of caring - this one is in Review Phase until Friday, and has received exactly one comment yet (strong support). I could use a *bit* more feedback here... thanks, Gert Doering, Address Policy WG Chair On Thu, Jul 31, 2014 at 01:30:43PM +0200, Marco Schmidt wrote: > > Dear colleagues, > > The draft document for version 2.0 of the policy proposal 2014-04, > "Relaxing IPv6 Requirement for Receiving Space from the Final /8", > has now been published, along with an impact analysis conducted by > the RIPE NCC. > > Some of the differences from version 1.0 include: > > - Extending the fulfilment of the IPv6 requirement to include any > globally routable unicast IPv6 address block > - Related wording adjustments in the summary and rationale of the proposal > > > You can find the full proposal and the impact analysis at: > > https://www.ripe.net/ripe/policies/proposals/2014-04 > > and the draft document at: > > https://www.ripe.net/ripe/policies/proposals/2014-04/draft > > We encourage you to read the draft document text and send any comments > to address-policy-wg(a)ripe.net before 29 August 2014. > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > > 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

21 46

2014-09 Policy Proposal Withdrawn (Language Clarification in "IPv6 Address Space Policy For Internet Exchange Points")
by Marco Schmidt 28 Nov '14

28 Nov '14

Dear colleagues, The proposal 2014-09, "Language Clarification in "IPv6 Address Space Policy For Internet Exchange Points"" has been withdrawn. It is now archived and can be found at: http://www.ripe.net/ripe/policies/proposals/2014-09 Reason for withdrawal: During the discussion phase there was feedback that IPv6 assignments for IXPs should be able to be used for other purposes besides a peering LAN. The proposer therefore believes that the current term "should" reflects the RIPE community’s understanding of this policy, and so decided withdraw the proposal. Regards, Marco Schmidt Policy Development Officer RIPE NCC

2 1

Re: [address-policy-wg] address-policy-wg Digest, Vol 39, Issue 10
by Lu 24 Nov '14

24 Nov '14

Should we put address policy wh together with IPv6 wg? Why we need two different wg for addressing?the day we start treat IPv6 as normal IP address is the day we really in a world of v6. This transmission is intended solely for the addressee(s) shown above. It may contain information that is privileged, confidential or otherwise protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons other than the intended addressee(s) is strictly prohibited. If you have received this transmission in error, please notify this office immediately and e-mail the original at the sender's address above by replying to this message and including the text of the transmission received. > On 2014年11月9日, at 上午11:00, address-policy-wg-request(a)ripe.net wrote: > > Send address-policy-wg mailing list submissions to > address-policy-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ripe.net/mailman/listinfo/address-policy-wg > or, via email, send a message with subject or body 'help' to > address-policy-wg-request(a)ripe.net > > You can reach the person managing the list at > address-policy-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of address-policy-wg digest..." > > > Today's Topics: > > 1. FW: [policy-announce] 2014-12 New Policy Proposal (Allow IPv6 > Transfers) (Erik Bais) > 2. Re: 2014-12 New Policy Proposal (Allow IPv6 Transfers) > (Andy Davidson) > 3. Re: 2014-13 New Policy Proposal (Allow AS Number Transfers) > (Andy Davidson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 8 Nov 2014 17:00:35 +0100 > From: "Erik Bais" <ebais(a)a2b-internet.com> > Subject: [address-policy-wg] FW: [policy-announce] 2014-12 New Policy > Proposal (Allow IPv6 Transfers) > To: <ipv6-wg(a)ripe.net> > Cc: address-policy-wg(a)ripe.net > Message-ID: <002601cffb6d$2647cb00$72d76100$(a)a2b-internet.com> > Content-Type: text/plain; charset="Windows-1252" > > Hi, > > This email is to inform the people who are subscribed on the IPv6 WG list > but not on the Address Policy WG list. > > There is a policy proposal currently in discussion phase to Allow IPv6 > Transfers. > >> You can find the full proposal at: > >> https://www.ripe.net/ripe/policies/proposals/2014-12 > >> We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 28 November 2014. > > Regards, > Erik Bais > > -----Oorspronkelijk bericht----- > Van: policy-announce-bounces(a)ripe.net > [mailto:policy-announce-bounces@ripe.net] Namens Marco Schmidt > Verzonden: donderdag 30 oktober 2014 13:43 > Aan: policy-announce(a)ripe.net > CC: address-policy-wg(a)ripe.net > Onderwerp: [policy-announce] 2014-12 New Policy Proposal (Allow IPv6 > Transfers) > > > Dear colleagues, > > > A proposed change to RIPE Document ripe-589, "IPv6 Address Allocation > and Assignment Policy" is now available for discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2014-12 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 28 November 2014. > > Regards > > Marco Schmidt > Policy Development Officer > RIPE NCC > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 9 Nov 2014 09:58:40 +0000 > From: Andy Davidson <andy(a)nosignal.org> > Subject: Re: [address-policy-wg] 2014-12 New Policy Proposal (Allow > IPv6 Transfers) > To: <address-policy-wg(a)ripe.net> > Message-ID: <20141109095830.GA31177(a)chilli.default.andyd.uk0.bigv.io> > Content-Type: text/plain; charset="us-ascii" > >> On Thu, Oct 30, 2014 at 01:43:29PM +0100, Marco Schmidt wrote: >> https://www.ripe.net/ripe/policies/proposals/2014-12 >> [... Allow IPv6 Transfer ...] >> We encourage you to review this proposal and send your comments to >> <address-policy-wg(a)ripe.net> before 28 November 2014. > > Support. > > -a > > > > ------------------------------ > > Message: 3 > Date: Sun, 9 Nov 2014 10:05:49 +0000 > From: Andy Davidson <andy(a)nosignal.org> > Subject: Re: [address-policy-wg] 2014-13 New Policy Proposal (Allow AS > Number Transfers) > To: <address-policy-wg(a)ripe.net> > Message-ID: <20141109100549.GB31177(a)chilli.default.andyd.uk0.bigv.io> > Content-Type: text/plain; charset="us-ascii" > >> On Thu, Oct 30, 2014 at 03:56:48PM +0100, Marco Schmidt wrote: >> https://www.ripe.net/ripe/policies/proposals/2014-13 >> [... Allow AS Number Transfers ...] >> We encourage you to review this proposal and send your comments to >> <address-policy-wg(a)ripe.net> before 28 November 2014. > > Support the end result but don't support text as it stands. > > - Would prefer not to see it possible to transfer ASN on a temporary > basis - if an organisation needs temporary resources these are > available from the RIPE NCC. > > - Not sure if a list of non-approved ASN transfers is useful, and > concerned that it might put people off registering transfers with > the NCC. > > -a > > > > > End of address-policy-wg Digest, Vol 39, Issue 10 > *************************************************

11 12