I support the continued use of plain-text email, but that’s not mutually exclusive with using the GIT repo for development of new policies.
It’s quite trivial to take the resulting new policy or even just the change proposed and extract them from GIT into plain text. Owen > On Dec 14, 2021, at 11:43 , John Curran <[email protected]> wrote: > > ARIN can support whatever formats for number resource policy changes that the > community wishes, but it is worth keeping two things in mind: > > 1. Supporting multiple formats increases the expense/overhead of the policy > process, in that materials must be converted and made available in each > format whenever a revision occurs in the content > 2. Using solely text-based email makes participation in ARIN’s policy > development process very open and accessible, and this is not the case of > some other formats as they presume software or skills that may not be readily > available to all. > > That being said, the ARIN Consultation and Suggestion Process > <https://www.arin.net/participate/community/acsp/process/ > <https://www.arin.net/participate/community/acsp/process/>> is available for > this purpose if you’d like to propose that ARIN support a particular set of > formats for number policy discussions. > > Thanks! > /John > > John Curran > President and CEO > American Registry for Internet Numbers > > >> On 14 Dec 2021, at 2:16 PM, Owen DeLong via ARIN-PPML <[email protected] >> <mailto:[email protected]>> wrote: >> >> There is, in fact, an even better tool available for the NRPM changes… >> >> There is a Bitbucket GIT repo containing all historic versions of the NRPM >> and it would be easy to create a fork and edit for proposed language. >> >> Diffs are automatic and produce side-by-side redline comparisons that are >> easy to read and quite nice. >> >> Owen >> >> >>> On Dec 13, 2021, at 13:07 , Martin Hannigan <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> >>> On Mon, Dec 13, 2021 at 4:02 PM ARIN <[email protected] <mailto:[email protected]>> >>> wrote: >>> >>> >>> >>> [ clip ] >>> >>> AS Number outside of utilizing a unique routing policy, such as one >>> implemented using, for example, a protocol such as Boarder Gateway Protocol >>> (BGP). >>> >>> ^^^^^^ >>> >>> >>> Someone spelled BORDER wrong. >>> >>> >>> [ clip ] >>> >>> Is there a reason why these changes can’t be presented to us in .docx >>> change control format AKA redline? You do it with bylaws changes. >>> >>> Thanks >>> >>> -M< >>> >>> >>> _______________________________________________ >>> ARIN-PPML >>> You are receiving this message because you are subscribed to >>> the ARIN Public Policy Mailing List ([email protected] >>> <mailto:[email protected]>). >>> Unsubscribe or manage your mailing list subscription at: >>> https://lists.arin.net/mailman/listinfo/arin-ppml >>> <https://lists.arin.net/mailman/listinfo/arin-ppml> >>> Please contact [email protected] <mailto:[email protected]> if you experience any >>> issues. >> >> _______________________________________________ >> ARIN-PPML >> You are receiving this message because you are subscribed to >> the ARIN Public Policy Mailing List ([email protected] >> <mailto:[email protected]>). >> Unsubscribe or manage your mailing list subscription at: >> https://lists.arin.net/mailman/listinfo/arin-ppml >> <https://lists.arin.net/mailman/listinfo/arin-ppml> >> Please contact [email protected] if you experience any issues. >
_______________________________________________ ARIN-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: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
