Ignore:
Timestamp:
Jun 21, 2012, 2:01:49 AM (7 years ago)
Author:
julian.reschke@…
Message:

Clarify that in general recipients MUST be able to parse everything allowed by the ABNF (see #361)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r1667 r1682  
    182182</t>
    183183<t>
    184    Unless noted otherwise, Recipients &MAY; take steps to recover a usable
    185    protocol element from an invalid construct. However, HTTP does not define
     184   Unless noted otherwise, Recipients &MUST; be able to parse all protocol
     185   elements matching the ABNF rules defined for them and &MAY; take steps to
     186   recover a usable protocol element from an invalid construct. However, HTTP does not define
    186187   specific error handling mechanisms, except in cases where it has direct
    187188   impact on security. This is because different uses of the protocol require
     
    17171718      "ABNF list expansion code problem"
    17181719    </t>
     1720    <t>
     1721      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
     1722      "ABNF requirements for recipients"
     1723    </t>
    17191724  </list>
    17201725</t>
Note: See TracChangeset for help on using the changeset viewer.