MIME-Version: 1.0 In-Reply-To: X-Mailer: MIME-tools 5.505 (Entity 5.505) Content-Disposition: inline X-RT-Interface: Web References: <646422AD-300A-4686-BB29-BBE1266746C4@cisco.com> Content-Type: text/plain; charset="utf-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: X-RT-Encrypt: 0 X-RT-Sign: 0 Content-Length: 1090 Hello Naiming: After re-reviewing your proposed changes in light of the intended use cases and your other comments, I tend to agree with your assessment that a single global alternate port value seems to make more sense. Thank you for creating the individual patches as requested. Given the draft's current status we may wrap the changes in a conditional compilation flag. This would allow it be included in the release, even if the draft has not been accepted. Testing the changes will not be trivial given the number of permutations. We'll need to make sure we covering not just new behavior but existing behavior for regressions. Toward that end, any additional testing that you might do and document would be helpful. We'll keep you posted as things progress. As we are focusing on our upcoming maintenance releases, 4.3.6 and 4.1-ESV-R15, due July 31st I would not expect too much to happen with this issue until after that. Should you have any follow up questions or concerns, please do not hesitate to contact us. Regards, Thomas Markwalder ISC Software Engineering