Visual RFC.
ALL RFCs / RFC 7111
Read the RFC ↗
RFC 7111 / CSV FRAGMENT GUIDE

Extend an inclusive range

03

A hyphen joins the first and last selected positions. The asterisk means the actual last row or column.

RFC 7111 · § 2.2EXAMPLE
4 / 4
Extend an inclusive rangeA hyphen joins the first and last selected positions. The asterisk means the actual last row or column.#col=2-991datetemp.place201-011Galway301-02−1Galway401-030Galway501-016Berkeley601-028Berkeley701-035BerkeleyClip to existing columns 2 and 3MUST NOT invent columns beyond the tableRFC 7111 · 3.4 · fictional table / schematic selection
04
Limit an oversized range

Separate example: col=2-99 is clipped to columns 2 through 3. Column 99 is not invented.

Source for this drawing: RFC 7111 · Read RFC section 2.2 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
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.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

row=5-7 selects rows 5, 6 and 7; endpoints are included (§2.1).

  • row=5-7 selects rows 5, 6 and 7; endpoints are included (§2.1).
  • row=5-* reaches the last row. The same * notation applies to columns.
  • Ranges extending past the document MUST be limited to its actual size (§4.2); an absent single position MUST be ignored.
DETAILS

Also RFC 7111 §§2.1, 3, 4.2. The example table is fictional; highlighted regions are client-side selections, not server filtering.

Read the RFC section ↗

All chapters in RFC 7111

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