Brian E Carpenter <[EMAIL PROTECTED]>
> ``Router manufacturers MUST ensure that said black hole cannot be deconfigured,
> turned off, or otherwise overridden in toto;''
|It's very simple. No sane router vendor would do this.
I pointed out in my original comments that most router vendors have lit
> >
> > Assuming that the pool size is "n", where n = 2^40.
> >
> > As per your formula the probability of choosing two unique numbers is (n-
> 1)/n,
> > and of three unique numbers is ((n-1)/n)*((n-1)/n).
> >
> > As per Geoff, the probability of choosing two unique numbers is (n-1)/n,
> and
> > o
> Hi Margaret, thanks for your prompt response.
> I still do not understand how does the fact that a Hinden/Haberman address
> is globally unique, removes the need for a zone id/ site id. How does it
> settle with paragraph 6 of the Hinden/Haberman ID? ("site boarder routers
> SHOULD NOT forward an
below...
Chirayu Patel wrote:
>
> > The usage that is actually envisaged is more limited: an identifier that
> > provides disambiguation in a limited environment, normally a single
> > site, possibly a small number of sites directly linked by VPN-like
> > relations. In that scenario, the collisio
> ``Router manufacturers MUST ensure that said black hole cannot be deconfigured,
> turned off, or otherwise overridden in toto;''
It's very simple. No sane router vendor would do this. There are lots
of real world cases where people need to route arbitrary address
blocks.
The MUST can only apply
Hi Anjanish,
There is no contradiction. The intermediate nodes which are to be traversed
will be listed as the destination address in the IPv6 datagram in the repsective
segments and hence they can process the Routing header.
Say H1 wants to talk to H2 using the route H1->R1->R2->R3->H2
Hi Margaret, thanks for your prompt response.
I still do not understand how does the fact that a Hinden/Haberman address is globally
unique, removes the need for a zone id/ site id. How does it settle with paragraph 6
of the Hinden/Haberman ID? ("site boarder routers SHOULD NOT forward any packe
Hi Aviad,
At 02:26 PM 9/4/2003 +0200, Aviad Raveh wrote:
After reading the Hinden/Haberman ID, I do not understand how does it (if
it does) simplify the routing mechanism as described in the "impact of
Site-Local addressing" ID, as described in 3.1.2.2:
Because the Hinden/Haberman prefixes are u
After reading the Hinden/Haberman ID, I do not understand how does it (if it does)
simplify the routing mechanism as described in the “impact of Site-Local addressing”
ID, as described in 3.1.2.2:
“First, the forwarding engine on an SBR must look at both the source and destination
addresses to
Hi All,
One statment in RFC 2460 Looks contradictory, to the behaviour of Routing
Header processing.
One Page 05. Sections 4. The below para says :
-
"With one exception, extension headers are not examined or processed
by any node along a packet's de
10 matches
Mail list logo
