Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-01
"A. Gregory Rabil" <greg.rabil@jagornet.com> Thu, 16 August 2012 18:08 UTC
Return-Path: <greg.rabil@jagornet.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 2601A21F8487 for <dhcwg@ietfa.amsl.com>; Thu, 16 Aug 2012 11:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3E1sniaVIDwv for <dhcwg@ietfa.amsl.com>; Thu, 16 Aug 2012 11:08:30 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2D221F847D for <dhcwg@ietf.org>; Thu, 16 Aug 2012 11:08:30 -0700 (PDT)
Received: by bkty7 with SMTP id y7so1224203bkt.31 for <dhcwg@ietf.org>; Thu, 16 Aug 2012 11:08:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=336fbbsGf91n1fYBFNPMOekZuo6lhe7obi4mujAGtLQ=; b=fLGK5yAVyNUtPqGMv5lP/Rr+uHHif5+Q+0HflZCthIiX2jzUafDFSEhODPj3cN5TW1 2sFu7mZbdHv2KDhL1M0boK/rCCLEFkXhEQS2TdfdlbbxRBhAhRyXWKuVetxvsCLMJs/I 1lVOp30mlatJhJZf3cdP6aPffRoWz16bWBpWumGZmwSFrnGWEcBPkPb4iuP6ZXsAYP6a XHt7ddjHjPfj4NFbieIzc1aZygOsJzu6KWfoVSyMuHxKQo973nkVXm91rQ0sEDtPg1/Z 7v3qHseCJrv1Y/5UT7/nIgzn9fb+3LpDhDGmG4iiHEvOQ7ZsUV3AwChLsoIq+GDQj44j PJPQ==
MIME-Version: 1.0
Received: by 10.204.148.78 with SMTP id o14mr1006685bkv.38.1345140509219; Thu, 16 Aug 2012 11:08:29 -0700 (PDT)
Received: by 10.204.189.6 with HTTP; Thu, 16 Aug 2012 11:08:29 -0700 (PDT)
In-Reply-To: <638607D0-D89C-4ED6-A3BF-FF2DECBF4D47@nominum.com>
References: <10414435.125914.1345139460853.JavaMail.root@network1.net> <638607D0-D89C-4ED6-A3BF-FF2DECBF4D47@nominum.com>
Date: Thu, 16 Aug 2012 14:08:29 -0400
Message-ID: <CAAed6vt6kA=-T0qwfNf7av7bRvcMB2ox=GBLXM6k=xy8Xs8ADw@mail.gmail.com>
From: "A. Gregory Rabil" <greg.rabil@jagornet.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary="0015175cac2e3999fc04c765ee61"
X-Gm-Message-State: ALoCoQk59iWKQCdTmsV38pUJcveN+vNaOL+97bV7dJU8VatXPkClpUi6WPuZHeKzS92/VaDzGQ/K
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 16 Aug 2012 18:08:31 -0000
Good point, Ted. Maybe some text should be added to the draft to explain that this is the expected configuration? Greg On Thu, Aug 16, 2012 at 1:53 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote: > On Aug 16, 2012, at 1:51 PM, perl-list wrote: > > Some of your other comments got me to thinking, however... On DHCPv4, the > client may start communicating directly with the DHCP server ignoring the > relay agent for renews (no idea if it is supposed to do that, but some do). > Is this the case in DHCPv6? Is it possible for the client to ignore the > relay agent and communicate directly with the DHCPv6 server on rebind? If > so, then this solution will only sort of work... > > > The client isn't allowed to do this unless it negotiates it with the > server, which presumably would say no in any environment where the > client-link-layer-address option was used. This was a deliberate design > decision in RFC3315, to deal with the exact problem you are talking about. > >
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Ted Lemon
- [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-link-l… Ted Lemon
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… A. Gregory Rabil
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Ted Lemon
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… A. Gregory Rabil
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… A. Gregory Rabil
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… A. Gregory Rabil
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Tomek Mrugalski
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Ted Lemon
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… sthaug
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Chuck Anderson
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… perl-list
- Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-client-li… Gaurav Halwasia (ghalwasi)