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

Draw a rectangle of cells

04

A cell coordinate is row,column. A range names the upper-left cell and the lower-right cell of a rectangle.

RFC 7111 · § 2.3EXAMPLE
4 / 4
Draw a rectangle of cellsA cell coordinate is row,column. A range names the upper-left cell and the lower-right cell of a rectangle.EXAMPLE · 7 ROWS, 3 COLUMNS1datetemp.place201-011Galway301-02−1Galway401-030Galway501-016Berkeley601-028Berkeley701-035Berkeley#cell=6,2-4,1MUST ignore: inverse rectangleRFC 7111 · 4.4 · fictional table / schematic selection
04
Stop an inverse range

Separate example: cell=6,2-4,1 runs backwards. The client MUST ignore this selection; it must not swap endpoints.

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

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

cell=4,1 identifies the field 2011-01-03: row first, then column.

  • cell=4,1 identifies the field 2011-01-03: row first, then column.
  • cell=4,1-6,2 identifies the whole rectangle spanning rows 4 through 6 and columns 1 through 2.
  • Both row and column bounds matter. An inverse range MUST be ignored (§4.2); this is not a diagonal path or an unordered pair of cells.
DETAILS

Also RFC 7111 §§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 ↗