Re: [sipcore] Proposal to revise the dual stack milestone

"A. Jean Mahoney" <mahoney@nostrum.com> Mon, 15 May 2017 19:33 UTC

Return-Path: <mahoney@nostrum.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF225128D69 for <sipcore@ietfa.amsl.com>; Mon, 15 May 2017 12:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.018
X-Spam-Level:
X-Spam-Status: No, score=0.018 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=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 lL-HaD7EBxmY for <sipcore@ietfa.amsl.com>; Mon, 15 May 2017 12:33:12 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 498061292C5 for <sipcore@ietf.org>; Mon, 15 May 2017 12:30:04 -0700 (PDT)
Received: from mutabilis-2.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v4FJU13F091689 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 15 May 2017 14:30:01 -0500 (CDT) (envelope-from mahoney@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be mutabilis-2.local
To: "Asveren, Tolga" <tasveren@sonusnet.com>, "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>
References: <87bmrdmxo0.fsf@hobgoblin.ariadne.com> <SN2PR03MB2350EF19DEF8578C7BD35002B2140@SN2PR03MB2350.namprd03.prod.outlook.com>
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <6d628729-482d-aace-0bb8-ab579d9e316c@nostrum.com>
Date: Mon, 15 May 2017 14:30:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <SN2PR03MB2350EF19DEF8578C7BD35002B2140@SN2PR03MB2350.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/MupGXAYU-rchxzlnD2c-MaMTE_U>
Subject: Re: [sipcore] Proposal to revise the dual stack milestone
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 15 May 2017 19:33:14 -0000

Hi everyone,

Does anyone else have any thoughts on modifying the milestone?

As the WG finishes up some of the current milestones and adds new WG 
documents, we'll need to update our milestone list.

Thanks!

Jean

On 5/1/17 2:18 AM, Asveren, Tolga wrote:
> I think that is a good idea with a few caveats:
> 
> i- Connectionless transports should be covered as well (possibly by
> making use of OPTIONS) ii- Use of multiple interfaces/transport
> protocols should be mentioned as well. I think this can be done just
> by adding a few sentences along the lines of: All IP Address
> Family/Transport Family/Interface triplet combinations should be
> tried simultaneously. Some headstart may be provided for certain
> combinations depending on local policy.
> 
> Otherwise I think it is the right approach not to dive into details
> of the algorithm to use.
> 
> Thanks, Tolga
> 
> -----Original Message----- From: sipcore
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Dale R. Worley Sent:
> Sunday, April 30, 2017 4:46 PM To: sipcore@ietf.org Subject:
> [sipcore] Proposal to revise the dual stack milestone
> 
> The Sipcore working group has the following milestone listed (at 
> https://datatracker.ietf.org/wg/sipcore/about/):
> 
> Dec 2017        Request publication of mechanisms for rapid
> dual-stack protocol selection in SIP
> 
> The draft draft-johansson-sip-he-connection is listed for this
> milestone.  However, that draft covers only a narrow subset of the
> overall problem.
> 
> Over the past month or so, I have been canvassing Sipcore members to
> find out if there is any practical demand for a dual-stack solution
> for SIP.  With the exception of a particular case, I have found no
> interest.
> 
> Because of this, I propose that we narrow the scope of this milestone
> to the one case for which I have found interest:
> 
> Request publication of a mechanism for rapid dual-stack protocol
> selection in SIP when the destination has multiple, unprioritized
> targets for connection-oriented protocols
> 
> Conveniently, draft-johansson-sip-he-connection describes such a
> mechanism.  Its mechanism closely parallels that of RFC 6555 ("Happy
> Eyeballs"), and the text is essentially complete.  Because there are
> no unresolved technical issues, the text is complete, and there are
> known implementation instances where this mechanism is needed, I urge
> the approval of this draft even if its scope is narrow.
> 
> Dale
> 
> _______________________________________________ sipcore mailing list 
> sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore
> 
> _______________________________________________ sipcore mailing list 
> sipcore@ietf.org https://www.ietf.org/mailman/listinfo/sipcore
>