Ignore:
Timestamp:
30/12/12 09:01:09 (8 years ago)
Author:
fielding@…
Message:

(editorial) make security considerations intro specific to each document and xref to the main ones

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2066 r2069  
    2525  <!ENTITY header-date                "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2626  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2728  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2829  <!ENTITY header-accept-encoding     "<xref target='Part2' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    11451146<section title="Security Considerations" anchor="security.considerations">
    11461147<t>
    1147    No additional security considerations have been identified beyond
    1148    those applicable to HTTP in general &messaging;.
     1148   This section is meant to inform developers, information providers, and
     1149   users of known security concerns specific to the HTTP/1.1 conditional
     1150   request mechanisms. No additional security considerations have been
     1151   identified beyond those applicable to HTTP messaging &messaging; and
     1152   semantics &semantics;.
    11491153</t>
    11501154<t>
Note: See TracChangeset for help on using the changeset viewer.