Ignore:
Timestamp:
Dec 30, 2012, 1:01:09 AM (7 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/p7-auth.xml

    r2066 r2069  
    1717  <!ENTITY mdash "&#8212;">
    1818  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
     19  <!ENTITY messaging                    "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     20  <!ENTITY semantics                    "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1921  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2022  <!ENTITY conformance                  "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    677679<section title="Security Considerations" anchor="security.considerations">
    678680<t>
    679    This section is meant to inform application developers, information
    680    providers, and users of the security limitations in HTTP/1.1 as
    681    described by this document. The discussion does not include
    682    definitive solutions to the problems revealed, though it does make
    683    some suggestions for reducing security risks.
     681   This section is meant to inform developers, information providers, and
     682   users of known security concerns specific to HTTP/1.1 authentication.
     683   More general security considerations are addressed in HTTP messaging
     684   &messaging; and semantics &semantics;.
    684685</t>
    685686
Note: See TracChangeset for help on using the changeset viewer.