IETF Logo Mail Archive

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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 03 February 2014 22:01 UTC

Return-Path: <Fred.L.Templin@boeing.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 0AC841A025F for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 14:01:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level:
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 mr-Tnr2cEElE for <dhcwg@ietfa.amsl.com>; Mon, 3 Feb 2014 14:01:17 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) by ietfa.amsl.com (Postfix) with ESMTP id 7076D1A025D for <dhcwg@ietf.org>; Mon, 3 Feb 2014 14:01:17 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s13M1HI9010792; Mon, 3 Feb 2014 14:01:17 -0800
Received: from XCH-PHX-210.sw.nos.boeing.com (xch-phx-210.sw.nos.boeing.com [130.247.25.65]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s13M1CkZ010225 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 3 Feb 2014 14:01:12 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.102]) by XCH-PHX-210.sw.nos.boeing.com ([169.254.10.145]) with mapi id 14.03.0174.001; Mon, 3 Feb 2014 14:01:11 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation
Thread-Index: AQHPIRoaEVV3nCWgQkC0s04abY7hyJqkEkZw
Date: Mon, 03 Feb 2014 22:01:11 +0000
Message-ID: <2134F8430051B64F815C691A62D983181C1EC8@XCH-BLV-504.nw.nos.boeing.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> <43881544-E397-4075-A898-4B2B91082738@gmail.com>
In-Reply-To: <43881544-E397-4075-A898-4B2B91082738@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
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 22:01:19 -0000

Hi Ralph,

> -----Original Message-----
> From: Ralph Droms [mailto:rdroms.ietf@gmail.com]
> Sent: Monday, February 03, 2014 11:57 AM
> To: Templin, Fred L
> Cc: dhcwg@ietf.org WG; Andre Kostur; Lemon Ted
> Subject: Re: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation
> 
> 
> 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.

Thanks, I think I remember this now. I now have a use case where it is
possible to ensure that all DHCPv6 messages are relayed through the same
device. Would it make sense to revive this work and try again?

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

Is this kind of snooping for the purpose of routing system manipulation
seen in common practice today?

Thanks - Fred
fred.l.templin@boeing.com

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

v2.23.0 | Report a Bug | By Email