Opened 15 years ago
Closed 12 years ago
#75 closed editorial (incorporated)
RFC2145 Normative
Reported by: | mnot@… | Owned by: | fielding@… |
---|---|---|---|
Priority: | normal | Milestone: | 13 |
Component: | p1-messaging | Severity: | Active WG Document |
Keywords: | Cc: |
Description
Should RFC2145 references be normative?
Change History (6)
comment:1 Changed 15 years ago by mnot@…
- Component set to auth
- Milestone set to unassigned
comment:2 Changed 15 years ago by mnot@…
- Component changed from auth to non-specific
comment:3 Changed 15 years ago by fielding@…
- Owner set to fielding@…
- Status changed from new to assigned
- Type changed from design to editorial
comment:4 Changed 15 years ago by mnot@…
- Component changed from non-specific to p1-messaging
comment:5 Changed 12 years ago by fielding@…
From [1148]:
Move section on transport independence up so that it can describe what connections are before they are used in other explanations.
Try to explain both the philosophy and practice of HTTP versioning so that future protocol designers will understand what the numbers mean and why they are necessary. Incorporated all of the relevant versioning requirements from RFC2145 and added that RFC to the obsoleted list.
Addresses #75
comment:6 Changed 12 years ago by fielding@…
- Milestone changed from unassigned to 13
- Priority set to normal
- Resolution set to incorporated
- Severity set to Active WG Document
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
It can't be normative -- 2145 is an Informational RFC. IIRC, the text was supposed to be included in the 2616 revision.
We should check that the text on versions is included (editorial).