>>>> 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. >>> This part of the text is carried over in verbatim from the current >>> policy. >> then why do we need a new policy? > To make one change at a time (+the directly necessary things following > from that). In this case: Removal of the dual-homing requirement, > because it no longer reflects the operational realities of ASN use.
two changes: i suspect (though you have not actually specified) that i now need to publish rpsl revealing my relationships, and you propose to remove the requirement for multi-homing. how does the regserv person tell from the rpsl how many asns your [singly homed] router needs? one, two, 42? are there a bunch of aut-num:s? an as-set:? perhaps my confusion is exacerbated by your choosing to use a data description from the '90s, but want to obsolete RFC 1930. :) but whether a raspberry pi on decix can have 42 asns because it can be described in rpsl is not a hill i particulatly want to climb, let alone die on. my concern is that policies be simple, clear, understandable, and easily implemented by the operator and by the regserv folk. 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/
