Procedures for Handling Liaison Statements to and from the IETF
RFC 4053, “Procedures for Handling Liaison Statements to and from the IETF”, is a Best Current Practice document published in April 2005 by S. Trowbridge, S. Bradner, F. Baker. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 4053 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4052 IAB Processes for Management of IETF Liaison Relationships
- RFC 4054 Impairments and Other Constraints on Optical Layer Routing
- RFC 4051 Additional XML Security Uniform Resource Identifiers
- RFC 4055 Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List Profile
- RFC 4050 Using the Elliptic Curve Signature Algorithm for XML Digital Signatures
- RFC 4056 Use of the RSASSA-PSS Signature Algorithm in Cryptographic Message Syntax
- RFC 4049 BinaryTime: An Alternate Format for Representing Date and Time in ASN.1
- RFC 4057 IPv6 Enterprise Network Scenarios