Re: [v6ops] v6ops Draft minutes Thursday March 29th 15:20
Wuyts Carl <Carl.Wuyts@technicolor.com> Fri, 06 April 2012 06:19 UTC
Return-Path: <Carl.Wuyts@technicolor.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A8311E8086 for <v6ops@ietfa.amsl.com>; Thu, 5 Apr 2012 23:19:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TzidT2i+NB49 for <v6ops@ietfa.amsl.com>; Thu, 5 Apr 2012 23:19:15 -0700 (PDT)
Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8C011E8085 for <v6ops@ietf.org>; Thu, 5 Apr 2012 23:19:12 -0700 (PDT)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKT36K1mPq9pHigBIGU2sWlABilAT9i8GC@postini.com; Thu, 05 Apr 2012 23:19:14 PDT
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 6 Apr 2012 08:18:50 +0200
Received: from MOPESMBX01.eu.thmulti.com ([169.254.1.134]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Fri, 6 Apr 2012 08:18:56 +0200
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Joel jaeggli <joelja@bogus.com>, IPv6 Ops WG <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>
Importance: high
X-Priority: 1
Date: Fri, 06 Apr 2012 08:18:54 +0200
Thread-Topic: [v6ops] v6ops Draft minutes Thursday March 29th 15:20
Thread-Index: Ac0Tk1+DyDSsyWocQyK8AICOLJnwgQAKK4tg
Message-ID: <867F4B6A1672E541A94676D556793ACD108F03E22A@MOPESMBX01.eu.thmulti.com>
References: <4F7D5D87.4090009@bogus.com>
In-Reply-To: <4F7D5D87.4090009@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [v6ops] v6ops Draft minutes Thursday March 29th 15:20
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Apr 2012 06:19:16 -0000
Well, I read on the last slide: "" How do we move forward? • Seeking community feedback on open issues • Recommendation: • Advance 6204bis as-is, and resolve DHC issues with DHC WG during IESG review • Additional CE-transitioning and DHC requirements should wait for a subsequent draft and guidance from homenet/v4exit(?). "" So, what I remember from the v6 world congress in Paris last February is that, in order to be able to progress, we need to draw a line somewhere and to get to a common set op requirements for the CPE, so it can be guaranteed that CPE vendors can be compliant to it. I re-quote my statements form the "Can we get an IPv6 panel session on Friday" again: "Stop adding things, draw a line somewhere because if we don’t do this, next year we'll be here again and lots of slides will again include a statement saying "no IPv6 CPE available". Now I read that again more drafts could/might be added to the reqs, so I AGAIN raise my concern here and AGAIN recommend to NOT do this. Please stick to what was agreed and stop adding things please. Also allow DHCP WG to work on the discussed items related to them, same applies for the homenet stuff. I'm quite sure that more things will pop-up in course of the next couple of weeks/months, so prepare your roadmap and schedule an update to include new reqs in a LATER phase. Thx and regs Carl -----Original Message----- From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Joel jaeggli Sent: donderdag 5 april 2012 10:53 To: IPv6 Ops WG; V6ops Chairs Subject: [v6ops] v6ops Draft minutes Thursday March 29th 15:20 v6ops ietf 83 session 2 commenced at 15:20 First presentation - IP Transitioning in CE Routers draft-townsley-troan-ipv6-ce-transitioning (old slides) http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-4.pdf (new slides) http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-13.pptx Second presentation - RFC 6204 bis http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-11.pdf Ole T - DHCP fix going on in dhc WG Fred B - regarding M/O bits read all discussion and take it up in 3315bis Francis D - w 6/7 remove them. Question, ready for last call? Answer - hum, (some in favor) (no opposed) Question - no one prefers 6rd to native? Answer - native prefered Fred B - My perception is that we await an updated draft that deals with the issues highlighted and we can run through a last call and be ready to ship. Third presentation - Implementation Advice for RA-Guard http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-6.pdf Question, ready for wglc? Answer, hum (most in favor) (one opposed) Fourth presentation - Wireline: Incremental IPv6 http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-7.pptx Fred B - going to have at least one more draft revision. Question, hum for new version and after WGLC? Answer, (favored) (no opposed). Fifth presentation - SP Wi-Fi Services over Residential Architectures http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-12.pptx Philip M - does this belong in other standards bodies such as wfa or 3gpp (or bbf) Sixth Presentation - Using Only Link-Local Address In Network Core http://www.ietf.org/proceedings/83/slides/slides-83-v6ops-9.pptx Janos M - wording is rather strong, prefer informational to bcp us of LL address is a matter of taste. Jan H - seems brilliant when you design it less so afterwards. Iljisch B - occasions where this is useful. Janos M - bgp needs global v6 addresses. Francois D - agree with iljisch meeting is concluded 1715 _______________________________________________ v6ops mailing list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
- [v6ops] v6ops Draft minutes Thursday March 29th 1… Joel jaeggli
- Re: [v6ops] v6ops Draft minutes Thursday March 29… Wuyts Carl