Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03

Wojciech Dec <wdec.ietf@gmail.com> Thu, 13 February 2014 19:53 UTC

Return-Path: <wdec.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 B391C1A0468 for <dhcwg@ietfa.amsl.com>; Thu, 13 Feb 2014 11:53: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 IpeHGRaiHRpA for <dhcwg@ietfa.amsl.com>; Thu, 13 Feb 2014 11:53:08 -0800 (PST)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7C59E1A045B for <dhcwg@ietf.org>; Thu, 13 Feb 2014 11:53:08 -0800 (PST)
Received: by mail-pd0-f169.google.com with SMTP id v10so10980135pde.0 for <dhcwg@ietf.org>; Thu, 13 Feb 2014 11:53:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=muHNmFW9kNFSRQCVwS8TKZuOSh5uXeaewQId1mqK3Uk=; b=XBvq+TxyDBgDl8Vm8tn4JLlIC87/4verJE86xwaRnEmSWXJD/32nIyBZTnDYgXs/8l tKTDS3oqfwBW211UuiVh0suA+7qn7MATlH47YK8Rx7/FzSA4Z2zpfmkTE5P2WUspIEkD 0+us5KPOe1GDP6o0yxx7bjbXtWeI2AyTPhp31CYanf55q3Db4bZuLAUVDabX2Mtxk78G jiR5sHv2/dvFmkT2bSXyETJsPKzBBIcCqW15MryQHvasbob+wMqetap8AHUAtIqdntwN J2dbDe0PNJ9pstpRjxKnLv8jfbgkn0q06un+OIbbcBGCZLKD2TWv4D6StrIoRG8A7oZC IKrQ==
MIME-Version: 1.0
X-Received: by 10.66.221.199 with SMTP id qg7mr3959370pac.88.1392321187127; Thu, 13 Feb 2014 11:53:07 -0800 (PST)
Received: by 10.70.1.70 with HTTP; Thu, 13 Feb 2014 11:53:07 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE64F11@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AE1EEB5@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1AE64F11@xmb-rcd-x04.cisco.com>
Date: Thu, 13 Feb 2014 20:53:07 +0100
Message-ID: <CAFFjW4jWFg_pSZ_PsX7HH7RpoOmMwo-nyzDgVdfd6NpqVrPfWA@mail.gmail.com>
From: Wojciech Dec <wdec.ietf@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/2CAqYJGauQYyS_n01lO4xd_mgl8
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03
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: Thu, 13 Feb 2014 19:53:12 -0000

Hi,

on re-reading the draft I have one question, perhaps obvious to the
authors, about a technical point that deserves to be clarified: What
is the expected behaviour for the DHCPv4/DHCPv6 server in terms of
selecting the IPv4 address scope? RFC 2131 gives the following SHOULD:

"A new address allocated from the server's pool of available
        addresses; the address is selected based on the subnet from which
        the message was received (if 'giaddr' is 0) or on the address of
        the relay agent that forwarded the message ('giaddr' when not 0)."

This draft doesn't mention anything about giaddr, so it's rather
ambivalent whether the relay agent inserts any giaddr and what is the
SHOULD behaviour of the server, etc.


Thanks,
Wojciech.

On 11 February 2014 22:56, Bernie Volz (volz) <volz@cisco.com> wrote:
> This document did pass the WGLC but we had been waiting for the v4configuration draft, which has passed.
>
> I believe (though need to confirm with the authors) that the 04 draft they published on Jan 17, 2014 incorporates all of the comments from the last call.
>
> We will shortly send this off to advance (we expect to send this and the v4configuration draft about the same time).
>
> - Bernie
>
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
> Sent: Tuesday, January 14, 2014 4:26 PM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03
>
> Hi:
>
> We've left this WGLC open pending the last call on the v4configuration draft. The authors of the v4configuration draft have been working on updating it and should be submitting it shortly, at which time we will start the WGLC for it. We will then close the last calls for both documents (dhcpv4-over-dhcpv6 and v4configuration) at the same time.
>
> Sorry for the delay but as the two documents are closely related, we feel it is best to hold off until both can be reviewed.
>
> - Bernie
>
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tomek Mrugalski
> Sent: Monday, December 16, 2013 9:58 AM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
>
> On 16.12.2013 15:40, Simon Perreault wrote:
>> Le 2013-12-14 10:10, Bernie Volz (volz) a écrit :
>>> WGLC on the related draft-ietf-dhc-v4configuration-03 is in progress
>>
>> Is this true? I can't find the announcement, and the datatracker
>> doesn't show the draft as being in WGLC...
> No, that was a mistake. Bernie and I exchanged preliminary WGLC announcement text, but due to the discussion about dhcpv4-over-dhcpv6 we still haven't sent it out. So no - there is no WGLC on v4configuration yet, but there likely will be in the next couple days.
> It will be long enough so people who take holiday + new year vacation will be able to get back and post their comments when they get back in January.
>
> Tomek
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg