Re: [sipcore] IPv6 in the sip core wg

Adam Roach <adam@nostrum.com> Tue, 21 January 2014 22:40 UTC

Return-Path: <adam@nostrum.com>
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 7E3DE1A02D2 for <sipcore@ietfa.amsl.com>; Tue, 21 Jan 2014 14:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
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 aCF83PMoaBzK for <sipcore@ietfa.amsl.com>; Tue, 21 Jan 2014 14:40:56 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id A2FD11A0263 for <sipcore@ietf.org>; Tue, 21 Jan 2014 14:40:56 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0LMemwK031797 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 16:40:48 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52DEF76B.9050706@nostrum.com>
Date: Tue, 21 Jan 2014 16:40:43 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <C774C9EA-4E79-4846-A834-BF86D2DD8018@edvina.net> <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> <52A8CFC3.3080309@alum.mit.edu> <CAHBDyN6qK6_Cone+wkrcV_LZCca3b_dbf6rkzwnATZg4R6kn5Q@mail.gmail.com> <52A9F990.1030201@alum.mit.edu> <40B29D11-A4EE-4F7B-97C9-612313CFFB7E@cisco.com> <949EF20990823C4C85C18D59AA11AD8B0F858B@FR712WXCHMBA11.zeu.alcatel-lucent.com> <A054AE81-F690-42DE-8B77-1F7E4F0EA7B1@cisco.com> <949EF20990823C4C85C18D59AA11AD8B0F87DC@FR712WXCHMBA11.zeu.alcatel-lucent.com> <A86516A3-8DAA-43B0-8345-7B26182B99E3@cisco.com> <52AB35A6.8030701@alum.mit.edu> <597D373F-6ACF-4D81-83F0-8CB5A08202E1@cisco.com> <52AF5C0C.9000206@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B0FA8CF@FR712WXCHMBA11.zeu.alcatel-lucent.com> <52B1D794.1080602@alum.mit.edu> <52DEF1ED.8040905@nostrum.com> <2AF35782-4049-4AD6-B1E6-A97171DB94EE@cisco.com>
In-Reply-To: <2AF35782-4049-4AD6-B1E6-A97171DB94EE@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
Cc: Olle E Johansson <oej@edvina.net>, 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: Tue, 21 Jan 2014 22:40:57 -0000

On 1/21/14 16:24, Cullen Jennings (fluffy) wrote:
> No, that implies that 3263 and 6157 are wrong and products that implement need to change - If you want that milestone, first you need to be able be clear about what is wrong with 3263 or 6157.  How about
>
>> June 2014  Request publication of procedures for dual-stack client and server handling of SIP URIs

That runs the risk of being confused with what 6157 already does. How about:

    June 2014 Request publication of Happy Eyeballs procedures for 
handling of SIP URIs

Which seems a fair summary of what Olle and Gonzalo's current document 
intends to do.

/a