Opened 6 years ago

Closed 6 years ago

#464 closed editorial (incorporated)

placement of extension point considerations

Reported by: julian.reschke@… Owned by:
Priority: normal Milestone: 23
Component: non-specific Severity: In WG Last Call
Keywords: Cc:

Description

The HTTPbis documents are currently inconsistent with respect to the placement of sections discussing considerations for extension points (main document vs IANA considerations)

Change History (8)

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

From [2242]:

Move sections about new auth schemes registration, other considerations) into IANA section (see #464).

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

From [2243]:

Move Cache Directive Reg Procedure into IANA section (see #464).

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

From [2244]:

Move Warn Code Reg Procedure into IANA section (see #464).

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

From [2245]:

consistency in IANA considerations (see #464)

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

From [2246]:

Consistency in registration descriptions, also add required fields for status code registrations (related to #464).

comment:6 Changed 6 years ago by mnot@…

From [2283]:

Move considerations for new cache control extensions into IANA considerations; addresses #464.

comment:7 Changed 6 years ago by mnot@…

p6 done; can this be closed?

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

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