RFC 3351

User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals

📅 published August 2002, from ietf

okay bestie, let's do the vibe check first 💅🦋 this is RFC 3351, called "User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals" 🎀. It's from the Network Working Group, filed as Informational (so it's info for the community, not a standard 🌸), and it's dated August 2002 ✨. The authors are N. Charlton (Millpark), M. Gasson (Koru Solutions), G. Gybels (no affiliation is listed next to their name), M. Spanner (RNID), and A. van Wijk (Ericsson) 👑. The header has no Obsoletes or Updates line, so it doesn't replace or change any other RFCs 💜

Here's the table of contents, copied exactly as it is:

1. Terminology and Conventions Used in this Document................2
2. Introduction.....................................................3
3. Purpose and Scope................................................4
4. Background.......................................................4
5. Deaf, Hard of Hearing and Speech-impaired Requirements for SIP...5
   5.1 Connection without Difficulty................................5
   5.2 User Profile.................................................6
   5.3 Intelligent Gateways.........................................6
   5.4 Inclusive Design.............................................7
   5.5 Resource Management..........................................7
   5.6 Confidentiality and Security.................................7
6. Some Real World Scenarios........................................8
   6.1 Transcoding Service..........................................8
   6.2 Media Service Provider.......................................9
   6.3 Sign Language Interface......................................9
   6.4 Synthetic Lip-reading Support for Voice Calls...............10
   6.5 Voice-Activated Menu Systems................................10
   6.6 Conference Call.............................................11
7. Some Suggestions for Service Providers and User Agent
   Manufacturers...................................................13
8. Acknowledgements................................................14
   Security Considerations.........................................14
   Normative References............................................15
   Informational References........................................15
   Author's Addresses..............................................15
   Full Copyright Statement........................................17

Status of this Memo

This memo gives information to the Internet community 🌈. It does not specify an Internet standard of any kind ✨. Distribution of this memo is unlimited 🫶.

Copyright (C) The Internet Society (2002). All Rights Reserved. 💜

Abstract

okay so this doc pulls together a set of Session Initiation Protocol (SIP) user requirements that support communications for deaf, hard of hearing and speech-impaired individuals 🫶. These requirements tackle the problems these folks currently run into when using communications facilities, while also recognizing how multi-functional SIP-based communications can be 🔥

A bunch of issues connected to these requirements also get raised in the doc 👀

It also has some real world scenarios and some technical requirements, so you can see how robust these requirements are at the concept level 🧚

Table of Contents

The table of contents is shown above, with its page numbers left exactly as they were 🎀

1. Terminology and Conventions Used in this Document

So first, the key words. In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be read as described in BCP 14, [RFC2119][1], and they show the requirement levels for compliant SIP implementations 💅

Next, some terms and what they mean here ✨

Abilities: A person's capacity for communicating, which could include a hearing or speech impairment or not. The terms Abilities and Preferences apply to both caller and call-recipient 🦋

Preferences: A person's choice of communication mode. This could be any combination of media streams, e.g., text, audio, video 🌸

The terms Abilities and Preferences apply to both caller and call-recipient 💖

Relay Service: A third-party or intermediary that enables communications between deaf, hard of hearing and speech-impaired people, and people without hearing or speech-impairment. Relay Services form a subset of the activities of Transcoding Services (see definition) 🧚

Transcoding Services: A human or automated third party acting as an intermediary in any session between two other User Agents (being a User Agent itself), and transcoding one stream into another (e.g., voice to text or vice versa) 🔥

Textphone: Sometimes called a TTY (teletypewriter), TDD (telecommunications device for the deaf) or a minicom, a textphone enables a deaf, hard of hearing or speech-impaired person to place a call to a telephone or another textphone. Some textphones use the V.18[3] protocol as a standard for communication with other textphone communication protocols world-wide 📞✨

User: A deaf, hard of hearing or speech-impaired individual. A user is otherwise referred to as a person or individual, and users are referred to as people 🌈

Note: For the purposes of this document, a deaf, hard of hearing, or speech-impaired person is an individual who chooses to use SIP because it can minimize or eliminate constraints in using common communication devices. Since SIP promises a total communication solution for any kind of person, regardless of ability and preference, the document does not try to specifically define deaf, hard of hearing or speech-impaired 💜

2. Introduction

The background here is the recent development of SIP[2] and SIP-based communications, plus a growing awareness of deaf, hard of hearing and speech-impaired issues in the technical community 👑

The SIP capacity to simplify setting up, managing and tearing down communication sessions between all kinds of User Agents has specific implications for deaf, hard of hearing and speech-impaired individuals 🫶

Since SIP enables multiple sessions with translation between multiple types of media, these requirements aim to provide the standard for recognizing and enabling these interactions, and for a communications model that includes any and all types of SIP-networking abilities and preferences 🦋

3. Purpose and Scope

The main goal of this document is to present a current set of user requirements for deaf, hard of hearing and speech-impaired individuals using SIP-enabled communications 🎀. After that come some real world scenarios in SIP communications that could be used in a test environment, plus some ideas on how service providers and User Agent manufacturers can develop these requirements 🧚

These recommendations spell out the needs of a user group that is often disadvantaged right now, and try to match those needs with what SIP can do 💅. It is not the intention here to prioritize the needs of deaf, hard of hearing and speech-impaired people in a way that would penalize other individuals 🫶

These requirements aim to encourage developers and manufacturers all over the world to think about the specific needs of deaf, hard of hearing and speech-impaired individuals 🌸. This document presents a world-vision where deafness, hard of hearing or speech impairment are no longer a barrier to communication 🌈✨

4. Background

Deaf, hard of hearing and speech-impaired people are often unable to use commonly available communication devices right now 😭. Although this is documented[4], that doesn't mean developers or manufacturers are always aware of it 💀. Communication devices for these people are often primitive in design, expensive, and non-compatible with more progressively designed, cheaper and more adaptable communication devices for other individuals. For example, many models of textphone can't communicate with other models 📞

Also, non-technical human communications, like sign languages or lip-reading, are non-standard around the world 🤍

There are intermediary or third-party relay services (e.g. transcoding services) that help communications, uni- or bi-directional, for deaf, hard of hearing and speech-impaired people 🦋. Right now relay services are mostly operator-assisted (manual), although some areas are starting to implement partial automation 🧚. These services give full access to modern facilities and conveniences for these people. They're somewhat limited, but their value is undeniable compared to their previous complete unavailability 💖

Yet communication methods in recent decades have multiplied: email, mobile phones, video streaming, and more 📱✨. These methods are an advance in the development of data transfer technologies between devices 🔥

Developers and advocates of SIP agree that it is a protocol that not only anticipates the growth in real-time communications between convergent networks, but also fulfills the potential of the Internet as a communications and information forum 👑. They also agree that these developments allow a standard of communication that can be applied across all networking communities, regardless of abilities and preferences 🫶

5. Deaf, Hard of Hearing and Speech-impaired Requirements for SIP

Introduction

The user requirements in this section are written for service providers, User Agent manufacturers and any other interested parties building products and services for deaf, hard of hearing and speech-impaired people 🎀

The user requirements are as follows 💅

5.1 Connection without Difficulty ✨

This requirement says:

Whatever the preferences and abilities of the user and User Agent, there SHOULD be no difficulty in setting up SIP sessions 🦋. These sessions could include multiple proxies, call routing decisions, transcoding services (e.g., the relay service Typetalk[5]) or other media processing, and could include multiple simultaneous or alternative media streams 🌸

This means that any User Agent in the conversation (including transcoding services) MUST be able to add or remove a media stream from the call without having to tear it down and re-establish it 🔥🧚

5.2 User Profile ✨

okay so this one is about the User Profile, which is basically a deaf, hard of hearing or speech-impaired person's whole vibe: their abilities and preferences, all packaged up. the requirement is literally:

Deaf, hard of hearing and speech-impaired user abilities and preferences (i.e., user profile) MUST be communicable by SIP, and these abilities and preferences MUST determine the handling of the session.

so the profile has to be communicable over SIP 💅 and it has to actually steer how the session gets handled 🫶

a profile for a deaf, hard of hearing or speech-impaired person might cover stuff like:

  • how media streams come in and go out (text, voice, video, or any combo, one-way or two-way) 📱
  • sending specific media streams through a transcoding service (e.g., the relay service Typetalk) 🔁
  • roaming, like a deaf person pulling up their profile from a web interface at an Internet cafe ☕
  • anonymity, meaning not revealing that a deaf person is calling, even through a transcoding service (e.g., some relay services tell the call-recipient there's an incoming text call without saying a deaf person is the one calling) 🙈

and this part is so important to me 🥺 the whole point is that deaf, hard of hearing and speech-impaired people can keep their preferences and abilities private from others, so nobody can discriminate against or prejudge them, and they can still set up a SIP session no problem 👑

5.3 Intelligent Gateways 🌉

this one's about gateways. the requirement says:

SIP SHOULD support a class of User Agents to perform as gateways for legacy systems designed for deaf, hard of hearing and speech-impaired people.

for example, someone could have a SIP User Agent acting as a gateway to a PSTN legacy textphone. old tech and new tech getting along, iconic 🧚

5.4 Inclusive Design 🎀

design is giving "include everyone" 💖 the requirement says:

Where applicable, design concepts for communications (devices, applications, etc.) MUST include the abilities and preferences of deaf, hard of hearing and speech-impaired people.

and the transcoding services and User Agents have to be able to connect with each other no matter who made them or who provides them. no gatekeeping allowed 🙅‍♀️ that means new User Agents MUST be able to support legacy protocols through appropriate gateways, so the old stuff doesn't get left behind 🌸

5.5 Resource Management 💜

User Agents SHOULD be able to figure out what's inside a media stream, so they can get info like how much the stream costs, if a transcoding service can support that. ✨

User Agents SHOULD also be able to pick between transcoding services and similar services based on what they can do (for example, whether a transcoding service carries a particular media stream) and any policy limits they come with (for example, charging for use). the vibe is shopping smart 🛍️ It SHOULD be possible for User Agents to find out which alternative media streams are available and to choose from them. choice = power 👑

5.6 Confidentiality and Security 🔒

here's the requirement, and it's serious 🫣

All third-party or intermediaries (transcoding services) employed in a session for deaf, hard of hearing and speech-impaired people MUST offer a confidentiality policy. All information exchanged in this type of session SHOULD be secure, that is, erased before confidentiality is breached, unless otherwise required.

so every third party or middleman (transcoding service) in these sessions MUST have a confidentiality policy, and all the info swapped should be secure. translated: erased before confidentiality can get breached, unless something else requires otherwise 💀

which means transcoding services (e.g., interpretation, translation) MUST publish their confidentiality and security policies. transparency is the moment 🍓

6. Some Real World Scenarios 🌈

these scenarios are here to show the different kinds of media streams that get started, managed, directed and ended in a SIP-enabled network. they also show how resources might get managed between SIP-enabled networks, transcoding services and service providers. bestie, it's a lot of moving parts but it's so cool 🧚

each scenario spells out which kinds of media streams get sent and whether User Agents and Transcoding Services are involved, so you can follow the vibe.

6.1 Transcoding Service 📞

in this one, a hearing person calls the household of a deaf person and a hearing person. here's how it goes:

  1. a voice conversation starts between the hearing participants:
( Person A) <-----Voice ---> ( Person B)
  1. during the convo, the hearing person asks to talk with the deaf person, but they keep the voice connection open so voice to voice can keep going if it's needed. 🎧
  2. a Relay Service gets invited into the conversation. 🙋‍♀️
  3. the Relay Service transcodes the hearing person's words into text. ✍️
  4. the text from the hearing person's voice shows up on the display of the deaf person's User Agent. 📱
  5. the deaf person types a response. ⌨️
  6. the Relay Service gets the text and reads it out to the hearing person:
(         ) <------------------Voice----------------> (         )
(Person A ) -----Voice---> ( Voice To Text  ) -Text-> (Person B )
(         ) <----Voice---- (Service Provider) <-Text- (         )
  1. the hearing person asks to talk with the hearing person in the deaf person's household.
  2. the Relay Service leaves the call. bye bye 👋

6.2 Media Service Provider 📻

in this scenario, a deaf person wants to get a radio program through a text stream that's been transcoded from the program's audio stream.

  1. the deaf person tries to connect to the radio broadcast, with User Agent preferences set to receive the audio stream as text.
  2. the deaf person's User Agent asks the radio station's User Agent if a text stream is available, besides the audio stream.
  3. but the radio station doesn't have a text stream for a deaf listener, so it says no. 😢
  4. no text stream means the deaf person's User Agent requests a voice-to-text transcoding service (e.g., a real-time captioning service) to join the conversation space.
  5. the transcoding service's User Agent sees the audio stream is a radio broadcast. but the transcoding service's policy is that it doesn't accept radio broadcasts, because it would overload their resources way too fast. 🫠
  6. in this case, the connection fails. rip 🥀

but here's the alternative, picking up from step 2 above:

  1. the radio station does provide text with their audio streams. 🎉
  2. the deaf person gets a text stream of the radio program. iconic 🙌
Note: to support deaf, hard of hearing and speech-impaired people, service providers are encouraged to provide text with audio streams.

6.3 Sign Language Interface 🤟

in this one, a deaf person turns on a signing avatar (e.g., ViSiCAST[6]) by setting up a User Agent to receive audio streams as XML data that runs an avatar for sign language. for outgoing communications, the deaf person types text, and that text gets transcoded into an audio stream for the other person in the conversation. 🧚‍♀️

for example:

(         )-Voice->(Voice To Avatar Commands) ----XMLData-->(        )
( hearing )                                                 (deaf    )
( Person A)<-Voice-( Text To Voice  ) <--------Text-------- (Person B)
(         )        (Service Provider)                       (        )

6.4 Synthetic Lip-speaking Support for Voice Calls 🫦

so to get voice calls, a hard of hearing person uses lip-speaking avatar software (e.g., Synface[7]) on a PC. the lip-speaking software processes the voice (audio) stream data and shows a synthetic animated face that the hard of hearing person might be able to lip-read. during the convo, they use the lip-speaking software to help them understand the audio stream. it's giving support system 💖

for example:

     (         ) <------------------Voice-------------->(         )
     ( hearing )                    ( PC with     )     ( hard of )
     ( Person A) -------Voice-----> ( lip-speaking)---->( hearing )
     (         )                    ( software    )     ( Person B)

6.5 Voice Activated Menu Systems 🎬

in this scenario, a deaf person wants to book cinema tickets with a credit card, so they use a textphone to place the call. the cinema has a voice-activated menu system for film titles and showing times. 🍿

  1. the deaf person calls the cinema with a textphone:
      (Textphone) <-----Text ---> (Voice-activated System)
  1. the cinema's voice-activated menu asks for an auditory response to keep going.
  2. a Relay Service gets invited into the conversation.
  3. the Relay Service transcodes the prompts from the voice-activated menu into text.
  4. the text from the voice-activated menu shows up on the display of the deaf person's textphone.
  5. the deaf person types a response.
  6. the Relay Service gets the text and reads it to the voice-activated system:
(           )         (Relay Service   )          (               )
( deaf      ) -Text-> (Provider        ) -Voice-> (Voice-Activated)
( Person A  ) <-Text- (Text To Voice   ) <-Voice- (System         )
  1. the transaction gets wrapped up with a confirmed booking time. 🎟️
  2. the Relay Service leaves the call. 👋

6.6 Conference Call 👯‍♀️

a conference call is scheduled between five people:

  • Person A listens and types text (hearing, no speech)
  • Person B recognizes sign language and signs back (deaf, no speech)
  • Person C reads text and speaks (deaf or hearing impaired)
  • Person D listens and speaks
  • Person E recognizes sign language and reads text and signs

a conference call server calls all five people and, based on their preferences, sets up the different transcoding services they need. assuming English is the base language for the call, these intermediate transcoding services get invoked:

  • A transcoding service (English speech to English text)
  • An English text to sign language service
  • A sign language to English text service
  • An English text to English speech service
Note: to translate English speech into sign language, a chain of intermediate transcoding services gets used (transcoding and English text to sign language), because there's no speech-to-sign language option available for direct translation. the same goes for translating sign language into English speech.

and here's the whole flow:

(Person A) ----- Text ----> (  Text-to-SL  ) --- Video ----> (Person B)
           ---------------------- Text --------------------> (Person C)
           ----- Text ----> (Text-to-Speech) --- Voice ----> (Person D)
           ---------------------- Text --------------------> (Person E)
           ----- Text ----> (  Text-to-SL  ) --- Video ----> (Person E)
(Person B) -Video-> (SL-to-Text) -Text-> (Text-to-Speech) -> (Person A)
           ---- Video ----> (  SL-to-Text  ) ---- Text ----> (Person C)
           -Video-> (SL-to-Text) -Text-> (Text-to-Speech) -> (Person D)
           --------------------- Video --------------------> (Person E)
           ---- Video ----> (  SL-to-Text  ) ---- Text ----> (Person E)
(Person C) --------------------- Voice --------------------> (Person A)
           Voice->(Speech-to-Text)-Text->(Text-to-SL)-Video->(Person B)
           --------------------- Voice --------------------> (Person D)
           ---- Voice ----> (Speech-to-Text) ---- Text ----> (Person E)
           Voice->(Speech-to-Text)-Text->(Text-to-SL)-Video->(Person E)
(Person D) --------------------- Voice --------------------> (Person A)
           Voice->(Speech-to-Text)-Text->(Text-to-SL)-Video->(Person B)
           ---- Voice ----> (Speech-to-Text) ---- Text ----> (Person C)
           ---- Voice ----> (Speech-to-Text) ---- Text ----> (Person E)
           Voice->(Speech-to-Text)-Text->(Text-to-SL)-Video->(Person E)
(Person E) -Video-> (SL-to-Text) -Text-> (Text-to-Speech) -> (Person A)
           --------------------- Video --------------------> (person B)
           ---- Video ----> (  SL-to-Text  ) ---- Text ----> (Person C)
           -Video-> (SL-to-Text) -Text-> (Text-to-Speech) -> (Person D)

Remarks:

  • Some services might be shared by users and/or other services. 🫶
  • Person E uses two parallel streams (SL and English Text). The User Agent might perform time synchronisation when displaying the streams. However, this would require synchronisation information to be present on the streams. ⏱️✨
  • The session protocols might support optional buffering of media streams, so that users and/or intermediate services could go back to previous content or to invoke a transcoding service for content they just missed. ⏪💜
  • Hearing impaired users might still receive audio as well, which they will use to drive some visual indicators so that they can better see where, for instance, the pauses are in the conversation. 👀🦋

7. Some Suggestions for Service Providers and User Agent Manufacturers ✨

Okay so this section is basically a big group hug for service providers and user agent manufacturers 🫶. It's here to encourage them to build products and services that as many people as possible can actually use, including deaf, hard of hearing and speech-impaired people. Let's make the internet slay for everyone 💅🌈.

  • Service providers and User Agent manufacturers can offer to a deaf, hard of hearing and speech-impaired person the possibility of being able to prevent their specific abilities and preferences from being made public in any transaction. 🙈🔒
  • If a User Agent performs auditory signalling, for example a pager, it could also provide another signalling method; visual (e.g., a flashing light) or tactile (e.g., vibration). 🔔➡️💡📳
  • Service providers who allow the user to store specific abilities and preferences or settings (i.e., a user profile) might consider storing these settings in a central repository, accessible no matter what the location of the user and regardless of the User Agent used at that time or location. ☁️🎀
  • If there are several transcoding services available, the User Agent can be set to select the most economical/highest quality service. 💖
  • The service provider can show the cost per minute and any minimum charge of a transcoding service call before a session starts, allowing the user a choice of engaging in the service or not. 💸👑
  • Service providers are encouraged to offer an alternative stream to an audio stream, for example, text or data streams that operate avatars, etc. 🧚🌸
  • Service providers are encouraged to provide a text alternative to voice-activated menus, e.g., answering and voice mail systems. 📞📝
  • Manufacturers of voice-activated software are encouraged to provide an alternative visual format for software prompts, menus, messages, and status information. 📊✨
  • Manufacturers of mobile phones are encouraged to design equipment that avoids electro-magnetic interference with hearing aids. 📱👂
  • All services for interpreting, transliterating, or facilitating communications for deaf, hard of hearing and speech-impaired people are required to:
    • Keep information exchanged during the transaction strictly confidential 🤐
    • Enable information exchange literally and simply, without deviating and compromising the content 🎯
    • Facilitate communication without bias, prejudice or opinion ⚖️
    • Match skill-sets to the requirements of the users of the service 🧠
    • Behave in a professional and appropriate manner 💼
    • Be fair in pricing of services 💅
    • Strive to improve the skill-sets used for their services. 📈🔥
  • Conference call services might consider ways to allow users who employ transcoding services (which usually introduce a delay) to have real-time information sufficient to be able to identify gaps in the conversation so they could inject comments, as well as ways to raise their hand, vote and carry out other activities where timing of their response relative to the real-time conversation is important. 🙋‍♀️🗳️⏰

8. Acknowledgements 🌷

The authors would like to thank the following individuals for their contributions to this document. Thank you, lovelies 💖🙏.

  • David R. Oran, Cisco
  • Mark Watson, Nortel Networks
  • Brian Grover, RNID
  • Anthony Rabin, RNID
  • Michael Hammer, Cisco
  • Henry Sinnreich, Worldcom
  • Rohan Mahy, Cisco
  • Julian Branston, Cedalion Hosting Services
  • Judy Harkins, Gallaudet University, Washington, D.C.
  • Cary Barbin, Gallaudet University, Washington, D.C.
  • Gregg Vanderheiden, Trace R&D Center University of Wisconsin-Madison
  • Gottfried Zimmerman, Trace R&D Center University of Wisconsin-Madison

Security Considerations 🔐😱

This document presents some privacy and security considerations. They are treated in Section 5.6 Confidentiality and Security. Privacy and security are NOT a vibe you skip, bestie, so go read that section 🚨💀.

Normative References 📚

  • [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
  • [2] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002.

Informational References 🧾

  • [3] International Telecommunication Union (ITU), "Operational and interworking requirements for DCEs operating in the text telephone mode". ITU-T Recommendation V.18, November 2000.
  • [4] Moore, Matthew, et al. "For Hearing People Only: Answers to Some of the Most Commonly Asked Questions About the Deaf Community, Its Culture, and the Deaf Reality". MSM Productions Ltd., 2nd Edition, September 1993.
  • [5] http://www.typetalk.org.
  • [6] http://www.visicast.co.uk.
  • [7] http://www.speech.kth.se/teleface.

Authors' Addresses 📮💌

Nathan Charlton
Millpark Limited
52 Coborn Road
London E3 2DG
Tel: +44-7050 803628
Fax: +44-7050 803628
EMail: nathan@millpark.com
Mick Gasson
Koru Solutions
30 Howland Way
London SE16 6HN
Tel: +44-20 7237 3488
Fax: +44-20 7237 3488
EMail: michael.gasson@korusolutions.com
Guido Gybels
RNID
19-23 Featherstone Street
London EC1Y 8SL
Tel: +44-20 7296 8000
Textphone: +44-20 7296 8001
Fax: +44-20 7296 8199
EMail: Guido.Gybels@rnid.org.uk
Mike Spanner
RNID
19-23 Featherstone Street
London EC1Y 8SL
Tel: +44-20 7296 8000
Textphone: +44-20 7296 8001
Fax: +44-20 7296 8199
EMail: mike.spanner@rnid.org.uk
Arnoud van Wijk
Ericsson EuroLab Netherlands BV
P.O. Box 8
5120 AA Rijen
The Netherlands
Fax: +31-161-247569
EMail: Arnoud.van.Wijk@eln.ericsson.se

Comments can be sent to the SIPPING mailing list. 📬💜

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. Thanks for hanging in there through all three parts, bestie 🥹🎀🦋

📦 where this page comes from