draft-ietf-sipcore-keep-09.txt   draft-ietf-sipcore-keep-10.txt 
SIPCORE Working Group C. Holmberg SIPCORE Working Group C. Holmberg
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track December 9, 2010 Intended status: Standards Track December 15, 2010
Expires: June 12, 2011 Expires: June 18, 2011
Indication of support for keep-alive Indication of support for keep-alive
draft-ietf-sipcore-keep-09.txt draft-ietf-sipcore-keep-10.txt
Abstract Abstract
This specification defines a new Session Initiation Protocol (SIP) This specification defines a new Session Initiation Protocol (SIP)
Via header field parameter, "keep", which allows adjacent SIP Via header field parameter, "keep", which allows adjacent SIP
entities to explicitly negotiate usage of the Network Address entities to explicitly negotiate usage of the Network Address
Translation (NAT) keep-alive mechanisms defined in SIP Outbound, in Translation (NAT) keep-alive mechanisms defined in SIP Outbound, in
cases where SIP Outbound is not supported, cannot be applied, or cases where SIP Outbound is not supported, cannot be applied, or
where usage of keep-alives is not implicitly negotiated as part of where usage of keep-alives is not implicitly negotiated as part of
the SIP Outbound negotiation. the SIP Outbound negotiation.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 June 12, 2011. This Internet-Draft will expire on June 18, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 36 skipping to change at page 2, line 36
7.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.2. Keep-alive negotiation associated with registration: 7.2. Keep-alive negotiation associated with registration:
UA-proxy . . . . . . . . . . . . . . . . . . . . . . . . . 10 UA-proxy . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.3. Keep-alive negotiation associated with dialog: UA-proxy . 11 7.3. Keep-alive negotiation associated with dialog: UA-proxy . 11
7.4. Keep-alive negotiation associated with dialog: UA-UA . . . 12 7.4. Keep-alive negotiation associated with dialog: UA-UA . . . 12
8. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 8. Grammar . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9.1. keep . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9.1. keep . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 10. Security Considerations . . . . . . . . . . . . . . . . . . . 15
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
12. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 17 12. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 16
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17
13.1. Normative References . . . . . . . . . . . . . . . . . . . 17 13.1. Normative References . . . . . . . . . . . . . . . . . . . 17
13.2. Informative References . . . . . . . . . . . . . . . . . . 18 13.2. Informative References . . . . . . . . . . . . . . . . . . 18
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction 1. Introduction
Section 3.5 of SIP Outbound [RFC5626] defines two keep-alive Section 3.5 of SIP Outbound [RFC5626] defines two keep-alive
mechanisms. Even though the keep-alive mechanisms are separated from mechanisms. Even though the keep-alive mechanisms are separated from
the rest of the SIP Outbound mechanism, SIP Outbound does not define the rest of the SIP Outbound mechanism, SIP Outbound does not define
skipping to change at page 16, line 30 skipping to change at page 16, line 30
a keep parameter with a value it did not create in the topmost Via a keep parameter with a value it did not create in the topmost Via
header field. To lower the chances of the malicious SIP entity's header field. To lower the chances of the malicious SIP entity's
actions having adverse affects on such proxies, when a SIP entity actions having adverse affects on such proxies, when a SIP entity
sends STUN keep-alives to an adjacent downstream SIP entity and does sends STUN keep-alives to an adjacent downstream SIP entity and does
not receive a response to those STUN messages, it MUST stop sending not receive a response to those STUN messages, it MUST stop sending
the keep-alive requests for the remaining duration of the dialog (if the keep-alive requests for the remaining duration of the dialog (if
the sending of keep-alives were negotiated for a dialog) or until the the sending of keep-alives were negotiated for a dialog) or until the
sending of keep-alives is re-negotiated for the registration (if the sending of keep-alives is re-negotiated for the registration (if the
sending keep-alives were negotiated for a registration). sending keep-alives were negotiated for a registration).
In order to prevent attacks, when a SIP entity sends STUN keep-alives
to an adjacent downstream SIP entity that is not willing to receive
keep-alives (or does not support STUN), but for which willingness to
receive keep-alives has been inidicated by some other downstream SIP
entity, if the sending SIP entity does not receive a response to any
of the STUN keep-alive requests, it MUST stop sending the keep-alive
requests for the remaining duration of the dialog (if the sending of
keep-alives were negotiated for a dialog) or until the sending of
keep-alives is re-negotiated for the registration (if the sending
keep-alives were negotiated for a registration). Further actions
taken by the sending SIP entity is outside the scope of this
specification.
Apart from the issues described above, this specification does not Apart from the issues described above, this specification does not
introduce security considerations in addition to those specified for introduce security considerations in addition to those specified for
keep-alives in [RFC5626]. keep-alives in [RFC5626].
11. Acknowledgements 11. Acknowledgements
Thanks to Staffan Blau, Francois Audet, Hadriel Kaplan, Sean Schneyer Thanks to Staffan Blau, Francois Audet, Hadriel Kaplan, Sean Schneyer
and Milo Orsic for their comments on the initial draft. Thanks to and Milo Orsic for their comments on the initial draft. Thanks to
Juha Heinaenen, Jiri Kuthan, Dean Willis, John Elwell, Paul Kyzivat, Juha Heinaenen, Jiri Kuthan, Dean Willis, John Elwell, Paul Kyzivat,
Peter Musgrave, Dale Worley, Adam Roach and Robert Sparks for their Peter Musgrave, Dale Worley, Adam Roach and Robert Sparks for their
comments on the list. Thanks to Vijay Gurbani for providing text comments on the list. Thanks to Vijay Gurbani for providing text
about the relationship with the connect reuse specification. about the relationship with the connect reuse specification.
12. Change Log 12. Change Log
[RFC EDITOR NOTE: Please remove this section when publishing] [RFC EDITOR NOTE: Please remove this section when publishing]
Changes from draft-ietf-sipcore-keep-09
o Changes based on AD review comments by Robert Sparks
o Redundant paragraph removed from security considerations
Changes from draft-ietf-sipcore-keep-08 Changes from draft-ietf-sipcore-keep-08
o Changes based on AD review comments by Robert Sparks o Changes based on AD review comments by Robert Sparks
o Additional security considerations text provided by Robert Sparks o Additional security considerations text provided by Robert Sparks
o http://www.ietf.org/mail-archive/web/sipcore/current/msg03779.html o http://www.ietf.org/mail-archive/web/sipcore/current/msg03779.html
(Nov 23rd) (Nov 23rd)
o http://www.ietf.org/mail-archive/web/sipcore/current/msg03780.html o http://www.ietf.org/mail-archive/web/sipcore/current/msg03780.html
(Nov 23rd) (Nov 23rd)
Changes from draft-ietf-sipcore-keep-07 Changes from draft-ietf-sipcore-keep-07
o Last paragraph of section 4.2.2 removed o Last paragraph of section 4.2.2 removed
 End of changes. 6 change blocks. 
18 lines changed or deleted 9 lines changed or added

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