Guidelines for Multiprotocol Traffic Selector Bindings in IPsec
draft-daley-mpsec-traffic-sel-ps-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2009-10-25 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-daley-mpsec-traffic-sel-ps-01.txt
Abstract
In IPsec, secure connectivity is provided for network layer entities. Traffic Selectors which specify interesting traffic for security association encapsulation are identified only by network and transport layer addressing. This document discusses extending traffic selectors to allow more generic definitions of interesting traffic.
Authors
Greg Daley
(gdaley@netstarnetworks.com)
Simon DeLord
(simon.a.delord@team.telstra.com)
Raymond Key
(raymond.key@team.telstra.com)
Suresh Krishnan
(suresh.krishnan@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)