Hi Vishwas, Hi *, "Vishwas Manral" <[EMAIL PROTECTED]> writes:
>> > One of the reasons the functionality is probably not present or used >> > as much is because IPv6 deployments aren't as widely present as IPv4. >> Are you implying that the functionality is used in IPv4 networks? > Please check the mails on the list. they do seem to suggest exactly > that. Sorry to insist but i'm pretty sure i carefully read all emails of the threads and I think I would have taken them into account and stop asking for people using the mechanism. Can you precisely point me to those? The ones I saw regarding the IPv4 options basically stated that operators of IPv4 networks all deactivate IP options processing on their routers. This is an applied BCP. Regarding users, i don't remember a single person providing feedback on its use of the mechanism on IPv4 networks (probably for previous reason). I also remember some mails from itojun and others regarding the inability to use IPv4 options between Japan and the USA as an example. > Arnaud, I do not want to keep it if it is of no use. But as I said and > have seen mails on the list as well as offline it seems to imply > otherwise. Can you please give me in one or two sentences (i.e. little effort) the specific purpose/use those people have. This is the only thing i keep asking for on the list and no one has still answered with specific use. I got only claims that keeping the mechanism would allow path selection or explicit traffic engineering by the source. Those are only generic ideas. IMHO, the most interesting directions is the question of locator/id separation for which some have hope keeping source-routing in our stacks today will perhaps help later. This is just a bet and it's not even asked by the people that currently work at trying to provide that (HIP, MIPv6, ...). If there was something on the table to explicitly help solving multi-homing issues, id/locator separation issues or simply improve addressing issues, i'd be more than happy to help. > By controlling the amount of functionality we reduce the attack > vectors. That is the entire aim here, to balance the risk to the > rewards. Exactly. Expressing uses followed by iterations on design decisions will help balancing the risk to the rewards. Let's start by expressing the uses. Regards, a+ -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
