[tsvwg] Fwd: New Version Notification for draft-herbert-fast-06.txt

[Tom Herbert <[e-mail]>]

Hi,

This is a draft to define a common carrier for host to networking
signaling of transport path signals as RFC8558 calls them.

At IETF117, there were a number of proposals to do host network
signaling, and they are using various protocol mechanisms to
annotate packets with the signals. I think this indicates a growing
interest in finding a solution.

Signaling requires a carrier and content. This draft focuses on the
carrier and proposes a Hop-by-Hop option to be the common carrier of
per packet host to network signaling. The typical concern raised with
Hop-by-Hop options is that they are undeployable. The draft surveys
other proposed methods and suggests mitigations for issues with
Hop-by-Hop options. Despite the issues, the conclusion of this draft
is that Hop-by-Hop options is the best option for an extensible,
generic, transport stateless, and standardizable method for host to
network signaling compared to any of the known alternatives.

Comments are appreciated.

(version 5 was also posted to 6man list)

Thanks,
Tom

---------- Forwarded message ---------
From: <[e-mail]>
Date: Fri, Aug 4, 2023 at 11:52 AM
Subject: New Version Notification for draft-herbert-fast-06.txt
To: Tom Herbert <[e-mail]>



A new version of I-D, draft-herbert-fast-06.txt
has been successfully submitted by Tom Herbert and posted to the
IETF repository.

Name:           draft-herbert-fast
Revision:       06
Title:          Firewall and Service Tickets (FAST)
Document date:  2023-08-04
Group:          Individual Submission
Pages:          35
URL:            https://www.ietf.org/archive/id/draft-herbert-fast-06.txt
Status:         https://datatracker.ietf.org/doc/draft-herbert-fast/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-herbert-fast
Diff:           https://author-tools.ietf.org/iddiff?url2=draft-herbert-fast-06

Abstract:
   Firewall and Service Tickets is a generic and extensible protocol
   mechanism for hosts to send explicit signals to on-path elements to
   request network services on a per packet basis.  This is a type of
   "host to networks signaling", and the data of the signal is a
   "ticket" that accompanies a packet.  A ticket indicates the requested
   services or a grant of admission into a network; tickets are
   processed by network nodes to instantiate the requested services.
   Tickets are scoped to be relevant to their "origin domain" which is
   the network or limited domain in which they are issued.  Outside of
   their origin domain tickets are not processed and are forwarded as
   opaque data.  To prevent forgery and to obscure the services being
   requested, tickets are authenticated, encrypted, or otherwise
   obfuscated such that they can only be read by network nodes in their
   origin domain.  Tickets are sent in IPv6 Hop-by-Hop options.




The IETF Secretariat