Hi,


On Fri, 2020-01-24 at 23:30 +0000, Ganga, Ilango S wrote:
> Magnus>> I think the above text is not particullar clear on what the issue is.
> Just to
> make sure I am not missunderstanding anything. So the Geneve encapsulating
> source node to avoid this issue has basically two possible implementation path
> to correctly handle ICMP messages or any other return path traffic that
> reverses
> the outer IP/UDP headers. Either it has a general listener that first try to
> determine if the packet incoming is return traffic, or one only uses "free"
> UDP
> ports on the outer IP address used when encapsulating.
>  
> I am fine with you leaving how to solve this up to the implementations, but
> you
> at least need to make the issue clear to the implementer. Also, I think it is
> dangerouse to make assumption that the outer IP address will not be used for
> anything else then GENEVE encapsulated tunnel traffic.
>  
> IG>> <Response> Instead of the previously suggested text, we will replace with
> the revised text below that is more specific in addressing the issue.
>  
> Add the following text to end of Section 3.3 source port definition (new
> paragraph):
> “If Geneve traffic is shared with other UDP listeners on the same IP address,
> tunnel endpoints SHOULD implement a mechanism to ensure ICMP return traffic
> arising from network errors is directed to the correct listener. Actual
> definition of the mechanism is beyond the scope of this document.”
> </Response>
> 

The above works for me. Ship it and I will clear.

Cheers

Magnus Westerlund 


----------------------------------------------------------------------
Networks, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: [email protected]
----------------------------------------------------------------------


Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3

Reply via email to