IETF Logo Mail Archive

Re: [sipcore] IPv6 in the sip core wg

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Thu, 06 March 2014 14:18 UTC

Return-Path: <gsalguei@cisco.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 6C2BE1A03B3 for <sipcore@ietfa.amsl.com>; Thu, 6 Mar 2014 06:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.047
X-Spam-Level:
X-Spam-Status: No, score=-15.047 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, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 XUvDfxY8sCMu for <sipcore@ietfa.amsl.com>; Thu, 6 Mar 2014 06:18:49 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9431A02F7 for <sipcore@ietf.org>; Thu, 6 Mar 2014 06:18:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4225; q=dns/txt; s=iport; t=1394115523; x=1395325123; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ovz/KOE7GcLUASL/zbemXzdCYPyqwoQG4UbDHupTG9g=; b=jEthFC4mMBdDPuYFHC6O+Scf1tmlVZeceDd5qKMnDq2MSFdrbRZUg1Rb lPzWyfL4xxERNzMAn7fjsnxtRRyaT0mrUIEn0QU1Z16yZLrQt1oA5azST EF8wv0DjO8Z9vOvwm29/0cEJcH0gN9XSiXTKMCd6UnF/HzNx9ZaiJbMnZ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIFALeCGFOtJXHA/2dsb2JhbABagwaBBgzBH4EXFnSCJgEBBClQEAIBAgYEOwcyFBECBA4Fh3nPJheOWwYBgySBFASYPpIrgy2CKg
X-IronPort-AV: E=Sophos; i="4.97,600,1389744000"; d="scan'208,217"; a="308442149"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-2.cisco.com with ESMTP; 06 Mar 2014 14:18:43 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s26EIhQ9022671 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Mar 2014 14:18:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.27]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 6 Mar 2014 08:18:42 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: [sipcore] IPv6 in the sip core wg
Thread-Index: AQHO92PvPaG9LxtinkCT+HMY0fMEHQ==
Importance: high
X-Priority: 1
Date: Thu, 06 Mar 2014 14:18:42 +0000
Message-ID: <53C92953-3CC0-4738-A41F-61EEF3853514@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> <52DEF76B.9050706@nostrum.com> <BC2BF195-1140-48C4-AF4E-C4CC6951E2FB@cisco.com>
In-Reply-To: <BC2BF195-1140-48C4-AF4E-C4CC6951E2FB@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.214.181]
Content-Type: multipart/alternative; boundary="_000_53C929533CC04738A41F61EEF3853514ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sipcore/H9SSFmpd_MjmpIvLhnJEL3TQ7JI
Cc: Olle E Johansson <oej@edvina.net>, SIPCORE WG <sipcore@ietf.org>
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: Thu, 06 Mar 2014 14:18:51 -0000

As per our discussion during the meeting...

I propose we narrow the scope of the proposed milestone to better suit the existing work.  The following two word edit is proposed:

OLD:

June 2014  Request publication of procedures for dual-stack client and server handling of SIP URIs


June 2014  Request publication of DNS look-up procedures for dual-stack client and server handling of SIP URIs


Are folks ok with this new text?  After further study of SIP dual-stack gaps, as Dan York proposed we do, we can add appropriately scoped milestones as they arise.

Cheers,

Gonzalo


On Jan 21, 2014, at 10:42 PM, Cullen Jennings (fluffy) <fluffy@cisco.com<mailto:fluffy@cisco.com>> wrote:


works for me

On Jan 21, 2014, at 3:40 PM, Adam Roach <adam@nostrum.com<mailto:adam@nostrum.com>> wrote:

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

v2.23.0 | Report a Bug | By Email