Hi Jiankang, all,

Thank you for the follow-up and detailed replies. I trust that relevant changes 
will be made to the text.

I suggest that we proceed in steps here: I will wait for the new version that I 
will use for follow-up on any pending points from my side. Hope this is OK with 
you.

If you are using github, please share the link as it is more convenient to send 
you PRs, etc.

Cheers,
Med

De : Jiankang Yao <[email protected]>
Envoyé : vendredi 22 mai 2026 15:27
À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; 
draft-ietf-regext-ep <[email protected]>
Cc : regext <[email protected]>; JGould <[email protected]>
Objet : [regext] Re: AD Review of draft-ietf-regext-epp-quic





From: mohamed.boucadair<mailto:[email protected]>
Date: 2026-05-05 20:41
To: draft-ietf-regext-ep<mailto:[email protected]>
CC: [email protected]<mailto:[email protected]>
Subject: [regext] AD Review of draft-ietf-regext-epp-quic
>Hi Jiankang, Hongtao, Zhang, Dan, and James,
>


Hi Med,

Thanks a lot for your kind comments.

>Thank you for the effort put into this specification. FYI,
>this is even timely as we are planning to have a dedicated
>slot on such uses during IETF#126 OPSAREA Meeting (*).

>You may find my full review (including all comments, edits, nits) of the 
>document at:


·         pdf: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2026/draft-ietf-regext-epp-quic-06-rev%20Med.pdf

·         doc: 
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2026/draft-ietf-regext-epp-quic-06-rev%20Med.doc
>>
>

After discussing with James Gould,
the full response or reply is attached in doc.



>FWIW, please find below an extract of main comments:

># (generic) Not sure we have the adequate anchor in the charter
>for this work. Will discuss this further with the Chairs.

># Are there deployment plans for this transport feature?

Both VeriSign and CNNIC have tested it and implemented it. CNNIC will deploy 
this protocol in our next version of EPP registration system after the 
publication of this document. James Gould can introduce the situation of 
Verisign.


># Be factual

>CURRENT:
>   leverages the performance and security features of the QUIC protocol
>   as an EPP transport.


has addressed it in the attachment.

>## On performance

>### Things are more subtle than that. Please check, for example,
 >https://datatracker.ietf.org/meeting/118/materials/slides-118-maprg-sustained-throughput-performance-of-quic-implementations
>or https://ieeexplore.ieee.org/document/10060785.
>There are many studies out there about performance.

has addressed it in the attachment.

>### Do we have a comparative study under typical EPP deployment conditions to 
>benchmark the options out there?

has addressed it in the attachment.

>## On Security: This is mainly based on TLS. That’s not specific to QUIC.

has addressed it in the attachment.

># Consider including a brief text about the expected transport service
>(e.g., is this mainly about long-lived connection).

has addressed it in the attachment.


># Design approach
>
>The current design assumes that all commands are sent over the same stream.
> I wonder whether you considered a design
 >where a stream is consumed per command/response exchange (e.g., design 
 >approach used for DNS over QUIC).

We fully understand the DNS over QUIC (DoQ) per-command stream approach you 
mentioned, and
 we’d like to clarify why EPP over QUIC adopts a single-stream-per-session 
design instead of one
stream per command/response exchange, which is fundamentally determined by the 
inherent service
characteristics of EPP.

There is a core difference in business interaction logic between DNS and EPP 
protocols.
DNS is a stateless, independent query protocol. All DNS query/response 
transactions are completely
 isolated without any sequential dependency. It is fully safe and efficient for 
DoQ to use an independent stream for each query,
allowing out-of-order processing and parallel response of arbitrary requests, 
which perfectly matches DNS’s service model.

In contrast, EPP is a stateful, session-bound management protocol with strict 
command sequence constraints clearly defined
in the EPP base specifications (RFC 5730 series). EPP operations for domain and 
resource management are continuous and logically associated within a single 
session, and many commands have rigid sequential dependencies:
1. Session lifecycle commands follow a fixed order: login → series of 
management commands → logout,
which cannot be disrupted or out-of-order;
2. Core business commands are context-dependent: For example,
 a domain update/delete command must be executed after a successful domain 
check and retrieve command;
subordinate operational commands rely on the execution state of previous 
commands in the same session.

