Re: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016

Kim Kinnear <kkinnear@cisco.com> Mon, 25 January 2016 20:27 UTC

Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F2E1A0113 for <dhcwg@ietfa.amsl.com>; Mon, 25 Jan 2016 12:27:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 1WFr2pX_aG4s for <dhcwg@ietfa.amsl.com>; Mon, 25 Jan 2016 12:27:09 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 980D71A0103 for <dhcwg@ietf.org>; Mon, 25 Jan 2016 12:27:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3272; q=dns/txt; s=iport; t=1453753628; x=1454963228; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=ES2zVRJamus7LIvTQlaFWs/QTbJWWaqTLlnJ4koGbfw=; b=lOkxY58xRUjOTEGncNN/9iqvUOFffpo3Y8d3rZYaOEpLC73s8cwYMvcH 2SJ4aVgjrNAnIdQKk7T6G1vBZpLj5QEaVwPIPtXCOB2Z5cQNjn4MjwJrT ELzw5aS/+kkF4xNbYanoarHXYiT2aw1T/cTfVTRxKy9QtLn9oEhOe5Y8t Q=;
X-IronPort-AV: E=Sophos;i="5.22,346,1449532800"; d="scan'208";a="624778169"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2016 20:27:06 +0000
Received: from dhcp-10-131-65-118.cisco.com (dhcp-10-131-65-118.cisco.com [10.131.65.118]) (authenticated bits=0) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u0PKR53Q018461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Jan 2016 20:27:06 GMT
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <acd163eee61e46d4895e2c3dcdb1d7f4@XCH-ALN-003.cisco.com>
Date: Mon, 25 Jan 2016 15:27:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <45451857-DAFA-46E2-B470-1CE115DDF70A@cisco.com>
References: <005134edeb9e4550b55a23776afaef15@XCH-ALN-003.cisco.com> <acd163eee61e46d4895e2c3dcdb1d7f4@XCH-ALN-003.cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.3112)
X-Authenticated-User: kkinnear
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/rSsnyI2PBfytNxnNZh3EqlB5_O4>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2016 20:27:10 -0000

Regarding DHCPv6 failover....

We have had two excellent reviews, and I folded the considerable comments
into a new draft right before the holidays in December:

https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-protocol-01 <https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-failover-protocol-01>

At this point, we could use another good technical review (or two).

If we don't have any before IETF-95, it would make sense to talk about
how to get some.  If we do have some, it would make sense to talk about
either:

  o Issues raised by the review(s)

  o Next steps

or both.

So, it would make sense to put DHCP Failover on the agenda, as there will
be *something* worth talking about.

Regards -- Kim


> On Jan 25, 2016, at 2:40 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> 
> Just a reminder about requesting agenda slots!
>  
> We have only one request:
> -          DHCPv6 bis
>  
> I would think we MAY want to discuss:
> -          Secure DHCPv6 (and draft-li-dhc-secure-dhcpv6-deployment)
> -          DHCPv6 Prefix Length Hint Issues (though perhaps we’ll just want to try to WGLC this?)
> -          Yang model?
> -          Failover?
> -          Relay Initiated Release (though this would need an update based on the IETF-94 discussions)??
>  
> -          Bernie
>  
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
> Sent: Monday, January 04, 2016 4:45 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WG Session @ IETF-95 (Buenos Aires) Agenda Requests - Deadline 2/14/2016
> Importance: High
>  
> Hi:
>  
> The scheduling requests for meeting slots for IETF-95 in Buenos Aires have opened up (we must submit a request before 2/19/2016).
>  
> Our plan for IETF-95 will be the same as we did for IETF-94:
> -                      We are encouraging agenda requests NOW thru February 14th, 2016 (this will give us a few days to organize the agenda and decide on the session length request).
> -                      We will submit our time request for IETF-95 based on the RECEIVED agenda requests (by the February 14th deadline).
> -                      Requests after February 14th will most likely be REJECTED (once the time slot is filled). In the past we have been more accommodating, but because of the pressure on IETF meeting time, we are being asked to justify our time slot request. And meeting time should be used to discuss and resolve issues, not present overviews of drafts or status updates.
>  
> Therefore, please submit requests as soon as you can (and well before 2/14) if you do plan to present at the DHC WG session in Buenos Aires.
>  
> As in the past, please provide:
>  
> Title Of Session:
> Presenter:
> Related Drafts:
> Time Required:
> Purpose of Session:
>  
> We do want to remind those requesting time that you should focus on discussing key issues that need resolution to move a draft forward.
>  
> We are 3 months from that next meeting.
>  
> -          Tomek & Bernie
>  
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg