#34 changes per @reschke comment 197ca56#r146538352

ietf-wg-httpapi · Sep 11, 2024 · aad383b · aad383b
1 parent 197ca56
commit aad383b
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/draft-ietf-httpapi-deprecation-header.md b/draft-ietf-httpapi-deprecation-header.md
@@ -73,9 +73,10 @@ The `Deprecation` HTTP response header field allows a server to communicate to a
 
 ## Syntax
 
-The `Deprecation` response header field describes the deprecation of the resource identified with the response it occurred within (see {{Section 6.4.2 of HTTP}}). It conveys the deprecation date, which may be in the future (the resource context will be deprecated at that date) or in the past (the resource context has been deprecated at that date). `Deprecation` is an Item Structured Header, refer to Section 3.3.7 of [STRUCTURED-FIELDS] for `sf-date`. 
+The `Deprecation` response header field describes the deprecation of the resource identified with the response it occurred within (see {{Section 6.4.2 of HTTP}}). It conveys the deprecation date, which may be in the future (the resource context will be deprecated at that date) or in the past (the resource context has been deprecated at that date).
+
+`Deprecation` is an Item Structured header field [STRUCTURED-FIELDS]. Its value MUST be a Date (Section 3.3.7 of [STRUCTURED-FIELDS]).
 
-    "Deprecation = sf-date"
 
 The following example shows that the resource context has been deprecated on Friday, June 30, 2023 at 23:59:59 UTC: