IETF Logo Mail Archive

[OSPF] proposed text for draft-ppsenak-ospf-te-link-attr-reuse

Chris Bowers <cbowers@juniper.net> Fri, 04 December 2015 17:32 UTC

Return-Path: <cbowers@juniper.net>
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 238F71A8F3B for <ospf@ietfa.amsl.com>; Fri, 4 Dec 2015 09:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 FQsZlmAtz-ik for <ospf@ietfa.amsl.com>; Fri, 4 Dec 2015 09:32:57 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0773.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:773]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B12811A8BC0 for <ospf@ietf.org>; Fri, 4 Dec 2015 09:32:55 -0800 (PST)
Received: from DM2PR05MB623.namprd05.prod.outlook.com (10.141.157.24) by DM2PR05MB624.namprd05.prod.outlook.com (10.141.157.27) with Microsoft SMTP Server (TLS) id 15.1.331.20; Fri, 4 Dec 2015 17:32:35 +0000
Received: from DM2PR05MB623.namprd05.prod.outlook.com ([10.141.157.24]) by DM2PR05MB623.namprd05.prod.outlook.com ([10.141.157.24]) with mapi id 15.01.0331.023; Fri, 4 Dec 2015 17:32:35 +0000
From: Chris Bowers <cbowers@juniper.net>
To: OSPF WG List <ospf@ietf.org>
Thread-Topic: proposed text for draft-ppsenak-ospf-te-link-attr-reuse
Thread-Index: AdEuuVWGMPE2YtM+Qkqm7ANnmAmrvw==
Date: Fri, 04 Dec 2015 17:32:34 +0000
Message-ID: <DM2PR05MB62385A916E792E20E1EB583A90C0@DM2PR05MB623.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cbowers@juniper.net;
x-originating-ip: [66.129.239.11]
x-microsoft-exchange-diagnostics: 1; DM2PR05MB624; 5:i5UgnP9rA4x0dzH5j7RvU55UIjKQt4a0u5Sspv3fk8SL5eMrCtU5R23h2MWpZKOHaTtatwEJJvm5aQDI5UBarfOnC2eghRNW6CKaFJA4oZgS+78aqYkiCZWX2HDzlakYJZfml5u/M5MwG7LwuViTuA==; 24:Dlpk+r0ZrBDKDR0ChJG/u0YEvQLds4FXjCDbdttgZ8vmKp45ljGiS3ZA7zB3BfpmnfFedop3suaotAj0OT6lYrP42v+dusKPlQD3QtJ6fGg=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR05MB624;
x-microsoft-antispam-prvs: <DM2PR05MB62496F3F23A9B8598D6E5C6A90C0@DM2PR05MB624.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(108003899814671);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(520078)(10201501046)(3002001); SRVR:DM2PR05MB624; BCL:0; PCL:0; RULEID:; SRVR:DM2PR05MB624;
x-forefront-prvs: 07807C55DC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(164054003)(66066001)(6116002)(586003)(102836003)(11100500001)(122556002)(10400500002)(5008740100001)(1220700001)(106356001)(450100001)(1096002)(3846002)(5004730100002)(76576001)(40100003)(97736004)(110136002)(74316001)(230783001)(5001960100002)(50986999)(5003600100002)(107886002)(81156007)(189998001)(5002640100001)(87936001)(86362001)(101416001)(105586002)(92566002)(19580395003)(99286002)(15975445007)(77096005)(2900100001)(33656002)(54356999)(229853001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB624; H:DM2PR05MB623.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM2PR05MB62385A916E792E20E1EB583A90C0DM2PR05MB623namprd_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2015 17:32:34.6065 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB624
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/b3WQFGv__mQTIBHj869ZE3hKjZY>
Subject: [OSPF] proposed text for draft-ppsenak-ospf-te-link-attr-reuse
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: Fri, 04 Dec 2015 17:32:59 -0000

Draft authors,

I would like to suggest the following text for the Backwards Compatibility section of this document.

-------
Some deployments of LFA and remote LFA currently rely on link attributes (such as SRLG and admin groups) being carried in the TE Opaque LSA.  These applications are described in RFC 5286, RFC 7490,  draft-ietf-rtgwg-lfa-manageability, and draft-psarkar-rtgwg-rlfa-node-protection.  When a network is using an application that relies on link attributes being carried in the TE Opaque LSA , care should be taken to continue to advertise the appropriate link attributes in the TE Opaque LSA.

Note that a node that does not directly participate in remote LFA by originating repair tunnels itself may still need to continue originating link attributes in the TE Opaque LSA for use by other nodes in the network.   Therefore, when evaluating software upgrades or configuration changes which may result in changes to which link attributes are being advertised in the TE Opaque LSA, even for a subset of routers in the network,  care should be taken to evaluate the impact of that change across the entire network.
-------

Thanks,
Chris

v2.23.0 | Report a Bug | By Email