Re: [dhcwg] New Version Notification for draft-sarikaya-nvo3-dhc-vxlan-multicast-00.txt
Behcet Sarikaya <sarikaya2012@gmail.com> Thu, 20 February 2014 17:50 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 0945C1A021D for <dhcwg@ietfa.amsl.com>; Thu, 20 Feb 2014 09:50:00 -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 TdQoLM_rAFwp for <dhcwg@ietfa.amsl.com>; Thu, 20 Feb 2014 09:49:58 -0800 (PST)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) by ietfa.amsl.com (Postfix) with ESMTP id C94F91A0053 for <dhcwg@ietf.org>; Thu, 20 Feb 2014 09:49:57 -0800 (PST)
Received: by mail-lb0-f177.google.com with SMTP id 10so1552501lbg.36 for <dhcwg@ietf.org>; Thu, 20 Feb 2014 09:49:53 -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=nYDdZLYucUYLQdBOVmJFg7NR2GdYqo1pyPKHr06yeT8=; b=Y41uENY52NeHZtiefU52cn+W75Fesg95u+xG9zZh/rhBwfm8+pCvkSDaTeaVw0f9GY mAAWm6+EVNrSYHdCd+LVJk3RL1BkTOeBN9tggnKXL6BlelpQPvZQeUmgOHihjij34xNs Mzr/sQ84GlrekOQoDyMuegBaWW5KXFSjOdjQ97INC5NKfd6EWnFFw1zC2fhMxOSEVFXV hqUMw/IYxFZEF6t2gbmHA3XyjYWeWu12WwxpDJLo7nwe0VmCI/v/0qqBPsRRbipRufKZ 8fY5Kk2QBMThdYVtBRFjRMoQ0TZEO6IMmk/bkX4mW9MgnycYOPD1bj42x6Vo791VGEG1 oC2A==
MIME-Version: 1.0
X-Received: by 10.112.41.100 with SMTP id e4mr1768138lbl.84.1392918593493; Thu, 20 Feb 2014 09:49:53 -0800 (PST)
Received: by 10.114.170.195 with HTTP; Thu, 20 Feb 2014 09:49:53 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AE9FC65@xmb-rcd-x04.cisco.com>
References: <20140214173114.23812.70162.idtracker@ietfa.amsl.com> <CAC8QAcfGgayrUkXZp4hNdGeZpfv3hazpg4n=2kx8qUHqObhUAg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1AE72D20@xmb-rcd-x04.cisco.com> <CAC8QAcfn-EQEvr6Mzvc7iQw2wQGL+YdGtMQuh2JxLr8jpmRvmg@mail.gmail.com> <CF2A661A.190C6%volz@cisco.com> <BA3D42CB-A15E-473E-B0B1-F7532A56ADB6@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1AE9FC65@xmb-rcd-x04.cisco.com>
Date: Thu, 20 Feb 2014 11:49:53 -0600
Message-ID: <CAC8QAceTCxMTDQO6VRA3dYGK_gbKhxoUs9ccKAP14-mW=NZkig@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary="001a1135e87af7631c04f2da2138"
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/GxQtu9YumN4WoUw7o1J2iHZa5XY
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 17:50:00 -0000
On Wed, Feb 19, 2014 at 3:54 PM, Bernie Volz (volz) <volz@cisco.com> wrote: > I agree. Though there now has been some discussion :). > > As this is now targeted at nvo3, I don't see a strong need for a > presentation in dhc at this time. If the nvo3 adopts this work (i.e., > believes it is a problem that needs a solution), we can revisit for a > future presentation? Of course, you should continue to make the dhc aware > of the progress of this draft and collecting input when offered or if you > raise specific issues or questions. > > It is odd that this isn't on the nvo3 agenda (at least at present), as it > would seem to be more appropriate there as the intended WG. > > Bernie, I presented it in nvo3 in Vancouver, this time we did not ask a slot. About dhc presentation slot, it is up to you, I remember last time we were assigned a slot but never had a chance. We would like to clarify all the comments made so far, right now Ted's comment has not yet been resolved, we are waiting for his reply. Regards, Behcet > --- > > General comment about many individual drafts: > > I think that people that submit individual drafts don't always take the > next [manual] step to notify the DHC WG of that draft. They (mistakenly) > believe somehow that the "group" is notified when it isn't (the main ietf > mailing list gets the notice, but not the dhc wg). > > I would highly recommend that any new or updated draft posting (whether WG > document or individual) is followed up with an email to the DHC WG: > - for new drafts, explain it (perhaps by using the abstract or > introduction) and why you feel it is important to the WG and what you want > the WG to do with the draft (if individual). Think of this as presenting > the main points and what areas you feel the WG may want to review or have a > particular concern about. > - for updates, indicate what has changed and why. And for individual, > again indicate what you want the WG to do next with the draft. Is it FYI? > Is it because you feel it is ready for adoption and will propose a call > shortly? ... > > There are some WGs where the chairs do post "a new draft or new revision > has been posted" (for individual drafts related to the WG). But in the DHC > WG we assume that the authors will do this and expect them to - the chairs > have enough to do! > > - Bernie > > -----Original Message----- > From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon > Sent: Wednesday, February 19, 2014 2:20 PM > To: Bernie Volz (volz) > Cc: dhcwg@ietf.org; Dhc Chairs > Subject: Re: [dhcwg] New Version Notification for > draft-sarikaya-nvo3-dhc-vxlan-multicast-00.txt > > Before the working group hears a presentation on this, it would be good if > Behcet could answer the question I asked on the mailing list. If the > draft isn't important enough to discuss on the mailing list, it surely > doesn't need time on the schedule in London! > > _______________________________________________ > 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] Fwd: New Version Notification for draft-s… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Bernie Volz (volz)
- Re: [dhcwg] New Version Notification for draft-sa… Ted Lemon
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Bernie Volz (volz)
- Re: [dhcwg] New Version Notification for draft-sa… Ted Lemon
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Bernie Volz (volz)
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya
- Re: [dhcwg] New Version Notification for draft-sa… Bernie Volz (volz)
- Re: [dhcwg] New Version Notification for draft-sa… Ted Lemon
- Re: [dhcwg] New Version Notification for draft-sa… Bernie Volz (volz)
- Re: [dhcwg] New Version Notification for draft-sa… Behcet Sarikaya