From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198055] New: Missing mechanism to find maximum datagram sizes (mandated by RFC 1122)
Date: Fri, 1 Dec 2017 10:07:03 -0800 [thread overview]
Message-ID: <20171201100703.36319d5f@xeon-e3> (raw)
Begin forwarded message:
Date: Fri, 01 Dec 2017 15:54:14 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198055] New: Missing mechanism to find maximum datagram sizes (mandated by RFC 1122)
https://bugzilla.kernel.org/show_bug.cgi?id=198055
Bug ID: 198055
Summary: Missing mechanism to find maximum datagram sizes
(mandated by RFC 1122)
Product: Networking
Version: 2.5
Kernel Version: 4.13.15-300.fc27.x86_64
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: kwyut@byom.de
Regression: No
It's currently impossible to reliably implement an application layer protocol
with UDP sockets in Linux. Applications can retrieve the PMTU from IP_RECVERR
control messages but are unable to account for the variable size of IP and UDP
headers beyond hard-coding a large enough guess.
Relevant section of RFC 1122
4.1.4 UDP/APPLICATION LAYER INTERFACE
The application interface to UDP MUST provide the full services
of the IP/transport interface described in Section 3.4 of this
document. Thus, an application using UDP needs the functions
of the GET_SRCADDR(), GET_MAXSIZES(), ADVISE_DELIVPROB(), and
RECV_ICMP() calls described in Section 3.4. For example,
GET_MAXSIZES() can be used to learn the effective maximum UDP
maximum datagram size for a particular {interface,remote
host,TOS} triplet.
In particular, GET_MAXSIZES() appears to be missing.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-12-01 18:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171201100703.36319d5f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).