IETF Logo Mail Archive

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

Radha Danda <rdanda@Brocade.com> Wed, 13 July 2016 11:17 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 AB32712DDF4 for <ospf@ietfa.amsl.com>; Wed, 13 Jul 2016 04:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 s79UDIzJ1rY8 for <ospf@ietfa.amsl.com>; Wed, 13 Jul 2016 04:17:10 -0700 (PDT)
Received: from mx0a-000f0801.pphosted.com (mx0a-000f0801.pphosted.com [67.231.144.122]) (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 8A39612DE22 for <ospf@ietf.org>; Wed, 13 Jul 2016 04:16:01 -0700 (PDT)
Received: from pps.filterd (m0048193.ppops.net [127.0.0.1]) by mx0a-000f0801.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u6DB7qMl024772 for <ospf@ietf.org>; Wed, 13 Jul 2016 04:15:39 -0700
Received: from brmwp-exmb12.corp.brocade.com ([208.47.132.227]) by mx0a-000f0801.pphosted.com with ESMTP id 245dx118bm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <ospf@ietf.org>; Wed, 13 Jul 2016 04:15:38 -0700
Received: from BRMWP-EXMB11.corp.brocade.com (172.16.59.77) by BRMWP-EXMB12.corp.brocade.com (172.16.59.130) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Wed, 13 Jul 2016 05:15:21 -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 05:15:21 -0600
From: Radha Danda <rdanda@Brocade.com>
To: "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: Forwarding address set for type-5
Thread-Index: AdHcFMgb2YvjBbMXTSS8ihl1XYxZfgAIIpygADCcLMA=
Date: Wed, 13 Jul 2016 11:15:21 +0000
Message-ID: <e371373fe61c4ea6a99d561ea4317e4c@BRMWP-EXMB11.corp.brocade.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.252.128.3]
Content-Type: multipart/alternative; boundary="_000_e371373fe61c4ea6a99d561ea4317e4cBRMWPEXMB11corpbrocadec_"
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-1607130125
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/UgQA5Ei4uinVsgi7S-cuBJs-4sw>
Subject: [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 11:17:12 -0000

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