>> to maybe be a bit clearer, or at least say it a different way, you >> seemto have chosen a syntax ( from the 1990s :) but have not made the >> semantics clear enough that i can understand them. likely my fault, >> of course. > > That bit actually carried over from the current policy. Interestingly > (despite being from the 90s) i do not see 'rpsl' in the text before > RIPE-496 (2010); 496 was the first revision of a policy in an effort > "aimed at improving the clarity and readability" [1]. > > So... what do you propose... take RPSL out and replace with more words > describing what is inteded?
i can live with the syntax from the '90s; though it was over-designed for goals it almost never achieved, automating router configuration. but you "have not made the semantics clear enough that i can understand them." please describe the criteria or algorithm the regserv person is to apply to that blob of rpsl which produces the number of asns to be assigned. randy ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
