[Dhcpv6bis] Proposed DHCPv6bis London meeting agenda
Tomek Mrugalski <tomasz.mrugalski@gmail.com> Wed, 26 February 2014 19:29 UTC
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcpv6bis@ietfa.amsl.com
Delivered-To: dhcpv6bis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C208C1A084B for <dhcpv6bis@ietfa.amsl.com>; Wed, 26 Feb 2014 11:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 jMmLl301kxnU for <dhcpv6bis@ietfa.amsl.com>; Wed, 26 Feb 2014 11:29:50 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 726B81A017D for <dhcpv6bis@ietf.org>; Wed, 26 Feb 2014 11:29:49 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id q59so2007499wes.6 for <dhcpv6bis@ietf.org>; Wed, 26 Feb 2014 11:29:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/e1bSgD/R/VekgrDgw6sibythaqyXl0OUxSnKlw8Ygw=; b=YbE1+BEZFHPdaljKBxFyVTjOc2D+aQ49bq7kk7iHP5Sb+ZLmtEH6C8tYQZNFkY6QVV m2qbdKqrEXPac4/UmNWeBxyBw0e2yhw4o0k3FEMKNVyx+Iq1DJX5/ypSpIV6mjMobh4O 3z7G8+NLJ6sx1bnlckOXM5tBzSSBHhPKG1enwJWPiIOOpIyACrsx9miQdS/uFX0XgspR MWGyyUdhNSzJa/ZFlcTX7M/tJqRxamIUNKIarxrIG1H22ZNsmtwAevbNHxK4T+M8Nl1e xcJPia55P1tgCEZiRhgEYpPo+XmKvGBvNvw0Bxk9+doqfxIz7oebWIXReqZe+CBNOvMq 1U1g==
X-Received: by 10.180.102.42 with SMTP id fl10mr6297495wib.42.1393442987586; Wed, 26 Feb 2014 11:29:47 -0800 (PST)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id h9sm4922663wjz.16.2014.02.26.11.29.46 for <dhcpv6bis@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 11:29:46 -0800 (PST)
Message-ID: <530E40A6.5010003@gmail.com>
Date: Wed, 26 Feb 2014 20:29:42 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dhcpv6bis@ietf.org
References: <530BABEE.10906@gmail.com>
In-Reply-To: <530BABEE.10906@gmail.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20140226202942612
X-Forwarded-Message-Id: <530BABEE.10906@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcpv6bis/a38pRr3R7PTk-uzm8BL4dYEUpv4
Subject: [Dhcpv6bis] Proposed DHCPv6bis London meeting agenda
X-BeenThere: dhcpv6bis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "DHCPv6 \(RFC3315\) bis discussion list" <dhcpv6bis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcpv6bis>, <mailto:dhcpv6bis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcpv6bis/>
List-Post: <mailto:dhcpv6bis@ietf.org>
List-Help: <mailto:dhcpv6bis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcpv6bis>, <mailto:dhcpv6bis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2014 19:29:55 -0000
It seems that we'll be meeting in London. That's good, because face 2 face meeting always moves things forward a lot. We should aim for 2 hours meeting. Although the exact time will be chosen among the design team, this is an open meeting and everyone is welcome to attend. Minutes from previous (on-line) meeting: http://www.ietf.org/mail-archive/web/dhcpv6bis/current/msg00066.html Here's proposed agenda: 0. Agenda bashing 1. Review the current status and next steps 2. Get over the remaining list of RFCs we can possibly merge: This is a follow-up after previous meeting. We did not make a decision for those two RFCs. RFC6977 - Triggered reconfigure We initially thought that it's about making explicit the currently implicit assumption that the relays do not modify client's messages and based on that info we decided to include clarification that relays do not modify any relayed message (regardless if the message goes up or down). Unfortunately, that is the clarification done in RFC6422. So the decision we made is not valid and this topic will have to be revisited. RFC6422 - relay supplied options Decision is postponed, as nobody on the call knew what exactly that RFC changes (it updates 3315). Please take a quick look at them, so we can make an informed decision. 3. The tickets that don't have milestone assigned yet As of today, that's 23 tickets. We'll triage them and assign to A,B or C category. If you have some time to spare before the meeting, please try to triage them and move to appropriate category. 4. Tickets in A category: easy, apply before merge These are trivial. It doesn't make sense to spend too much time on those. If we deal with all A tickets, we'll be ready for the -01 upload. 5. The plan to merge 3633 into bis draft Michael and Andrew said on Jun. 22 meeting that they'll work on the plan. (naming convention, sections to copy as-is, what to merge etc.) Once the merge is done, we can upload -02 and request adoption. 6. Tickets in B category: moderate difficulty, apply after merge Let's go over those next. They are the next in line once A tickets and the merge are done. This should be a quick one. There's not much to discuss here, we just need to do them once the merge is done. 7. Tickets in C category: awaiting consensus. These are the tricky ones. Let's try to solve as many of them as possible (or pick those that we need to bring to the DHC list). Ideally, majority of the meeting time should be spent on this item. Tomek
- [Dhcpv6bis] Proposed DHCPv6bis London meeting age… Tomek Mrugalski
- Re: [Dhcpv6bis] Proposed DHCPv6bis London meeting… Bernie Volz (volz)
- Re: [Dhcpv6bis] Proposed DHCPv6bis London meeting… Leaf Yeh