IETF Logo Mail Archive

Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt

"Acee Lindem (acee)" <acee@cisco.com> Fri, 17 March 2017 20:57 UTC

Return-Path: <acee@cisco.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 5505B1292F4 for <ospf@ietfa.amsl.com>; Fri, 17 Mar 2017 13:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.501
X-Spam-Level:
X-Spam-Status: No, score=-13.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 NCd6DlE0ub6y for <ospf@ietfa.amsl.com>; Fri, 17 Mar 2017 13:57:37 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75801126D85 for <ospf@ietf.org>; Fri, 17 Mar 2017 13:57:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2458; q=dns/txt; s=iport; t=1489784257; x=1490993857; h=from:cc:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=a/dRvIM9SZbR5RXjAOfIFwrHcNnxbfe1e1F+fsZgsPg=; b=MwB6a7L46kVmwPRf0G3EOYEHHbz0jM/v6Veu9y+gsZyFGzEUZYUxN8b5 IsqxRdMaa8Qnr8xAVDBDKRo6UIHANxjb5iULR6DPzawkmSQ7cPnK6rSNs CkfgtNDHPL8gkbe8d4ZA45FTi+a0AmxMF0yj16DWnF+hI5fUBDnGtXUxE I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AtAwCHTMxY/4YNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1FhfA4HjWqRKgSVb4IOHwuFeAImgls/GAECAQEBAQEBAWsohQ0JAgEDAQE4NAsQAgEINhAnCyUCEgWFcoQODrUJikgBAQEBAQEEAQEBAQEBASGLPYMXhFWCTQWcSQGGeItJgXtUhFSKCJNSAR84gQRYFRgpZgyFZXWISoENAQEF
X-IronPort-AV: E=Sophos;i="5.36,178,1486425600"; d="scan'208";a="219628702"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Mar 2017 20:57:36 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v2HKva19025758 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Fri, 17 Mar 2017 20:57:36 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 17 Mar 2017 16:57:35 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Fri, 17 Mar 2017 16:57:35 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
CC: "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
Thread-Index: AQHSjfByPDMVUGpybkyZjaXlMR2SrKGZplAA
Date: Fri, 17 Mar 2017 20:57:35 +0000
Message-ID: <D4F1C502.A346C%acee@cisco.com>
References: <148786668469.20333.199396876398174521.idtracker@ietfa.amsl.com>
In-Reply-To: <148786668469.20333.199396876398174521.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1402AE0E55B8B74FBD79BBF1DC72F3C6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/E7oEuQVtkRCIB_5YvRc0e4_Jlog>
Subject: Re: [OSPF] I-D Action: draft-ietf-ospf-link-overload-05.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Mar 2017 20:57:39 -0000

Hi Shraddha, et al,

With respect to section 4.1, I agree that matching link endpoints in
OSPFv2 requires more information. However, this is a general problem and
the remote address should be a separate OSPFv2 Link Attribute LSA TLV
rather than overloading the link overload TLV ;^)

Thanks,
Acee

On 2/23/17, 11:18 AM, "OSPF on behalf of internet-drafts@ietf.org"
<ospf-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>This draft is a work item of the Open Shortest Path First IGP of the IETF.
>
>        Title           : OSPF Link Overload
>        Authors         : Shraddha Hegde
>                          Pushpasis Sarkar
>                          Hannes Gredler
>                          Mohan Nanduri
>                          Luay Jalil
>	Filename        : draft-ietf-ospf-link-overload-05.txt
>	Pages           : 13
>	Date            : 2017-02-23
>
>Abstract:
>   When a link is being prepared to be taken out of service, the traffic
>   needs to be diverted from both ends of the link.  Increasing the
>   metric to the highest metric on one side of the link is not
>   sufficient to divert the traffic flowing in the other direction.
>
>   It is useful for routers in an OSPFv2 or OSPFv3 routing domain to be
>   able to advertise a link being in an overload state to indicate
>   impending maintenance activity on the link.  This information can be
>   used by the network devices to re-route the traffic effectively.
>
>   This document describes the protocol extensions to disseminate link-
>   overload information in OSPFv2 and OSPFv3.
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-ospf-link-overload/
>
>There's also a htmlized version available at:
>https://tools.ietf.org/html/draft-ietf-ospf-link-overload-05
>
>A diff from the previous version is available at:
>https://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-link-overload-05
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf

v2.23.0 | Report a Bug | By Email