Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/internet-drafts/draft-martinsen-ice-ice-timers-00.txt Дата изменения: Mon Oct 19 10:40:47 2015 Дата индексирования: Sun Apr 10 07:28:35 2016 Кодировка:

ICE P. Martinsen
Internet-Draft Cisco
Intended status: Informational October 19, 2015
Expires: April 21, 2016


ICE Timers, values and recommendations
draft-martinsen-ice-ice-timers-00

Abstract

The ICE set of RFCs contains pacing and timer values. The network
gear initially used to test and figure out those values can now
safely be considered obsolete. This document describes the current
timer values and pacing recommendations for the ICE RFCs.

Status of This Memo

This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

This Internet-Draft will expire on April 21, 2016.

Copyright Notice

Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.




Martinsen Expires April 21, 2016 [Page 1]

Internet-Draft ICE Timers October 2015


Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Notational Conventions . . . . . . . . . . . . . . . . . . . 2
3. Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3.1. RTO . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3.2. Ta . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. Pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Keep-Alive . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Consent . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
7. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3

1. Introduction

This document describes updated ICE related timing values and pacing
recommendations. As the world moves on and new knowledge is acquired
it might be necessary or useful to update some of the timing
sensitive recommendations in the ICE set of RFCs. Rather then
updating the entire set of ICE RFCs this document will be updated.
(How is this done? Obsolete an RFC and create a new one? How many
bis versions can there be?)

2. Notational Conventions

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].

This document uses terminology defined in [RFC5245].

3. Timers

How to deal with RTO vs just sending a new STUN request with a new
TransID? (Implementation differences)

3.1. RTO

Since recent advancements in networking and the speed off light
problem is no longer an issue this timer value can now be set to 0.

3.2. Ta

Some nice text describing the usage and current recommended values
here..




Martinsen Expires April 21, 2016 [Page 2]

Internet-Draft ICE Timers October 2015


4. Pacing

4.1. Keep-Alive

4.2. Consent

5. IANA Considerations

None.

6. Acknowledgements

Todo

7. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
.

[RFC5245] Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", RFC 5245, DOI
10.17487/RFC5245, April 2010,
.

Author's Address

Paal-Erik Martinsen
Cisco Systems, Inc.
Philip Pedersens Vei 22
Lysaker, Akershus 1325
Norway

Email: palmarti@cisco.com















Martinsen Expires April 21, 2016 [Page 3]