RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
"LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com> Tue, 03 June 2014 08:01 UTC
Return-Path: <marc.lasserre@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF331A016C; Tue, 3 Jun 2014 01:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 TDW-33ItEWpm; Tue, 3 Jun 2014 01:01:35 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CE2D1A0162; Tue, 3 Jun 2014 01:01:35 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s5381GxJ017464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 3 Jun 2014 03:01:18 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s53817be010384 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Jun 2014 10:01:15 +0200
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.131]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 3 Jun 2014 10:01:15 +0200
From: "LASSERRE, MARC (MARC)" <marc.lasserre@alcatel-lucent.com>
To: Alia Atlas <akatlas@gmail.com>, Thomas Narten <narten@us.ibm.com>
Subject: RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Topic: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC
Thread-Index: AQHPdQIKiFgojcPjTkKOT8QRrMyEo5tMzYgAgBE5NoCAABcJAIAA+uBw
Date: Tue, 03 Jun 2014 08:01:14 +0000
Message-ID: <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>
In-Reply-To: <CAG4d1rfUunY2Q-2qe0Ugp_zERM9wYJ6547aNPQ1BRS5tiHUtyQ@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_B30152B129674240ADF67727A967301408CBA0FR711WXCHMBA03zeu_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5xyzznTxSa8jaSJdc7fCwSf4sHU
X-Mailman-Approved-At: Tue, 03 Jun 2014 08:09:28 -0700
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jun 2014 08:01:37 -0000
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<mailto: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<mailto:nvo3@ietf.org> https://www.ietf.org/mailman/listinfo/nvo3
- 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-… Ken Gray (kegray)
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Ken Gray (kegray)
- RE: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Linda Dunbar
- Re: Last Call: <draft-ietf-nvo3-framework-06.txt>… Brian E Carpenter
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Ken Gray (kegray)
- RE: Last Call: <draft-ietf-nvo3-framework-06.txt>… Templin, Fred L
- 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-… Linda Dunbar
- Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-… Larry Kreeger (kreeger)
- 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-… 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-… 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-… 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-… LASSERRE, MARC (MARC)