Re: Anycast support in draft-ietf-ipv6-addr-arch-v4-02.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Anycast support in draft-ietf-ipv6-addr-arch-v4-02.txt



(Sorry for the long delay for this thread.  I've been off-list for a
vacation.)

>>>>> On Thu, 14 Apr 2005 10:33:45 -0700, 
>>>>> Bob Hinden <bob.hinden at nokia.com> said:

>> Anycast is complicated, and the complications are not specific to
>> IPv6.  It really would be doing the world a favor if the IPv6 WG were
>> to get rid of the language in the IPv6 address architecture doc that
>> places IPv6-specific restrictions on anycast, then let the GROW WG
>> handle the general anycast problem.

> OK, I think this makes sense.

> The proposal is then to remove the following text from the end of Section 
> 2.6 the document:

>     There is little experience with widespread, arbitrary use of Internet
      [...]

> Is everyone else OK with this proposed change?

I generally agree with the change, but I'm afraid a fresh reader of
this RFC-to-be will wonder about the removal, comparing to RFC3315.
So it would be nice to provide at least a pointer to relevant
discussion/drafts.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei at isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.