Opened 6 years ago

Closed 6 years ago

#544 closed editorial (incorporated)

moving 2616/2068/2145 to historic

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 26
Component: p1-messaging Severity: In IESG Evaluation
Keywords: Cc:

Description (last modified by julian.reschke@…)

This HTTP/1.1 specification obsoletes and moves to historic status RFC 2616, its predecessor RFC 2068, and RFC 2145 (on HTTP versioning).

Please, no, it doesn't (and shouldn't) move any of these documents to Historic (even if it were capitalized correctly ;-) ). It obsoletes them. Please strike "and moves to historic status". (I'm happy to give you the long explanation of why moving to Historic is not the right thing if you like.)

Change History (3)

comment:1 Changed 6 years ago by julian.reschke@…

  • Description modified (diff)

comment:2 Changed 6 years ago by julian.reschke@…

From [2529]:

do not move 2068/2616/2145 to historic (see #544)

comment:3 Changed 6 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.