Deep Dive into IPv6 Extension Header Testing: Behind a CDN
draft-elkins-v6ops-eh-deepdive-cdn-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nalini Elkins , michael ackermann , Dhruv Dhody | ||
| Last updated | 2023-08-24 (Latest revision 2023-02-20) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 proposes a methodology for isolating the location and reasons for IPv6 Extension Headers blockage in a network where the operator has access to install products and run diagnostic tests on both the client and server. The client will be outside the Content Delivery Network (CDN) and the server inside the CDN. This document will discuss the testing and topology which need to be considered when testing using a CDN infrastructure. This document is a part of the Deep Dive into EH Testing set of documents.
Authors
Nalini Elkins
michael ackermann
Dhruv Dhody
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)