Re: [sipcore] IPv6 in the sip core wg
Adam Roach <adam@nostrum.com> Tue, 21 January 2014 22:17 UTC
Return-Path: <adam@nostrum.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 2D93E1A01BB for <sipcore@ietfa.amsl.com>; Tue, 21 Jan 2014 14:17:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] 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 er8rrIEzYIVc for <sipcore@ietfa.amsl.com>; Tue, 21 Jan 2014 14:17:40 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 23EDD1A0127 for <sipcore@ietf.org>; Tue, 21 Jan 2014 14:17:40 -0800 (PST)
Received: from orochi-2.roach.at (99-152-145-110.lightspeed.dllstx.sbcglobal.net [99.152.145.110]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s0LMHMXQ030861 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 16:17:22 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <52DEF1ED.8040905@nostrum.com>
Date: Tue, 21 Jan 2014 16:17:17 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <C774C9EA-4E79-4846-A834-BF86D2DD8018@edvina.net> <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> <52B1D794.1080602@alum.mit.edu>
In-Reply-To: <52B1D794.1080602@alum.mit.edu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 99.152.145.110 is authenticated by a trusted mechanism)
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: Tue, 21 Jan 2014 22:17:42 -0000
It's really quite silly that we're blocked on a trivial matter of terminology here. Grabbing my thesaurus, I suggest: June 2014 Request publication of procedures to amend RFC3263 and RFC6157 for dual-stack client and server handling of SIP URIs containing domain names (PS) Does that work for everyone? /a On 12/18/13 11:12, Paul Kyzivat wrote: > 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 mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore
- [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