IETF Logo Mail Archive

Re: [Rum] IPv6 support

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 12 March 2021 18:25 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BB83A1A41 for <rum@ietfa.amsl.com>; Fri, 12 Mar 2021 10:25:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1ro445JaCKY for <rum@ietfa.amsl.com>; Fri, 12 Mar 2021 10:25:16 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2043.outbound.protection.outlook.com [40.107.220.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCDCB3A1A40 for <rum@ietf.org>; Fri, 12 Mar 2021 10:25:16 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oNZrgC2JZ8br/VNhyLH7rPu0nsRAKTx43U8gdyGHX0mxi/QwkphXg1p2r12d59VugwOLmrurm6ZDi1yrxALBlL+x4L6QDjpOFNow1ev0JaYkE02QCsR/NyDp1Sz2DSXJek3DZvNhHL62Xsf4VGRne9DlHn6TVVdMeJxOjH9UsWWtgRU0UBWGRQMk3/8KCE3ikBha9WtQiPHTjQRKnY2GDdd7/doMZ5odAOyoQ3H+U7NZAbLCiDkVORLSDZIOUn5FCMexefoBB50Ie8rVEWENr4hTH0E5tdQfUADv/IOIXnqwH/zl4XG680p2W8qhh5laBvcjt4IFvn1Xph9bRKEKwQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fRLHEdNYD+mSGOvFzfSS2u0bDb6LkrVzAMXRcSf6Lpg=; b=ihw7XCQnkAEKKFTzEamIW66TcyjsAhs6H+3Dqt7Y11PL4goqkokZYb/vG55vmk5yquhfo22fPl91uuUEEf0HEDfLYX6TqSiJOdBsDXKXWyoZ4bn/A8z5G9X0v5H8TzNsn7kDEvLueu2zHGMpYmX1Q2q4whX5d55CYJKbhJ7dt5APbnZNHe2qPskoH5QlXT537Wnu72L8dvT9k+sKuQJkUx92pb+zG7OwVkgkMy870IBM4qUUaj9HwA6TI4uB2Z7WItKe+EByjkogKRBhaRrgMMnbYUytP31uognErGhnoOBHYHyXmr/T2khGWUGG3w6odnPGil+GCdVv2GgU9ok0FQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=edvina.net smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fRLHEdNYD+mSGOvFzfSS2u0bDb6LkrVzAMXRcSf6Lpg=; b=YZAko9DhTFZLaiJIyO4eAiWMZuSWmtsODq9YHaa4uakCK7SHuhnvtMx+Hr1XgxEOQJQLQ1Pf2J1PIzOrfEMseMbF08biAxh37yPdFLJuWUriawJgjNi27lo524KDicmgqLI2sq7YBG+lMl2pxgG/wQP67p1n5H07BYvRb+FoaXU=
Received: from SA9PR13CA0035.namprd13.prod.outlook.com (2603:10b6:806:22::10) by SN1PR12MB2397.namprd12.prod.outlook.com (2603:10b6:802:27::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.21; Fri, 12 Mar 2021 18:25:15 +0000
Received: from SN1NAM02FT015.eop-nam02.prod.protection.outlook.com (2603:10b6:806:22:cafe::f) by SA9PR13CA0035.outlook.office365.com (2603:10b6:806:22::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.11 via Frontend Transport; Fri, 12 Mar 2021 18:25:15 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; edvina.net; dkim=none (message not signed) header.d=none;edvina.net; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT015.mail.protection.outlook.com (10.152.72.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3912.25 via Frontend Transport; Fri, 12 Mar 2021 18:25:13 +0000
Received: from MacBook-Air.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 12CIPBUP021866 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 12 Mar 2021 13:25:11 -0500
To: "Olle E. Johansson" <oej@edvina.net>
Cc: rum@ietf.org
References: <AEA553BF-3F7C-402B-B184-99224EC0AFD9@brianrosen.net> <1658FF38-1A4E-462D-BBD0-D3D807655DA3@edvina.net> <6e181cd2-0e22-bd6b-1558-9b6796ea820c@alum.mit.edu> <D9C677BC-3266-435A-B5E9-662A40B4A1A7@edvina.net>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8163cf21-1c86-f435-9015-3bfa22d4d425@alum.mit.edu>
Date: Fri, 12 Mar 2021 13:25:11 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.8.0
MIME-Version: 1.0
In-Reply-To: <D9C677BC-3266-435A-B5E9-662A40B4A1A7@edvina.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3261756f-278c-4f83-dd32-08d8e5842db4
X-MS-TrafficTypeDiagnostic: SN1PR12MB2397:
X-Microsoft-Antispam-PRVS: <SN1PR12MB23972A955A84983DFF12062DF96F9@SN1PR12MB2397.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:8882;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: mmynne6Is8uYs2C2ij1T8OSdLci26L2+84tFFWxEBL8DJvJy6k7oXr7cADfda4oylcg2FiQV5Q5xIhVkjKqLNwlTt47kg/JwPatqvWWr1XX+ck17/F9g2OEdnAImzmGCKtUNtmIAdw1BzRqm3+j2HafBRhIUI3ArsuA5ZdVw7akRyA3FUxZ+LRRX8irzcCIurg6LS9frhmrhc63Vhr2Qa3RxipI6PPfQg7AO4yrIGo2iM14jQLxG2o+nwfyU/eRqjRuXNiz7iiLyr/6JJSqqmH8JMIMD4EucQzqcF+xYEpSYFsP5UXMC2UGbGsKYnUzhDb8yBvtk7YSwnir4nb2kIupiCm38BxZ7eJ9UitwyI26KdEfZTQQJptLGXDpywANs4s8CVUeNrNw9/q8bLLDlXbWZVlC1GynywvgvHpOOb6iNwjOch9sLlDG0hfFyGBCrhK9liSpQZXvxfLy+6DOLRvpSmWySH5U0rCmfKjr9li7BvhLq/FoHfn2BEKYYueZHpPJExJX06w6FVpMWhq6uoYOtrrGNBq8OWf2MHto76+4uZfI/Qpm64cVoYFowkMw7Bi+RdxKCkBzkhu/yaB5lwrd5BwiQI38mquyLVhWsb39jhw7kOgXFBGVzP/CliI41uTTMYfMkQOEWeWTxb/ODaP/EKrTpUOdhBRydMnfomUqNuHkK02agkrbbiY2WW3tisjCnp/IiQUrSUA3vtGdpVBHd0kaQCXIXozM1onlU9LM84w/27sygSdrlQ6URYyg1
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFS:(376002)(39860400002)(136003)(396003)(346002)(36840700001)(46966006)(7596003)(336012)(356005)(83380400001)(26005)(70586007)(8676002)(82310400003)(478600001)(70206006)(966005)(47076005)(6916009)(36860700001)(956004)(36906005)(31686004)(86362001)(31696002)(316002)(4326008)(786003)(2906002)(75432002)(2616005)(53546011)(186003)(5660300002)(8936002)(82740400003)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 12 Mar 2021 18:25:13.5298 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 3261756f-278c-4f83-dd32-08d8e5842db4
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-AuthSource: SN1NAM02FT015.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR12MB2397
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/Z9Gt4WLQ9iG9fytZpn0y-DObybM>
Subject: Re: [Rum] IPv6 support
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2021 18:25:19 -0000

On 3/12/21 1:05 PM, Olle E. Johansson wrote:
> 
> 
>> On 12 Mar 2021, at 17:29, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> On 3/11/21 1:57 AM, Olle E. Johansson wrote:
>>>> On 10 Mar 2021, at 22:08, Brian Rosen <br@brianrosen.net <mailto:br@brianrosen.net>> wrote:
>>>>
>>>> We’re still having discussions on IPv6 mandatory to support.
>>>>
>>>> ISTM that since some very important systems are IPv6 only, and most ISPs are supporting both, that it’s hard to not require support for it.  In the meeting Adam discussed using gateways and 4-in-6 support.  We need to decide what to do.  I point out that many SBCs are capable of being a fully functional B2BUA and media relay with IPv4 or IPv6 on either side.  Since it already rewrites addresses for both signaling and media it has no issues supporting IPv6 on one side and IPv4 on the other side.  I am checking on support for IPv6 addresses in US auditing/reporting CDRs and will report my findings shortly.  I would like to just require both sides to support IPv6, without saying how.
>>>>
>>>> Other thoughts?
>>> IPv6 has to get in.
>>> Both IETF and the SIP forum has produced documents on dual stack behaviour and there’s a lot of potential
>>> issues to be aware of there. SIPconnect 2.0 also added some helpful guidelines.
>>
>> Thanks for the useful pointers.
>>
>>> https://www.rfc-editor.org/rfc/rfc7984.html <https://www.rfc-editor.org/rfc/rfc7984.html>
>>> https://www.sipforum.org/activities/technical-wg-overview-and-charter/ipv6-task-group-charter/ <https://www.sipforum.org/activities/technical-wg-overview-and-charter/ipv6-task-group-charter/>
>>> https://tools.ietf.org/html/draft-klatsky-dispatch-ipv6-impact-ipv4-02 <https://tools.ietf.org/html/draft-klatsky-dispatch-ipv6-impact-ipv4-02>
>>> https://www.sipforum.org/download/sipconnect-technical-recommendation-version-2-0/?wpdmdl=2818 <https://www.sipforum.org/download/sipconnect-technical-recommendation-version-2-0/?wpdmdl=2818>
>>
>> We might want to consider section 15 of the last reference above as a pattern that might meet our needs.
> 
> Yes, but at that point we declared ICE out of scope and as you pointed out, I think it’s very much IN
> scope for RUE.

That gives us a couple of different ways forward to consider.

	Thanks,
	Paul

v2.23.0 | Report a Bug | By Email