[OSPF] link-LSA for ospfv3 multi area adjacency
Nischal Sheth <nsheth@juniper.net> Wed, 11 June 2008 01:18 UTC
Return-Path: <ospf-bounces@ietf.org>
X-Original-To: ospf-archive@optimus.ietf.org
Delivered-To: ietfarch-ospf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 884DD3A68AB; Tue, 10 Jun 2008 18:18:25 -0700 (PDT)
X-Original-To: ospf@core3.amsl.com
Delivered-To: ospf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C90163A68AB for <ospf@core3.amsl.com>; Tue, 10 Jun 2008 18:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ha5vWDfhO3w for <ospf@core3.amsl.com>; Tue, 10 Jun 2008 18:18:24 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id E642F3A6853 for <ospf@ietf.org>; Tue, 10 Jun 2008 18:18:23 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP; Tue, 10 Jun 2008 18:18:45 PDT
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emsmtp01.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Jun 2008 18:18:06 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Jun 2008 18:18:06 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 10 Jun 2008 18:18:06 -0700
Received: from [172.24.24.238] (nsheth-xp-lt.jnpr.net [172.24.24.238]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m5B1I6x89122 for <ospf@ietf.org>; Tue, 10 Jun 2008 18:18:06 -0700 (PDT) (envelope-from nsheth@juniper.net)
Message-ID: <484F27CD.6070007@juniper.net>
Date: Tue, 10 Jun 2008 18:18:05 -0700
From: Nischal Sheth <nsheth@juniper.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: OSPF List <ospf@ietf.org>
X-OriginalArrivalTime: 11 Jun 2008 01:18:06.0263 (UTC) FILETIME=[009D3C70:01C8CB61]
Subject: [OSPF] link-LSA for ospfv3 multi area adjacency
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ospf-bounces@ietf.org
Errors-To: ospf-bounces@ietf.org
Section 4 of RFC 5185 says that a link-LSA SHOULD NOT be advertised for a ospfv3 multi-area adjacency. Instead, it suggests that the neighbor's link local address can be gleaned from hello packets. It appears to me that this won't work for multi-area adjacencies in non-IPv6 AFs. Any thoughts on loosening this recommendation and generating link-LSAs for multi-area adjacencies in general or at least for non-IPv6 AFs? Any other ideas to solve the above problem? Thanks, Nischal _______________________________________________ OSPF mailing list OSPF@ietf.org https://www.ietf.org/mailman/listinfo/ospf
- [OSPF] link-LSA for ospfv3 multi area adjacency Nischal Sheth
- Re: [OSPF] link-LSA for ospfv3 multi area adjacen… Peter Psenak
- Re: [OSPF] link-LSA for ospfv3 multi area adjacen… Nischal Sheth