Keep context and protect the file
06The media-type registration adds fragments and charset guidance. A selected region does not make the rest of a CSV private or trustworthy.
Different clients can display selections differently. Confirm the table, coordinates and source; add integrity or confidentiality protection separately.
Source for this drawing: RFC 7111 · Read RFC section 5.1 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
Updates the text/csv registration with row, column and cell fragments plus charset/security considerations. It does not replace the CSV quoting rules or make fragments server-side filters.
Read the updated RFC section ↗RFC 7111 updates RFC 4180, including its text/csv registration: charset SHOULD be used; when absent, UTF-8 SHOULD be assumed. Other registered text charsets can be specified.
- RFC 7111 updates RFC 4180, including its text/csv registration: charset SHOULD be used; when absent, UTF-8 SHOULD be assumed. Other registered text charsets can be specified.
- The optional header parameter is present or absent; without it, implementers choose how to determine header presence. Fragment numbering still starts at row 1.
- CSV supplies no confidentiality or integrity protection. Fragment display differences can mislead users; protection must come from elsewhere. A fragment is not access control.
Also RFC 7111 §§1.3, 4.2, 6 and RFC 4180 §3. No later update or obsoletion is listed in the checked official metadata. The example table is fictional; highlighted regions are client-side selections, not server filtering.
Read the RFC section ↗