John, Thanks.
My intention was to make 6.5.5.4 not be any less required or give the impression that it is any more optional than 6.5.5.1. It sounds like enforcement of 6.5.5.4 "shall" could reasonably match 6.5.5.1 shall. Talking off line I get the impression that some people thought the intent was that a single complaint of a downstream customer could trigger consequences (i.e. potential revocation of the IPv6 number resources.) That is not my intention. My intention is that a single violation of 6.5.5.4 makes the ISP just as much out of compliance with number resource policy as a single violation of 6.5.5.1. I support shall. Anyone else support shall for both.5.5.4 and 6.5.5.1? Oppose shall for 6.5.5.4 but support it for 6.5.5.1? Oppose shall for both 6.5.5.4 and 6.5.5.1? Either is fine? Don't really care? Support shall for both: 2 Oppose shall for 6.5.5.4 but support it for 6.5.5.1: 0 Oppose shall for both: 0 Either: 0 don't care: 0 (I count 7 unique posters in this thread, and another 27 across other posts on this policy... Of course a bunch of that is concerned with residential privacy and DNS) ___Jason On Thu, Sep 28, 2017 at 1:16 AM, james machado <[email protected]> wrote: > I oppose as written. > > I support Jason's language of replacing "should" with "shall" in 6.5.5.4. > > James > > > > _______________________________________________ > PPML > You are receiving this message because you are subscribed to > the ARIN Public Policy Mailing List ([email protected]). > Unsubscribe or manage your mailing list subscription at: > http://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. > -- _______________________________________________________ Jason Schiller|NetOps|[email protected]|571-266-0006
_______________________________________________ PPML You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List ([email protected]). Unsubscribe or manage your mailing list subscription at: http://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
