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

Re: [address-policy-wg] 2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by Mike Simkins 28 Feb '13

28 Feb '13

Support Mike. On 28 Feb 2013, at 13:04, Marco Schmidt wrote: > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2013-02/ > > We encourage you to review this proposal and send your comments to > <apwg-chairs(a)ripe.net> before 28 March 2013. > > Regards > > Marco Schmidt > on behalf of the Policy Development Office > RIPE NCC > >

1 0

Re: [address-policy-wg] 2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by Sebastian Wiesinger 28 Feb '13

28 Feb '13

* Marco Schmidt <mschmidt(a)ripe.net> [2013-02-28 14:21]: > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2013-02/ Support -- GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9CE) 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE. -- Terry Pratchett, The Fifth Elephant

1 0

Re: [address-policy-wg] 2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by James Blessing 28 Feb '13

28 Feb '13

Support J On 28 February 2013 13:04, Marco Schmidt <mschmidt(a)ripe.net> wrote: > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2013-02/ > > We encourage you to review this proposal and send your comments to > <apwg-chairs(a)ripe.net> before 28 March 2013. > > Regards > > Marco Schmidt > on behalf of the Policy Development Office > RIPE NCC > > -- James Blessing 07989 039 476

2 1

Re: [address-policy-wg] 2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by Sascha Lenz 28 Feb '13

28 Feb '13

Hi all, Am 28.02.2013 um 14:04 schrieb "Marco Schmidt" <mschmidt(a)ripe.net>: > > Dear Colleagues > > A new RIPE Policy Proposal has been made and is now available for > discussion. > > > You can find the full proposal at: > > https://www.ripe.net/ripe/policies/proposals/2013-02/ > > We encourage you to review this proposal and send your comments to > <apwg-chairs(a)ripe.net> before 28 March 2013. > even though i actually liked the intention of the current policy text, there seems to be no choice here but to support this change due to the lack of a certification policy. I don't really want to go there again for a while. So, support. -- Mit freundlichen Grüßen / Kind Regards Sascha Lenz [SLZ-RIPE] Senior System- & Network Architect

2 1

2013-02 New Policy Proposal (Removal of requirement for certification of reallocated IPv4 addresses)
by Marco Schmidt 28 Feb '13

28 Feb '13

Dear Colleagues A new RIPE Policy Proposal has been made and is now available for discussion. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2013-02/ We encourage you to review this proposal and send your comments to <apwg-chairs(a)ripe.net> before 28 March 2013. Regards Marco Schmidt on behalf of the Policy Development Office RIPE NCC

1 0

Re: [address-policy-wg] 2012-09 Last Call for Comments (Modification of The Time Limits For Temporary Internet Assignments)
by Gert Doering 27 Feb '13

27 Feb '13

Dear Working Group, On Wed, Feb 27, 2013 at 02:08:15PM +0100, Marco Schmidt wrote: > The proposal described in 2012-09, "Modification of The Time Limits For Temporary Internet Assignments", is now in its > Concluding Phase. > > The Address Policy Working Group co-Chairs have declared that consensus for > the proposal has been reached and it will now move to Last Call. well, technically we have not yet formally declared that (just in coordination e-mails between the WG chairs and the RIPE NCC PDO), so I now need to do so :-) 2012-09 saw a high amount of "support!" and "+1" voices in discussion phase, and no opposition, so moving to review phase was straightforward (there was a side-track discussion about "what is a month?" but that did not lead to changes in the text, or stated opposition). In review phase, things started slowly because we (chairs) didn't remind the WG that supporting voices do not carry over from the discussion phase. After I did that, we received 16 clear voices of support, and no opposing voices. So, we have quite strong consensus, and thus moved to Last Call. In Last Call, supporting voices do not need to be repeated - this is the phase where "silence is consent". But if you disagree with our interpretation of the comments in discussion or review phase, or with the propsal in general, now is the time to speak up. Gert Doering -- Address Policy WG Chair -- 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 (89) 32356-444 USt-IdNr.: DE813185279

1 0

Policy update request on certification of transferred IPv4 allocations
by Andrew de la Haye 27 Feb '13

27 Feb '13