These stateful and sequential constraints are mandatory for EPP service 
consistency and data accuracy,
and they are not applicable to stateless DNS transactions at all.

The current design ensures full behavioral consistency with the standard EPP 
workflow,
avoids state confusion and command disorder risks caused by multi-stream 
parallelism,
and eliminates potential data inconsistency and service exceptions in domain 
resource management.
We have fully evaluated the DoQ per-transaction stream design during the draft 
design phase.
Considering EPP’s stateful session mechanism, and some mandatory command 
sequence specifications,
we finally confirmed that single-stream-per-session is the most reasonable,
specification-compliant and deployment-friendly design for EPP over QUIC.

>If that design was considered, can we please have a note about
>the rationale for preferring the current design vs. DoC approach?


How about the text below:
"
EPP sessions use a single QUIC stream for all command and response exchanges 
throughout the session lifecycle.
Unlike stateless transaction protocols that permit per-command independent 
streams,
EPP is a stateful protocol with inherent sequential command dependencies 
defined in RFC 5730.
Maintaining a single stream preserves ordered transaction processing, 
consistent session state,
and full compatibility with existing EPP operational and implementation models.
"

># MUST well-known port number

>CURRENT:
  > server MUST listen for QUIC connection requests on

>I know this is inherited from the TCP mapping spec, however, I don’t think 
>this is great from an operational
 >standpoint. I suggest to update to:

>NEW:
  > By default, an EPP server MUST
    >listen for QUIC connection requests on a well-known UDP port number 
assigned
   > by IANA (see Section 8.1), unless there is a mutual agreement to use 
another port number.

yes, thanks.
has addressed it in the attachment.

># Unconditional behaviors are problematic

>There are several such constricts in the document that need to be fixed. For 
>example:

>CURRENT:
>   Once the QUIC connection is established, the EPP client MUST then

>This assumes that the server has always to accept the connection!
>From an operational standpoint, a server may have a
 >policy to rate-limit connections. This MUST is thus to be revisited.

>For example, the part can be fixed as follows:

>OLD:
>  The server accepts the QUIC stream, reads the EoQ Connection

>NEW:
>  Absent processing errors or local policy, the server accepts the QUIC 
> stream, reads the EoQ Connection

yes, thanks.
has addressed it in the attachment.



># Lack of application-specific errors

>CURRENT:
  > A client MAY end an
   > EoQ session by closing the QUIC stream and the server MUST end the
   > EoQ session by closing the QUIC stream.

>This and other similar text makes it difficult at the remote side
> to diagnostic the error cause. I think that having specific error messages to 
> ease diagnostic would be helpful. See,
>for example, https://datatracker.ietf.org/doc/html/rfc9250#name-doq-error-codes



has addressed it in the attachment.



># Consider adding explicit behavior about error handling

>For example,

>CURRENT:
 >  Each EPP data unit MUST contain a single EPP message.  Commands MUST
   > be processed independently.

>I guess failing to adhere to this MUST will lead to connection closure.
> Please consider adding an explicit mention in
>the document. Also, how to signal the error to the peer?



has addressed it in the attachment.


># There are many SHOULDs that need to be checked for compliance
> with 
> https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/.

>My edited version includes fixes, but please double check through the document.


yes, thanks.
has addressed it in the attachment.


># Size and fragmentation

>CURRENT:
        0                   1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                           Total Length                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         EPP XML Instance                      |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+//-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>Please add a discussion under OPS Considerations Section about size/MTU and 
>fragmentation. You may refer to
>rfc9000#section-14.


yes, thanks.
has addressed it in the attachment.

># What about other ways to close a connection

>Do we need to negotiate idle timeout? See, for example, the use in 4.4 of 
>RFC9250.

># Missing Operational Considerations Section

will add it.
has addressed it in the attachment.



># Acknowledgements and RFC5734

>The text is inspired (and grabs) some portion from RFC5734.
>I suggest we add an explicit statement to the Acknowledgements Section to ACK 
>that.



yes, thanks.
has addressed it in the attachment.


>Let me know if any clarification is needed.
>


Thanks. It is very clear.


Best Regards
Jiankang Yao


>Cheers,
>Med

>(*) 
>https://github.com/IETF-OPS-AD/OPSAREA-meetings/blob/main/ietf126.md#foo-over-quic-operational-motivations--challenges-per-andersson-20-min

____________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.
_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to