IETF Logo Mail Archive

Re: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation

Ralph Droms <rdroms.ietf@gmail.com> Mon, 03 February 2014 19:57 UTC

Return-Path: <rdroms.ietf@gmail.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 6119B1A016D for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 11:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 lrZmjLK3EvZl for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 11:57:09 -0800 (PST)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id CF54A1A01DA for <dhcwg@ietf.org>; Mon, 3 Feb 2014 11:57:07 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id c9so11886130qcz.17 for <dhcwg@ietf.org>; Mon, 03 Feb 2014 11:57:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=632DM4+ShcfyqljzUyuyQPivT8T7sjEDGJhYhAhuFXU=; b=NJYxHwJHt/er5D52sp2XI7d5SIK5zuF2Mp88s99kcE7SA59JcioDXNpsoh+6e3DVMX CdoDK1mWgzEv6VKKisVH+6dzdFHAEf9yfLq7V51emy9xOs+/v5qi113s1CEv4irLAAjs /+P3x2gYWo9O8SqFRBtPmLz0HRfSnhQXwLhYhmxqfIWbhKsI4Cro7OGfwsVGpFvARWOJ YoGcZeiHIBvN+WwiBbRedfHsKHOja/pclxYO51ASsfXwiRiIpYZbWYZjko36smBFS+kH K1QYOTgm5QrqcyeOdNPJrd72kN52d6pGQRVluJJvgn8bp2nvlW88YqWbqEPrZ1rIwoJU 1CTg==
X-Received: by 10.224.2.194 with SMTP id 2mr59925876qak.44.1391457427119; Mon, 03 Feb 2014 11:57:07 -0800 (PST)
Received: from ?IPv6:2001:420:2c52:1316:a12a:883:79cf:6178? ([2001:420:2c52:1316:a12a:883:79cf:6178]) by mx.google.com with ESMTPSA id 72sm28638419qgv.19.2014.02.03.11.57.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 11:57:03 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <0A4C2767-D7B2-4712-93F9-CC547871D7E9@nominum.com>
Date: Mon, 03 Feb 2014 14:57:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <43881544-E397-4075-A898-4B2B91082738@gmail.com>
References: <2134F8430051B64F815C691A62D983181C095B@XCH-BLV-504.nw.nos.boeing.com> <CAL10_BpTKHhfux8H7oYGuLYKEhZ5XQe7EokH_==2zCwBQFuPJw@mail.gmail.com> <2134F8430051B64F815C691A62D983181C0A8C@XCH-BLV-504.nw.nos.boeing.com> <0A4C2767-D7B2-4712-93F9-CC547871D7E9@nominum.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Andre Kostur <akostur@incognito.com>, Lemon Ted <ted.lemon@nominum.com>
Subject: Re: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation
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: <http://www.ietf.org/mail-archive/web/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, 03 Feb 2014 19:57:11 -0000

On Feb 3, 2014, at 2:41 PM 2/3/14, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 3, 2014, at 1:10 PM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>> But, are there any more recent publications
>> that have either attempted or succeeded in specifying a standard method?
> 
> I can't think of any.

"DHCP Relay Agent Assignment Notification Option" <draft-droms-dhc-dhcpv6-agentopt-delegate>, R. Droms, B. Volz, O. Troan

1.  Introduction

   The DHCP Relay Agent Assignment Notification option encapsulates
   address and prefix options to indicate that an address or prefix has
   been assigned.  The option may also carry other information required
   by the network element for configuration related to the assigned
   address or prefix.

   For example, a network administrator uses the DHCP Relay Agent
   Assignment Notification option to inform a relay agent of a prefix
   that has been delegated through DHCP PD to a DHCP client.  The relay
   agent notifies the network element on which the it is implemented of
   the delegation information so the network element can add routing
   information about the delegated prefix into the appropriate routing
   protocols.

The dhc WG discussed the idea and decided not to take on the work due to some fundamental issues in using the option reliably; e.g., ensuring that all DHCPv6 messages were relayed through the device that was actually interested in configuring itself for the delegated prefix.

The idea was to formalize what is now accomplished through snooping.

- Ralph


> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email