[regext] REGEXT Interim Meeting

[Roger D Carney]

Good Afternoon,

We held an interim meeting on October 11th, 2017 to discuss the current Fee and 
Validate draft documents.

In attendance was Jody Kolker, Antoin Verschuren, James Galvin, and Roger 
Carney. Alex Mayrhofer sent his regrets.

Agenda:

  1.  Fee
 *   Confirm Edits (section 3.8 and section 4.0)
 *   Discuss WG Last Call
  2.  Validate
 *   A validate/verification framework discussion
 *   Validate group processing of contacts

With the limited number of participants the only topic we briefly discussed was 
the Fee document and that we have a few more minor edits (coming from 
implementation findings) for a revision 9 and that revision should be ready for 
last call. This next revision will be publish prior to IETF-100.

Again, thanks to all that participated in this call, hopefully we can get more 
participation in future meetings.


Thanks
Roger



___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Re: [regext] Preparing for IETF 100

[Andrew Newton]

Mario,

Sorry for the later than usual response. My comments are inline.

On Wed, Oct 11, 2017 at 11:20 AM, Mario Loffredo
 wrote:
>
> - in RFC7480 (section "5.3")  it is written "If a server wishes to respond
> that it has an empty result set (that is, no data appropriately satisfying
> the query), it returns a 404  (Not Found) response code."
>According to this statement, it seems that search response arrays should
> have at least one element so for example the rule $domainSearchResult =
> "domainSearchResult" : [ $domain_oc * ] should be replaced by the rule
> $domainSearchResult = "domainSearchResult" : [ $domain_oc + ]
>
> - Is it possible to have RDAP responses without any value (at least
> "rdap_level_*" seems to be required) in the rdapConformance array? If no,
> the rule about rdapConformance should be $rdapConformance =
> "rdapConformance" : [ string + ]

These are good points, but I'm not sure I can answer them (they are
working group interpretations). But these issues do highlight why a
more formal syntax is a good thing.

>
> - Handle seems to be required for an entity. If so, the handle defintion in
> common_mixin should be overrided by an identical definition without  '?' in
> entity_mixin. The same occurs if rdapConformance is required for all the
> reponses except the error response.

I think you are correct here.

-andy

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

[regext] FW: I-D Action: draft-hollenbeck-regext-rdap-object-tag-05.txt

[Hollenbeck, Scott]

> -Original Message-
> From: I-D-Announce [mailto:i-d-announce-boun...@ietf.org] On Behalf Of
> internet-dra...@ietf.org
> Sent: Tuesday, October 24, 2017 9:02 AM
> To: i-d-annou...@ietf.org
> Subject: [EXTERNAL] I-D Action: draft-hollenbeck-regext-rdap-object-tag-
> 05.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
> Title   : Registration Data Access Protocol (RDAP) Object
> Tagging
> Authors : Scott Hollenbeck
>   Andrew Lee Newton
>   Filename: draft-hollenbeck-regext-rdap-object-tag-05.txt
>   Pages   : 12
>   Date: 2017-10-24
>
> Abstract:
>The Registration Data Access Protocol (RDAP) includes a method that
>can be used to identify the authoritative server for processing
>domain name, IP address, and autonomous system number queries.  The
>method does not describe how to identify the authoritative server for
>processing other RDAP query types, such as entity queries.  This
>limitation exists because the identifiers associated with these query
>types are typically unstructured.  This document describes an
>operational practice that can be used to add structure to RDAP
>identifiers that makes it possible to identify the authoritative
>server for additional RDAP queries.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-object-tag/

With thanks to Tom Harwood, this version includes a description of the 
implementation work done by OpenRDAP, https://www.openrdap.org.

Scott

___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext