Re: [Int-area] [nvo3] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt

Joe Touch <touch@isi.edu> Fri, 17 June 2016 15:42 UTC

Return-Path: <touch@isi.edu>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5588F12D7A6; Fri, 17 Jun 2016 08:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 ILw8_Gewx5lN; Fri, 17 Jun 2016 08:42:13 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 608D812D79A; Fri, 17 Jun 2016 08:42:13 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u5HFfBHx004126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Jun 2016 08:41:21 -0700 (PDT)
To: Xuxiaohu <xuxiaohu@huawei.com>, Tom Herbert <tom@herbertland.com>
References: <20160610171451.30437.44413.idtracker@ietfa.amsl.com> <CALx6S34_ba2kBhUY7keEMmPO3fTRAAQsCkyGiy47=NnPm8xgug@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D5647FB@NKGEML515-MBX.china.huawei.com> <CALx6S37K2H+SuEN+5Nmi-GOX0nX-k34YQt0anWJWTUBpBZZGew@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D564ABD@NKGEML515-MBX.china.huawei.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D564B19@NKGEML515-MBX.china.huawei.com> <57637C4B.3040603@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D564BD3@NKGEML515-MBX.china.huawei.com> <5763A13F.9090009@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D564C44@NKGEML515-MBX.china.huawei.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <57641A16.7000902@isi.edu>
Date: Fri, 17 Jun 2016 08:41:10 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D564C44@NKGEML515-MBX.china.huawei.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/wJFhdnlFnRZpQuDy92zgnFi2Kik>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>
Subject: Re: [Int-area] [nvo3] Fwd: New Version Notification for draft-ietf-nvo3-gue-03.txt
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jun 2016 15:42:14 -0000


On 6/17/2016 1:31 AM, Xuxiaohu wrote:
>> > I don't see the benefit of moving this document out of NVO3 to obtain this
>> > feedback. You're already getting it from very active members of both TSVWG
>> > and INTAREA in this discussion, and there are already procedures for cross-area
>> > review.
> It depends on whether this document is describing an generic UDP-based tunneling technology or a network overlay technology for multi-tenancy. It seems that this document is the former while draft-hy-nvo3-gue-4-nvo is the latter. 
So where does IP-in-UDP belong? It's a link for IP, so that belongs in
the group designing/using the link. It's intended for IP, so that
belongs in INTAREA. It uses and ties closely to UDP, so that belongs in
TSVWG. But any service *over* a transport is an application, so it
belongs in APP (do we even have that anymore?).

There's no simple answer.

> Besides, IMHO, cross-area review could never replace the detailed and deep work within the most appropriate WG.
We have IETF-wide LC, cross-area targeted reviews requested by the
document shepherd, and subgroups (e.g., Directorates in most areas,
though it was recently renamed "TSV-Triage" in transport) who already
handle these sort of "multihomed" docs just fine. If that didn't work,
we'd constantly be reshuffling where docs appear, which we don't.

Joe