IETF Logo Mail Archive

Re: [OSPF] draft-ietf-ospf-two-part-metric : Max metric handling

"Acee Lindem (acee)" <acee@cisco.com> Thu, 08 October 2015 09:33 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D671A8F46; Thu, 8 Oct 2015 02:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 30WeWjlfOQhm; Thu, 8 Oct 2015 02:33:06 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4E961A8F37; Thu, 8 Oct 2015 02:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5393; q=dns/txt; s=iport; t=1444296785; x=1445506385; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=JcvAtrE/o7EO+t96IDZS8t0p5SZt6Ba30aDu/WR7AWA=; b=l5trIuHyYIfY2GDWTCCRZLq+gxqEHmEeAljIg4i7scyby+K7+yL/o3TX 2t20fvyu7w7HMX16zGHf1yVWwHjP04wdI7ewjFvz2Zk+0GTi9+c4uBTlb OLyKyZGF3u3cZ5JNcNVpwRgSowu5RtbeYqdkRed3oWkm335UQYuy8XtY7 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DqAgCcNxZW/5RdJa1eglpNgUIGvUABDYFagxOCCn8CHIEoOBQBAQEBAQEBgQqEJgEBAQQjCkwQAgEIBA0DAQIoAwICAjAUCQgCBAENBYgurjGUNAEBAQEBAQEBAQEBAQEBAQEBAQEBAReLcYR8EQeCaYFFBZYIAY0Wm3gfAQFChAJxhmaBBgEBAQ
X-IronPort-AV: E=Sophos; i="5.17,654,1437436800"; d="scan'208,217"; a="33710952"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-7.cisco.com with ESMTP; 08 Oct 2015 09:33:04 +0000
Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t989X4KU000732 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 8 Oct 2015 09:33:04 GMT
Received: from xch-aln-019.cisco.com (173.36.7.29) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 8 Oct 2015 04:33:03 -0500
Received: from xhc-aln-x09.cisco.com (173.36.12.83) by xch-aln-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Thu, 8 Oct 2015 04:33:03 -0500
Received: from xmb-aln-x06.cisco.com ([169.254.1.127]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0248.002; Thu, 8 Oct 2015 04:33:03 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Shraddha Hegde <shraddha@juniper.net>, "draft-ietf-ospf-two-part-metric@ietf.org" <draft-ietf-ospf-two-part-metric@ietf.org>
Thread-Topic: draft-ietf-ospf-two-part-metric : Max metric handling
Thread-Index: AQHRAaxU3pGsXjsztkqBbWdrAPCuWw==
Date: Thu, 08 Oct 2015 09:33:03 +0000
Message-ID: <D23B45ED.34208%acee@cisco.com>
References: <BY1PR0501MB138192B8D1A44024E5BAD8D9D5370@BY1PR0501MB1381.namprd05.prod.outlook.com>
In-Reply-To: <BY1PR0501MB138192B8D1A44024E5BAD8D9D5370@BY1PR0501MB1381.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.36.7.14]
Content-Type: multipart/alternative; boundary="_000_D23B45ED34208aceeciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/__TTYKWE4yolUmbkLjHVWWqJEzE>
Cc: OSPF WG List <ospf@ietf.org>
Subject: Re: [OSPF] draft-ietf-ospf-two-part-metric : Max metric handling
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 08 Oct 2015 09:33:09 -0000

Hi Shraddha,
Since RFC 2328 and RFC 5340 don’t explicitly call out the case of 0xffff, I don’t see why this should be handled. Perhaps, we should state both metric SHOULD be set to 0xffff in the stub router case.
Thanks,
Acee

From: Shraddha Hegde <shraddha@juniper.net<mailto:shraddha@juniper.net>>
Date: Tuesday, October 6, 2015 at 5:58 AM
To: "draft-ietf-ospf-two-part-metric@ietf.org<mailto:draft-ietf-ospf-two-part-metric@ietf.org>" <draft-ietf-ospf-two-part-metric@ietf.org<mailto:draft-ietf-ospf-two-part-metric@ietf.org>>
Cc: OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: draft-ietf-ospf-two-part-metric : Max metric handling

Authors,

As per my understanding of the draft, SPF calculation uses sum of metric from the interface cost and the network to router cost advertised by the neighbor.
Handling of MAX metric is not described in the draft.  Since the metric will be sum of 2 16 bit numbers it can exceed the normal 0xffff metric value and the draft should talk about how to handle these cases.

Rgds
Shraddha

v2.27.8 | Report a Bug | By Email | System Status