Hi,
I am looking through the Address Autoconfig (RFC 2462) and Neighbor
Discovery (RFC 2461) drafts, and there seems to be a bit of discrepancy
about deprecating prefixes.
Specifically, let's consider the scenario described in RFC 2461 on page
78-79. A prefix has been advertised with a lifetime
Hi,
I am looking through the Address Autoconfig (RFC 2462) and Neighbor
Discovery (RFC 2461) drafts, and there seems to be a bit of discrepancy
about deprecating prefixes.
Specifically, let's consider the scenario described in RFC 2461 on page
78-79. A prefix has been advertised with a lifetime
> On Thu, 01 Feb 2001 23:06:31 -0800,
> "T.J. Kniveton" <[EMAIL PROTECTED]> said:
> However, RFC 2462 has stated that unless router advertisements are
> authenticated, any router advertisement trying to expire the prefix
> (which still has a few days, to most of a month, of validity left
Is it OK with everyone that a node that has been turned off for a while,
could possibly be *unusable* on a network for two hours? We can not say
I think "unusuable" is too strong. There will presumably be newer
prefixes advertised and no rule makes the node ignore those.
Also, doesn't t
on 2/2/01 5:26 AM, JINMEI Tatuya / wrote:
>> On Thu, 01 Feb 2001 23:06:31 -0800,
>> "T.J. Kniveton" <[EMAIL PROTECTED]> said:
>
>> However, RFC 2462 has stated that unless router advertisements are
>> authenticated, any router advertisement trying to expire the prefix
>> (which stil
[I am crossposting to Mobile-IP since I am throwing in some info about
mobiles]
on 2/2/01 7:41 AM, Matt Crawford wrote:
> Is it OK with everyone that a node that has been turned off for a while,
> could possibly be *unusable* on a network for two hours? We can not say
>
> I think "unusuable" is
>Now the mobile node is turned on, on September 25th, in a visited network.
>It starts receiving router advertisements for the local link. It configures
>a link-local care-of address. It wants to contact its Home Agent to register
>a binding for its care-of address.
link-local care-of add
Jun-ichiro itojun Hagino wrote:
>
> >Now the mobile node is turned on, on September 25th, in a visited network.
> >It starts receiving router advertisements for the local link. It configures
> >a link-local care-of address. It wants to contact its Home Agent to register
> >a binding for its care-
> On Fri, 02 Feb 2001 11:17:32 -0800,
> "T.J. Kniveton" <[EMAIL PROTECTED]> said:
>> In this case, we can reasonably assume that a new prefix (with positive
>> valid and preferred lifetimes) is being advertised. Thus, we have at
>> least one preferred address. Also, in the scenario abo
> -Original Message-
> From: T.J. Kniveton [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 2:58 PM
> To: Matt Crawford
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: IPv6 Prefix Deprecation Problem
>
> Some layer above IP is choosing the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
> >
> > Also, doesn't the node's stack need to allow for the possibility that
> > when it is powered back on, it is connected to a different link entirely?
>
> Good point. I didn't even get into the problems with mobile nodes. Imagine,
> for instance the following twist:
>
> The mobile node had
"T.J. Kniveton" wrote:
>
> [I am crossposting to Mobile-IP since I am throwing in some info about
> mobiles]
> >
> > Also, doesn't the node's stack need to allow for the possibility that
> > when it is powered back on, it is connected to a different link entirely?
>
> Good point. I didn't eve
> Specifically, let's consider the scenario described in RFC
> 2461 on page
> 78-79. A prefix has been advertised with a lifetime of two months, a
> machine is turned off on July 31st, then on Aug. 1st, it's decided the
> prefix should expire on Sep 1st. The host is turned back during
> September
Richard Draves wrote:
>
> > Specifically, let's consider the scenario described in RFC
> > 2461 on page
> > 78-79. A prefix has been advertised with a lifetime of two months, a
> > machine is turned off on July 31st, then on Aug. 1st, it's decided the
> > prefix should expire on Sep 1st. The host
> > I don't know of any implementations that keep prefixes in a
> persistent
> > store. My expectaction would be that when the host is
> turned back on in
> > September, it will send an RS and get RAs and
> auto-configure itself without
> > any memory of the old prefix.
>
> No, the mobile node
"T.J. Kniveton" wrote:
>
> Mattias Pettersson wrote:
> > Are your prefix lifetimes not supposed to be in the same order as the
> > renumbering period? If your renumbering takes one month, set valid
> > lifetime to one month for prefixes announces long before the renumbering
> > phase starts. In
> I don't know of any implementations that keep prefixes in a persistent
> store. My expectaction would be that when the host is turned back on in
> September, it will send an RS and get RAs and auto-configure itself without
> any memory of the old prefix.
The Solaris 8 IPv6 implementation retai
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
"Hesham Soliman (ERA)" wrote:
> => I don't have a concrete proposal but basically the problem
> here is manual configuration of the Home address / prefix.
> If the MN can decouple its identity from the Home prefix
> and use something more abstract (eg. NAI) then the
> > One requirement that we came up to when writing Mobile IPv6 i-d v13 was
> > that the Mobile Node must somehow know its home prefix or a DNS name
> > representing the home prefix or home agents anycast address. How the
>
> Well, DNS is the option that's most likely to survive a network
> renu
33 matches
Mail list logo
