IETF Logo Mail Archive

Re: [dhcwg] Adoption Call for draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020

Erik Kline <ek.ietf@gmail.com> Wed, 15 January 2020 01:04 UTC

Return-Path: <ek.ietf@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 F291D120803 for <dhcwg@ietfa.amsl.com>; Tue, 14 Jan 2020 17:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Mi3FVoNzjTdd for <dhcwg@ietfa.amsl.com>; Tue, 14 Jan 2020 17:04:08 -0800 (PST)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 7CCE112006D for <dhcwg@ietf.org>; Tue, 14 Jan 2020 17:04:08 -0800 (PST)
Received: by mail-ed1-x52f.google.com with SMTP id m8so13869982edi.13 for <dhcwg@ietf.org>; Tue, 14 Jan 2020 17:04:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pdQmB8CgQPQiHUyaJdjC262xeeFosI5QxJKvYrzXzGw=; b=ntoLgVtkagH6LrnZmf0ag/Zx07cfu/up0+GDaRr1kcsIj6ppSCri9moZYI3KXsq5tn rbi/s4Yt1O+xjX59JYKYHoj5Ped1ywl/Wgx0qFyw8ntKa6CGQZmZbjNw7XG6F1NL1Nzw iL8UjIL25J9ftDeceaJB6poEjBLh0D+Le2pfHAck/J8cEgO614tB46warieFJPhtnRB1 3Xo7sItrUWPVIi9b1PuNWvGXiheAPJHd1bQM50ktjd8kG9mTa7mFqYE0hhIgysBPdIxe 4aZwPemTeNSzMsAyRuitWkhI53TtCXq2n1MTgDeWY9W2mZGR9h3oFvx5VJJz4Jlg3h9l co/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pdQmB8CgQPQiHUyaJdjC262xeeFosI5QxJKvYrzXzGw=; b=gwOYg+pQbOOBbAsWNuYbj/nsEypudY3PfmL9ABgKMGLZPEiDoeXiWomJrvHCARc8A6 8eovFNroNDtMUvyiDz/zg+1jjtF9e7tE3RDAOSK08zpBDJiP8u51bfhmyiL8ExRz5au5 h/yQIdtdYB61oUVhXCS9XX/iWG6lfia9Up6E4/cVx68ny9h1XCZRQrG5QMj8SYzj/3ov XERop+RcREb5F6ORqjpdarhEJPeYr/AV7UFDk69Pl0g93ZPkykc58Wzv7Wm+0U/WVEUS d9T1RCklC0YiqIE1qIREQrej/KC87+7Hs87meGJRf4/pGhOBDHRRf3RxwhGQnk6WEMD5 oofA==
X-Gm-Message-State: APjAAAWcpGhUvVdAdmXNTPAXVjLhhFO8CXAQzhufMRFJIM66Rnr3p3GF BBglZDr8qocyq4d5e3Q7zSN9ci+UcUwWj873LajmSPv0
X-Google-Smtp-Source: APXvYqzq284A8KY/JQoMWHez7I37In5ez51yx67xaCw9t3O4a9gQ3S7PJV+W23JBW6N4htCkFIIaOdhi5S9i3a8Lmzo=
X-Received: by 2002:a50:fa41:: with SMTP id c1mr26611122edq.153.1579050247021; Tue, 14 Jan 2020 17:04:07 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR11MB2888345B6D3728C02AE410EFCF240@BYAPR11MB2888.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB2888345B6D3728C02AE410EFCF240@BYAPR11MB2888.namprd11.prod.outlook.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Tue, 14 Jan 2020 17:03:55 -0800
Message-ID: <CAMGpriX0F8FfbvjdEOG1rz10d8fsqS5YfQPaZhVv_Puwc24U-A@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, ianfarrer@gmx.com
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000e6d1d059c2349d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/FzYdEIIcu-UijDeBq1pNzVb9NUo>
Subject: Re: [dhcwg] Adoption Call for draft-fkhp-dhc-dhcpv6-pd-relay-requirements - Respond by Jan 14, 2020
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Jan 2020 01:04:11 -0000

I support adoption.

I am confused about some things though.  Specifically related to 3.4 and
4.1 G-5.  Should the delegating relay support a client moving from one
interface to another (presumably this just means honoring a request with
previously allocated IA_PDs in it, updating the routes accordingly)?  I
guess, what's the guidance for supporting a duplicate versus detecting a
migration?

[nits]
S2.1: s/should be understand/should be understood/

S2.1: s/specificcally/specifically/

On Sun, Dec 29, 2019 at 8:03 AM Bernie Volz (volz) <volz@cisco.com> wrote:

> Hello:
>
>
>
> As follow up from the IETF-106 DHC WG meeting, we are initiating the WG
> call for adoption on
> *https://datatracker.ietf.org/doc/draft-fkhp-dhc-dhcpv6-pd-relay-requirements/*
> <https://datatracker.ietf..org/doc/draft-fkhp-dhc-dhcpv6-pd-relay-requirements/>
> (DHCPv6 Prefix Delegating Relay). This document was presented at IETF-106 –
> see
> https://datatracker.ietf.org/meeting/106/materials/slides-106-dhc-dhcpv6-prefix-delegating-relay-00
> .
>
>
>
> This starts the call for Adoption of this document. Please respond by
> January 14, 2020.
>
>
>
> Thanks in advance for your consideration of whether the WG should or
> should not adopt this document as a work item.
>
>
>
> And, Happy New Year!
>
>
>
>    - Tomek & Bernie
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

v2.23.0 | Report a Bug | By Email