IETF Logo Mail Archive

Re: [dhcwg] [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function

Lorenzo Colitti <lorenzo@google.com> Tue, 28 November 2017 05:22 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF76126DD9 for <ipv6@ietfa.amsl.com>; Mon, 27 Nov 2017 21:22:21 -0800 (PST)
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, HTML_MESSAGE=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=google.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 KvQCdsg-Pfy1 for <ipv6@ietfa.amsl.com>; Mon, 27 Nov 2017 21:22:20 -0800 (PST)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) (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 7ABC61201F8 for <6man@ietf.org>; Mon, 27 Nov 2017 21:22:20 -0800 (PST)
Received: by mail-yw0-x235.google.com with SMTP id k191so12839870ywe.1 for <6man@ietf.org>; Mon, 27 Nov 2017 21:22:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=F4JbUxgVK5DiwbrmUMAH++GyHjlmYhDr8uHGeNL611E=; b=IxZDwrJw6AiJ62cYLqmwIMSM81J2//OdBM/2iZt6Vk7zmqMlP4hPSW+IJASWT+gJXI x5QRH75jnshu7QTOaoz8qnhij00QsEDdsLd7DuS/4JRpmp/CYp3GUFgSJNqL0ppCnEku 3/jwDH1taH/VCVEbCURrUa2VnYbPxCPDlfmztuv2MDL/YJT4riUHoiuBj3Ei0HQofO6J VD64x6uFohRGh57ZV3OlqiPhYy96u5EEo8d0yvEvtGJXfzag2H1Ofo3amuFmwT7dk6eH ZjZgQ+TCSoOVqry98Yab17SZC7v195wxx2k74VjsBG8s2ikHJEXdsVRNqBsICvrGruiH GZtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=F4JbUxgVK5DiwbrmUMAH++GyHjlmYhDr8uHGeNL611E=; b=Y42kA7R5Wir1g6BmcfTTPpt0xsvbAD5T6kgIWAJrK3daZulaI26znZ/ZIA7CNUosKh WoWcybPctbtEbtYRiHOA63m0ngEYKgXOpFBfrHsRPa2wVsRmCPVCO6DeGkVlF1T7YdZw RnPTDRh55z16F7KhhTaOCituLbWFxrhtpe0z4N83bFNe0O/4yOErXgz2P4DlQAm0G98y kvzBEqYdmFpkn8X077bQjQgwYa//b+4ykmFb6yNE+Hp08e8sQp351T4FJFdwVqATtgM6 R1h+j2kudoq+KMtDv9heGRp2ls9SOdUDORIYBrAYgjtJR/+NoX/M7ooyB15VzVtoJmSI M9yg==
X-Gm-Message-State: AJaThX5GZRky5QooetcYLznAbpZFNzg1LoZ+E7TKMYrUuwsGi6ZhYaK3 UdCNop8Mv8gkIqcs+aZ++IZx7v1F9MSJkPEEdvHxsw==
X-Google-Smtp-Source: AGs4zMbo/78We1GsJ3/+no0Gqso04bjEKzQD3zqTjlmwFl7XjIRL+sRF+3+KfRnwCs9kd6bCm4aWo6+/3CIrcJSIBIY=
X-Received: by 10.13.232.140 with SMTP id r134mr27137246ywe.344.1511846539466; Mon, 27 Nov 2017 21:22:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.4.194 with HTTP; Mon, 27 Nov 2017 21:21:58 -0800 (PST)
In-Reply-To: <8a5feb3a-d18e-1773-0539-3da22e582c70@gmail.com>
References: <9debb1672e3d4f0d89d672d64e0fe579@XCH15-06-08.nw.nos.boeing.com> <CAKD1Yr1+a+Bg3N=pX5_X2vhvkf50hY7N_Ay=aQQyq5ogsEWWMw@mail.gmail.com> <4e01cd6cc5234daca2f7be55b8cc28b0@XCH15-06-08.nw.nos.boeing.com> <27327.1511369630@obiwan.sandelman.ca> <E49D982F-9A83-4B7E-B65F-2CB07AB56ADD@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DCC2BF8@GAALPA1MSGUSRBF.ITServices.sbc.com> <8a5feb3a-d18e-1773-0539-3da22e582c70@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 28 Nov 2017 14:21:58 +0900
Message-ID: <CAKD1Yr3_2QnFdz6ooEnSeXc7P2HPkf=dSwT8L8NKf4=XqLfHWQ@mail.gmail.com>
Subject: Re: [dhcwg] [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "STARK, BARBARA H" <bs7652@att.com>, Fred Baker <fredbaker.ietf@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c086fbaf12236055f0433fe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/M-Y2Ro_EZju1THka7-nbvxnYIcU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Nov 2017 05:22:22 -0000

On Tue, Nov 28, 2017 at 8:06 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Yes and no. Let's consider a host that needs a particular piece of
> information. As an example, consider the address of the next-hop router
> for a given prefix. There are three separate parts to this:
>
> 1. Receiving some sort of message containing an appropriate option.
> 2. Decoding the option
> 3. Storing the result.
> [...]
>

You can't really separate these steps because the protocols that deliver
configuration information have different semantics. For example, DHCPv6 is
poll-based and requires explicit renewal, but RAs are push-based.

v2.23.0 | Report a Bug | By Email