-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2005-03-17, at 15.02, Lowell Gilbert wrote:
Kurtis Lindqvist [EMAIL PROTECTED] writes:
Shouldn't we be a bit more explicit on what routers/hosts should do
with
these addresses when found?
We're already allowing for multiple behaviours.
test email, sorry.
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
From: Kurt Erik Lindqvist [EMAIL PROTECTED]
Sure. But I am more worried of creating ambiguity with what
applications does when receiving IPv4 compatible addresses as source
addresses. If we are replying to them, we have the-facto not actually
deprecated them :-)
There are many other
Just a test, sorry
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
Kurt Erik Lindqvist [EMAIL PROTECTED] writes:
On 2005-03-17, at 15.02, Lowell Gilbert wrote:
Kurtis Lindqvist [EMAIL PROTECTED] writes:
Shouldn't we be a bit more explicit on what routers/hosts should do
with
these addresses when found?
We're already allowing for multiple
Kurtis,
I don't think it is necessary as there wasn't any special handling
defined in this document for these addresses. Their handling falls
under the default rules for global unicast.
So If I am an application that receives a packet with a deprecated
IPv4-compatible address, I should just
Iljitsch,
I submit that as someone who has English as a first language (right?) and
who has been doing this for a long time, your perception of a clear
standards text isn't the same as someone who is still strugling with the
language and is new to all of this.
Unless others think this is
Lowell Gilbert [EMAIL PROTECTED] writes:
Kurt Erik Lindqvist [EMAIL PROTECTED] writes:
On 2005-03-17, at 15.02, Lowell Gilbert wrote:
Kurtis Lindqvist [EMAIL PROTECTED] writes:
Shouldn't we be a bit more explicit on what routers/hosts should do
with
these addresses when
Hi,
Here is what I hope is the final text that specifies the deprecation of the
IPv4-compatible IPv6 address. Included below are the revised sections
IPv6 Addresses with Embedded IPv4 Addresses and IANA Consideration.
Please review. I hope to submit an update draft tomorrow.
Thanks,
Bob
On Tue, 22 Mar 2005, Bob Hinden wrote:
Here is what I hope is the final text that specifies the deprecation of the
IPv4-compatible IPv6 address. Included below are the revised sections
IPv6 Addresses with Embedded IPv4 Addresses and IANA Consideration.
Please review. I hope to submit an
It seems good to keep the last sentence, as we don't want to risk
breaking existing implementations. The same basic logic applies to why
existing implementations are allowed to continue using site-local
unicast addresses even though they were formally deprecated in RFC 3879.
Best regards,
Tim
11 matches
Mail list logo
