Opened 15 years ago
Closed 14 years ago
#40 closed editorial (fixed)
Header registration
Reported by: | mnot@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | Milestone: | 04 | |
Component: | p1-messaging | Severity: | |
Keywords: | Cc: |
Description (last modified by mnot@…)
A revision of RFC2616 should mention BCP 90 (Registration Procedures for Message Header Fields) and should take over as the authoritative reference for the headers it contains.
Change History (13)
comment:1 Changed 15 years ago by mnot@…
- Description modified (diff)
comment:2 Changed 15 years ago by mnot@…
- Component set to messaging
- Milestone set to unassigned
comment:3 Changed 15 years ago by mnot@…
- version set to 00-draft
comment:4 Changed 15 years ago by fielding@…
- Milestone changed from unassigned to 02
comment:5 Changed 15 years ago by mnot@…
- Milestone changed from 02 to 03
comment:6 Changed 15 years ago by mnot@…
also hop-by-hop vs. end-to-end
comment:7 Changed 15 years ago by julian.reschke@…
Are you suggesting to augment the registration template? That would require updating BCP90, right?
comment:8 Changed 15 years ago by julian.reschke@…
comment:9 Changed 15 years ago by julian.reschke@…
comment:10 Changed 15 years ago by julian.reschke@…
- Milestone changed from 03 to 04
- Owner set to julian.reschke@…
comment:11 Changed 15 years ago by julian.reschke@…
comment:12 Changed 14 years ago by julian.reschke@…
- Milestone changed from 04 to unassigned
comment:13 Changed 14 years ago by mnot@…
- Milestone changed from unassigned to 04
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
When we do this, we should consider adding extra information to the template (Graham has done this for a lot of the Mail registrations IIRC).
E.g., header classification, whether it's a single value or a list, etc.
I'm happy to help with this if you like.