[address-policy-wg] 2019-06 New Policy Proposal (Multiple Editorial Changes in IPv6 Policy)

Hi David,

 

Responding below, in-line.

 

 

Regards,

Jordi

@jordipalet

 

 

 

El 10/10/19 7:01, "address-policy-wg en nombre de David Farmer" <address-policy-wg-bounces at ripe.net en nombre de farmer at umn.edu> escribió:

 

 

On Tue, Oct 8, 2019 at 9:01 AM Sander Steffann <sander at steffann.nl> wrote:

Hi,

> A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 Policy"
> is now available for discussion.
> 
> This proposal aims to remove obsoleted text and simplify the IPv6 policy.

I think this is a sensible update. Support.

Cheers,
Sander

 

I support the update, but have a question that I hope leads to a possible further clarification;

 

In section 5.4.2 is an end site intended to be an end-user at a single physical location, or the entirety of an end-user organization, that may exist in many locations or on a large multi-building campus, and therefore might easily justify an assignment shorter than /48.  

 

My intent is to support both cases.

 

I agree it is difficult to imagine a single physical location needing more than a /48.  On the other hand, a large multi-site organization, say with hundreds of locations or hundreds of buildings on a single campus can easily need a prefix significantly shorter than /48. Further, it seems like a waste of resources to have RIPE or a NIR review shorter prefix assignments when made for multi-site organizations or large campuses. 

 

Exactly, the point is that LIR must be able to do that by themselves, and only have it reviewed in case they request a further allocation or there is an explicit audit.

 

Further, the definition of "End Site" doesn't really add much clarity to this question. 

 

2.9. End Site

 

An End Site is defined as an End User (subscriber) who has a business or legal relationship (same or associated entities) with a service provider that involves:

 

that service provider assigning address space to the End User

that service provider providing transit service for the End User to other sites

that service provider carrying the End User's traffic

that service provider advertising an aggregate prefix route that contains the End User's assignment

 

So, as currently written it seems a little ambiguous whether an end site is intended to refer to a single location or a single organization.

 

My Reading of “An End Site is defined as an End User (subscriber) who has a business or legal relationship”, is that it applies the same to a single end-site or an end-user having multiple end-sites.

 

If we believe that this is not correct, maybe we need to re-word that text as well?


Thanks.

 

-- 

===============================================
David Farmer               Email:farmer at umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota   
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=============================================== 



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20191010/e9f7a655/attachment.html>