zilinlin/RFC2PSM huggingface dataset:
Section 1 Introduction

There are many applications of the Internet that require the creation
   and management of a session, where a session is considered an
   exchange of data between an association of participants.  The
   implementation of these applications is complicated by the practices
   of participants: users may move between endpoints, they may be
   addressable by multiple names, and they may communicate in several
   different media - sometimes simultaneously.  Numerous protocols have
   been authored that carry various forms of real-time multimedia
   session data such as voice, video, or text messages.  The Session
   Initiation Protocol (SIP) works in concert with these protocols by
   enabling Internet endpoints (called user agents) to discover one
   another and to agree on a characterization of a session they would
   like to share.  For locating prospective session participants, and
   for other functions, SIP enables the creation of an infrastructure of
   network hosts (called proxy servers) to which user agents can send
   registrations, invitations to sessions, and other requests.  SIP is
   an agile, general-purpose tool for creating, modifying, and
   terminating sessions that works independently of underlying transport
   protocols and without dependency on the type of session that is being
   established.
Section 29 Normative References

[1]  Handley, M. and V. Jacobson, "SDP: Session Description
   [2]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
   [4]  Rosenberg, J. and H. Schulzrinne, "SIP: Locating SIP Servers",
   [5]  Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
   [6]  Chown, P., "Advanced Encryption Standard (AES) Ciphersuites for
   [7]  Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC
        2279, January 1998.
   [8]  Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
        Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol --
   [9]  Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, April
        2000.
   [10] Crocker, D. and P. Overell, "Augmented BNF for Syntax
   [11] Freed, F. and N. Borenstein, "Multipurpose Internet Mail
        Extensions (MIME) Part Two: Media Types", RFC 2046, November
        1996.
   [12] Eastlake, D., Crocker, S. and J. Schiller, "Randomness
   [13] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
   [14] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August
        1980.
   [15] Postel, J., "DoD Standard Transmission Control Protocol", RFC
        761, January 1980.
   [16] Stewart, R., Xie, Q., Morneault, K., Sharp, C., Schwarzbauer,
        H., Taylor, T., Rytina, I., Kalla, M., Zhang, L. and V. Paxson,
   [17] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
        Leach, P., Luotonen, A. and L. Stewart, "HTTP authentication:
   [18] Troost, R., Dorner, S. and K. Moore, "Communicating Presentation
        Information in Internet Messages: The Content-Disposition Header
   [19] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, F.,
        Watson, M. and M. Zonoun, "MIME media types for ISUP and QSIG
   [20] Braden, R., "Requirements for Internet Hosts - Application and
   [21] Alvestrand, H., "IETF Policy on Character Sets and Languages",
   [22] Galvin, J., Murphy, S., Crocker, S. and N. Freed, "Security
        Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",
   [23] Housley, R., "Cryptographic Message Syntax", RFC 2630, June
        1999.
   [24] Ramsdell B., "S/MIME Version 3 Message Specification", RFC 2633,
        June 1999.
   [25] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC
        2246, January 1999.
   [26] Kent, S. and R. Atkinson, "Security Architecture for the
Section 30 Informative References

[27] R. Pandya, "Emerging mobile and personal communication systems,"
        IEEE Communications Magazine, Vol. 33, pp. 44--52, June 1995.
   [28] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
        "RTP:  A Transport Protocol for Real-Time Applications", RFC
        1889, January 1996.
   [29] Schulzrinne, H., Rao, R. and R. Lanphier, "Real Time Streaming
   [30] Cuervo, F., Greene, N., Rayhan, A., Huitema, C., Rosen, B. and
        J. Segers, "Megaco Protocol Version 1.0", RFC 3015, November
        2000.
   [31] Handley, M., Schulzrinne, H., Schooler, E. and J. Rosenberg,
   [32] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL
   [33] E. M. Schooler, "A multicast user directory service for
        synchronous rendezvous," Master's Thesis CS-TR-96-18, Department
        of Computer Science, California Institute of Technology,
        Pasadena, California, Aug. 1996.
   [35] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, April
        1992.
   [36] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC
        2426, September 1998.
   [37] Good, G., "The LDAP Data Interchange Format (LDIF) - Technical
   [38] Palme, J., "Common Internet Message Headers",  RFC 2076,
        February 1997.
   [39] Franks, J., Hallam-Baker, P., Hostetler, J., Leach, P.,
        Luotonen, A., Sink, E. and L. Stewart, "An Extension to HTTP:
   [40] Johnston, A., Donovan, S., Sparks, R., Cunningham, C., Willis,
        D., Rosenberg, J., Summers, K. and H. Schulzrinne, "SIP Call
        Flow Examples", Work in Progress.
   [41] E. M. Schooler, "Case study: multimedia conference control in a
        packet-switched teleconferencing system," Journal of
        Internetworking:  Research and Experience, Vol. 4, pp. 99--120,
        June 1993.  ISI reprint series ISI/RS-93-359.
   [42] H. Schulzrinne, "Personal mobility for multimedia services in
        the Internet," in European Workshop on Interactive Distributed
        Multimedia Systems and Services (IDMS), (Berlin, Germany), Mar.
        1996.
   [43] Floyd, S., "Congestion Control Principles", RFC 2914, September
        2000.
Section Full Copyright Statement

Copyright (C) The Internet Society (2002).  All Rights Reserved.
   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.
   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.
   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
   Funding for the RFC Editor function is currently provided by the
   Internet Society.