IETF Logo Mail Archive

Re: [OSPF] FW: Forwarding address set for type-5

Radha Danda <rdanda@Brocade.com> Wed, 13 July 2016 12:25 UTC

Return-Path: <rdanda@Brocade.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C2112DF2A for <ospf@ietfa.amsl.com>; Wed, 13 Jul 2016 05:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBW2xOf3O5Lg for <ospf@ietfa.amsl.com>; Wed, 13 Jul 2016 05:25:12 -0700 (PDT)
Received: from mx0b-000f0801.pphosted.com (mx0b-000f0801.pphosted.com [IPv6:2620:100:9005:71::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA9E112DF44 for <ospf@ietf.org>; Wed, 13 Jul 2016 05:25:08 -0700 (PDT)
Received: from pps.filterd (m0000700.ppops.net [127.0.0.1]) by mx0b-000f0801.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u6DCNpaK020700; Wed, 13 Jul 2016 05:25:07 -0700
Received: from brmwp-exmb11.corp.brocade.com ([208.47.132.227]) by mx0b-000f0801.pphosted.com with ESMTP id 242xw3vp1f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 13 Jul 2016 05:25:06 -0700
Received: from BRMWP-EXMB11.corp.brocade.com (172.16.59.77) by BRMWP-EXMB11.corp.brocade.com (172.16.59.77) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 13 Jul 2016 06:25:05 -0600
Received: from BRMWP-EXMB11.corp.brocade.com ([fe80::39a0:e6f2:6a5c:18a9]) by BRMWP-EXMB11.corp.brocade.com ([fe80::39a0:e6f2:6a5c:18a9%23]) with mapi id 15.00.1156.000; Wed, 13 Jul 2016 06:25:05 -0600
From: Radha Danda <rdanda@Brocade.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] FW: Forwarding address set for type-5
Thread-Index: AQHR3PwaXm8y5VG7+EaCNXtDO1/J26AWSTN8
Date: Wed, 13 Jul 2016 12:25:04 +0000
Message-ID: <sppt8mc9ffsk53cfsb34lmfx.1468412697471@email.android.com>
References: <D3ABA0CA.6B844%acee@cisco.com>
In-Reply-To: <D3ABA0CA.6B844%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_sppt8mc9ffsk53cfsb34lmfx1468412697471emailandroidcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-07-13_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 impostorscore=0 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607130133
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/ttnszx49OBsybw0pQ-sKFz2FJfI>
Subject: Re: [OSPF] FW: Forwarding address set for type-5
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Wed, 13 Jul 2016 12:25:14 -0000

Thank you Acee

Best Regards ,
Radha



-------- Original message --------
From: "Acee Lindem (acee)"
Date:13/07/2016 5:15 PM (GMT+05:30)
To: Radha Danda , ospf@ietf.org
Subject: Re: [OSPF] FW: Forwarding address set for type-5

Hi Radha,
The forwarding address (next-hop) for an AS-External LSA may be advertised if it is reachable via an OSPF inter-area or intra-area route. You included connected routes  in your question and this is not necessarily correct since a connected route will only be accessible to other OSPF routers in the domain if it is advertised in OSPF. For NSSA LSAs, the next-hop should be reachable via an intra-area route in the NSSA.

Some implementations limit the advertising to the case where the next-hop is on a multi-access network.

Hope this helps,
Acee



From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of Radha Danda <rdanda@Brocade.com<mailto:rdanda@Brocade.com>>
Date: Wednesday, July 13, 2016 at 7:15 AM
To: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: [OSPF] FW: Forwarding address set for type-5

Hi All,

I need clarification on setting the Forwarding address set for type-5 LSA. As per RFC 2328 it is not obviously mentioned anywhere that the forwarding address can be set to connected, inter-area or intra-area routers but in the section 16.4 (Calculating AS external routes) it is mentioned that the forwarding address can be set to inter-area or intra-area as well. Snippet from the RFC is provided below for quick reference. Can you please confirm if the forwarding address can be set to ospf connected, inter-area or intra-area route while generating external LSA. Thanks.

**********************************
If the forwarding address is non-zero, look up the
            forwarding address in the routing table.[24] The matching
            routing table entry must specify an intra-area or inter-area
            path; if no such path exists, do nothing with the LSA and
            consider the next in the list.
******************************

Best Regards,
Radha

v2.23.0 | Report a Bug | By Email