[nvo3] Control plane interface between NVE and Oracle

Hi, folks: We have submitted the new versions of draft-fw-nvo3-server2vcenter-01 and Draft-wu-nvo3-nve2nve-01 http://tools.ietf.org/html/draft-fw-nvo3-server2vcenter-01 http://tools.ietf.org/html/draft-wu-nvo3-nve2nve-01 http://tools.ietf.org/html/draft-wu-nvo3-mac-learning-arp-01 which target NV

[nvo3] Review of draft-tsao-nvo3-auth-issues-00.txt

Looks interesting draft. A few comments below: 1.I am wondering how much this draft is related to SCIMP protocol http://tools.ietf.org/html/draft-scim-api-00 2. which interfaces in the NVO3 framework or architecture you really look at? a.The interface between Tenant system and NVE? b. The interace

Re: [nvo3] Control plane interface between NVE and Oracle

Hi,Zhen: Thank for your quick review, please see my reply inline below. - Original Message - From: "Cao,Zhen (cz)" To: "Qin Wu" Cc: Sent: Wednesday, February 27, 2013 8:15 PM Subject: Re: [nvo3] Control plane interface between NVE and Oracle Hi Qin, The drafts

Re: [nvo3] WG Last Call for draft-ietf-nvo3-framework-02

Dear authors: I have read this draft and think is is well written and now in good shape. Here is a few comments I like you to consider: 1. Section 2.1 You use mangement entity inconsistently, e.g., a. management entity b. management control entity c. management plane entity It is better to use con

Re: [nvo3] WG Last Call for draft-ietf-nvo3-overlay-problem-statement-02

Hi, I reviewed the change in section 3.7 "optimal forwarding"of NVO3 problem statement. It said: " IP implementations in network endpoints typically do not distinguish between multiple routers on the same subnet - there may only be a single default gateway in use, and any use of multiple

[nvo3] 答复: Orlando minutes

Hi, Mattew: For people who make comments to topic 7 discussion, I believe Dacheng should be corrected as me. Thanks! Regards! -Qin 发件人: nvo3-boun...@ietf.org [mailto:nvo3-boun...@ietf.org] 代表 Bocci, Matthew (Matthew) 发送时间: 2013年4月3日 23:14 收件人: nvo3@ietf.org 主题: [nvo3] Orlando minutes WG I have

Re: [nvo3] NVO3 Terminology changes

1) Oracle -> Information Mapping Authority Stewart mentioned that he has copyright concerns with using the term "oracle", and others have expressed distaste as well. In draft-kreeger-nvo3-hypervisor-nve-cp-01 we replaced the term with "Information Mapping Authority" (IMA). We would like to ge

[nvo3] 答复: NVO3 Terminology changes

Hi, Larry: Please see my followup comments below. Regards! -Qin 发件人: Larry Kreeger (kreeger) [mailto:kree...@cisco.com] 发送时间: 2013年4月9日 11:36 收件人: Qin Wu; nvo3@ietf.org 主题: Re: NVO3 Terminology changes Hi Qin, My responses are below marked with LK>. - Larry From: Qin Wu mailto:b

[nvo3] 答复: Comments on draft-ietf-nvo3-overlay-problem-statement

Hi, Eric: Sorry for my missing your reply for quite a long time. I believe you understand my concern. However when I revisit the section3.7 of PS draft, I feel even confusing, it said: “ The optimal forwarding problem applies to both outbound and inbound traffic. For outbound traffic, the c

[nvo3] 答复: NVO3 Terminology changes

That is the option I have thought about. I used this term (i.e.,NVE controller) in my presentation of Orlando meeting. Regards! -Qin -邮件原件- 发件人: nvo3-boun...@ietf.org [mailto:nvo3-boun...@ietf.org] 代表 Lou Berger 发送时间: 2013年4月10日 6:19 收件人: Larry Kreeger (kreeger) 抄送: nvo3@ietf.org 主题: Re:

[nvo3] 答复: NVO3 Terminology changes

face is a clear and distinct name �C it’s a name, not a full description. But vNIC was probably inconsistent as we came to an understanding that the interface could be virtual or physical. There is no reason to restrict the tenant interfaces to being virtual. [Qin Wu]: Agree. That is what I

[nvo3] 答复: 答复: NVO3 Terminology changes

>[Qin]: In that case, vNIC is not equivalent to Tenant System interface since >tenant system interface can be either physical interface or virtual interface. >The reason I propose such change is vNIC is virtual NIC not physical NIC, >therefore if you replace vNIC with Tenant system interface, tha

[nvo3] 答复: 答复: 答复: NVO3 Terminology changes

>>I believe one tenant system can host multiple VMs, each VM may have multiple >>vNIC adapters that it uses to communicate with both the virtual and physical >>networks. >LK> A VM is one example of a tenant system…so it would not host VMs. You may >be thinking of "End Device". >[Qin]: Not sur

[nvo3] 答复: 答复: 答复: 答复: NVO3 Terminology changes

