Changeset 2259


Ignore:
Timestamp:
May 19, 2013, 1:07:18 PM (6 years ago)
Author:
fielding@…
Message:

(editorial) #476 : Remove odd sentence about SHOULD-level requirements that is inconsistent with RFC2119

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2258 r2259  
    950950      </p>
    951951      <p id="rfc.section.2.5.p.3">An implementation is considered conformant if it complies with all of the requirements associated with the roles it partakes
    952          in HTTP. Note that SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
     952         in HTTP.
    953953      </p>
    954954      <p id="rfc.section.2.5.p.4">Conformance applies to both the syntax and semantics of HTTP protocol elements. A sender <em class="bcp14">MUST NOT</em> generate protocol elements that convey a meaning that is known by that sender to be false. A sender <em class="bcp14">MUST NOT</em> generate protocol elements that do not match the grammar defined by the ABNF rules for those protocol elements that are applicable
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2258 r2259  
    619619<t>
    620620   An implementation is considered conformant if it complies with all of the
    621    requirements associated with the roles it partakes in HTTP. Note that
    622    SHOULD-level requirements are relevant here, unless one of the documented
    623    exceptions is applicable.
     621   requirements associated with the roles it partakes in HTTP.
    624622</t>
    625623<t>
Note: See TracChangeset for help on using the changeset viewer.