Message-ID: Content-Type: text/plain; charset="utf-8" In-Reply-To: X-Mailer: MIME-tools 5.508 (Entity 5.508) Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 Content-Disposition: inline MIME-Version: 1.0 References: X-RT-Interface: Web RT-Send-CC: Content-Length: 1590 Feedback received on visual inspection of the patch (but not from actual testing): "I haven't had a chance to try out the patch, though it looks like it should address the immediate issue. There does appear to be an inconsistency in some of the code that the patch continues. In some places it appears as if prefixes for PD can be defined globally while in others it appears as if globally scoped prefixes aren't handled. For an example of possible globally scoped prefixes see dhcpv6.c:find_client_prefix() There is a comment of: /* * Consider this prefix if it is in a global pool or * if it is scoped in a pool under the client's shared * network. */ The patch doesn't directly address the case that the prefix is in a global pool. Note that I have not had a chance to try using a global pool for prefixes so I don't know if that actually works or perhaps this comment is left over from previous versions of the code that did allow for global prefixes and that has now been restricted."