Re: [dhcwg] IETF-96 (Berlin) DHC WG Session - requesting slot for DHCPv6 failover

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Wed, 25 May 2016 18:49 UTC

Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB8612D8EF for <dhcwg@ietfa.amsl.com>; Wed, 25 May 2016 11:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 pLcazSxvMXiP for <dhcwg@ietfa.amsl.com>; Wed, 25 May 2016 11:49:21 -0700 (PDT)
Received: from mail-lb0-x244.google.com (mail-lb0-x244.google.com [IPv6:2a00:1450:4010:c04::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45E7C12D62A for <dhcwg@ietf.org>; Wed, 25 May 2016 11:49:21 -0700 (PDT)
Received: by mail-lb0-x244.google.com with SMTP id sh2so3160692lbb.2 for <dhcwg@ietf.org>; Wed, 25 May 2016 11:49:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=VQPytpEOpJwEJCX3GQGDOuXURFPNsI4QWF6lHoUayGs=; b=jP3qe+IHW8h2hQyWIpYft16R77/sbsXHSwvy66wJGUZcnh+WcVCleyJjshyy3QY8It LvHOVh2qdT3wRikTJIAJzUDUhEqOzY2ZNPA3kVULWka2uJngnqu5a5hV27cFKIQ9OYT1 5cspeKAoiyMHp/kmMble66WL4fb77pirzPjcOAwSDIa2Qk1aSOZORp0twUpBVTW4ugLP 5C4omP0mXGmZBhBMBFNFFBS5HYP/H8UHK5cI0T37aqCXAhrUPyujTfEuZSVu3BH5NHZO R79NYRIAaqOxfYUUumcSTK9s+sh2hXgEJUiATIq77D/llkpq2+Mv4qHkqcyiu34j0FjY 37Iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VQPytpEOpJwEJCX3GQGDOuXURFPNsI4QWF6lHoUayGs=; b=bTaEg8MlboplA4wIbtZerKBKHiThfrdFG5qP683nbhrJs/qqYprXDWTs70Z750C6EP ZGi5cHLRg3aZEVLKQpz/13ApdXAMjof6x2pO4+aQT7wr6NW92yqpxcNrxQfIDaz79OHS nfnuQ6MW6fIFdZVgQTmVLffr13AgM8zMJBwOEcgI6ximzarAy8bR/6DGhVL1DX1tsz+M OCsDKuw6lHp9+A19iPjFxplozqJX/cj/la+M4BmvfKiqqfwo+drlL3Rpj8TM3m2DIqc0 cup6RApPjFJQ5TW7avUA7hwPhvg4jLBNJqkVZfRwTM2fzCXqvuqJ2vjr6a5S1ckhjXpq byHA==
X-Gm-Message-State: ALyK8tLdIvPR9v1UkwpPjCBHbcVD0m4xIXWi4iCkbomi2ZxRhn1myfYYIUx4GQ+V5CkOGQ==
X-Received: by 10.112.219.233 with SMTP id pr9mr1672698lbc.47.1464202159484; Wed, 25 May 2016 11:49:19 -0700 (PDT)
Received: from [10.0.0.100] (088156132194.dynamic-ww-04.vectranet.pl. [88.156.132.194]) by smtp.googlemail.com with ESMTPSA id w17sm1746626lfd.45.2016.05.25.11.49.10 for <dhcwg@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2016 11:49:19 -0700 (PDT)
To: dhcwg@ietf.org
References: <b1b9c2b3e38846b2bbd104a01ac24523@XCH-ALN-003.cisco.com>
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5745F3A5.8040507@gmail.com>
Date: Wed, 25 May 2016 20:49:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <b1b9c2b3e38846b2bbd104a01ac24523@XCH-ALN-003.cisco.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/s5OIAO7NkUPhvufI1sjwf6muaQ4>
Subject: Re: [dhcwg] IETF-96 (Berlin) DHC WG Session - requesting slot for DHCPv6 failover
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 25 May 2016 18:49:23 -0000

Title: Next Steps for DHCPv6 failover
Presenter: Tomek Mrugalski
Related drafts: draft-ietf-dhc-dhcpv6-failover-protocol-01
Time Required: 10 mins
Purpose of Session: to ask people why there was no response during WGLC
and determine what the next steps are

The question I'd like to ask will be:
Do people think this is no longer a problem that needs solving?
Should authors continue the work on it or abandon?
Is there anything authors could do to make the I-D more review friendly?

Tomek

On 27.04.2016 19:07, Bernie Volz (volz) wrote:
>
> Hi:
>
>  
>
> We are planning to request a 2 hour time slot for the DHC WG for
> IETF-96 (Berlin). Please submit agenda requests as soon as you can if
> you do plan to present at the DHC WG session in Berlin.
>
>  
>
> 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.
>
>  
>
> You can view the working agenda at
> https://github.com/dhcwg/wg/wiki/IETF-96-(Berlin)-DHC-WG-Agenda
> <https://github.com/dhcwg/wg/wiki/IETF-96-%28Berlin%29-DHC-WG-Agenda>.
>
>  
>
> We are now less than 3 months from that next meeting.
>
>  
>
> Thanks!
>
>  
>
> -          Tomek & Bernie
>