Ignore:
Timestamp:
Oct 23, 2011, 1:20:31 PM (8 years ago)
Author:
julian.reschke@…
Message:

Rephrase description of conformance; explain how the spec handles error handling (see #186)

File:
1 edited

Legend:

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

    r1450 r1452  
    300300</t>
    301301
    302 <section title="Requirements" anchor="intro.requirements">
     302<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
    303303<t>
    304304   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     
    307307</t>
    308308<t>
    309    An implementation is not compliant if it fails to satisfy one or more
    310    of the "MUST" or "REQUIRED" level requirements for the protocols it
    311    implements. An implementation that satisfies all the "MUST" or "REQUIRED"
    312    level and all the "SHOULD" level requirements for its protocols is said
    313    to be "unconditionally compliant"; one that satisfies all the "MUST"
    314    level requirements but not all the "SHOULD" level requirements for its
    315    protocols is said to be "conditionally compliant".
     309   This document defines conformance criteria for several roles in HTTP
     310   communication, including Senders, Recipients, Clients, Servers, User-Agents,
     311   Origin Servers, Intermediaries, Proxies and Gateways. See <xref target="architecture"/>
     312   for definitions of these terms.
     313</t>
     314<t>
     315   An implementation is considered conformant if it complies with all of the
     316   requirements associated with its role(s). Note that SHOULD-level requirements
     317   are relevant here, unless one of the documented exceptions is applicable.
     318</t>
     319<t>
     320   This document also uses ABNF to define valid protocol elements
     321   (<xref target="notation"/>). In addition to the prose requirements placed
     322   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
     323</t>
     324<t>
     325   Unless noted otherwise, Recipients &MAY; take steps to recover a usable
     326   protocol element from an invalid construct. However, HTTP does not define
     327   specific error handling mechanisms, except in cases where it has direct
     328   impact on security. This is because different uses of the protocol require
     329   different error handling strategies; for example, a Web browser may wish to
     330   transparently recover from a response where the Location header field
     331   doesn't parse according to the ABNF, whereby in a systems control protocol
     332   using HTTP, this type of error recovery could lead to dangerous consequences.
    316333</t>
    317334</section>
     
    58615878  <list style="symbols">
    58625879    <t>
     5880      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/186"/>:
     5881      "Document HTTP's error-handling philosophy"
     5882    </t>
     5883    <t>
    58635884      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/215"/>:
    58645885      "Explain header registration"
Note: See TracChangeset for help on using the changeset viewer.