IETF Logo Mail Archive

Re: [sipcore] IPv6 in the sip core wg

Cullen Jennings <fluffy@iii.ca> Mon, 16 December 2013 19:31 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D6E71A1F4C for <sipcore@ietfa.amsl.com>; Mon, 16 Dec 2013 11:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
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 4rOvsuSzl1Tw for <sipcore@ietfa.amsl.com>; Mon, 16 Dec 2013 11:31:01 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA0E1A1F3D for <sipcore@ietf.org>; Mon, 16 Dec 2013 11:31:01 -0800 (PST)
Received: from [192.168.4.100] (unknown [128.107.239.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F10E050A86; Mon, 16 Dec 2013 14:30:59 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <FD51E29F-9CD3-42F7-B7F6-DB09A60701C9@edvina.net>
Date: Mon, 16 Dec 2013 12:30:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5673C5D-E520-4EB1-8983-977398FB15F1@iii.ca>
References: <C774C9EA-4E79-4846-A834-BF86D2DD8018@edvina.net> <52A2094E.8020009@alum.mit.edu> <86897DAD-AEAE-4EEC-BCEC-D8501D8491D2@cisco.com> <CAHBDyN7AT0m7P5miYa+hCvh55Ov3f1Nc-U1zUK6H-0i4aHTW+g@mail.gmail.com> <52A7486E.2090005@alum.mit.edu> <FFB57ECD-8CDB-44E9-9A3F-5418AAC01C5B@iii.ca> <26C3B24F-FCBE-4D10-ADD5-E28B6E95A8FB@edvina.net> <BCD747C2-B0E9-492E-97E2-58B078AF5F74@iii.ca> <E9BFFB26-2E71-42D3-A126-0DA7535DD688@edvina.net> <7886ADB0-BDB3-4D15-800B-AAEB34713547@iii.ca> <FD51E29F-9CD3-42F7-B7F6-DB09A60701C9@edvina.net>
To: "Olle E. Johansson" <oej@edvina.net>
X-Mailer: Apple Mail (2.1510)
Cc: SIPCORE WG <sipcore@ietf.org>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Subject: Re: [sipcore] IPv6 in the sip core wg
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Dec 2013 19:31:03 -0000

On Dec 13, 2013, at 9:17 AM, Olle E. Johansson <oej@edvina.net> wrote:

> The problem is really that RFC 3263 repeats "A or AAAA" - which means that if we follow RFC 3263 verbatim we won't have both IPv4 and IPv6 addresses to connect to. I have not claimed that it talks about how we connect.

A or B does not mean you are not allowed to do both

v2.23.0 | Report a Bug | By Email