> I'm lost as to why you don't just do the appropriate IANA action to > register "geofeed". Well, okay I looked it up, and maybe it's a > challenge. > > RFC2622 section 10.2 says: > New attributes can be added to any class. To ensure full > compatibility, new attributes should not contradict the semantics of > the objects they are attached to. Any tool that uses the IRR should > be designed so that it ignores attributes that it doesn't understand. > Most existing tools adhere to this design principle. > > And neither RFC2622 nor RFC4012 have an IANA Considerations. > > I'm not sure what this means in the end, but it seems that your > document can just define geofeed: and Update RFC2622. Maybe some AD > will want you to create a registry, but cross that bridge when you get > to it. > > Maybe Warren will comment. > > The Remark: hack reminds me of COBOL or JCL, and I gotta wonder if > it's necessary. Are the ARIN and/or RIPE and... databases really so > ossified that you need this hack?
welcome to the realities of network operations, five registries who have social issues, an ietf rps wg that was moribund, ... if you really care, i perhaps someone with more social skills than i can explain it all to meet your interest. but trust me, the remarks: finesse is needed, and the doc and massimo's hack [geofeed-finder], are set to handle a transition should it happen. randy _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
