IETF Logo Mail Archive

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

"cb.list6" <cb.list6@gmail.com> Mon, 09 September 2013 16:50 UTC

Return-Path: <cb.list6@gmail.com>
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 D8E5B11E8109 for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 09:50:59 -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 qdWu7NUA0-Fy for <rtcweb@ietfa.amsl.com>; Mon, 9 Sep 2013 09:50:59 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E686021F9E9A for <rtcweb@ietf.org>; Mon, 9 Sep 2013 09:50:29 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id c10so3682343wiw.5 for <rtcweb@ietf.org>; Mon, 09 Sep 2013 09:50:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Fvn9KzcNTn1cHMocST/sNX9yh57Pb1k6EAQTES/8Qws=; b=Jf990w8NV0vyT/5whkWJ6cugPr9sOlM8TU7Q2Dic1rysSIfPwKjWMBPPiOY1UM/Mut G+MsffCScMhT8IM7eGyW3vg+zoPH4rUKonDQZbUkt5CdrqjiePVuGU+qsIkijgUoE8ZE jxN9dOVDYn4QARNJZEoeRx/9TjXWabpXATSCaCzqF8F28q9XRqGp8oWqsNYAgVqGq5OI jkCZFPw2oBBEAThY/oDZGPQLmo46fmD7Vdh7e7LGwCKj5BW+YZP6AhFZR+RQUJCwgKHp uRTjSxep71Gu8pBm8EafeOS+6nZLjUa+mkMjkpM73jb3fDa+8nIR1XmzntEBEPTXI0wk cYxw==
MIME-Version: 1.0
X-Received: by 10.194.134.97 with SMTP id pj1mr1726537wjb.58.1378745429117; Mon, 09 Sep 2013 09:50:29 -0700 (PDT)
Received: by 10.217.114.137 with HTTP; Mon, 9 Sep 2013 09:50:29 -0700 (PDT)
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17BBC905@MCHP04MSX.global-ad.net>
References: <20130903094045.23789.92925.idtracker@ietfa.amsl.com> <5225B1AF.7050906@alvestrand.no> <9F33F40F6F2CD847824537F3C4E37DDF17BBC905@MCHP04MSX.global-ad.net>
Date: Mon, 09 Sep 2013 09:50:29 -0700
Message-ID: <CAD6AjGQXhGRBJxFtAF5oUa5mR_BPrPisPphdS9hdYVOP3Ez+Ng@mail.gmail.com>
From: "cb.list6" <cb.list6@gmail.com>
To: "Hutton, Andrew" <andrew.hutton@siemens-enterprise.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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:51:00 -0000

On Mon, Sep 9, 2013 at 9:36 AM, Hutton, Andrew
<andrew.hutton@siemens-enterprise.com> wrote:
> 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".
>
> 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?
>

+1 on covering IPv6 in the transport draft.

I would specifically state that much of the challenges with NATs are
resolved by preferring IPv6.

I would also cover the use case of using TURN to bridge IPv6-only
clients to communicate with IPv4 clients.

It would also be wise to reference RFC6540 to underscore that IPv6 use
is a BCP of the IETF

CB


> Regards
> Andy
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email