Changeset 641


Ignore:
Timestamp:
Jul 28, 2009, 2:31:52 AM (10 years ago)
Author:
julian.reschke@…
Message:

Editorial: make link into RFC2045 more specific

File:
1 edited

Legend:

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

    r640 r641  
    17861786</t>
    17871787<t>
    1788    Transfer-codings are analogous to the Content-Transfer-Encoding
    1789    values of MIME <xref target="RFC2045"/>, which were designed to enable safe transport of
    1790    binary data over a 7-bit transport service. However, safe transport
     1788   Transfer-codings are analogous to the Content-Transfer-Encoding values of
     1789   MIME, which were designed to enable safe transport of binary data over a
     1790   7-bit transport service (<xref target="RFC2045" x:fmt="," x:sec="6"/>).
     1791   However, safe transport
    17911792   has a different focus for an 8bit-clean transfer protocol. In HTTP,
    17921793   the only unsafe characteristic of message-bodies is the difficulty in
Note: See TracChangeset for help on using the changeset viewer.