Skip to content

Commit

Permalink
references
Browse files Browse the repository at this point in the history
  • Loading branch information
mirjak authored Feb 21, 2025
1 parent 0d96dd3 commit c4dd202
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions draft-kuehlewind-iab-rfc4053bis.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ Further the following guidance has been updated in the -00 version:
5. New section on "Recording Liaison Statements" that replaces Section 2.4. on "Lifetime of a Liaison Statement"
to underline how important the public record of a liaison statement is and clarify the responsibility of the receiver
to ensure that all incoming statements get appropriately recorded.
6. Section 4 from RFC4052 on "Approval and Transmission of Liaison Statements" has been moved to this document, without modification so far.
6. Section 4 from {{RFC4052}} on "Approval and Transmission of Liaison Statements" has been moved to this document, without modification so far.

# Content of Liaison Statements

Expand Down Expand Up @@ -515,14 +515,14 @@ This document has no IANA actions.
# Acknowledgments
{:numbered="false"}

RFC4053 was authored by Stephen Trowbridge, Scott Bradner, Fred Baker.
{{RFC4053}} was authored by Stephen Trowbridge, Scott Bradner, Fred Baker.
The text in RFC4053 further has been prompted by discussions with numerous individuals
within IETF and other SDOs and fora, including Gary Fishman and Bert
Wijnen. It has been developed in cooperation with {{RFC4052}}, which
is to say with the express cooperation of the chair of the IAB at that time,
Leslie Daigle.

This document contain parts of the text from RFC4053, however, all tooling
This document contain parts of the text from {{RFC4053}}, however, all tooling
details were removed and the remaining text will be reworked step by step with
the goal to end up with a shorter and clear document that outlines requirements
and gives high-level guidance to people sending and receiving liaison statements.
Expand Down

0 comments on commit c4dd202

Please sign in to comment.