[Apologies for duplicate emails] Dear colleagues, Based on recent discussions on the RIPE Address Policy WG mailing list, the RIPE NCC is now seeking policy related action from the RIPE community with regards to clear guidelines on how it should proceed with certifying transferred IPv4 allocations. It has recently come to our notice, via two of the policy authors, that the original intention (in 2007) of the sentence "Re-allocated blocks will be signed to establish the current allocation owner" was that the transferred block *must* be signed *after* the transfer in order to completely establish holdership. This sentence can be found under section 5.5 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" here: http://www.ripe.net/ripe/docs/ripe-582#Transfers-of-Allocations Because the RIPE community provided guidance saying that certification should be an opt-in system, the RIPE NCC built an RPKI Certification system based on this opt-in notion, therefore it is not currently possible for the RIPE NCC to issue certificates without the resource holder initiating the process. Therefore, the RIPE NCC's interpretation and implementation of this specific sentence has been: Registration Services verifies and reflects the change in holdership of the re-allocated blocks by updating the database objects and internal records following the transfer. Any certificates that had been attached to these number resources before the transfer automatically become invalid/revoked due to the holdership change. The transfer recipient can then request a new certificate for the address space and the RIPE NCC will proceed to sign these resources to establish the current allocation holder. Therefore, the RIPE NCC does not make certification of any resources mandatory. As the sentence in section 5.5 of "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" is open to interpretation, the RIPE NCC is seeking representative(s) from the RIPE community to submit an update to ripe-582 that will replace this sentence with more accurate and appropriate wording or perhaps remove it completely. Kind regards, Andrew de la Haye Chief Operations Officer RIPE NCC

17 24

2012-06 Proposal Accepted (Revert "Run Out Fairly")
by Emilio Madaio 27 Feb '13

27 Feb '13

Dear Colleagues Consensus has been reached, and the proposal for a change to RIPE Document ripe-577, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-06 The updated RIPE document is ripe-582 and is available at: https://www.ripe.net/ripe/docs/ripe-582 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

3 2

2012-09 Last Call for Comments (Modification of The Time Limits For Temporary Internet Assignments)
by Marco Schmidt 27 Feb '13

27 Feb '13

Dear Colleagues, The proposal described in 2012-09, "Modification of The Time Limits For Temporary Internet Assignments", is now in its Concluding Phase. The Address Policy Working Group co-Chairs have declared that consensus for the proposal has been reached and it will now move to Last Call. As per the RIPE Policy Development Process (PDP), the purpose of these coming four weeks of Last Call is to give the community the opportunity to present well-justified objections in case anyone missed the previous two phases and want to oppose the proposal. Any objection must be made by 27 March 2013 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 co-Chairs of all RIPE Working Groups for consensus. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-09 Please e-mail any final comments about this proposal to apwg-chairs(a)ripe.net before 27 March 2013. Regards Marco Schmidt on behalf of the Policy Development Office RIPE NCC

1 0

Re: [address-policy-wg] [ncc-services-wg] 2012-08 Discussion Period extended until 1 March 2013 (Publication of Sponsoring LIR for Independent Number Resources)
by Erik Bais 25 Feb '13

25 Feb '13

Hi Daniel, > We see it quite often. And the answer is that the sponsorships is rather an entry in some hidden RIPE db than a contract. When an end user is asked "Do you have a sponsoring LIR for this resource and if so, who is it?", the answer is usuallu " > We have no idea". And the only way to be certain is to send an email to the RIPE hostmasters. If you don't know, check the LIR Portal to see the registered PI spaces you hold there. For the customer, there is no requirement (if they really don't know.. ) and not get an invoice from some LIR, so it is very easy to just transfer the resources to another LIR and that way you are both sure ... > Let's say you do have the documents in the first situation. How do you know they are still valid? Yes, we used to be sponsor for this resource but how do we know that in RIPE:s point of view, we still are? Again, check the LIR portal for the registered PI resources under your LIR account. If there are company changes for the registered resources, inform the RIPE NCC that that is the case, send them the old info and the new info and if needed you will be requested additional paperwork of information. Typically, it is a 10 minute fix for a contact or address change. That is what it means to be a LIR, too many people see being an LIR as a way to get resources for themselves. We have customers that we provide RIPE Administration services for, they are an LIR themselves, but stay away from the actual administration or registration part. If an End-Customer wants a more formal registration service instead of a 'sponsoring LIR, could you do me a favor' kind of service, you should transfer the resources of that customer to your LIR within a blink of an eye ... Don't you think ? Publishing the information who the registration LIR is, doesn't fix the fact that information might not be correct. Go through the process of a PI transfer as an actual LIR and then decide if this is still something that is required. Regards, Erik Bais

