Ignore:
Timestamp:
Aug 26, 2011, 7:08:10 AM (8 years ago)
Author:
julian.reschke@…
Message:

reduce verbosity in reference annotations

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1410 r1414  
    18681868    RFC 1950 is an Informational RFC, thus it might be less stable than
    18691869    this specification. On the other hand, this downward reference was
    1870     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1870    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    18711871    therefore it is unlikely to cause problems in practice. See also
    18721872    <xref target="BCP97"/>.
     
    18871887    RFC 1951 is an Informational RFC, thus it might be less stable than
    18881888    this specification. On the other hand, this downward reference was
    1889     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1889    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    18901890    therefore it is unlikely to cause problems in practice. See also
    18911891    <xref target="BCP97"/>.
     
    19181918    RFC 1952 is an Informational RFC, thus it might be less stable than
    19191919    this specification. On the other hand, this downward reference was
    1920     present since the publication of RFC 2068 in 1997 (<xref target="RFC2068"/>),
     1920    present since the publication of <xref target="RFC2068" x:fmt="none">RFC 2068</xref> in 1997,
    19211921    therefore it is unlikely to cause problems in practice. See also
    19221922    <xref target="BCP97"/>.
Note: See TracChangeset for help on using the changeset viewer.