On Nov 7, 2012, at 2:28 PM, "Murphy, Sandra" <[email protected]> wrote: > My concerns derive from the section PROHIBITED CONDUCT. > > That section says it forbids the relying party (the one retrieving RPKI data > from ARIN and validating wrt the ARIN trust anchor) from transferring, giving > access to, copying, broadcasting, etc., any "related content". > > I think that could impact the envisioned architecture and dominant use cases,
Sandy - Could you elaborate on this just a bit? i.e. which types of parties are expected to be subject to the relying party agreement would also need to share the obtained information with others? (others who would potentially be unaware of the RPA as well as the CP and CPS, in all likelihood...?) > It also forbids "derivative works". > > I think that could impact looking-glass-like or route-views-like public > services, the many different sites that are reporting status and route > validity, etc, so an impact on operational usability. This can be addressed directly, as it is not the intent of ARIN to interfere in any way with such reporting and summary services. Obviously, it is directly intended to prevent us from having parties relying on the published objects themselves who are not also aware of the various terms and conditions which apply. If you are running a reporting or status RPKI public service, feel free to ask me directly and I'll send you an official note that says "feel free to summarize our published data for such purposes." If we can find a way to increment the RPA to safely exclude such status & reporting uses in the future, we will do so. Thanks! /John John Curran President and CEO ARIN _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