2 1

2012-09 New Draft Document and Impact Analysis Published (Modification of The Time Limits For Temporary Internet Assignments)
by Emilio Madaio 25 Feb '13

25 Feb '13

Dear Colleagues, The draft document for the proposal described in 2012-09, "Modification of The Time Limits For Temporary Internet Assignments", has been published. The impact analysis that was conducted for this proposal has also been published You can find the full proposal and the impact analysis at: https://www.ripe.net/ripe/policies/proposals/2012-09 and the draft document at: https://www.ripe.net/ripe/policies/proposals/2012-09/draft We encourage you to read the draft document text and send any comments to address-policy-wg(a)ripe.net before 25 February 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

20 22

Re: [address-policy-wg] [ncc-services-wg] 2012-08 Discussion Period extended until 1 March 2013 (Publication of Sponsoring LIR for Independent Number Resources)
by Erik Bais 25 Feb '13

25 Feb '13

Peter makes some very good points here. If the End User doesn't know who their Sponsoring LIR is, there is nothing keeping them from transferring the resource to another LIR. You would be surprised how may LIR's are sponsoring PI space without any contract or charge to their customers of 8 years ago ... and those LIR's still keep paying the bill to RIPE. Last year I cleaned up an LIR of 25+ PI resources of former customers. If the LIR themselves is unaware of the situation or simply don't care and the customer never receives any invoice for resources. Who are we to decide to publish this information. The last argument, that it would make abuse easier ... /sigh. Being a sponsoring LIR has nothing to do with abuse management. Being an LIR has nothing to do with having a network or route packets. Being / running an LIR doesn't mean you have your own network .. nor does it say that you are an ISP .. or a hoster. You are running a resource registration office. Yes we register PI space for end-users, even if they are not consuming our network services. We charge end-users for that service, we provide RIPE with all the required paperwork and handle the PI request, but if someone is routing some "bad" packets on the IP's we registered for them in the past, why would it help abuse if someone knows who registered the PI space in the first place? It is not that we can put a null-route for the IP's or 'drop the BGP announcement' as they are not in our network. Perhaps the name 'Sponsoring LIR' is a bit tricky as it might give the impression it is for free. But registration of resources (PI space, AS numbers etc) is just like any other kind of registration services, it takes time to provide the service and we charge for the time. So, perhaps a bit longer story than what Peter said, but the result it the same. Not in favor for this policy. Regards, Erik Bais A2B Internet

1 0

Was : RE: 2012-09 - now : PDP 'I Agree discussion'
by Erik Bais 23 Feb '13

23 Feb '13

Hi Jan, >> It's an oddity of the PDP. I'm not sure if it serves a useful purpose >> because at the times when there are piles of proposals flying around (e.g. >> now), people end up getting jaded by the requirement for constant acks >> and me-toos. >Agree... is this painful enough that we need to change it? Looking at how the process currently goes, I don't think that changing this would make everyone his/her live so much easier. Personally I think doing it the way that we currently do it, might look a bit redundant, but it does provide clear consensus during all phases of the PDP. Typically we seem to be pretty easy to get on top of policies again if it is needed .. (just look at the simple email from one of the chairs to restate support in the current phase / or state of the proposal. ) How would you propose to change it if it would be changed ? Erik Bais

4 3

Information/log over all temporarily/experimental assignments?
by Roger Jørgensen 21 Feb '13

21 Feb '13

Hi, Are there any place online where I can see how many, how long, and for what purpose assignments have been done under the temporary assignments policy? -- Roger Jorgensen | ROJO9-RIPE rogerj(a)gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger(a)jorgensen.no

2 2

2012-05 Proposal Accepted (Transparency in Address Block Transfers)
by Emilio Madaio 13 Feb '13

