<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Apr 19, 2020, at 08:33 , Fernando Frediani <<a href="mailto:fhfrediani@gmail.com" class="">fhfrediani@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class="">
<div class="moz-cite-prefix">On 19/04/2020 05:07, Owen DeLong wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:2E7A4FD7-8E4D-42E2-9B20-0C56C73D2AF7@delong.com" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<br class="">
<div class="">Right… IETF designed a good architecture and then came under
pressure from a bunch of people with an IPv4 mindset and given
the modern state of the IETF decided to just punt on the whole
thing rather than waste more time on an argument where people
were determined to do what they were going to do anyway. RFC
6177 is more of a cop-out than a legitimate standards document.</div>
</blockquote>
We cannot just choose the RFCs we will follow from those we like and
disregard those which we don't. Imagine if vendors start to do the
same !<br class=""></div></div></blockquote><div><br class=""></div>The RFC you are holding out as gospel states that it is a BCOP, not a standards track document.</div><div><br class=""></div><div>It also supports /48s while admitting that other choices are available.</div><div><br class=""></div><div>Your characterization of my attitude is not correct, sir.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class="">Since it correctly (in my view) does putting that /48 for
residential customers should be treated as an exception therefore
no RIRs should have to adapt their policies to it. If ISPs assign
/48 to these customers in exceptional basis (not as default) then
they would have less or none of of the problems discussed here.<br class=""></p></div></div></blockquote><div><br class=""></div>It does NOT make /48s for residential customers an exception. Please show any language which does so. It states that longer than /48s are possible without structural harm to IPv6 itself. That’s as far as it goes.</div><div><br class=""></div><div>You’re also wrong about the nature of the problem being discussed.</div><div><br class=""></div><div>ISPs cannot under current policy obtain an allocation smaller than a /36. The policy language here would make /40s available (on an exceptional basis).</div><div><br class=""></div><div>As such, the concern is not to turn reduced price /40s into an incentive for bad addressing policy. You may think that the bad addressing policy I advocate avoiding is good address policy, but, that doesn’t change the nature of the initial problem in any way and is orthogonal to it.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class="">
</p><p class=""><clip></p>
<blockquote type="cite" cite="mid:2E7A4FD7-8E4D-42E2-9B20-0C56C73D2AF7@delong.com" class="">
<div class=""><br class="">
</div>
<div class="">There’s absolutely noting in RFC6177 that says /48s
should not be given out to residential customers. It punts it to
the operational community and says it really shouldn’t</div>
<div class="">be up to the IETF. That’s generally true, but that
does come with a responsibility that the operational community
doesn’t arbitrarily create negative impacts without good</div>
<div class="">reason.</div>
</blockquote>
One of the main points of the document, if not the most, is that /48
is no longer the default and not recommended as well. Therefore if
it still possible to assign to a residential customer it should then
be considered an exception not a normal thing as the others.<br class="">
Let me quote an important part of it within section 2: "<i class="">Hence, it
is strongly intended that even home sites be given multiple
subnets worth of space, by default. Hence, this document still
recommends giving home sites significantly more than a single /64,
but does not recommend that every home site be given a /48 either.</i>”</div></div></blockquote><div><br class=""></div>That’s _NOT_ what it says.</div><div><br class=""></div><div>It says that /48 no longer needs to be a one-size-fits-all default.</div><div><br class=""></div><div>It goes no further than that. It does not advocate for longer prefixes, it merely says that they could be acceptable or desirable in some cases and that the decision is left to the operational community and no longer a matter for the IETF.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><p class="">Furthermore at the time of the write of the document it also
mentions: "Since then, APNIC [APNIC-ENDSITE], ARIN [ARIN-ENDSITE],
and RIPE [RIPE-ENDSITE] have revised the end site assignment
policy to encourage the assignment of smaller (i.e., /56) blocks
to end sites.". Although some of these might have been retired in
their manuals it is possible to notice the spirit of the change
RFC6177 brings, and is still valid.</p></div></div></blockquote>ARIN has never had a policy that encouraged the assignment of smaller blocks to end sites. Currently ARIN most definitely has policy language that is intended to (admittedly subtly) encourage the assignment of /48s to end sites.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>