Agree with Deepak.
-Qin
-----邮件原件-----
发件人: nvo3 [mailto:[email protected]] 代表 Deepak Kumar (dekumar)
发送时间: 2015年5月23日 4:29
收件人: Erik Nordmark
抄送: [email protected]
主题: 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 but
it will required in few scenarios and need to be use judiciously by user.
Network Diagram (Tried my best I will do better diagram in the draft)
/ S1 \ / S2 \ (L3 VTEP)
/ \ / \ (full mesh in east/west, x1<->s1,s2,
x2<->s1,s2, ...)
/ \ / \
X1 X2 X3 X4 ...
/ \ / |
/ \ / | full mesh in east/west l1<->x1, x2, x3, x4,
l2 <-> x1,x2,x3,x4, l3 ..)
/ \ / |
L1 L2 L3 L4 Š (L2 VTEP)
| |
H1 H2 ŠŠ
Now H1 is host, L1 is Switch, X1 is switch in underlay, S1 is switch with
l3 gateway functionality.
All switches are connected in East West fully connected with multiple way ecmp.
Customer want to test L1 - Lx scenario providing Host information (H1, and
Hx)
For example: H1 and Hx are in inter subnet and across mobility domain or any
scenario where traffic will reach till L3 VTEP.
L3 VTEP will do de-encap of outer header, vxlan header and do again re-encap of
packet towards Lx.
Now to forward packet toward Lx Inner payload should be same as customer
information so right hashing is choosen as it's done for real data packet.
Thanks,
Deepak
On 5/22/15 8:31 AM, "Erik Nordmark" <[email protected]> wrote:
>Deepak,
>
>Didn't have time to go into this on the call, but the draft and your
>slides refer to "96 bits of customer data"
>I understand why that was needed for TRILL - basically the entropy for
>ECMP/LAG is calculated at each hop in TRILL so it needs to look at the
>inner Ethernet, IP, and TCP/UDP headers.
>
>But for NVO3 the thinking is to use a UDP header where the source UDP
>port is set (in the ingress NVE) to some hash of those inner addresses
>and ports.
>If that is the source of entropy, why do we need to also carry 96 bits
>of the inner packet in the OAM frames?
>
>Regards,
> Erik
>
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