13 Feb '13

Dear Colleagues, Consensus has been reached, and the proposal for a change to RIPE Document ripe-553, "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region", has been accepted by the RIPE community. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-05 The updated RIPE document is ripe-577 and is available at: https://www.ripe.net/ripe/docs/ripe-577 Thank you for your input. Regards Emilio Madaio Policy Development Officer RIPE NCC

3 3

New on RIPE Labs: 1, 000 /22 Allocated from Last /8
by Mirjam Kuehne 06 Feb '13

06 Feb '13

[apologies for duplicates] Dear colleagues, We allocated the 1,000th /22 from the last /8. Please read more on RIPE Labs: https://labs.ripe.net/Members/ingrid/1000-slash-22s-allocated-from-last-sla… Kind regards, Mirjam Kuehne RIPE NCC

13 17

Status of Policy Proposal 2012-04 - PI Assignments from the last /8
by Erik Bais 04 Feb '13

04 Feb '13

Hi, Is there any news on this proposal yet ? https://www.ripe.net/ripe/policies/proposals/2012-04 I would like to see this proposal binned rather today than tomorrow. No disrespect to Nick for putting this in writing and bringing this discussion in front of us, but opening the gates will not solve the problems most companies face, if they notice IPv4 shortage... Especially since it will only delay their pain for a very short period. And the problems for new entries (after that short period) for not having v4 available in the (not too far) future for NAT64 or alike technologies weigh much higher imho than providing cheap PI resources. So in short, I don't support this policy and I would like to have this archived for future references asap. Kind regards, Erik Bais

2 1

2012-10 Draft Document and Impact Analysis will be produced (Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis)
by Emilio Madaio 31 Jan '13

31 Jan '13

Dear Colleagues The discussion period for the proposed change to RIPE Document ripe-552, "IPv6 Address Allocation and Assignment Policy", has ended. A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-10 Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

2012-09 Draft Document and Impact Analysis will be produced (Modification of The Time Limits for Temporary Internet Assignments)
by Emilio Madaio 15 Jan '13

15 Jan '13

Dear Colleagues, The discussion period for the proposed change to RIPE Document ripe-526, "Temporary Internet Number Assignment Policies", has ended. A draft document and the RIPE NCC Impact Analysis will now be prepared for review. We will publish the documents shortly and we will make an announcement. You can find the full proposal at: https://www.ripe.net/ripe/policies/proposals/2012-09 Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Cosmetic Surgery Project: new revised document for Reverse Delegation Policy
by Emilio Madaio 14 Jan '13

14 Jan '13

Dear Colleagues, At the RIPE 59 Meeting in Lisbon, the RIPE NCC announced that it would undertake a project to improve the language of various RIPE Policy Documents, without changing their substance or meaning. This project is aimed at improving the clarity and readability of RIPE Documents. For more information, see: http://www.ripe.net/ripe/readability The last RIPE Policy Document to be revised was ripe-302, "Policy For Reverse Address Delegation of IPv4 and IPv6 Address Space in the RIPE NCC Service Region". The revised document is now available at: https://www.ripe.net/ripe/docs/ripe-581/ An update on the current status of the Cosmetic Surgery Project and the next step of the project will be presented no later than the RIPE 66 Meeting in May. Regards Emilio Madaio Policy Development Officer RIPE NCC

1 0

Last Mile: COMPUTATION TOOLS 2013 || May 27 - June 1, 2013 - Valencia, Spain
by Sandra Sendra 11 Jan '13

11 Jan '13

