Re: [dhcwg] Question on relay agent behavior in DHCPv6 prefix delegation
Ralph Droms <rdroms.ietf@gmail.com> Tue, 04 February 2014 16:33 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 B2C9E1A0201 for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 08:33:56 -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 FfubviYFx_fP for <dhcwg@ietfa.amsl.com>; Tue, 4 Feb 2014 08:33:53 -0800 (PST)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 39D541A01BE for <dhcwg@ietf.org>; Tue, 4 Feb 2014 08:33:52 -0800 (PST)
Received: by mail-qa0-f48.google.com with SMTP id f11so12606800qae.35 for <dhcwg@ietf.org>; Tue, 04 Feb 2014 08:33:51 -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=mfJCkTD3xquJ5IMyc3ZUKK1cO/7MOXjqe80969l+4s4=; b=fN3PvYv+fqA11dAhT95dLRCfDo6EEiWJ8RK4z/6Z7GlAxT5cXnywk9/kaCsVqXFTrO oBk3M/FYp7uAoCNgAamHGYtTBbqsXQYmFpMfHoWB67DuQxyYLNHzLDnLBHPwQTGTyjDR lpn6+ONRvVl4SwpCV5R68lkwhM4/Rc5FKxu17x0s63d7VjAfTvqcjiiW3qQReq7gKO+D ttFtcgZW4hmce4SdqWbbsRzRnIwW6qQI14L5fKNL3cM7WGOAXWiw6Yjhif70YbMqAlJK KOVoTeFVG5KcI9sJBkuW8ixuMsN5XZwxDqDKdSHTbbnfgQJrSQroHcWLHh9EWAn4tuAU PhkA==
X-Received: by 10.140.100.135 with SMTP id s7mr20774790qge.114.1391531631734; Tue, 04 Feb 2014 08:33:51 -0800 (PST)
Received: from [161.44.68.171] ([161.44.68.171]) by mx.google.com with ESMTPSA id l2sm68221201qae.19.2014.02.04.08.33.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 08:33:48 -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: <2134F8430051B64F815C691A62D983181C1EC8@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 04 Feb 2014 11:33:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <22985236-2327-49EF-8FE1-4569972DCC00@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> <43881544-E397-4075-A898-4B2B91082738@gmail.com> <2134F8430051B64F815C691A62D983181C1EC8@XCH-BLV-504.nw.nos.boeing.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: Tue, 04 Feb 2014 16:33:57 -0000
On Feb 3, 2014, at 5:01 PM 2/3/14, "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote: > 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? I can't speak for the WG. I recommend you review the discussion of the previous draft in detail and be sure to address the issues raised there... > >> 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? Cisco implements snooping. I can't say how widely it is used. - Ralph > > Thanks - Fred > fred.l.templin@boeing.com > >> - Ralph >> >> >>> >>> _______________________________________________ >>> dhcwg mailing list >>> dhcwg@ietf.org >>> https://www.ietf.org/mailman/listinfo/dhcwg >
- [dhcwg] Question on relay agent behavior in DHCPv… Templin, Fred L
- Re: [dhcwg] Question on relay agent behavior in D… Andre Kostur
- Re: [dhcwg] Question on relay agent behavior in D… Templin, Fred L
- Re: [dhcwg] Question on relay agent behavior in D… Ted Lemon
- Re: [dhcwg] Question on relay agent behavior in D… Ralph Droms
- Re: [dhcwg] Question on relay agent behavior in D… Templin, Fred L
- Re: [dhcwg] Question on relay agent behavior in D… Alexandru Petrescu
- Re: [dhcwg] Question on relay agent behavior in D… Templin, Fred L
- Re: [dhcwg] Question on relay agent behavior in D… Ralph Droms
- Re: [dhcwg] Question on relay agent behavior in D… Alexandru Petrescu