Subject: [nvo3] FW: comments to draft-ietf-nvo3-dataplane-requirements-00

From: Linda Dunbar <[email-masked]>
Date: Fri, 31 May 2013 21:33:00 +0000

Nabil, et al:

Here are some comments and questions to your draft:

-        3.2.1: L2 VNI:

"..standard MAC learning procedures are used: The source MAC address is learned against the VAP or the NVO3 tunnel on which the frame arrived.."

Standard MAC learning is actually: Inner MAC Source address is learned to be mapped to the outer (IP) Source address.

"..the NVE MUST either support ingress replication or multicast. In this latter case, the NVE MUST be able to build at least a default flooding tree per VNI. In such cases, multiple VNIs MAY share the same default flooding tree."

One sentence says "at least a default flooding tree per VNI". The next sentence says "multiple VNIs may share the same default flooding tree". It is inconsistent.

I don't think it is necessary to require that "NVE MUST be able to build one flooding tree per VNI". Besides, it is  not the NVE who builds the multicast tree.

-        3.2.2: L3 VNI:
"L3 VNIs MUST support per-tenant forwarding instance with IP address isolation..."

Is it same as L3VPN requirement?

"the inner TTL field MUST be decremented by (at least) 1 as if the NVO3 egress NVE was one (or more) hop(s) Away"

Is it referring to the Ingress  NVE decrementing the TTL by 1? Does Egress NVE also decrement the TTL by 1?
Why "Away" has to be capitalized?

-        4.1.1. VPN and internet GWs:
"..The translation function SHOULD NOT require provisioning touches.."

GW will need external input to match the VPN ID to the NV03 VNID. It is the "provisioning".
Why you say "Should not"?

Linda Dunbar