[sipcore] Proposal to revise the dual stack milestone

worley@ariadne.com (Dale R. Worley) Sun, 30 April 2017 20:48 UTC

Return-Path: <worley@alum.mit.edu>
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 52289129441 for <sipcore@ietfa.amsl.com>; Sun, 30 Apr 2017 13:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.766
X-Spam-Level:
X-Spam-Status: No, score=0.766 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 RI-UZ2qzCH53 for <sipcore@ietfa.amsl.com>; Sun, 30 Apr 2017 13:48:27 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 3F996127863 for <sipcore@ietf.org>; Sun, 30 Apr 2017 13:46:15 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-01v.sys.comcast.net with SMTP id 4vj8dIaoPO3Qo4vjSdGiY5; Sun, 30 Apr 2017 20:46:14 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-18v.sys.comcast.net with SMTP id 4vjRd4fGSStKd4vjRdW8lK; Sun, 30 Apr 2017 20:46:14 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v3UKk7tR026757 for <sipcore@ietf.org>; Sun, 30 Apr 2017 16:46:07 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v3UKk7eP026753; Sun, 30 Apr 2017 16:46:07 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: sipcore@ietf.org
Sender: worley@ariadne.com
Date: Sun, 30 Apr 2017 16:46:07 -0400
Message-ID: <87bmrdmxo0.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfGLUi1mH9sRdvbUnPP8yPuY43C03VzQwZxwQueBeZ3F8UTwixdtS5zeLdiWh4SSsyLnO+VsC/WuOttwtNhLs78pVkWXVGqJBZMpQBoyYuQejFpmWCFzG bB2MUHRZBU598iRXs44AtpMrotWeJUkW2txcdhiGDQcUPUz53WEelexu
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/fEfIf5eYmUU2e6sSusz11wngOuY>
Subject: [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: Sun, 30 Apr 2017 20:48:28 -0000

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