Re: [nvo3-dt-encap] Fwd: Uncaught bounce notification

[David Mozes <[e-mail]>]

Hi ,
I think one the things we forgot to discussed is the maximum length of the Geneve single option that it is 5 bits ,means 32x4 = 128bytes.
This is too  short if we are speaking on in band telemetry (INT) or in-situ or even security (SHA2-256)  It will be good to recommended of increasing it in 1 bit than  it become 256 bytes (There are 3 reserves bits ) the advantages will be:
1) Sufficient   length for in-band telemetry and future use.
2) Combatable with IPV6 HBH options .
3)Backward compatible to previous Geneve implementations


Thx
David 

-----Original Message-----
From: nvo3-dt-encap [mailto:[e-mail]] On Behalf Of Pankaj Garg
Sent: Tuesday, January 24, 2017 6:10 PM
To: [e-mail]
Subject: [nvo3-dt-encap] Fwd: Uncaught bounce notification

---------- Forwarded message ----------
From:  <[e-mail]>
Date: Tue, Jan 24, 2017 at 8:08 AM
Subject: Uncaught bounce notification
To: [e-mail]


The attached message was received as a bounce, but either the bounce format was not recognized, or no member addresses could be extracted from it.  This mailing list has been configured to send all unrecognized bounce messages to the list administrator(s).

For more information see:
https://www.ietf.org/mailman/admin/nvo3-dt-encap/bounce



---------- Forwarded message ----------
From: Sami Boutros <[e-mail]>
To: nvo3-dt-encap <[e-mail]>
Cc:
Date: Tue, 24 Jan 2017 16:08:47 +0000
Subject: FW: Draft updated with Tal, Michael, David and Sami i/p


From: Sami Boutros <[e-mail]>
Date: Tuesday, January 24, 2017 at 7:58 AM
To: nvo3-dt-encap <[e-mail]>
Subject: Draft updated with Tal, Michael, David and Sami i/p