[Manet-dt] Re: Valid routes vs. active routes

"Ian Chakeres" <ian.chakeres@gmail.com> Fri, 25 August 2006 22:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGkKZ-0006Vq-Dd; Fri, 25 Aug 2006 18:39:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGkKY-0006UR-86 for manet-dt@ietf.org; Fri, 25 Aug 2006 18:39:14 -0400
Received: from ug-out-1314.google.com ([66.249.92.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GGkKW-0007Wj-Ut for manet-dt@ietf.org; Fri, 25 Aug 2006 18:39:14 -0400
Received: by ug-out-1314.google.com with SMTP id e2so1011305ugf for <manet-dt@ietf.org>; Fri, 25 Aug 2006 15:39:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sA3fNfve51+cZJ2Lm5O2QdakhxduGD1DbZr+AJatSdzDLJoLRS2SeUfimEZ2B0y5jY2hUlSVX25/wk1ULPd4yUZZ5eLFdbiZAVvrqDis4ZbEKspVtvuCHxAtQhodrZgW5nfvII1BHGwXONHQMKm0oi03TsEGI58/NImClvHHywM=
Received: by 10.67.105.19 with SMTP id h19mr2192466ugm; Fri, 25 Aug 2006 15:39:11 -0700 (PDT)
Received: by 10.67.23.16 with HTTP; Fri, 25 Aug 2006 15:39:11 -0700 (PDT)
Message-ID: <374005f30608251539l7f998718tc5c2f8cce394e21b@mail.gmail.com>
Date: Fri, 25 Aug 2006 15:39:11 -0700
From: "Ian Chakeres" <ian.chakeres@gmail.com>
To: "Charles E. Perkins" <charles.perkins@nokia.com>
In-Reply-To: <44EF7433.5060200@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <374005f30608121539x76d7a943v8e7cb5c4261a308c@mail.gmail.com> <44EF7433.5060200@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: karim.seada@nokia.com, manet-dt@ietf.org
Subject: [Manet-dt] Re: Valid routes vs. active routes
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

I am currently in the process of refining this very area of the spec.

Here is what I'm thinking (and writing into dymo-06-pre)

Current - routing information that is new, good, and should be
maintained for a while

Recently used - the route has been used for forwarding data recently
and should be maintained for a while

Broken - the link to the next hop broke or a RERR was received that
told me this route isn't good any more

I agree that RERR are only issued for recently used routes. I also
think that only Current and Recently Used routes should actually be in
the forwarding table.

What do you think?
Ian

On 8/25/06, Charles E. Perkins <charles.perkins@nokia.com> wrote:
>
> Hello Ian,
>
> There is not a definition for "active" route in the DYMO
> specification.  I think we should distinguish "active" from
> "valid".  The definition of "valid" seems correct.  We can
> say that a route is active if it is valid and it has been used.
>
> Then we can say that a RERR is only issued for active
> routes.  A RERR does not have to be issued for valid
> routes when they are broken.  This behavior is already
> in the specification, but with the proper definition for
> active I think it is more easily stated.
>
> Regards,
> Charlie P.
>
>

_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt