Extensible Provisioning Protocol (EPP) Transport over QUIC
draft-yao-regext-epp-quic-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jiankang Yao , Hongtao Li , Zhang | ||
| Last updated | 2023-11-24 (Latest revision 2023-05-23) | ||
| Replaced by | draft-ietf-regext-epp-quic | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes how an Extensible Provisioning Protocol (EPP) session is mapped onto a UDP-Based Multiplexed and Secure Transport connection(QUIC). EPP over QUIC (EoQ) has privacy properties similar to EPP over TCP with TLS specified in RFC 5734. This mapping can protect information exchanged between an EPP client and an EPP server, and can reduce protocol-induced delays due to QUIC features.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)