INVITATION: ================= Please consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to COMPUTATION TOOLS 2013. The submission deadline is extended to January 27, 2013. Authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org ================= ============== COMPUTATION TOOLS 2013 | Call for Papers =============== CALL FOR PAPERS, TUTORIALS, PANELS COMPUTATION TOOLS 2013, The Fourth International Conference on Computational Logics, Algebras, Programming, Tools, and Benchmarking May 27 - June 1, 2013 - Valencia, Spain General page: http://www.iaria.org/conferences2013/COMPUTATIONTOOLS13.html Call for Papers: http://www.iaria.org/conferences2013/CfPCOMPUTATIONTOOLS13.html - regular papers - short papers (work in progress) - posters Submission page: http://www.iaria.org/conferences2013/SubmitCOMPUTATIONTOOLS13.html Submission deadline: January 27, 2013 Sponsored by IARIA, www.iaria.org Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org Print proceedings will be available via Curran Associates, Inc.: http://www.proceedings.com/9769.html Articles will be archived in the free access ThinkMind Digital Library: http://www.thinkmind.org Please note the Poster and Work in Progress options. The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas. All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels. Before submission, please check and conform with the Editorial rules: http://www.iaria.org/editorialrules.html COMPUTATION TOOLS 2013 Topics (topics and submission details: see CfP on the site) Logics Reasoning logics; Fuzzy logics; Semantic logics; Temporal logics; Emotion logics; Ambiant logics; Modal logics; Description logics; Computational tree logic; Computational logics and constraints; Quantum computational logics; Executable computational logics; Monadic computational logics; Many-valued computational logics; Computability logic Algebras Computational algebras; K-theories, C*-algebras, Index theory; Algebraic and topological K-theory; Geometric group theory and group C*-algebras; Noncommutative geometry and topology; Pseudodifferential operators on singular manifolds; Topological invariants of non-simply connected manifolds; Deformation quantization; Lambda calculus; Relation algebra; Algebras for symbolic computation; Constructive algebras Advanced computation techniques Machine learning; Fuzzy theory/computation/logic; (Artificial) neuronal networks; Distributed artificial intelligence; Genetic algorithms; Analytic tableaux; Autonomous agent-based techniques; Knowledge-based systems and automated reasoning; Logical issues in knowledge representation /non-monotonic reasoning/belief; Dempster-Shafer theory; Concurrent computation and planning; Deduction and reasoning Specialized programming languages Logic programming; Specialized computation languages; Real-time computation languages; Embedded-computing languages; Programming semantics; Content-driven programming; Multimedia-oriented programming; Context-driven programming; Service-oriented programming; Pattern-oriented programming; Regenerative programming; Progressive programming; Sensing-oriented programming; Mobile-ubiquity-oriented computing; Compilation issues Tools for distributed computation Platforms for distributed computing; Specification and verification of programs and systems; Techniques for cloud computing; On-request resource allocation mechanisms; Security and privacy techniques; Computational benchmarking metrics, criteria and methodologies; Distributed debug and on-fly repairing; Inference of schemas, integrity constraints in computational applications; Real-world applications, experiments, projects ------------------------------------------- Committee: http://www.iaria.org/conferences2013/ComCOMPUTATIONTOOLS13.html ================================================

1 0

2012-10 New Policy Proposal (Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis)
by Emilio Madaio 05 Jan '13

05 Jan '13

Dear Colleagues, A proposed change to RIPE Document ripe-552, "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/2012-10 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 28 January 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC

23 23

2012-10 New Policy Proposal (Extension of IPv6/32 to /29 > on a per-allocation vs per-LIR basis)
by Iftikhar Ahmad Mehar 05 Jan '13

05 Jan '13

