Firewall and Service Tickets
draft-herbert-fast-03

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2019-03-25 (latest revision 2018-09-19)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-herbert-fast-03.txt

Abstract

This document describes the Firewalls and Service Tickets protocol. A ticket is data that accompanies a packet and indicates a granted right to traverse a network or a request for network service to be applied. Applications request tickets from a local agent in the network and attach issued tickets to packets. Firewall tickets are issued to grant packets the right to traverse a network; service tickets indicate the desired service to be applied to a packets. A single ticket may provide both firewall and service ticket information. Tickets are sent in IPv6 Hop-by-Hop options.

Authors

Tom Herbert (tom@quantonium.net)

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