On Tue, Nov 6, 2012 at 11:38 AM, Brian E Carpenter < brian.e.carpen...@gmail.com> wrote:
> I think it's a bit of a stretch to say that > draft-ietf-mif-dhcpv6-route-option explicitly targets this > model; it's actually a generic mechanism, even if some of the > use cases do fit the walled garden model. > That was not the assertion made in this ticket. I believe that (part of) the assertion was that use cases that target walled gardens should be removed as justification, because IAB guidance is that protocol and architecture development should not target walled gardens. If there are other use cases, then we should decide on the merits of those, but the use cases that are targeting walled gardens should be removed. Does that make sense? Do you agree?
_______________________________________________ mif mailing list mif@ietf.org https://www.ietf.org/mailman/listinfo/mif
