Hi Jasdip and Tom, I like this draft, but I do have a couple of questions.
1. This draft mentions the ip network object class but none of the other object classes. Are those not allowed by this extension? What happens if a server uses a geofeed link in a domain object? Should that be covered under a different extension? What if bigisp.com wants to allow other network operators to find their geofeeds just by looking up bigisp.com in RDAP? That seems like it might be a useful thing. If not, are clients to ignore processing the link if found any object other than an ip network?
2. Do the IPs in the geofeed file have to be in the IP boundaries of the ip network object class where the link is found? That doesn't look to be a requirement, but perhaps this should be explicitly stated.
3. What is a client to do if it finds the geofeed link in a response without a "geofeed1" extension? Is it suppose to treat the link as if the response had a "geofeed1" extension? The expectation of client processing should be more explicit in this allowable corner case.
-andy On 7/12/24 17:12, James Galvin wrote:
The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: An RDAP Extension for Geofeed Data https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/ Please indicate your support or no objection for the publication of this document by replying to this message on list (a simple “+1” is sufficient). If any working group member has questions regarding the publication of this document please respond on the list with your concerns by close of business everywhere, Friday, 2 August 2024. This WGLC has been extended to 3 weeks because of the IETF120 meeting. If there are no objections the document will be submitted to the IESG. The Document Shepherd for this document is Gavin Brown. Thanks, Antoin and Jim REGEXT WG Co-Chairs _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
