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

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Mon, 15 May 2017 20:37 UTC

Return-Path: <gsalguei@cisco.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 70A5A129B8C for <sipcore@ietfa.amsl.com>; Mon, 15 May 2017 13:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 OrpAAAk_RhUH for <sipcore@ietfa.amsl.com>; Mon, 15 May 2017 13:37:56 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B023129AD4 for <sipcore@ietf.org>; Mon, 15 May 2017 13:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17562; q=dns/txt; s=iport; t=1494880515; x=1496090115; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=IEHMbMvajkhXfBaxphypdGshcS7THABxQZbRScpKIvY=; b=jAOwiAdvUWHl0Acmi6s20gjDPrUApU71bFwLQv/IysOujhfFh5SeMvkB mHTkvx5DFF3rXXDyyrcfXd1Al3rKY2OuUbyj48y8NMKp7k0YvNjJIKxB5 EfGPx3SSbuIrbZCjPmuMeScmcOkkQM5UFdelyq4a3/D3HoLHdHlpn/P1J g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BQAQCoDxpZ/4MNJK1cGQEBAQEBAQEBAQEBBwEBAQEBgm5nYoEMB4NkihiRYJA9hTiCDyEBCoUuSgIahRw/GAECAQEBAQEBAWsohRgBAQEBAwEBIUsLDAQCAQgRBAEBKAMCAgIlCxQJCAIEDgUbiggOrF+CJop6AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWGX4IJgnCHdS+CMQEElm+HGwGHG4t/C4F5j2eIf4tDAR84gQpwFUYSAYZjdodfgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.38,346,1491264000"; d="scan'208,217";a="426192739"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 May 2017 20:35:14 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v4FKZD9k001851 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 15 May 2017 20:35:13 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 15 May 2017 15:35:13 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1210.000; Mon, 15 May 2017 15:35:13 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "A. Jean Mahoney" <mahoney@nostrum.com>
CC: "Asveren, Tolga" <tasveren@sonusnet.com>, "Dale R. Worley" <worley@ariadne.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Thread-Topic: [sipcore] Proposal to revise the dual stack milestone
Thread-Index: AQHSwfMi1SPtLrxom0ufEMFt41ORJKHfZhwAgBbNGYCAABI4gA==
Date: Mon, 15 May 2017 20:35:13 +0000
Message-ID: <ED38E7C8-946F-4E31-AB1E-14FEC90010F3@cisco.com>
References: <87bmrdmxo0.fsf@hobgoblin.ariadne.com> <SN2PR03MB2350EF19DEF8578C7BD35002B2140@SN2PR03MB2350.namprd03.prod.outlook.com> <6d628729-482d-aace-0bb8-ab579d9e316c@nostrum.com>
In-Reply-To: <6d628729-482d-aace-0bb8-ab579d9e316c@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.250.251]
Content-Type: multipart/alternative; boundary="_000_ED38E7C8946F4E31AB1E14FEC90010F3ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/gw7aLdtA117bQWVN_BZCP2ucd7s>
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 20:37:58 -0000

Hi Jean -

There are two distinct sub-milestones for this milestone, in my opinion.  The first one is narrower and can be scoped as Dale indicated:

       Request publication of a mechanism for rapid dual-stack
       protocol selection in SIP when the destination has multiple,
       unprioritized targets for connection-oriented protocols

I think draft-johansson-sip-he-connection can be adopted for this.

Subsequently we hope to provide a more comprehensive dual-stack solution for SIP along the lines of draft-worley-sipcore-happy-earballs. My preference is we give the latter its due rigor and focus, so I don’t think they should be done in parallel, rather in series.

Thanks,

Gonzalo


On May 15, 2017, at 3:30 PM, A. Jean Mahoney <mahoney@nostrum.com<mailto:mahoney@nostrum.com>> wrote:

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<mailto: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<mailto:sipcore@ietf.org> https://www.ietf.org/mailman/listinfo/sipcore
_______________________________________________ sipcore mailing list sipcore@ietf.org<mailto:sipcore@ietf.org> https://www.ietf.org/mailman/listinfo/sipcore

_______________________________________________
sipcore mailing list
sipcore@ietf.org<mailto:sipcore@ietf.org>
https://www.ietf.org/mailman/listinfo/sipcore