Re: [Tsv-art] TSV Triage team: Review of IETF LC documents as of 01/11
"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Tue, 17 January 2017 12:10 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2432A129447 for <tsv-art@ietfa.amsl.com>; Tue, 17 Jan 2017 04:10:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Level:
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 WUFmOlsiONXs for <tsv-art@ietfa.amsl.com>; Tue, 17 Jan 2017 04:10:54 -0800 (PST)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DE671293E9 for <tsv-art@ietf.org>; Tue, 17 Jan 2017 04:10:54 -0800 (PST)
Received: (qmail 17715 invoked from network); 17 Jan 2017 13:10:52 +0100
Received: from p5dec276e.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.39.110) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 17 Jan 2017 13:10:52 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <65b73a6b-dadc-89ec-bf84-adba0a6b7ca7@isi.edu>
Date: Tue, 17 Jan 2017 13:10:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA3B83DD-24EA-446C-B6AE-42354F4767E2@kuehlewind.net>
References: <7c475f41-c31d-b149-c20b-011cb2f87db0@gmail.com> <7aa4a8d0-8270-40b9-4bb8-0d09fd79ea81@isi.edu> <D12ABF2F-674B-473B-B7B0-34B3B17E8771@kuehlewind.net> <CE03DB3D7B45C245BCA0D243277949362F7CFDF1@MX307CL04.corp.emc.com> <30599C28-08A3-4146-BB8D-116B864574EB@isi.edu> <65b73a6b-dadc-89ec-bf84-adba0a6b7ca7@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/OQZk_GuHumdVVMWSPJM5Tuis_RI>
Cc: Martin Stiemerling <mls.ietf@gmail.com>, "Black, David" <David.Black@dell.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: Re: [Tsv-art] TSV Triage team: Review of IETF LC documents as of 01/11
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 12:10:56 -0000
Hi Joe, I finally read the draft myself completely. I agree that there is nothing in the draft that motivates a new tunnel protocol, however, the draft is also not (explicitly) requiring a new protocol. This says in the summary: „A tunnel encapsulation protocol is necessary.“ which clearly doesn’t say that an existing one might not be sufficient. I don’t think there is anything we can do at this stage and with this draft… I’ll wait for David’s review before I put in my ballot. Mirja > Am 14.01.2017 um 18:22 schrieb Joe Touch <touch@isi.edu>: > > David - I think it'd be useful for fresh eyes on this. IMO, it's full of > vendor terminology that I don't think sufficiently differentiates the > data center case from any other variant of virtual network. > > This is the use case doc that purports to motivate "yet another" UDP > tunneling mechanism, which has generated quite a bit of controversy and > I expect would be more relevant to TSV. > > However, I'm struck by the need to publish a use case doc so soon after > the problem statement doc (just two years ago), but that's not a TSV issue. > > Joe > > > On 1/14/2017 8:09 AM, Joe Touch wrote: >> I've been giving them feedback for a while. >> >> Joe >> >>> On Jan 14, 2017, at 7:07 AM, Black, David <David.Black@dell.com> wrote: >>> >>> As one of the authors of the NVO3 architecture RFC, RFC 8014, I'd be willing to help with a Transport review of this NVO3 use case draft. That'll have to happen quickly, as it looks like IETF LC ended on Wednesday, and the draft's on this week's telechat agenda. >>> >>> Joe? >>> >>> Thanks, --David >>> >>>> -----Original Message----- >>>> From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Mirja Kuehlewind >>>> (IETF) >>>> Sent: Saturday, January 14, 2017 6:49 AM >>>> To: Joe Touch >>>> Cc: Martin Stiemerling; tsv-art@ietf.org >>>> Subject: Re: [Tsv-art] TSV Triage team: Review of IETF LC documents as of 01/11 >>>> >>>> Hi Joe, >>>> >>>> I also thought that this could potentially have a transport review. If you’d be able >>>> to send one that be great, please do so. Or what do you meant by it’s already >>>> being watched? >>>> >>>> Mirja >>>> >>>> >>>>> Am 13.01.2017 um 23:09 schrieb Joe Touch <touch@isi.edu>: >>>>> >>>>> Hi Martin, >>>>> >>>>> I've been tracking this one for a while: >>>>> >>>>> draft-ietf-nvo3-use-case-15 >>>>> >>>>> It does have significant transport issues, but it's already being >>>>> watched ;-) >>>>> >>>>> Joe >>>>> >>>>> >>>>>> On 1/11/2017 1:52 PM, Martin Stiemerling wrote: >>>>>> Dear TSVers, >>>>>> >>>>>> First of all, a happy new (western) year! :) >>>>>> >>>>>> I did work through all documents that are in IETF LC, IESG processing >>>>>> or being requested for publication as of 01/11, 09:00 pm UTC. >>>>>> >>>>>> Please find below all documents checked and what to do with these >>>>>> documents. >>>>>> >>>>>> >>>>>> Documents that require TSV attention: >>>>>> none. >>>>>> >>>>>> >>>>>> Documents that do not require TSV attention: >>>>>> draft-ietf-oauth-jwsreq-09 >>>>>> draft-ietf-ipsecme-rfc4307bis-15 >>>>>> draft-ietf-geojson-text-sequence-03 >>>>>> draft-ietf-dime-agent-overload-08 >>>>>> draft-ietf-bmwg-ipv6-nd-04 >>>>>> draft-ietf-intarea-hostname-practice-03 >>>>>> draft-mohali-dispatch-cause-for-service-number-12 >>>>>> draft-ietf-trill-rfc6439bis-04 >>>>>> draft-ietf-trill-directory-assist-mechanisms-10 >>>>>> draft-ietf-teas-p2mp-loose-path-reopt-08 >>>>>> draft-ietf-teas-gmpls-resource-sharing-proc-06 >>>>>> draft-ietf-sidr-rpki-oob-setup-06 >>>>>> draft-ietf-sidr-publication-10 >>>>>> draft-ietf-sidr-adverse-actions-03 >>>>>> draft-ietf-rtgwg-rlfa-node-protection-10 >>>>>> draft-ietf-mpls-residence-time-12 >>>>>> draft-ietf-lisp-type-iana-04 >>>>>> draft-ietf-ecrit-ecall-22 >>>>>> draft-ietf-ecrit-car-crash-21 >>>>>> draft-ietf-bfcpbis-bfcp-websocket-13 >>>>>> draft-ietf-6man-rdnss-rfc6106bis-14 >>>>>> draft-holmberg-dispatch-mcptt-rp-namespace-04 >>>>>> draft-murchison-webdav-prefer-13 >>>>>> draft-ietf-dnsop-edns-key-tag-03 >>>>>> draft-ietf-payload-melpe-04 >>>>>> draft-ietf-insipid-logme-reqs-11 >>>>>> draft-ietf-softwire-multicast-prefix-option-11 >>>>>> draft-ietf-clue-rtp-mapping-10 >>>>>> draft-ietf-bfcpbis-sdp-ws-uri-07 >>>>>> draft-ietf-dhc-dhcpv6-failover-protocol-03 >>>>>> draft-ietf-nvo3-use-case-15 >>>>>> draft-ietf-softwire-dslite-multicast-14 >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Martin >>>>>> >>>>>> _______________________________________________ >>>>>> Tsv-art mailing list >>>>>> Tsv-art@ietf.org >>>>>> https://www.ietf.org/mailman/listinfo/tsv-art >>>>> _______________________________________________ >>>>> Tsv-art mailing list >>>>> Tsv-art@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/tsv-art >>>> _______________________________________________ >>>> Tsv-art mailing list >>>> Tsv-art@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tsv-art > > _______________________________________________ > Tsv-art mailing list > Tsv-art@ietf.org > https://www.ietf.org/mailman/listinfo/tsv-art
- [Tsv-art] TSV Triage team: Review of IETF LC docu… Martin Stiemerling
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Spencer Dawkins at IETF
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Joe Touch
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Mirja Kuehlewind (IETF)
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Black, David
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Joe Touch
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Joe Touch
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Black, David
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Joe Touch
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Mirja Kuehlewind (IETF)
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Black, David
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Mirja Kuehlewind (IETF)
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Mirja Kuehlewind (IETF)
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Joe Touch
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Mirja Kuehlewind (IETF)
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Spencer Dawkins at IETF
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Black, David
- Re: [Tsv-art] TSV Triage team: Review of IETF LC … Martin Stiemerling