Authenticated Middlebox Traversal with the Pickle Packet
draft-mccann-picklepacket-01

Document Type Expired Internet-Draft (individual)
Last updated 2010-12-07
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)

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-mccann-picklepacket-01.txt

Abstract

This document describes the Pickle Packet, a message that can be used to coordinate the opening of a transport connection with various middleboxes that may lie on the path. It contains the DNS names of both the initiator and the responder of the connection and some authentication data. Because the authentication data uses public key cryptography, any middlebox can independently authenticate the initiator and make a policy decision whether to allow or deny the flow based on the DNS names. The Pickle Packet allows for middleboxes to establish state such as firewall pinholes or security associations that can be used to filter out unwanted traffic.

Authors

Pete McCann (mccap@petoni.org)
Steve Gilbert (steve.gilbert@motorola.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)