<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloCorreo18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span class=EstiloCorreo18><span style='font-size:12.0pt'></span></span><span class=EstiloCorreo18><span lang=EN-US style='font-size:12.0pt'>Hi David,<o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Responding below, in-line.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 10/10/19 7:01, "address-policy-wg en nombre de David Farmer" <<a href="mailto:address-policy-wg-bounces@ripe.net">address-policy-wg-bounces@ripe.net</a> en nombre de <a href="mailto:farmer@umn.edu">farmer@umn.edu</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>On Tue, Oct 8, 2019 at 9:01 AM Sander Steffann <<a href="mailto:sander@steffann.nl" target="_blank">sander@steffann.nl</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal style='margin-left:35.4pt'>Hi,<br><br>> A new RIPE Policy proposal, 2019-06, "Multiple Editorial Changes in IPv6 Policy"<br>> is now available for discussion.<br>> <br>> This proposal aims to remove obsoleted text and simplify the IPv6 policy.<br><br>I think this is a sensible update. Support.<br><br>Cheers,<br>Sander<o:p></o:p></p></blockquote><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>I support the update, but have a question that I hope leads to a possible further clarification;<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>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. <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>My intent is to support both cases.<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>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. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'>Further, the definition of "End Site" doesn't really add much clarity to this question. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div></div></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><div><p class=MsoNormal style='margin-left:35.4pt'>2.9. End Site<o:p></o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>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:<o:p></o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>that service provider assigning address space to the End User<o:p></o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>that service provider providing transit service for the End User to other sites<o:p></o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>that service provider carrying the End User's traffic<o:p></o:p></p></div></div><div><div><p class=MsoNormal style='margin-left:35.4pt'>that service provider advertising an aggregate prefix route that contains the End User's assignment<o:p></o:p></p></div></div></blockquote><div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>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.<o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>My Reading of “</span><span lang=EN-US>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>If we believe that this is not correct, maybe we need to re-word that text as well?<o:p></o:p></span></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US><br clear=all><o:p></o:p></span></p><div><p class=MsoNormal style='margin-left:35.4pt'>Thanks.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>-- <o:p></o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>=============================================== <o:p></o:p></p></div></div></div></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
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.<br>
<br>
</body></html>