Hi, I do support this proposal too. Regards, Mehar Iftikhar Ahmad > From: address-policy-wg-request(a)ripe.net > Subject: address-policy-wg Digest, Vol 17, Issue 4 > To: address-policy-wg(a)ripe.net > Date: Thu, 3 Jan 2013 12:00:02 +0100 > > 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. Re: 2012-10 New Policy Proposal (Extension of IPv6 /32 to /29 > on a per-allocation vs per-LIR basis) (Sascha Luck) > 2. FW: 2012-10 New Policy Proposal (Extension of IPv6/32 to /29 > on a per-allocation vs per-LIR basis) (Sleigh, Robert) > 3. Re: 2012-10 New Policy Proposal (Extension of IPv6/32 to /29 > on a per-allocation vs per-LIR basis) (Sleigh, Robert) > 4. Re: 2012-10 New Policy Proposal (Extension of IPv6 /32 to /29 > on a per-allocation vs per-LIR basis) (Julien Rabier) > 5. Re: 2012-10 New Policy Proposal (Extension of IPv6 /32 to > /29) (Sonderegger Olaf ABRAXAS INFORMATIK AG) > 6. Re: 2012-10 New Policy Proposal (Extension of IPv6 /32 to /29 > on a per-allocation vs per-LIR basis) (Anfinsen, Ragnar) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 2 Jan 2013 15:47:42 +0000 > From: Sascha Luck <lists-ripe(a)c4inet.net> > Subject: Re: [address-policy-wg] 2012-10 New Policy Proposal > (Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis) > To: address-policy-wg(a)ripe.net > Message-ID: <20130102154742.GA49689(a)cilantro.c4inet.net> > Content-Type: text/plain; charset=us-ascii; format=flowed > > On Mon, Dec 31, 2012 at 11:12:50AM +0100, Emilio Madaio wrote: > > https://www.ripe.net/ripe/policies/proposals/2012-10 > > Support +1 > > cheers, > Sascha Luck > > > > > ------------------------------ > > Message: 2 > Date: Wed, 2 Jan 2013 23:28:47 -0000 > From: "Sleigh, Robert" <Robert.Sleigh(a)ee.co.uk> > Subject: [address-policy-wg] FW: 2012-10 New Policy Proposal > (Extension of IPv6/32 to /29 on a per-allocation vs per-LIR basis) > To: <address-policy-wg(a)ripe.net> > Message-ID: > <7589326DC369BE4EAACEB3A2EB92F8E31172F57C(a)HATMSG025.TMOUSERSUK.AD.T-MOBILE.CO.UK> > > Content-Type: text/plain; charset="us-ascii" > > > I support this proposal, +1 > > Regards > > Bob > 07958 318592 > > Life's for sharing... and what I like to share the most is a smile > > > > -----Original Message----- > From: address-policy-wg-bounces(a)ripe.net > [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Emilio Madaio > Sent: 31 December 2012 10:13 > To: policy-announce(a)ripe.net > Cc: address-policy-wg(a)ripe.net > Subject: [address-policy-wg] 2012-10 New Policy Proposal (Extension of > IPv6/32 to /29 on a per-allocation vs per-LIR basis) > > > Dear Colleagues, > > > A proposed change to RIPE Document ripe-552, "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/2012-10 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 28 January 2013. > > Regards > > Emilio Madaio > Policy Development Officer > RIPE NCC > > > NOTICE AND DISCLAIMER > This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. > > We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. > > Everything Everywhere Limited > Registered in England and Wales > Company Registered Number: 02382161 > Registered Office Address: Hatfield Business Park, Hatfield, Hertfordshire, AL10 9BW > > > > ------------------------------ > > Message: 3 > Date: Wed, 2 Jan 2013 17:28:48 -0000 > From: "Sleigh, Robert" <Robert.Sleigh(a)ee.co.uk> > Subject: Re: [address-policy-wg] 2012-10 New Policy Proposal > (Extension of IPv6/32 to /29 on a per-allocation vs per-LIR basis) > To: <address-policy-wg(a)ripe.net> > Message-ID: > <7589326DC369BE4EAACEB3A2EB92F8E31172F568(a)HATMSG025.TMOUSERSUK.AD.T-MOBILE.CO.UK> > > Content-Type: text/plain; charset="us-ascii" > > Support +1 > > Regards > > Bob > 07958 318592 > > Life's for sharing... and what I like to share the most is a smile > > > > -----Original Message----- > From: address-policy-wg-bounces(a)ripe.net > [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Emilio Madaio > Sent: 31 December 2012 10:13 > To: policy-announce(a)ripe.net > Cc: address-policy-wg(a)ripe.net > Subject: [address-policy-wg] 2012-10 New Policy Proposal (Extension of > IPv6/32 to /29 on a per-allocation vs per-LIR basis) > > > Dear Colleagues, > > > A proposed change to RIPE Document ripe-552, "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/2012-10 > > We encourage you to review this proposal and send your comments to > <address-policy-wg(a)ripe.net> before 28 January 2013. > > Regards > > Emilio Madaio > Policy Development Officer > RIPE NCC > > > NOTICE AND DISCLAIMER > This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. > > We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. > > Everything Everywhere Limited > Registered in England and Wales > Company Registered Number: 02382161 > Registered Office Address: Hatfield Business Park, Hatfield, Hertfordshire, AL10 9BW > > > > ------------------------------ > > Message: 4 > Date: Thu, 3 Jan 2013 08:47:27 +0100 > From: Julien Rabier <jrabier(a)ilico.org> > Subject: Re: [address-policy-wg] 2012-10 New Policy Proposal > (Extension of IPv6 /32 to /29 on a per-allocation vs per-LIR basis) > To: address-policy-wg(a)ripe.net > Message-ID: <20130103074727.GA4475@taupo> > Content-Type: text/plain; charset=iso-8859-1 > > Hello, > > Le 31 d?c. ? 11:12, Emilio Madaio a ?crit : > > A proposed change to RIPE Document ripe-552, "IPv6 Address Allocation > > and Assignment Policy", is now available for discussion. > > I support this proposal. > > Julien > > > > ------------------------------ > > Message: 5 > Date: Thu, 3 Jan 2013 07:37:52 +0000 > From: Sonderegger Olaf ABRAXAS INFORMATIK AG > <Olaf.Sonderegger(a)abraxas.ch> > Subject: Re: [address-policy-wg] 2012-10 New Policy Proposal > (Extension of IPv6 /32 to /29) > To: "address-policy-wg(a)ripe.net" <address-policy-wg(a)ripe.net> > Message-ID: > <7C49C19C69319E4FB1279CA15A84D18B61D6E929(a)SAX10244.bia.abraxas.ch> > Content-Type: text/plain; charset="iso-8859-1" > > Dear all > > First: I wish everyone a good start in 2013. > > Second: I support Emilio's proposal. > > Best regards, Olaf > > -- > Olaf Sonderegger > Dipl. Ingenieur FH > IT Architekt > Shared Services Operations > > Abraxas Informatik AG > > Waltersbachstrasse 5 | CH-8006 Z?rich > Direkt +41 58 660 44 94 | Mobile +41 79 708 70 86 | Fax +41 58 660 00 09 > olaf.sonderegger(a)abraxas.ch | www.abraxas.ch > >

