Best Current Practices for network services in an RCM context
draft-henry-madinas-bcp-network-rcm-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jerome Henry , Amelia Andersdotter | ||
| Last updated | 2023-10-15 (Latest revision 2023-04-13) | ||
| Replaces | draft-henry-bcp-for-madinas | ||
| 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
End devices are implementing Randomized and Changing MAC addresses (RCM), with the advertised goal of improving the user privacy, by making the continued association between a MAC address and a personal device more difficult. RCM may be disruptive to some network services. This document is a collection of best practices for the general implementation of network services within an RCM context.
Authors
Jerome Henry
Amelia Andersdotter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)