Michael,

Can I echo what Tom and Christian have said - that you join the 6man working
group and start by clearly and concisely stating the problem that this RFC
poses
for your application and how you suggest we fix it?

When you speak of "hundreds of millions of printers..." it gives the
impression that
the RFC makes illegal something that printers have been doing for some
time.  If
so, can you also provide relevant references to the deployed functionality
that you
believe this RFC makes illegal?

-K-

On Fri, May 24, 2013 at 1:45 PM, Christian Huitema <huit...@microsoft.com>wrote:

> Can we move from the process discussion to the technical discussion?
>
> Michael raised an interesting issue, and we have to analyze it. The
> consensus of the working group so far is that interface identifiers are
> private to the host, that any leakage outside the host should be prevented,
> and that a way to prevent that leakage is to ask proxies to erase them
> whenever they have an opportunity. Michael points that some servers take an
> opposite approach, want to record the interface from which the host called
> them, and want to ensure that further calls in the same session use exactly
> the same interface. That seems that a fairly legitimate debate, and I can
> see two alternatives -- one would be to reaffirm the old guidance and
> provides alternative to ensure session continuity, and the other would be
> to reverse the guidance and accept that the layer violation performed by
> servers is just fine.
>
> -- Christian Huitema
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to