Thats a good question. Whois lookups CAN ask for superior covering blocks. Its in the protocol to do it (flags) in the port 43 query. I don't think its normal.
This is the problem with data services which push to the most specific record (and, in Whois, many exist) and inclusion of signing, which strongly depends on chain verification which automatically includes the parents as necessary components of the proof. One method you punch to the edge. The other, you get the path along with the edge. It's about making a decision. How do you guide what people do? (shepherd hat) I didn't mean to perturb a process in WGLC. I think this is worth discussing, I am unsure it has to be said in this draft, I don't object to people working it out if it makes sense. It is actually kind-of a side observation in the shepherd write-up as-is. -G On Thu, Feb 18, 2021 at 10:25 AM Randy Bush <[email protected]> wrote: > > > But if a lookup process was interested in finding a geofeed for an IP > > address within B, would it have any reason or automated means to > > backtrack and lookup knowledge of the signed geofeed for A? Do > > inetnum lookups return all superprefix inetnums as well? (asking for > > a friend) > > whoops! > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
