Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Alia Atlas <akatlas@gmail.com> Tue, 03 June 2014 13:31 UTC
Return-Path: <akatlas@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BC21A026D; Tue, 3 Jun 2014 06:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 OjZqHFku5O-B; Tue, 3 Jun 2014 06:31:28 -0700 (PDT)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B62C51A01F6; Tue, 3 Jun 2014 06:31:27 -0700 (PDT)
Received: by mail-yh0-f50.google.com with SMTP id 29so5071436yhl.37 for <multiple recipients>; Tue, 03 Jun 2014 06:31:21 -0700 (PDT)
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; bh=mECdWv/1n1aUiMdL+kodxM2mu2Mwus8ZJQcfJ9l0CIA=; b=u1ntx9Qhh4NIYHtfmaT3SqDovQTOWDYFaDmTlJmacdyMPQmisnqreyX4WSrvlhxDpb c3m55eVzgF9pv0BD+AtAsiaei9qXiF7RYspbVMUfWnte+K2lTRJnpQJZdzX8sppLhnPH lEm1d+w4hxpTe4AqQPkq2tqU34YSS1+IoNq68j7tq9aGfRT6fpLSjYaJu2MnKxQ54g02 5AZcqwa/mCMVk+LnokiXUVY+knRVT/RY07lz8WDPlqc9hDqFxZ35oKOoiQrUBP9ry5HY ksMPutgX3ft+F5OBNh3CCgjp3/aJKYV6EiLmqRS37eCDtzlGCgsLpWDiMFil3T0VQt08 tNmQ==
MIME-Version: 1.0
X-Received: by 10.236.150.205 with SMTP id z53mr63022560yhj.75.1401802281708; Tue, 03 Jun 2014 06:31:21 -0700 (PDT)
Received: by 10.170.194.2 with HTTP; Tue, 3 Jun 2014 06:31:21 -0700 (PDT)
In-Reply-To: <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <20140521143310.22736.34790.idtracker@ietfa.amsl.com> <4A95BA014132FF49AE685FAB4B9F17F645D23B76@dfweml701-chm.china.huawei.com> <m3d2erdxis.wl%narten@us.ibm.com> <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com> <B30152B129674240ADF67727A967301408CBA0@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Date: Tue, 03 Jun 2014 09:31:21 -0400
Message-ID: <CAG4d1rfKk_b=DqYwj+rd-KjbJzfqgd86kbzApd+Ae19Gve1SKQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="20cf303a2d610bf22504faee879b"
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/5CG3NomHQBg7T6PIZRF_vY9orCU
Cc: Thomas Narten <narten@us.ibm.com>, "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 13:31:30 -0000
Marc, An updated draft would be excellent -before Thursday, preferably. Thanks, Alia On Tue, Jun 3, 2014 at 4:01 AM, LASSERRE, MARC (MARC) < marc.lasserre@alcatel-lucent.com> wrote: > Alia, > > I have replied and suggested some minor edits to address Linda and Lucy's > comments. I have suggested to be protocol agnostic rather than giving > specific examples in the multi-homing case. > Some of Linda's comments have been discussed at length in the past and > there was clear WG consensus that the framework draft addressed NVO3's > problem. > > Let me know if you want me to post a revised draft based on these minor > edits and some other suggested edits from other IETF reviewers received > last week prior to next week IESG review. > > Regards, > Marc > > ------------------------------ > *From:* nvo3 [mailto:nvo3-bounces@ietf.org] * On Behalf Of *Alia Atlas > *Sent:* Monday, June 02, 2014 8:59 PM > > *To:* Thomas Narten > *Cc:* nvo3@ietf.org; ietf@ietf.org; Linda Dunbar > *Subject:* Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> > (Framework for DC Network Virtualization) to Informational RFC > > Thomas, > > The NVO3 Framework draft is in IETF Last Call, which isn't precisely > stalled. > It is true that Linda and Lucy have raised some concerns about it. > > I have not yet heard from the WG chairs or authors whether the desired > changes > have been previously discussed and had consensus determined in the WG. > Linda indicated that her > comments had already been discussed on the nvo3 mailing list. Lucy is > requesting that different > technology be indicated as examples - perhaps to give a sense of future > possible solutions to the > readers of the draft. > > If there is WG consensus to make a few minor edits, that can be done > before the > IESG review next week. It is on the next telechat, so I would appreciate > speed in > resolving the minor comment. > > Regards, > Alia > > > On Mon, Jun 2, 2014 at 1:36 PM, Thomas Narten <narten@us.ibm.com> wrote: > >> I've followed the discussion on this thread and want to go back to >> something folk may have forgotten. >> >> More than a year ago, the WG made a considered and conscious decision >> to "ship" the framework documemnt more or less "as is" and start work >> on a followup architecure document. It was known and expected that the >> architecture document would become the focus of work moving forward >> and that substantive additions/changes would go there. Even if it >> meant the framework document would be less complete. >> >> Sadly, it has been more than a year since that decision was made, yet >> the framework document appears stalled and unable to get >> published. I'll note that the problem statement document to which the >> framework is a companion, has been languishing in the RFC editor queue >> for almost a year now, blocked on a normative reference to the >> definitions in the framework document. >> >> FWIW, I think the framework is good enough to publish more-or-less as >> is. Or more to the point, there just isn't energy to make significant >> changes to the document given that the focus of the WG has long since >> moved to the architecture document. >> >> If folk have substantive issues with the framework, I'd strongly >> suggest first looking at the architecture >> (draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists >> there, and of so, whether the archictecture document would be a better >> place to address the concern. >> >> Thomas >> >> _______________________________________________ >> nvo3 mailing list >> nvo3@ietf.org >> https://www.ietf.org/mailman/listinfo/nvo3 >> > >
- [nvo3] Last Call: <draft-ietf-nvo3-framework-06.t… The IESG
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Ken Gray (kegray)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Ken Gray (kegray)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Ken Gray (kegray)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Brian E Carpenter
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Larry Kreeger (kreeger)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Black, David
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Lucy yong
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Thomas Narten
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Barry Leiba
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Black, David
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Thomas Narten
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Barry Leiba
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Alia Atlas
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Alia Atlas
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… LASSERRE, MARC (MARC)