Re: OSPFv3 fwd'ing address
Paul Jakma <paul@CLUBI.IE> Sat, 06 August 2005 14:42 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E1Psm-00088c-WE for ospf-archive@megatron.ietf.org; Sat, 06 Aug 2005 10:42:41 -0400
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26579 for <ospf-archive@LISTS.IETF.ORG>; Sat, 6 Aug 2005 10:42:38 -0400 (EDT)
Received: from vms.dc.lsoft.com (209.119.0.2) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <15.010C1110@cherry.ease.lsoft.com>; Sat, 6 Aug 2005 10:42:38 -0400
Received: by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 14.4) with spool id 81626804 for OSPF@PEACH.EASE.LSOFT.COM; Sat, 6 Aug 2005 10:42:37 -0400
Received: from 212.17.55.49 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0m) with TCP; Sat, 6 Aug 2005 10:42:36 -0400
Received: from sheen.jakma.org (sheen.jakma.org [212.17.55.53]) by hibernia.jakma.org (8.13.1/8.13.1) with ESMTP id j76EgUpU004683 for <OSPF@peach.ease.lsoft.com>; Sat, 6 Aug 2005 15:42:34 +0100
X-X-Sender: paul@sheen.jakma.org
References: <OF06940A42.8EB24A30-ON85257053.0067A0D7-85257053.0068512B@us.ibm.com>
Mail-Copies-To: paul@hibernia.jakma.org
Mail-Followup-To: paul@hibernia.jakma.org
X-NSA: arafat al aqsar jihad musharef jet-A1 avgas ammonium qran inshallah allah al-akbar martyr iraq saddam hammas hisballah rabin ayatollah korea vietnam revolt mustard gas british airways washington
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Message-ID: <Pine.LNX.4.63.0508061540320.16504@sheen.jakma.org>
Date: Sat, 06 Aug 2005 15:42:29 +0100
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Paul Jakma <paul@CLUBI.IE>
Subject: Re: OSPFv3 fwd'ing address
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <OF06940A42.8EB24A30-ON85257053.0067A0D7-85257053.0068512B@us.ibm.com>
Precedence: list
Hi, On Thu, 4 Aug 2005, Mike Fox wrote: > specify a forwarding address to use on that route, with the > restrictions that it can't be a link-local address and it has to be > an address or prefix that is routable in the OSPF domain. Which seem like quite reasonable restrictions really. And definitely far more reasonable than mandating the sucking up of details of global->LL address resolution and/or neighbour discovery into OSPF. > Mike regards, -- Paul Jakma paul@clubi.ie paul@jakma.org Key ID: 64A2FF6A Fortune: "All the people are so happy now, their heads are caving in. I'm glad they are a snowman with protective rubber skin" -- They Might Be Giants
- OSPFv3 fwd'ing address Alex Zinin
- Re: OSPFv3 fwd'ing address Acee Lindem
- Re: OSPFv3 fwd'ing address Alex Zinin
- Re: OSPFv3 fwd'ing address Acee Lindem
- Re: OSPFv3 fwd'ing address Alex Zinin
- Re: OSPFv3 fwd'ing address Naiming Shen
- Re: OSPFv3 fwd'ing address Mike Fox
- Re: OSPFv3 fwd'ing address Paul Jakma
- Re: OSPFv3 fwd'ing address Acee Lindem
- Re: OSPFv3 fwd'ing address Acee Lindem