Yes, Randy clearly understands this best, and I believe his proposal explains it well.
On Mon, May 17, 2021 at 5:43 PM George Michaelson <[email protected]> wrote: > I also think Randy's version is better because of two things: > > 1) it aligns with reality: fields are added to RPSL as a response of > operator driven demand. > > 2) it aligns with the least cost path out: the likelihood of a reprise > or -bis of RPSL completing in the short or medium term in either IETF > or RIPE is low, because it is subject to a huge debate about the > applicability of modern routing praxis like RPKI, and disagreements > inside the operations community. > > I checked with an IRR code developer, and adding fields "does no harm" > because they are used to recognizing an instance of an uknown > type:value form, and dealing with them (ignore) > > -G > > On Tue, May 18, 2021 at 5:48 AM Randy Bush <[email protected]> wrote: > > > > < rant > > > > > > "While the IETF published one of the specifying documents for RPS > > > [RFCXXXX], effective change control for RPSL today lies with the RIPE > > > community [ref]. However, it is in scope to use the Remarks: field..." > > > > i wish. ripe has the energy and the momentum. ripe does a lot of the > > docs. ripe has running code. and ripe is where this is moving forward > > in the sense of documentation and open code. otoh, most rirs are moving > > on hacking geofeed: attributes. massimo tracks far better than i. > > > > but the rirs are immature siblings who pretend to get along when > > grownups are watching, but fight dirty in the back seat of the car. do > > not judge their words; but their actions. arin does not even have a > > remarks: attribute, as you can see in the draft. > > > > and if you wonder if this is a disservice to the members, note that arin > > membership, last time i asked, represents less than 20% of the address > > holders in their region. > > > > so, ripe is indeed where it is happening. but saying that ripe has > > change control of the rpsl specification in the ietf sense is a dream. > > > > how about > > > > The original RPSL specifications starting with [RIPE81], [RIPE181], > > and a trail of subsequent documents were done by the RIPE community. > > The IETF standardardized RPSL in [RFC2622] and [RFC4012]. Since > > then, it has been modified and extensively enhanced in the RIR > > community, mostly by RIPE, [RIPE-DB]. Currently, change contol > > effectively lies in the operator community. > > > > randy >
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
