[tsvwg] Fwd: New Version Notification for draft-trammell-tsvwg-443-is-enough-00.txt

[Brian Trammell <[e-mail]>]

Greetings, all,

After some hallway discussion in Vienna, I’d like to bring this work to TSVWG for further discussion and development. This revision moves the draft into the -tsvwg namespace, and incorporates some changes from Christian’s comments (thanks again!)

I’d like to do this relatively quickly (ask for adoption at 127 or before, ask for WGLC shortly thereafter) as it’s a relatively simple proposition: augment 7605 to make it clearer when a port is warranted for applications over HTTP, and provide some commentary for application developers about why.

Cheers,

Brian

> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-trammell-tsvwg-443-is-enough-00.txt
> Date: 23 July 2026 at 18:24:19 GMT+2
> To: "Brian Trammell" <[e-mail]>
> 
> A new version of Internet-Draft draft-trammell-tsvwg-443-is-enough-00.txt has
> been successfully submitted by Brian Trammell and posted to the
> IETF repository.
> 
> Name:     draft-trammell-tsvwg-443-is-enough
> Revision: 00
> Title:    443 is Enough: Guidance on Port Allocation for HTTP-based Services
> Date:     2026-07-23
> Group:    Individual Submission
> Pages:    8
> URL:      https://www.ietf.org/archive/id/draft-trammell-tsvwg-443-is-enough-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-trammell-tsvwg-443-is-enough/
> HTML:     https://www.ietf.org/archive/id/draft-trammell-tsvwg-443-is-enough-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-trammell-tsvwg-443-is-enough
> 
> 
> Abstract:
> 
>   [RFC7605] provides guidance on the use of port numbers and the
>   criteria for new port assignments, including a test for whether a
>   proposed service is distinct from an existing service.  It gives the
>   example that "an automated system that happens to use HTTP framing --
>   but is not primarily accessed by a browser -- might be a new
>   service."  It also might not.  This document clarifies the
>   application of the distinct-protocol test in [RFC7605] Section 7.1 to
>   services built on HTTP as a substrate, in light of HTTP's evolution
>   since its publication, and provides guidance to applicants and
>   reviewers on when an HTTP-based service qualifies for a new port
>   assignment and when it does not.
> 
> 
> 
> The IETF Secretariat
> 
>