Using DNS Names in the IETF ACL Model
draft-lear-ietf-netmod-acl-dnsname-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eliot Lear | ||
| Last updated | 2016-08-04 (Latest revision 2016-01-19) | ||
| Replaced by | draft-lear-ietf-netmod-mud | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-lear-ietf-netmod-mud | |
| 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 points are commonly referenced by higher level functions through the DNS. This is especially the case in cloud-based functions, which might have hundreds of IP addresses for the same name. This brief memo extends the IETF-ACL model to allow access-control via domain names.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)