Skip to main content

Procedures for Handling Liaison Statements to and from the IETF
RFC 4053 also known as BCP 103

Revision differences

Document history

Date By Action
2023-12-12
(System) Imported membership of rfc4053 in bcp103 via sync to the rfc-index
2023-12-12
(System) No history of BCP103 is currently available in the datatracker before this point
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This document describes the procedure for proper handling of incoming liaison statements from other standards development …
Received changes through RFC Editor sync (changed abstract to 'This document describes the procedure for proper handling of incoming liaison statements from other standards development organizations (SDOs), consortia, and industry fora, and for generating liaison statements to be transmitted from IETF to other SDOs, consortia and industry fora. This procedure allows IETF to effectively collaborate with other organizations in the international standards community.

The IETF expects that liaison statements might come from a variety of organizations, and it may choose to respond to many of those. The IETF is only obligated to respond if there is an agreed liaison relationship, however. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.')
2005-06-06
Michael Lee State Changes to RFC Published from RFC Ed Queue by Michael Lee
2005-06-06
Michael Lee [Note]: 'See also draft-iab-liaison-mgt
RFC 4053 (2005-4-26)' added by Michael Lee
2005-04-26
(System) RFC published