Changes between Version 15 and Version 17 of Ticket #502
- Timestamp:
- 04/11/13 23:31:09 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #502 – Description
v15 v17 38 38 ---- 39 39 40 In Section 6.1: 40 ~~In Section 6.1:~~ 41 41 42 "Recipients that trigger certain connection behavior based on the presence of connection options MUST do so based on the presence of the connection-option rather than only the presence of the optional header field. In other words, if the connection option is received as a header field but not indicated within the Connection field-value, then the recipient MUST ignore the connection-specific header field because it has likely been forwarded by an intermediary that is only partially conformant. 42 ~~ "Recipients that trigger certain connection behavior based on the presence of connection options MUST do so based on the presence of the connection-option rather than only the presence of the optional header field. In other words, if the connection option is received as a header field but not indicated within the Connection field-value, then the recipient MUST ignore the connection-specific header field because it has likely been forwarded by an intermediary that is only partially conformant.~~ 43 43 44 I am flagging the usage of a requirement followed by the "must ignore" requirement as an issue as the "in other words" suggest that it is a clarification of the first requirement. 44 ~~I am flagging the usage of a requirement followed by the "must ignore" requirement as an issue as the "in other words" suggest that it is a clarification of the first requirement.~~ 45 45 46 46 ----