This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Previous message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jamie Stallwood
Jamie.Stallwood at imerja.com
Wed May 5 17:08:49 CEST 2010
Hello, [de-lurk] Are split-location delegations any different / more evil than TE'd or distinct-routed subnets? I can't see where this is going. Kind regards Jamie Stallwood -- Jamie Stallwood Security Specialist Imerja Limited Tel: 07795 840385 jamie.stallwood at imerja.com -----Original Message----- From: address-policy-wg-admin at ripe.net on behalf of michael.dillon at bt.com Sent: Wed 5/5/2010 15:00 To: address-policy-wg at ripe.net Subject: RE: [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space > "Using addresses from a PI block to number other parties' devices is > permitted as long as these devices are connected to the > same network, > documentation about the usage can be presented to the RIPE NCC, and > full responsibility for the addresses (abuse handling etc) > is done by > the PI holder". Such a long explanation! Right now it says this: The PI assignment cannot be further assigned to other organisations. How about changing it like this: The PI assignment cannot be further assigned to other organisations unless their network infrastructure is wholly contained within the same building as the applicant for a PI assignment. If the word "wholly" seems to old-fashioned, replace it with "completely". Or you could say The PI assignment can be used for any devices connected to the network on the PI applicant's premises such as a data centre, regardless of who owns and controls those devices. --Michael Dillon -- Imerja Limited Tel: 0870 8611488 | Fax: 0870 8611489 | 24x7 ISOC: 0870 8611490 | Web: www.imerja.com Registered Office: Paragon House, Paragon Business Park, Chorley New Road, Horwich, Bolton BL6 6HG Registered in England and Wales No. 5180119 VAT Registered No. 845 0647 22 ISO Registered Firm No. GB2001527 This email is confidential and intended solely for the person or organisation to which it is addressed. It may contain privileged and confidential information. If you are not the intended recipient(s) you should not use, copy, distribute or take any action or reliance on it, since to do so is strictly prohibited and may be unlawful. If you have received this transmission in error please notify the sender immediately by email reply and delete it from your system. E-mail messages are not secure and attachments could contain software viruses which may damage your system. Whilst every reasonable precaution has been taken to minimise this risk, Imerja Limited cannot accept any liability for any damage sustained as a result of these factors. You are advised to carry out your own virus checks before opening any attachment. Any views or opinions expressed in this e-mail are solely those of the author and do not represent those of Imerja Limited unless otherwise stated. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/address-policy-wg/attachments/20100505/2fe5e76e/attachment.html>
- Previous message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
- Next message (by thread): [address-policy-wg] Discrepancy Between RIPE Policies on IPv4 and IPv6 Provider Independent (PI) Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]