IETF Logo Mail Archive

Re: [sipcore] IPv6 in the sip core wg

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 17 December 2013 23:55 UTC

Return-Path: <keith.drage@alcatel-lucent.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 E22911ADE8B for <sipcore@ietfa.amsl.com>; Tue, 17 Dec 2013 15:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-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 v8rGJgWoHD0P for <sipcore@ietfa.amsl.com>; Tue, 17 Dec 2013 15:55:26 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE561AD9AC for <sipcore@ietf.org>; Tue, 17 Dec 2013 15:55:26 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id rBHNswxf004176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 17 Dec 2013 17:55:00 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rBHNsvL8015984 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Dec 2013 00:54:57 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.203]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 18 Dec 2013 00:54:56 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Thread-Topic: [sipcore] IPv6 in the sip core wg
Thread-Index: AQHO9f1rFmxMwFa6OUik7RkhLMXct5pXNmkAgAHP3sA=
Date: Tue, 17 Dec 2013 23:54:55 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B0FA8CF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <C774C9EA-4E79-4846-A834-BF86D2DD8018@edvina.net> <52A2094E.8020009@alum.mit.edu> <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>
In-Reply-To: <52AF5C0C.9000206@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
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, 17 Dec 2013 23:55:28 -0000

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.

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.

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
> 
> 
> 
>

v2.23.0 | Report a Bug | By Email