with what Pat comment on this list. Regards! -Qin 发件人: Reith, Lothar [mailto:lothar.re...@detecon.com] 发送时间: 2013年4月15日 19:18 收件人: Qin Wu; Larry Kreeger (kreeger); nvo3@ietf.org 主题: AW: [nvo3] 答复: 答复: 答复: NVO3 Terminology changes I believe that it is not possible to replace the term vNIC with “TSI

[nvo3] 答复: 答复: Comments on draft-ietf-nvo3-overlay-problem-statement

th dealing with this case? It is not clear to me. Regards! -Qin -邮件原件- 发件人: nvo3-boun...@ietf.org [mailto:nvo3-boun...@ietf.org] 代表 Thomas Narten 发送时间: 2013年4月18日 0:38 收件人: Qin Wu 抄送: Eric Gray; nvo3@ietf.org 主题: Re: [nvo3] 答复: Comments on draft-ietf-nvo3-overlay-problem-statement Hi Q

[nvo3] 答复: 答复: 答复: 答复: 答复: NVO3 Terminology changes

WARNING: contains banned part --- Begin Message --- Hi, Larry: Please see my follow-up comment below. Regards! -Qin 发件人: Larry Kreeger (kreeger) [mailto:kree...@cisco.com] 发送时间: 2013年4月18日 0:56 收件人: Qin Wu; Anoop Ghanwani; Black, David 抄送: nvo3@ietf.org; Reith, Lothar 主题: Re: [nvo3] 答复

[nvo3] 答复: 答复: 答复: 答复: 答复: NVO3 Terminology changes

Hi, : Sorry, my figure is filtered out. So I send it again. Regards! -Qin 发件人: Larry Kreeger (kreeger) [mailto:kree...@cisco.com] 发送时间: 2013年4月18日 0:56 收件人: Qin Wu; Anoop Ghanwani; Black, David 抄送: nvo3@ietf.org; Reith, Lothar 主题: Re: [nvo3] 答复: 答复: 答复: 答复: NVO3 Terminology changes >Hi Qin,

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

we need to distinct pNIC from vNIC, two type of tenant NICs have Already existed. Please see my reply inline below. Regards! -Qin -Original Message- From: Thomas Narten [mailto:nar...@us.ibm.com] Sent: Friday, April 19, 2013 10:07 PM To: Qin Wu Cc: nvo3@ietf.org Subject: vNICs and pN

Re: [nvo3] 答复: 答复: Comments on draft-ietf-nvo3-overlay-problem-statement

Narten [mailto:nar...@us.ibm.com] Sent: Thursday, April 18, 2013 8:41 PM To: Qin Wu Cc: Eric Gray; nvo3@ietf.org Subject: Re: [nvo3] 答复: 答复: Comments on draft-ietf-nvo3-overlay-problem-statement Hi Qin. > Your proposed text improve a lot since it deal with both communication > between two

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

haler Sent: Saturday, April 20, 2013 2:30 AM To: Thomas Narten; Qin Wu Cc: nvo3@ietf.org Subject: Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt In addition to Thomas's point, we should not restrict the number of physical NICs that a tenant system can have. Some tenant systems will hav

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

f view, tenant system >should know whether it is pNIC or vNIC. Regards! -Qin -Original Message- From: Pat Thaler [mailto:ptha...@broadcom.com] Sent: Saturday, April 20, 2013 3:44 AM To: Thomas Narten Cc: Qin Wu; nvo3@ietf.org Subject: RE: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-0

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

arten; Pat Thaler Cc: nvo3@ietf.org; Qin Wu Subject: AW: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt Thomas, See below. I do not agree to the wording. And I suggest to change the definition of tenant system, which I identified as being perhaps a root cause of confusio

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

[mailto:lothar.re...@detecon.com] Sent: Monday, April 22, 2013 3:36 PM To: Qin Wu; Thomas Narten; Pat Thaler Cc: nvo3@ietf.org Subject: AW: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt Hi Qin, I had read that a bare metal server is being used by people who do want to eliminate the overhead

Re: [nvo3] New name for "oracle"

Larry: I agree to use NVA. Regards! -Qin From: nvo3-boun...@ietf.org [mailto:nvo3-boun...@ietf.org] On Behalf Of Larry Kreeger (kreeger) Sent: Tuesday, April 23, 2013 6:25 AM To: nvo3@ietf.org Subject: [nvo3] New name for "oracle" It looks like the thread about the new term for oracle has stoppe

Re: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04.txt

+1 -Qin -Original Message- From: David Allan I [mailto:david.i.al...@ericsson.com] Sent: Thursday, April 25, 2013 12:10 AM To: Reith, Lothar; ramki Krishnan; Jon Hudson Cc: Thomas Narten; Pat Thaler; nvo3@ietf.org; Qin Wu Subject: RE: [nvo3] vNICs and pNics in draft-wu-nvo3-nve2nve-04

