Re: [sipcore] IPv6 in the sip core wg
Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 18 December 2013 17:12 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 C979B1ADED7 for <sipcore@ietfa.amsl.com>; Wed, 18 Dec 2013 09:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 O_DyltTR3zCJ for <sipcore@ietfa.amsl.com>; Wed, 18 Dec 2013 09:12:54 -0800 (PST)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6351ADEBA for <sipcore@ietf.org>; Wed, 18 Dec 2013 09:12:54 -0800 (PST)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta01.westchester.pa.mail.comcast.net with comcast id 30a71n0041GhbT8515CsEh; Wed, 18 Dec 2013 17:12:52 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id 35Cs1n00A3ZTu2S3T5CssD; Wed, 18 Dec 2013 17:12:52 +0000
Message-ID: <52B1D794.1080602@alum.mit.edu>
Date: Wed, 18 Dec 2013 12:12:52 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <C774C9EA-4E79-4846-A834-BF86D2DD8018@edvina.net> <86897DAD-AEAE-4EEC-BCEC-D8501D8491D2@cisco.com> <CAHBDyN7AT0m7P5miYa+hCvh55Ov3f1Nc-U1zUK6H-0i4aHTW+g@mail.gmail.com> <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>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B0FA8CF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1387386772; bh=dQyXW+ENODLBh2bYVXlhshx1xNqUyFxDE9H+6MVMbq8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=EA7P1m73fXe7oPJHqPfOIU78kz3DTzEazBAQj1DCcPOsqbUTpff/5BwNnwIr8JIlf NTd7+5N1ib64Xdm1YSgUTJ9fikPFIIeH1MVjnOYlUv4YNDu+PjVXZ4jr5LsXlYpaP7 5GCgwmvbJer+4WE4m5CDoz4865a6w6ZeR38ispTY0h7iZvRhy4AYCMveRbQ0iMD38M P7RlwLGztEVD4zZ6Y+poiPhmuBdfYSe3rvv/yuiqPvFAUoBhaT/GtRA3/pYVpADYhD 8y32hFEgn1LfsxGoPaPQq0ZwezPXj1P8kVwHZpajMPSGMcb9tM4BKPYio7QMUWRhgf HpXfDcDIW9VNg==
Cc: SIPCORE WG <sipcore@ietf.org>, "Olle E. Johansson" <oej@edvina.net>, "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: Wed, 18 Dec 2013 17:12:56 -0000
On 12/17/13 6:54 PM, DRAGE, Keith (Keith) wrote: > I said in a previous mail that I would like to avoid the use of the word "supplement" and did suggest alternative wording. My reason is that some SDOs treat the word "supplement" as identifying informative material, and given that you want reuse in other SDOs it is best not to confuse the issue. I don't see why that should prevent us from using "supplement" in this context. We can have that discussion again if the word is used in a draft, but I don't see why it's a concern there either. (The definitive indication is whether the RFC is standards track, and the normative language in the draft.) > In any case I don't think we need to bring out in either the title or the milestone the exact relationship with RFC 3263, only that one exists. Defining that relationship more accurately belongs to the abstract. My latest proposal was: June 2014 Request publication of procedures to supplement RFC3263 and RFC6157 for dual-stack client and server handling of SIP URIs containing domain names (PS) Your earlier proposal was: "Use of RFC 3263 in dual-stack devices". RFC6157 already addresses dual-stack devices. What we are trying to deal with is that 3263 and 6157 are insufficient and/or wrong for dual-stack clients. I see no way to avoid using *some* verb - supplement, update, clarify, expand, ... Feel free to offer something that addresses both your concerns and the others that have been raised. Thanks, Paul > Keith > >> -----Original Message----- >> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu] >> Sent: 16 December 2013 20:01 >> To: Cullen Jennings (fluffy) >> Cc: Gonzalo Salgueiro (gsalguei); DRAGE, Keith (Keith); >> SIPCORE WG; Olle E. Johansson >> Subject: Re: [sipcore] IPv6 in the sip core wg >> >> On 12/16/13 2:33 PM, Cullen Jennings (fluffy) wrote: >>> >>> On Dec 13, 2013, at 9:28 AM, Paul Kyzivat >> <pkyzivat@alum.mit.edu> wrote: >>> >>>> Having said that, I suggest the following as the milestone: >>>> >>>> May 2014 WGLC of procedures to supplement RFC3263 for >> dual-stack >>>> client and server handling of SIP URIs containing domain names >>>> (PS) >>> >>> Good with me. And if you want to change "WGLC of" to >> "Request publication of" that seems like it would fix the >> point Mary raised. >> >> OK. Latest candidate is: >> >> June 2014 Request publication of procedures to >> supplement RFC3263 >> for dual-stack client and server handling of SIP URIs containing >> domain names (PS) >> >> (I put back the extra month for Mary.) >> >> Richard - does this work for you? >> >> Thanks, >> Paul >> >> >> >>
- [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Mary Barnes
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Mary Barnes
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg DRAGE, Keith (Keith)
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg DRAGE, Keith (Keith)
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Vijay K. Gurbani
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg DRAGE, Keith (Keith)
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Vijay K. Gurbani
- Re: [sipcore] IPv6 in the sip core wg Mary Barnes
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings (fluffy)
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Richard Barnes
- Re: [sipcore] IPv6 in the sip core wg Vijay K. Gurbani
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Mary Barnes
- Re: [sipcore] IPv6 in the sip core wg Vijay K. Gurbani
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg DRAGE, Keith (Keith)
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Adam Roach
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings (fluffy)
- Re: [sipcore] IPv6 in the sip core wg Adam Roach
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings (fluffy)
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Paul Kyzivat
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson
- Re: [sipcore] IPv6 in the sip core wg Vijay K. Gurbani
- Re: [sipcore] IPv6 in the sip core wg Dale R. Worley
- Re: [sipcore] IPv6 in the sip core wg Gonzalo Salgueiro (gsalguei)
- Re: [sipcore] IPv6 in the sip core wg Cullen Jennings (fluffy)
- Re: [sipcore] IPv6 in the sip core wg Olle E. Johansson