secure anycast tunneling protocol (SATP)
draft-gsenger-secure-anycast-tunneling-protocol-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Othmar Gsenger | ||
| Last updated | 2008-05-06 | ||
| 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
The secure anycast tunneling protocol (SATP) defines a protocol used for communication between any combination of unicast and anycast tunnel endpoints. It allows tunneling of every ETHER TYPE protocol (ethernet, ip ...). SATP directly includes cryptography and message authentication based on the methods used by the Secure Real-time Transport Protocol(SRTP) [1]. It can be used as an encrypted alternative to IP Encapsulation within IP [3] and Generic Routing Encapsulation (GRE) [4]. Both anycast receivers and senders are supported.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)