ETS (continued)

ETS (continued)

  • Application layer IP telephony capabilities must not preclude the ability to do application layer accounting.
  • Application layer mechanisms in gateways and stateful proxies that are specifically in place to recognize ETS type labels must be able to support “best available” service (i.e., better than “best effort”).

See also RFC 4375 and RFC 4542.


Slide Notes

K. Carlberg, “Emergency Telecommunications Services (ETS) Requirements for a Single Administrative Domain”, Internet Request for Comments", RFC Editor, RFC 4375 (Informational), ISSN 2070-1721, January 2006, http://www.rfc-editor.org/rfc/rfc4375.txt Links to an external site.

F. Baker and J. Polk, “Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite”, Internet Request for Comments, RFC Editor, RFC 4542 (Informational), ISSN 2070-1721, May 2006, Updated by RFC 5865 http://www.rfc-editor.org/rfc/rfc4542.txt Links to an external site.


Transcript

[slide434] So, if you read RFCs 4375 and 4542, you can read more about this emergency telecom labels.