Re: [sipcore] IPv6 in the sip core wg

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Tue, 10 December 2013 17:08 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 3D08A1AE222 for <sipcore@ietfa.amsl.com>; Tue, 10 Dec 2013 09:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level:
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 ra0wfz4EniKS for <sipcore@ietfa.amsl.com>; Tue, 10 Dec 2013 09:08:55 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 984081AE1F9 for <sipcore@ietf.org>; Tue, 10 Dec 2013 09:08:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2903; q=dns/txt; s=iport; t=1386695330; x=1387904930; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+/Ttqb3qATXB7Y+GGNCundWzoftINqmHgcTQSZO3mAk=; b=C1FrR63VMJ64/EfiCzBicYZA5KwEIp3+4hcgeGuCr242Rxk40MqdvlLQ w5zfMR3ZsTNM1G4k/INYt+oMj+Iu3OF4kUsQixGoM3EHpMeprxHAQrbXB W3vgUje2rRBznnubbBQODLp89++reEbQ6syEo/BuLWi+7R32wYipnW9k/ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAEVKp1KtJV2c/2dsb2JhbABZgwc4U7hQToEeFnSCJQEBAQMBAQEBJkULBQsCAQIGGC4hBgslAgQOBYdwAwkGDboVDYZnEwSMc4E+ITMHgyGBEwSJCo0fgWuMWoU5gymCKg
X-IronPort-AV: E=Sophos;i="4.93,865,1378857600"; d="scan'208";a="5722218"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-6.cisco.com with ESMTP; 10 Dec 2013 17:08:50 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBAH8oSF012398 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Dec 2013 17:08:50 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Tue, 10 Dec 2013 11:08:49 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Thread-Topic: [sipcore] IPv6 in the sip core wg
Thread-Index: AQHO8oXtPaG9LxtinkCT+HMY0fMEHZpH0MUAgAV1OYCAAK/bAIAAHqsA
Importance: high
X-Priority: 1
Date: Tue, 10 Dec 2013 17:08:49 +0000
Message-ID: <64750EC7-8E66-447B-8710-8FAD841DC457@cisco.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>
In-Reply-To: <CAHBDyN7AT0m7P5miYa+hCvh55Ov3f1Nc-U1zUK6H-0i4aHTW+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.239.182]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <702948BA8A94894EBCD3E235F19C3ECB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org" <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: Tue, 10 Dec 2013 17:08:57 -0000

Hi Mary - 

Agree with both points raised. Thanks.

Gonzalo

On Dec 10, 2013, at 10:19 AM, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:

> On Mon, Dec 9, 2013 at 10:49 PM, Gonzalo Salgueiro (gsalguei) <gsalguei@cisco.com> wrote:
> Paul -
> 
> On Dec 6, 2013, at 12:28 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> > Olle,
> >
> > Yes, this is something it seems evident we should take on.
> > I don't believe we need to change the "charter", but we should add a milestone for this.
> >
> > If you would like to propose milestone text (in the same style as the existing milestones) and take a first guess at a date for it, that would be great.
> 
> How about:
> 
> Apr 2014  Amended procedures for dual-stack server handling of SIP URIs containing domain names
> [MB] I would suggest to just use the term "Updated" as opposed to "Amended".
> While all of our dates are always optimistic, I think June 2014 is probably beyond the usually level of optimism, since that's the date for the doc to go to the IESG.   It often takes at least 2 months to get a doc from WGLC to ready for IESG review.  That would mean the document completes WGLC in February 2014.  If you think that's possible, then April is fine, but I would anticipate that it could take a tad longer. 
> [/MB] 
> 
> >
> > Now that we have this, and some other things, that are on the table we are planning on having a sipcore session in London. This will be one (or more) of the agenda items for that meeting.
> 
> Sounds good.
> 
> Gonzalo
> 
> >
> >       Thanks,
> >       Paul
> >
> > On 12/6/13 8:20 AM, Olle E. Johansson wrote:
> >> Hi!
> >>
> >> Coming back to an earlier discussion, it seemed to me that we had a few people that supported adding IPv6 dual stack issues to the charter of this wg - if it's not in there already.
> >>
> >> I would like to propose that we add this to the charter and that we plan a meeting at the IETF in London to discuss this and happy eyeballs issues.
> >>
> >> We have two drafts in the pipeline and one that should have been written about the actual happy eyeballs connection setup, but currently only exists as promiseware...
> >>
> >> /O
> >> _______________________________________________
> >> sipcore mailing list
> >> sipcore@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sipcore
> >>
> >
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore