[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ipv6 anycast

To: Randy Bush <randy@psg.com>
Subject: Re: ipv6 anycast
From: Ole Troan <ot@cisco.com>
Date: Wed, 1 Sep 2010 11:55:14 +0200
Cc: IPv6 v6ops <v6ops@ops.ietf.org>
In-reply-to: <m2mxs1yemx.wl%randy@psg.com>
References: <m2fwxuyn26.wl%randy@psg.com> <alpine.DEB.1.10.1009010918170.13746@uplift.swm.pp.se> <alpine.LRH.2.00.1009011226520.9708@netcore.fi> <m2r5hdyfjq.wl%randy@psg.com> <alpine.LRH.2.00.1009011236521.9708@netcore.fi> <m2pqwxyf4v.wl%randy@psg.com> <5A057A67-6A45-4AA5-A34E-D5A3F1F639CF@cisco.com> <m2mxs1yemx.wl%randy@psg.com>

>> I use them for my network. RFC5969.
> 
> aha!  do you mean
> 
> 5.  Troubleshooting and Traceability
>   ...
>   The 6rd CE and BR SHOULD support the IPv6 Subnet-Router anycast
>   address [RFC4291] for its own 6rd delegated prefix.  This allows, for
>   example, IPv6 ICMP echo messages to be sent to the 6rd virtual
>   interface itself for additional troubleshooting of the internal
>   operation of 6rd at a given CE or BR.

indeed. and note that this makes no requirement that _any_ type of interface has to support this.

cheers,
Ole

Follow-Ups:
- Re: ipv6 anycast
  - From: Randy Bush <randy@psg.com>
- Re: ipv6 anycast
  - From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>

References:
- ipv6 anycast
  - From: Randy Bush <randy@psg.com>
- Re: ipv6 anycast
  - From: Mikael Abrahamsson <swmike@swm.pp.se>
- Re: ipv6 anycast
  - From: Pekka Savola <pekkas@netcore.fi>
- Re: ipv6 anycast
  - From: Randy Bush <randy@psg.com>
- Re: ipv6 anycast
  - From: Pekka Savola <pekkas@netcore.fi>
- Re: ipv6 anycast
  - From: Randy Bush <randy@psg.com>
- Re: ipv6 anycast
  - From: Ole Troan <ot@cisco.com>
- Re: ipv6 anycast
  - From: Randy Bush <randy@psg.com>

Prev by Date: Re: ipv6 anycast
Next by Date: Re: ipv6 anycast
Previous by thread: Re: ipv6 anycast
Next by thread: Re: ipv6 anycast
Index(es):
- Date
- Thread