Re: [OSPF] OSPFv3: Multiple Interfacee to Single Link .

Paul Wells <pauwells@cisco.com> Fri, 10 July 2009 16:07 UTC

Return-Path: <pauwells@cisco.com>
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 1097B28C33A for <ospf@core3.amsl.com>; Fri, 10 Jul 2009 09:07:57 -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 1ymlKcxyG6va for <ospf@core3.amsl.com>; Fri, 10 Jul 2009 09:07:56 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 38E3828C2CF for <ospf@ietf.org>; Fri, 10 Jul 2009 09:07:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,378,1243814400"; d="scan'208";a="341457414"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 10 Jul 2009 16:08:24 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n6AG8Pr3020576; Fri, 10 Jul 2009 09:08:25 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n6AG8OF8029286; Fri, 10 Jul 2009 16:08:24 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 09:08:24 -0700
Received: from pauwells-linux.cisco.com ([10.19.20.100]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 10 Jul 2009 09:08:24 -0700
Message-ID: <4A576777.8090604@cisco.com>
Date: Fri, 10 Jul 2009 11:08:23 -0500
From: Paul Wells <pauwells@cisco.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: "Keshava.Ayanur" <keshavaak@huawei.com>
References: <002001ca008d$167f2320$1f01120a@china.huawei.com> <4A566E4B.4080800@cisco.com> <000301ca0128$cfb78170$1f01120a@china.huawei.com>
In-Reply-To: <000301ca0128$cfb78170$1f01120a@china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jul 2009 16:08:24.0518 (UTC) FILETIME=[A7219660:01CA0178]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2862; t=1247242105; x=1248106105; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pauwells@cisco.com; z=From:=20Paul=20Wells=20<pauwells@cisco.com> |Subject:=20Re=3A=20[OSPF]=20OSPFv3=3A=20Multiple=20Interfa cee=20to=20Single=20Link=20. |Sender:=20; bh=uQKPkiJQoFJ9aJUC4kCg92n/+pB74vqaeBbVBDmHRnQ=; b=srzDtNlKLrGvYQRrRv+VtY0wGG4NdtFR5l6mfc6p4/v8M7TNZAN3Vz0cHo sd8OD3ZGzjc6sVpYp9bVMF+6dXRbiom1bMghYNRxw55Bt0YIXAucqr20In8N WkpAKWoekYYD2s6RhUGT9vDULNZ41nMc9NM6hQxir3D5cinCt3upo=;
Authentication-Results: sj-dkim-1; header.From=pauwells@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: ospf@ietf.org
Subject: Re: [OSPF] OSPFv3: Multiple Interfacee to Single Link .
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/mail-archive/web/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>
X-List-Received-Date: Fri, 10 Jul 2009 16:07:57 -0000

Hi Keshava,

Since the Hello packets sent by R1 and R2 will have different 
router IDs there should be no confusion in this case.

This isn't explicitly mentioned in section 4.9 of 5340. Perhaps 
because it was considered too obvious?

Regards,
Paul

Keshava.Ayanur wrote:
> Hi,
> 
> Consider the following scenario.
> 
>     E0  |N1
>   R1----|				
> 	  | E1   E2  |N2
> 	  |---R2-----|
> 
> R1 E0: Link Local Address = X, Interface-Id = a.
> R2 E1: Link Local Address = Y, Interface-Id = b.
> R2 E2: Link Local Address = X, Interface-Id = a.
> 
> According to [OSPFv3], if R2 Receives Hello from R1,
> 
> Check if one of the router's link-local addresses as the source address and
> Interface ID other than the Interface ID of the receiving interface.
> 
> So we find interface R2 E2.BUT, the hello packet received was not sent by R2
> on E2.
> 
> How to handle this issue?
> 
> Regards,
> Keshava.
> 	   	  	
> 
> 
> -----Original Message-----
> From: Michael Barnes [mailto:mjbarnes@cisco.com] 
> Sent: Friday, July 10, 2009 3:55 AM
> To: Keshava.Ayanur
> Cc: ospf@ietf.org
> Subject: Re: [OSPF] OSPFv3: Multiple Interfacee to Single Link .
> 
> Hello keshava,
> 
> Keshava.Ayanur wrote:
>> Under the Section 3.9 in OSPFv3 RFC 5340
>>
>> "Each of the multiple interfaces are assigned different Interface
>> IDs.  A router will automatically detect that multiple interfaces
>> are attached to the same link when a Hello packet is received with
>> one of the router's link-local addresses as the source address and
>> an Interface ID other than the Interface ID of the receiving interface."
>>
>> If the 'Link Local address' is same for different interfaces with in the
> same Router, then how to detect that the multiple interfaces are attached to
> same link ?
> 
> That doesn't change the fact that the packet is received with one of the 
> router's own link-local addresses as the source address. This text 
> doesn't say that the source address must be different than the one for 
> the interface on which it is received. The differentiator is the 
> Interface ID, which must be unique even if the source address is not.
> 
> However, IMHO there is little advantage to having multiple interfaces to 
> a link unless the interfaces have different link-local addresses. If the 
> automatically generated link-local addresses happen to be the same, the 
> user must manually configure unique addresses on those interfaces which 
> will be connected to the same link. Otherwise any packet sent to the 
> router will be received on all of the interfaces, which seems highly 
> undesirable.
> 
> Regards,
> Michael
> 
>> Regards,
>> keshava
> 
> _______________________________________________
> OSPF mailing list
> OSPF@ietf.org
> https://www.ietf.org/mailman/listinfo/ospf