Re: [OSPF] link-LSA for ospfv3 multi area adjacency

Nischal Sheth <nsheth@juniper.net> Wed, 11 June 2008 20:41 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 6DB7E3A6881; Wed, 11 Jun 2008 13:41:26 -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 AF9E13A6881 for <ospf@core3.amsl.com>; Wed, 11 Jun 2008 13:41:25 -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 Jbp33Z5wuzGN for <ospf@core3.amsl.com>; Wed, 11 Jun 2008 13:41:24 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with ESMTP id BEEA43A6867 for <ospf@ietf.org>; Wed, 11 Jun 2008 13:41:24 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP; Wed, 11 Jun 2008 13:41:13 PDT
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emsmtp01.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Jun 2008 13:40:57 -0700
Received: from emailsmtp56.jnpr.net ([172.24.60.77]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Jun 2008 13:40:56 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Jun 2008 13:40:56 -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 m5BKeux36078 for <ospf@ietf.org>; Wed, 11 Jun 2008 13:40:56 -0700 (PDT) (envelope-from nsheth@juniper.net)
Message-ID: <48503858.10200@juniper.net>
Date: Wed, 11 Jun 2008 13:40:56 -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>
References: <484F27CD.6070007@juniper.net> <484F86DE.5000908@cisco.com>
In-Reply-To: <484F86DE.5000908@cisco.com>
X-OriginalArrivalTime: 11 Jun 2008 20:40:56.0572 (UTC) FILETIME=[72F583C0:01C8CC03]
Subject: Re: [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

Peter Psenak wrote:

> Nischal,
> 
> Nischal Sheth wrote:
>> 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?
> 
> 5185 is based on the current OSPFv3 spec that supports only a single AF.
> If the multi AF support in OSPFv3 requires changes to the 5158, it 
> should be done as a part of the OSPFv3 multi-AF effort.
> 

Hi Peter,

Fair enough.  This sounds like a good course of action.

It seems that the most straightforward solution would be to override the
RFC 5185 behavior for non-IPv6 AFs and generate link-LSAs for multi-area
adjacencies.  These must contain only the link local address and no other
prefixes.

Could the authors of the multi-AF draft please address this issue in the
next version?

Thanks,
Nischal
_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf