Hi Tom and Jasdip,
here in the following a first feedback on this draft:
1) It looks inconsistent to me that the draft is titled "RDAP RIR
Search" but in the rest of the document the term "INR registries" is
used instead.
However, I agree that "INR searches" is the right term to identify
collectively autnums and ips-related searches because RIRs can implement
the entity search too.
Therefore, IMO it would be better to use RIR instead of INR in both the
abstract and the introduction (excluding the sentence " ... with the
existing INR Whois services ..") and
change the following sentence
No searches were defined for IP networks or autonomous system numbers.
into (or something similar)
No searches were defined for Internet Number Resources (INRs), namely IP
networks and autonomous system numbers.
As a result, think you can also consider to generally use INR whenever
you refer to "IP network and autonomous system number".
2) Since the partial matching is used in the examples, I would add text
referencing Section 4.1 of RFC9082.
3) Would add a reference to the sections of RFC9083 when talikng about
the attributes for IP networks and Autonomous System numbers.
The right place in my opinion is the definitions of new path segments in
Section 2, here in the following an example:
'ips': Used to identify an IP network search using a pattern to
match one of the "ip network" object class properties as defined in
Section 5.4 of [RFC9083].
4) In section 4, you state when up/down links must not be included in
the response but it's not clear to me if they may/should/must be
included in the other cases.
The sentences ".. an operator includes.." should be changed to clarify it.
5) Looks also inconsistent to me the href value
"http://rdap.example.com/ip-down/192.0.2.0/25"; because ip-down is an
undefined RDAP segment path.
6) Sorry but I don't cacth why this document can't specify the structure
of the links. Most probably I misunderstood that sentence. Isn't the
structure of the link object in RDAP defined in section 4.2 of RFC9083 ?
7) "Link Relations" is the registry group, the registry name is "Link
Relation Types".
Best,
Mario
Il 06/03/2023 02:21, internet-dra...@ietf.org ha scritto:
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This Internet-Draft is a work item of the Registration Protocols Extensions WG
of the IETF.
Title : RDAP RIR Search
Authors : Tom Harrison
Jasdip Singh
Filename : draft-ietf-regext-rdap-rir-search-01.txt
Pages : 11
Date : 2023-03-05
Abstract:
The Registration Data Access Protocol (RDAP) is used by Internet
Number Resource (INR) registries and domain name registries to
provide access to their resource registration information. The core
specifications for RDAP define basic search functionality, but there
are various IP and ASN-related search options provided by INR
registries via their Whois services for which there is no
corresponding RDAP functionality. This document extends RDAP to
support those search options.
The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-rir-search/
There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-regext-rdap-rir-search-01
A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-rdap-rir-search-01
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dott. Mario Loffredo
Technological Unit “Digital Innovation”
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web:http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
