Re: [dhcwg] New Version Notification for draft-sarikaya-nvo3-dhc-vxlan-multicast-00.txt

Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 20 February 2014 21:05 UTC

Return-Path: <sarikaya2012@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 1314B1A02E6 for <dhcwg@ietfa.amsl.com>; Thu, 20 Feb 2014 13:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 C_X9PN9CGzWC for <dhcwg@ietfa.amsl.com>; Thu, 20 Feb 2014 13:05:23 -0800 (PST)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id BACC41A02E0 for <dhcwg@ietf.org>; Thu, 20 Feb 2014 13:05:22 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id mc6so1730772lab.14 for <dhcwg@ietf.org>; Thu, 20 Feb 2014 13:05:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Y7r6jN5BAoCgb7nyGe6Xo2ufIFtZ3THJLP6whkCAnks=; b=DKvkdW1vMfyzyOBEE00/aKytJrTDCtgWR6xvkVLyO81p5hDCOwQcv/GTFwF9nsPfcZ yxzyH90enB/XFXE+aFZhWy8PwQxBpi5xzzPgfbQnAq2cc78WNGpTeMkLWEJAOalqgA82 ht8x1wd3pL0PdzjP6H7goC/bKTO9XNtE9rRvBzPK6sYaJty2RmPkgwByIzXcNu0A+rlj tCFbjNM5dmgImV+8ww/qv16E/F8IURvwmOALBO6CsSeEuxLCtMJNVH3HBfpcxTD/esaM xTe7Sc1gHEOyAzxthtEGLEUrcJUU6A7DXKUZPnOqqgDjS03fBW7EsEHR2kq6OnD1NflD A/EQ==
MIME-Version: 1.0
X-Received: by 10.152.164.199 with SMTP id ys7mr2325003lab.31.1392930318205; Thu, 20 Feb 2014 13:05:18 -0800 (PST)
Received: by 10.114.170.195 with HTTP; Thu, 20 Feb 2014 13:05:18 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AEA2DE8@xmb-rcd-x04.cisco.com>
References: <20140214173114.23812.70162.idtracker@ietfa.amsl.com> <CAC8QAcfGgayrUkXZp4hNdGeZpfv3hazpg4n=2kx8qUHqObhUAg@mail.gmail.com> <2D6D46E6-15C5-4465-843B-3FECA8DC729D@nominum.com> <CAC8QAcfL9aO4GXNN=g+vioNWvbbQM2Y-GLRf3qZ1cWS3YLpW+g@mail.gmail.com> <4A06ECB4-7F41-469A-915E-280C25FE7530@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1AEA2DE8@xmb-rcd-x04.cisco.com>
Date: Thu, 20 Feb 2014 15:05:18 -0600
Message-ID: <CAC8QAcdGVtYQWJeTKBcVjp=u6Qb9b5U7i2KfYXxJM3UM_WxuNQ@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary="001a11349626d047be04f2dcdc35"
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/byruLj-OZ16P-MCSzcVw0nqjwdk
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Dhc Chairs <dhc-chairs@tools.ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] New Version Notification for draft-sarikaya-nvo3-dhc-vxlan-multicast-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
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, 20 Feb 2014 21:05:25 -0000

Hi Ted, Bernie,



On Thu, Feb 20, 2014 at 12:21 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> >My concern is that I got the impression that the addresses this document
> provides need to be tracked by the server, that is that they are stateful
> ...
>
> I don't think that is the case. This is the address of a Rendezvous Point
> and the multicast group that the client needs to join. I think there is one
> set of these for each VNI (VXLAN Network Identifier). So the DHCP server
> needs to have a mapping from VNI to this information to return it to the
> client when requested, and this thus makes more careful review by the dhc
> likely a requirement before it becomes a 'standard'.
>
>
agreed.


> I'm not exactly sure why this isn't just a property of the scope or prefix
> the client is on (i.e., assigned addresses from - or if stateless is used,
> the address from which the "inform" is received) and why the VNI would have
> to be sent from client to server, but that's probably because of my lack of
> understanding as to this entire area.
>
> We clarified this, client will not send VNI instead it will ask it with
ORO as you suggested.


> > As for whether this should get a presentation in the DHC working group
> ...
>
> That is also my concern. If nvo3 is not interested in this work, why
> should we be?
>
> If this were targeted to be adopted by dhc (as it was originally) it would
> be more reasonable to request a presentation.
>
> However, I think it more appropriate in that this be a nvo3 draft as they
> better understand whether it is needed and appropriate; the dhc wg should
> certainly continue to monitor this work and provide suggestions and
> recommendations with respect to the dhc options format and processing
> requirements. Once adopted by nvo3 (or if the nvo3 chairs request an
> assessment by dhc), we can certainly take a more careful look including a
> presentation.
>
>
Agreed.


Regards,

Behcet

> - Bernie
>
> -----Original Message-----
> From: Ted Lemon [mailto:ted.lemon@nominum.com]
> Sent: Thursday, February 20, 2014 1:08 PM
> To: <sarikaya@ieee.org>; Behcet Sarikaya
> Cc: dhcwg@ietf.org; Dhc Chairs
> Subject: Re: [dhcwg] New Version Notification for
> draft-sarikaya-nvo3-dhc-vxlan-multicast-00.txt
>
> My concern is that I got the impression that the addresses this document
> provides need to be tracked by the server, that is that they are stateful.
>   I'm not sure that's the case-it just looked that way to me.
>
> As for whether this should get a presentation in the DHC working group,
> that is of course up to the chairs, but given that this is work needed by
> another working group, it would be nice if the working group chairs for
> nvo3 were to tell the working group chairs of dhc that they are seriously
> looking to adopt this document as a working group item and want the DHC
> working group's advice.   Otherwise, what's the point?   I certainly
> wouldn't support advancing this document in the DHC working group without
> such a request, and then only if this is in fact a stateful option.
>
>