Re: [nvo3] Introduction to TIME Mailing List

FYI. 发件人: Time [mailto:time-boun...@ietf.org] 代表 Qin Wu 发送时间: 2014年6月10日 14:48 收件人: t...@ietf.org 抄送: Romascanu, Dan (Dan); Mishael Wexler 主题: [Time] Introduction to TIME Mailing List Dear all, This is to introduce the TIME mailing list. TIME stands for “Transport Independent OAM in Multi

Re: [nvo3] YANG models for OAM

Hi, Tissa: Thanks for initiating discussion on this topic. Unified OAM for multi-Layer network is a good idea to me. draft-ww-opsawg-multi-layer-oam-00 we proposed in opsawg laid out the an initial description of the problem. The question to draft-tissa-netmod-oam is I am wondering how this generi

Re: [nvo3] YANG models for OAM

. Regards! -Qin 发件人: Tissa Senevirathne (tsenevir) [mailto:tsene...@cisco.com] 发送时间: 2014年6月30日 0:20 收件人: Qin Wu; t...@ietf.org 抄送: net...@ietf.org; nvo3@ietf.org; tr...@ietf.org; l2...@ietf.org; ops...@ietf.org 主题: RE: YANG models for OAM Hi Qin There are several way this is applicable to SFC

Re: [nvo3] YANG models for OAM

consolidation in the data plane. Please see my reply inline below. Regards! -Qin 发件人: Tissa Senevirathne (tsenevir) [mailto:tsene...@cisco.com] 发送时间: 2014年7月8日 22:48 收件人: Qin Wu; t...@ietf.org 抄送: net...@ietf.org; nvo3@ietf.org; tr...@ietf.org; l2...@ietf.org; ops...@ietf.org 主题: RE: YANG models for OAM Hi

Re: [nvo3] YANG models for OAM

I think MEF more look at Yang data module for Y.1731, It is Ethernet technology specific Yang Data model. Regards! -Qin 发件人: OPSAWG [mailto:opsawg-boun...@ietf.org] 代表 O'Connor, Don 发送时间: 2014年8月1日 7:32 收件人: Tissa Senevirathne; Greg Mirsky; Tissa Senevirathne (tsenevir) 抄送: l2...@ietf.org; ops...

Re: [nvo3] YANG models for OAM

Exactly, different layer may have different addressing schemes. But I am wondering which layer the flow entropies are applied? L2, L3, MPLS layer? 发件人: netmod [mailto:netmod-boun...@ietf.org] 代表 Tissa Senevirathne (tsenevir) 发送时间: 2014年8月1日 7:49 收件人: O'Connor, Don; Tissa Senevirathne; Greg Mirsky

Re: [nvo3] OAM: 96 bits of customer data?

Agree with Deepak. -Qin -邮件原件- 发件人: nvo3 [mailto:nvo3-boun...@ietf.org] 代表 Deepak Kumar (dekumar) 发送时间: 2015年5月23日 4:29 收件人: Erik Nordmark 抄送: nvo3@ietf.org 主题: Re: [nvo3] OAM: 96 bits of customer data? Hi Erik, Agreed we don't ned 96 bytes of customer data in all scenario for intra-DC b

Re: [nvo3] New NVO3 Chair: Sam Aldrin

Congratulation to Sam! -Qin 发件人: nvo3 [mailto:nvo3-boun...@ietf.org] 代表 Alia Atlas 发送时间: 2016年7月7日 23:56 收件人: nvo3@ietf.org 抄送: Sam Aldrin; Matt Bocci 主题: [nvo3] New NVO3 Chair: Sam Aldrin I am pleased to announce that Sam Aldrin has accepted my request to serve as NVO3 chair. As previously anno

Re: [nvo3] WG adoption poll for draft-zhang-nvo3-yang-cfg-07.txt

I believe this draft is a good starting point of NVO3 YANG data model. The essence of this model is overlay tunnel model which is independent of various encapsulation technology. Therefore I support WG to adopt this draft. -Qin Wu -邮件原件- 发件人: nvo3 [mailto:nvo3-boun...@ietf.org] 代表 Bocci

Re: [nvo3] Opsdir last call review of draft-ietf-nvo3-encap-10

Eastlake [mailto:d3e...@gmail.com] 发送时间: 2023年11月24日 12:40 收件人: Qin Wu 抄送: ops-...@ietf.org; draft-ietf-nvo3-encap@ietf.org; last-c...@ietf.org; nvo3@ietf.org 主题: Re: Opsdir last call review of draft-ietf-nvo3-encap-10 Thanks for your thorough review. However, I think a few of your questions are

[nvo3] Opsdir last call review of draft-ietf-nvo3-encap-10

Reviewer: Qin Wu Review result: Has Nits This document can be seen as NVO3 encapsulation design team report and compares 3 typical data plane encapsulation formats including GENEVE, GUE, VXLAN-GPE and explores technical problem and limitation and provides guidance and recommendation for