A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1068 ====================================================================== Reported By: dannyniu Assigned To: ====================================================================== Project: 1003.1(2013)/Issue7+TC1 Issue ID: 1068 Category: Base Definitions and Headers Type: Omission Severity: Objection Priority: normal Status: Resolved Name: DannyNiu/NJF Organization: User Reference: Section: Base Definition, Headers <netinet/in.h> Page Number: 307 Line Number: 10260 Interp Status: --- Final Accepted Text: https://austingroupbugs.net/view.php?id=1068#c5902 Resolution: Accepted As Marked Fixed in Version: ====================================================================== Date Submitted: 2016-08-22 03:14 UTC Last Modified: 2022-07-22 08:21 UTC ====================================================================== Summary: Binding to a system-assigned port. ======================================================================
---------------------------------------------------------------------- (0005906) kre (reporter) - 2022-07-22 08:21 https://austingroupbugs.net/view.php?id=1068#c5906 ---------------------------------------------------------------------- Re https://austingroupbugs.net/view.php?id=1068#c5904 What Geoff said in https://austingroupbugs.net/view.php?id=1068#c5905, plus, the IETF does not write standards for OS interfaces to the protocols they design, that's someone else's business, like ours for POSIX. When the IETF decides to define some use for port number 0, in either UDP or TCP, beyond what is defined now, and that is for some use which a normal (as opposed to special system dependent) application might want to use, we can apply for special dispensation to the purple unicorn emperor of the soviet states of america to permit us to add a new option which will allow applications to actually bind to port 0. In the meantime, what this is adding is what systems actually implement, which is what the standard is supposed to say. Issue History Date Modified Username Field Change ====================================================================== 2016-08-22 03:14 dannyniu New Issue 2016-08-22 03:14 dannyniu Name => DannyNiu/NJF 2016-08-22 03:14 dannyniu Section => Base Definition, Headers <netinet/in.h> 2016-08-22 03:14 dannyniu Page Number => 307 2016-08-22 03:14 dannyniu Line Number => 10260 2016-08-22 16:45 shware_systems Note Added: 0003354 2017-02-19 05:28 dannyniu Note Added: 0003561 2017-02-19 16:18 shware_systems Note Added: 0003562 2022-07-21 15:36 geoffclare Note Added: 0005902 2022-07-21 15:37 geoffclare Interp Status => --- 2022-07-21 15:37 geoffclare Final Accepted Text => https://austingroupbugs.net/view.php?id=1068#c5902 2022-07-21 15:37 geoffclare Status New => Resolved 2022-07-21 15:37 geoffclare Resolution Open => Accepted As Marked 2022-07-21 15:37 geoffclare Tag Attached: issue8 2022-07-21 16:37 shware_systems Note Added: 0005904 2022-07-21 16:43 geoffclare Note Added: 0005905 2022-07-22 08:21 kre Note Added: 0005906 ======================================================================