draft-ietf-sipcore-rfc4028bis-04.txt   draft-ietf-sipcore-rfc4028bis-05.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Obsoletes: 4028 (if approved) S. Donovan Obsoletes: 4028 (if approved) S. Donovan
Intended status: Standards Track J. Rosenberg Intended status: Standards Track J. Rosenberg
Expires: July 17, 2021 Cisco Systems Expires: January 28, 2022 Cisco Systems
January 13, 2021 July 27, 2021
Session Timers in the Session Initiation Protocol (SIP) Session Timers in the Session Initiation Protocol (SIP)
draft-ietf-sipcore-rfc4028bis-04 draft-ietf-sipcore-rfc4028bis-05
Abstract Abstract
This document defines an extension to the Session Initiation Protocol This document defines an extension to the Session Initiation Protocol
(SIP). This extension allows for a periodic refresh of SIP sessions (SIP). This extension allows for a periodic refresh of SIP sessions
through a re-INVITE or UPDATE request. The refresh allows both user through a re-INVITE or UPDATE request. The refresh allows both user
agents and proxies to determine whether the SIP session is still agents and proxies to determine whether the SIP session is still
active. The extension defines two new header fields: Session- active. The extension defines two new header fields: Session-
Expires, which conveys the lifetime of the session, and Min-SE, which Expires, which conveys the lifetime of the session, and Min-SE, which
conveys the minimum allowed value for the session timer. conveys the minimum allowed value for the session timer.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 17, 2021. This Internet-Draft will expire on January 28, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 42 skipping to change at page 2, line 42
22. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 22. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
23. IANA Registration of Min-SE and Session-Expires Header Fields 19 23. IANA Registration of Min-SE and Session-Expires Header Fields 19
24. IANA Registration of the 422 (Session Interval Too Small) 24. IANA Registration of the 422 (Session Interval Too Small)
Response Code . . . . . . . . . . . . . . . . . . . . . . . . 20 Response Code . . . . . . . . . . . . . . . . . . . . . . . . 20
25. IANA Registration of the 'timer' Option Tag . . . . . . . . . 20 25. IANA Registration of the 'timer' Option Tag . . . . . . . . . 20
26. Example Call Flow . . . . . . . . . . . . . . . . . . . . . . 20 26. Example Call Flow . . . . . . . . . . . . . . . . . . . . . . 20
27. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 27. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
28. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 28. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
28.1. Normative References . . . . . . . . . . . . . . . . . . 25 28.1. Normative References . . . . . . . . . . . . . . . . . . 25
28.2. Informative References . . . . . . . . . . . . . . . . . 25 28.2. Informative References . . . . . . . . . . . . . . . . . 25
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [RFC3261] does not define a The Session Initiation Protocol (SIP) [RFC3261] does not define a
keepalive mechanism for the sessions it establishes. Although the keepalive mechanism for the sessions it establishes. Although the
user agents may be able to determine whether the session has timed user agents may be able to determine whether the session has timed
out by using session specific mechanisms, proxies will not be able to out by using session specific mechanisms, proxies will not be able to
do so. The result is that call stateful proxies will not always be do so. The result is that call stateful proxies will not always be
able to determine whether a session is still active. For instance, able to determine whether a session is still active. For instance,
skipping to change at page 26, line 14 skipping to change at page 26, line 14
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
Event Notification", RFC 3265, DOI 10.17487/RFC3265, June Event Notification", RFC 3265, DOI 10.17487/RFC3265, June
2002, <https://www.rfc-editor.org/info/rfc3265>. 2002, <https://www.rfc-editor.org/info/rfc3265>.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550, Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
July 2003, <https://www.rfc-editor.org/info/rfc3550>. July 2003, <https://www.rfc-editor.org/info/rfc3550>.
Appendix A.
Funding for the RFC Editor function is currently provided by the
Internet Society.
Authors' Addresses Authors' Addresses
Christer Holmberg Christer Holmberg
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: christer.holmberg@ericsson.com Email: christer.holmberg@ericsson.com
 End of changes. 5 change blocks. 
10 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/