So, i will - Define a Shim6 error message- substtitute the current usage of ICMP error messages for the newly defined shim6 error message - define an error type suitable for debugging purposes (i.e. error that can be enabled for debugging but that are not normally in the protocol) - add e new paragraph mentioning that instead of silently discarding packet with error, a host can be configured to send an shim6 error messages for debugging purposes
makes sense?the plan is to submit the new version of the proto draft this week, so if you have issues with this or other comments, please comment
regards, marcelo El 07/04/2007, a las 0:24, Henderson, Thomas R escribió:
-----Original Message----- From: marcelo bagnulo braun [mailto:marcelo@it.uc3m.es] Sent: Friday, March 30, 2007 8:44 AM To: Brian E Carpenter; Erik Nordmark Cc: shim6-wg Subject: Re: error messages and silently discarding packets<snip>So accroding to Brian's criteria, we shoudl define a shim6 error message.. what do others think?I posted on this a few months ago, but we decided in HIP to adopt the approach taken in IKE to define these messages (HIP NOTIFY similar toIKEv2 Notify), especially for debugging, and I don't see why shim6 wouldnecessarily want to take a different stance. Tom