Extensible Provisioning Protocol (EPP) Transport over QUIC
draft-ietf-regext-epp-quic-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-regext-epp-quic@ietf.org, gavin.brown@icann.org, mohamed.boucadair@orange.com, regext-chairs@ietf.org, regext@ietf.org, rfc-editor@rfc-editor.org, zalbanna@verisign.com
Subject: Protocol Action: 'Extensible Provisioning Protocol (EPP) Transport over QUIC' to Proposed Standard (draft-ietf-regext-epp-quic-12.txt)

The IESG has approved the following document:
- 'Extensible Provisioning Protocol (EPP) Transport over QUIC'
  (draft-ietf-regext-epp-quic-12.txt) as Proposed Standard

This document is the product of the Registration Protocols Extensions Working
Group.

The IESG contact persons are Mahesh Jethanandani and Mohamed Boucadair.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-regext-epp-quic/

Ballot Text

Technical Summary

   This document specifies how an Extensible Provisioning Protocol (EPP)
   session is mapped onto a QUIC connection.  EPP over QUIC (EoQ)
   leverages features of the QUIC protocol. The document specifies
   how it adheres to transport mapping considerations set in
   Section 2.1 of RFC5730.

Document Quality

    Existing implementation can be found in the Verisign EPP SDK 1.17.0.2.
    Both VeriSign and CNNIC indicated that they tested and implemented EoE.
    CNNIC indicated they will deploy EoQ in their next version of EPP
    registration system after the publication of this document.

Personnel

   The Document Shepherd for this document is Zaid AlBanna.
   The Responsible Area Director is Mohamed Boucadair.

RFC Editor Note