Scott,
The timing of support for draft-ietf-regext-epp-eai should be up to server
policy and not based on a built-in constraint of the protocol itself. When
RDDS transitions from WHOIS to RDAP and natively supports UTF8, that is one
server policy factor. When SMTPUTF8 addresses can be used re
This report should be accepted. The example shown in Figure 33 is described as
an "elided example", which means that some response elements have been omitted.
However, the example in Figure 32 is also described as an elided example, and
it includes an rdapConformance data structure. The two exam
I'm inclined to reject this report. The example cited in Figure 28 is described
in the text as a "common response body", not a complete RDAP response. The
error response body is described in the context of a complete RDAP response in
Figure 29, which includes an rdapConformance data structure. A
On 6/12/24 10:37, Hollenbeck, Scott wrote:
*/If "mail system support for SMTPUTF8 addresses isn't ubiquitous"
isn't a given, then both use cases can be approached differently. If
it is a given, we have a requirement to continue to support exchange
of all-ASCII email addresses. An extension c
Arnt wrote:
Much later, if someone sends you mail, they may or may not be able to
accept your reply. Replying to email is however outside the scope of EPP.
There's an interop problem, but no single RFC and no single actor is
unambiguously at fault. And in consequence, no requirement in this
extens
From: Gould, James
Sent: Wednesday, June 12, 2024 8:41 AM
To: orie@transmute.industries; Hollenbeck, Scott
Cc: regext@ietf.org; regext-cha...@ietf.org
Subject: Re: [EXTERNAL] [regext] Re: draft-ietf-regext-epp-eai update
Orie,
The draft has implemented multiple approaches to address the fee
Hi all,
During his Document Shepherd review, Andy noticed a few issues that this
version of the draft addresses.
Please note the changes in the diff:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-regext-epp-ttl-13
Most of the changes are minor, but one does affect normative language, in
Internet-Draft draft-ietf-regext-epp-ttl-13.txt is now available. It is a work
item of the Registration Protocols Extensions (REGEXT) WG of the IETF.
Title: Extensible Provisioning Protocol (EPP) mapping for DNS Time-To-Live
(TTL) values
Author: Gavin Brown
Name:draft-ietf-regext-
The following errata report has been submitted for RFC9083,
"JSON Responses for the Registration Data Access Protocol (RDAP)".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7986
--
Type: Tech
The following errata report has been submitted for RFC9083,
"JSON Responses for the Registration Data Access Protocol (RDAP)".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7985
--
Type: Tech
Orie,
The draft has implemented multiple approaches to address the feedback from John
Klensin, related to the desire to have an all-ASCII email address. I include
the approaches below for summary. I believe the protocol should support either
an ASCII email address or an SMTPUTF9 email address
Hi,
All-ASCII addresses are sort of optional in EPP already…
If you want to use 名字@例子.中国 as a contact address, all you need to do is
open to your registrar's web site, register a domain and tick the checkbox
labelled something like "keep my email address private". The registrar will
provide a
12 matches
Mail list logo
