Ignore:
Timestamp:
15/09/10 12:53:21 (11 years ago)
Author:
julian.reschke@…
Message:

fix one typo in 5987 ref, plus the reference itself

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.xml

    r1008 r1009  
    414414  <reference anchor="RFC5987">
    415415        <front>
    416       <title abbrev="RFC2231 Encoding in HTTP">Applicability of RFC 2231
    417       Encoding to Hypertext Transfer Protocol (HTTP) Headers</title>
     416      <title>Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</title>
    418417      <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke">
    419418        <organization abbrev="greenbytes">greenbytes GmbH</organization>
     
    432431    <seriesInfo name="RFC" value="5987"/>
    433432  </reference>
    434 
    435433
    436434  <reference anchor="ISO-8859-1">
     
    691689<t>
    692690  Unfortunately, as of September 2010, neither the encoding defined in RFCs 2231
    693   and 5789, nor any of the alternate approaches discussed above was
     691  and 5987, nor any of the alternate approaches discussed above was
    694692  implemented interoperably. Thus, this specification recommends the approach
    695693  defined in RFC 5987, which at least has the advantage of actually being
Note: See TracChangeset for help on using the changeset viewer.