Re: [rtcweb] draft-ietf-rtcweb-transports-01 TURN/IPV6 RFC 6156.

Simon Perreault <simon.perreault@viagenie.ca> Mon, 09 September 2013 16:44 UTC

Return-Path: <simon.perreault@viagenie.ca>
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 44D9911E8155 for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 09:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 j8JSIbgtGiPB for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 09:44:32 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9D51211E80D7 for <rtcweb@ietf.org>; Mon, 9 Sep 2013 09:44:32 -0700 (PDT)
Received: from [IPv6:::1] (unknown [IPv6:2001:660:3001:4012:245a:a34b:600:fe8b]) by jazz.viagenie.ca (Postfix) with ESMTPSA id AA81F4039A for <rtcweb@ietf.org>; Mon, 9 Sep 2013 12:44:31 -0400 (EDT)
Message-ID: <522DFAEE.3060200@viagenie.ca>
Date: Mon, 09 Sep 2013 18:44:30 +0200
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20130903094045.23789.92925.idtracker@ietfa.amsl.com> <5225B1AF.7050906@alvestrand.no> <9F33F40F6F2CD847824537F3C4E37DDF17BBC905@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BBC905@MCHP04MSX.global-ad.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [rtcweb] draft-ietf-rtcweb-transports-01 TURN/IPV6 RFC 6156.
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: Mon, 09 Sep 2013 16:44:33 -0000

Le 2013-09-09 18:36, Hutton, Andrew a écrit :
> Currently draft-ietf-rtcweb-transports-01 does not say anything about IPV6 which I assume it should. Specifically I am thinking that it needs to state a requirement to support RFC6156 support "Traversal Using Relays around NAT (TURN) Extension for IPv6".

+1

> I am not sure how much we need to say about webrtc client procedures around RFC6156 and whether they should be included in the draft-ietf-rtcweb-transport or whether it is something we should add to our nat/firewall draft (draft-hutton-rtcweb-nat-firewall-considerations).  Any opinions on this?

Something along the lines of "IPv6 allocations MUST be requested even
when the client only has IPv4 connectivity." ?

Simon