Secure Beacon: Securely Detecting a Trusted Network
draft-sheffer-ipsec-secure-beacon-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Yaron Sheffer , Yoav Nir | ||
| Last updated | 2008-01-21 (Latest revision 2007-11-11) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-sheffer-ipsec-secure-beacon-03.txt
https://www.ietf.org/archive/id/draft-sheffer-ipsec-secure-beacon-03.txt
Abstract
Remote access clients, in particular IPsec-based ones, are heavily deployed in enterprise environments. In many enterprises the security policy allows remote-access clients to switch to unprotected operation when entering the trusted network. This document specifies a method that lets a client detect this situation in a secure manner, with the help of a security gateway. We propose a minor extension to IKEv2 to achieve this goal.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)