Re: [rtcweb] HIP option for draft-ietf-rtcweb-overview and which ICE?

Iñaki Baz Castillo <ibc@aliax.net> Thu, 29 September 2011 21:26 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E592B21F8E07 for <rtcweb@ietfa.amsl.com>; Thu, 29 Sep 2011 14:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJYhleXbpFWk for <rtcweb@ietfa.amsl.com>; Thu, 29 Sep 2011 14:26:43 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8CC21F8E02 for <rtcweb@ietf.org>; Thu, 29 Sep 2011 14:26:43 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so1261295vcb.31 for <rtcweb@ietf.org>; Thu, 29 Sep 2011 14:29:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.151.19 with SMTP id a19mr3135632vcw.6.1317331774846; Thu, 29 Sep 2011 14:29:34 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Thu, 29 Sep 2011 14:29:34 -0700 (PDT)
In-Reply-To: <CAAA4416.1E0DC%henry.sinnreich@gmail.com>
References: <EBECF0F0-B158-47B2-9740-C93E398D58D9@cisco.com> <CAAA4416.1E0DC%henry.sinnreich@gmail.com>
Date: Thu, 29 Sep 2011 23:29:34 +0200
Message-ID: <CALiegfkdogwLDd8LEdot9OCs-nWzJ2uxCfGZaN2veTSCmpifUA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Henry Sinnreich <henry.sinnreich@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: stiemerling@nw.neclab.eu, "rtcweb@ietf.org" <rtcweb@ietf.org>, lars.eggert@nokia.com, quittek@nw.neclab.eu
Subject: Re: [rtcweb] HIP option for draft-ietf-rtcweb-overview and which ICE?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Sep 2011 21:26:44 -0000

2011/9/29 Henry Sinnreich <henry.sinnreich@gmail.com>:
> Sorry, my shortened link was not inaccurate. It is
> http://tools.ietf.org/html/draft-rosenberg-mmusic-ice-nonsip-01

Abstract
   Interative Connectivity Establishment (ICE) has been specified as a
  NAT traversal mechanism for protocols based on the offer/answer
exchange model.  In practice, only the Session Initiation Protocol
(SIP) has used ICE.  This document provides guidance on how other
protocols can make use of ICE.


Well, "only the Session Initiation Protocol (SIP) has used ICE"...
I would replace that with "ICE has been initially specified for SIP"
(the usage of ICE in SIP is just anecdotal, ICE is more used in
XMPP-Jingle than in SIP).


-- 
Iñaki Baz Castillo
<ibc@aliax.net>