CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 date: Tue, 15 Jul 2025 11:31:17 GMT content-type: text/html; charset=UTF-8 content-encoding: gzip set-cookie: PHPSESSID=rvrher0i56ejlspnj9lh7kd993; path=/ expires: Thu, 19 Nov 1981 08:52:00 GMT cache-control: no-store, no-cache, must-revalidate pragma: no-cache vary: Accept-Encoding strict-transport-security: max-age=31536000; includeSubDomains x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff cf-cache-status: DYNAMIC server: cloudflare cf-ray: 95f8eebf4bfba9c3-BLR alt-svc: h3=":443"; ma=86400 RFC Errata Report » RFC Editor

RFC Errata

Errata Search
RFC Number:		Errata ID:

Source of RFC		Status:
Area Acronym:		Type:
WG Acronym:		Submitter Name:
Other:		Date Submitted:
Summary Table Full Records

RFC 6335, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry", August 2011

Source of RFC: tsvwg (wit)

Errata ID: 4999
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Nottingham
Date Reported: 2017-04-19
Held for Document Update by: Mirja Kühlewind
Date Held: 2020-03-04

Throughout the document, when it says:

Notes:

Many port number assignments are to individuals, but the document does not
contemplate how they should be handled when the assignee is dead or
otherwise can't be contacted.

The most obvious procedure to follow is a transfer (8.5), but that requires
de-assignment (8.2), and that doesn't cover the case above.

Report New Errata

Original Source | Taken Source

Search RFCs

RFC Editor

The Series

For Authors

Sponsor

RFC Errata

Errata Search

RFC 6335, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry", August 2011