1 0

Re: [address-policy-wg] 2012-10 New Policy Proposal (Extension of IPv6 /32 to /29)
by Sonderegger Olaf ABRAXAS INFORMATIK AG 03 Jan '13

03 Jan '13

Dear all First: I wish everyone a good start in 2013. Second: I support Emilio's proposal. Best regards, Olaf -- Olaf Sonderegger Dipl. Ingenieur FH IT Architekt Shared Services Operations Abraxas Informatik AG Waltersbachstrasse 5 | CH-8006 Zürich Direkt +41 58 660 44 94 | Mobile +41 79 708 70 86 | Fax +41 58 660 00 09 olaf.sonderegger(a)abraxas.ch | www.abraxas.ch

1 0

FW: 2012-10 New Policy Proposal (Extension of IPv6/32 to /29 on a per-allocation vs per-LIR basis)
by Sleigh, Robert 03 Jan '13

03 Jan '13

I support this proposal, +1 Regards Bob 07958 318592 Life's for sharing... and what I like to share the most is a smile -----Original Message----- From: address-policy-wg-bounces(a)ripe.net [mailto:address-policy-wg-bounces@ripe.net] On Behalf Of Emilio Madaio Sent: 31 December 2012 10:13 To: policy-announce(a)ripe.net Cc: address-policy-wg(a)ripe.net Subject: [address-policy-wg] 2012-10 New Policy Proposal (Extension of IPv6/32 to /29 on a per-allocation vs per-LIR basis) Dear Colleagues, A proposed change to RIPE Document ripe-552, "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/2012-10 We encourage you to review this proposal and send your comments to <address-policy-wg(a)ripe.net> before 28 January 2013. Regards Emilio Madaio Policy Development Officer RIPE NCC NOTICE AND DISCLAIMER This e-mail (including any attachments) is intended for the above-named person(s). If you are not the intended recipient, notify the sender immediately, delete this email from your system and do not disclose or use for any purpose. We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you. Everything Everywhere Limited Registered in England and Wales Company Registered Number: 02382161 Registered Office Address: Hatfield Business Park, Hatfield, Hertfordshire, AL10 9BW

1 0