+1. As I said in my original request:
"The authors believe it's in good shape given the feedback received to date and
it may be close to ready for working group last call if the working group
agrees with our descriptions of the documented practices and recommendations
for those that we
The REGEXT WG has placed draft-newton-regext-rdap-x-media-type in state
Candidate for WG Adoption (entered by Antoin Verschuren)
The document is available at
https://datatracker.ietf.org/doc/draft-newton-regext-rdap-x-media-type/
___
regext mailing
The REGEXT WG has placed draft-newton-regext-rdap-simple-contact in state
Candidate for WG Adoption (entered by Antoin Verschuren)
The document is available at
https://datatracker.ietf.org/doc/draft-newton-regext-rdap-simple-contact/
___
regext
The REGEXT WG has placed draft-newton-regext-rdap-extensions in state
Candidate for WG Adoption (entered by Antoin Verschuren)
The document is available at
https://datatracker.ietf.org/doc/draft-newton-regext-rdap-extensions/
___
regext mailing list
The REGEXT WG has placed draft-gould-regext-rdap-versioning in state
Candidate for WG Adoption (entered by Antoin Verschuren)
The document is available at
https://datatracker.ietf.org/doc/draft-gould-regext-rdap-versioning/
___
regext mailing list
As a reminder, the Chairs have suggested having an interim meeting as
described below. There were no objections to this suggestion and 4
expressions of support. However, the Chairs have found themselves
unable to find time to schedule this meeting.
Here is what we propose.
Next week, the
This is the formal adoption request for Best Practices for Deletion of Domain
and Host Objects in the Extensible Provisioning Protocol (EPP):
https://datatracker.ietf.org/doc/draft-hollenbeck-regext-epp-delete-bcp/
Please review this draft to see if you think it is suitable for adoption
The REGEXT WG has placed draft-hollenbeck-regext-epp-delete-bcp in state
Call For Adoption By WG Issued (entered by Antoin Verschuren)
The document is available at
https://datatracker.ietf.org/doc/draft-hollenbeck-regext-epp-delete-bcp/
___
regext
I'd very much prefer to stay with a literal reading of what's in RFC 9083:
"A response to a "help" request will include identifiers for all of the
specifications supported by the server. A response to any other request will
include only identifiers for the specifications used in the
Speaking as your Chairs:
Mario brings up an interesting question for which the Chairs need to hear some
other opinions.
On the one hand, there does seem to be some ambiguity regarding the proper use
of the rdapConformance array. If this is a concern, then the Chairs believe
that the WG needs
A new meeting session request has just been submitted by Antoin Verschuren, a
Chair of the REGEXT Working Group.
-
Working Group Name: Registration Protocols Extensions
Area Name: Applications and Real-Time Area
Session Requester: Antoin
I don't need presentation timer, but I would like to ask that my request for
working group adoption of "draft-hollenbeck-regext-epp-delete-bcp" be discussed
if it's not addressed before the meeting.
Scott
> -Original Message-
> From: regext On Behalf Of Antoin Verschuren
> Sent:
Hi Antoin and Jim,
I would like to present the following:
* draft-ietf-regext-epp-ttl (5 mins should be enough)
* draft-brown-rdap-ttl-extension (5 mins)
* draft-brown-epp-deleg[1] (5-10 mins)
I am happy to yield on the latter two if others need time for their
presentations. [1] is also being
Hi all,
This version updates the extension with Jim's feedback, so that the
min/default/max attributes on elements are only included in
responses if the client includes in the command.
I haven't received much feedback other than Jim's, so apart from fixing any
minor issues that may be
14 matches
Mail list logo
