Opened 10 years ago

Closed 9 years ago

Last modified 8 years ago

#254 closed design (fixed)

move RFCs 2145, 2616, 2817 to Historic status

Reported by: julian.reschke@… Owned by: julian.reschke@…
Priority: later Milestone: 16
Component: non-specific Severity: Active WG Document
Keywords: Cc:

Description (last modified by mnot@…)

See charter as well as IESG statement <​http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html>.

Attachments (1)

254.diff​ (1.7 KB) - added by julian.reschke@… 9 years ago.
proposed change for p1

Download all attachments as: .zip

Change History (11)

comment:1 Changed 9 years ago by mnot@…

  • Component changed from p2-semantics to non-specific
  • Description modified (diff)
  • Summary changed from move RFC 2817 to Historic status to move RFCs 2145, 2616, 2817 to Historic status

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

Should this include RFC 2068 then?

comment:3 Changed 9 years ago by mnot@…

  • Priority changed from normal to later

Yes.

comment:4 Changed 9 years ago by julian.reschke@…

Not sure about 2817; we take over pieces from it, but to move it to Historic we need more spec text (proposals, anyone?)

comment:5 Changed 9 years ago by julian.reschke@…

  • Owner set to julian.reschke@…

Changed 9 years ago by julian.reschke@…

proposed change for p1

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

From [1377]:

move 2068, 2145, 2616, 2817 to historic (see #254)

comment:7 Changed 9 years ago by julian.reschke@…

  • Milestone changed from unassigned to 16
  • Resolution set to incorporated
  • Status changed from new to closed

comment:8 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:9 Changed 9 years ago by mnot@…

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