[OSPF] [OSPF-SR] Regarding graceful restart behavior with change in SR informaiotn carrying LSAs

Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> Mon, 29 May 2017 09:42 UTC

Return-Path: <veerendranatharv@huawei.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 18496127869; Mon, 29 May 2017 02:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 EbIzksApXmVA; Mon, 29 May 2017 02:42:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E37681200C1; Mon, 29 May 2017 02:42:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DNZ40108; Mon, 29 May 2017 09:42:03 +0000 (GMT)
Received: from BLREML701-CAH.china.huawei.com (10.20.4.170) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 29 May 2017 10:41:57 +0100
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml701-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Mon, 29 May 2017 15:11:54 +0530
From: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
To: "draft-ietf-ospf-segment-routing-extensions@ietf.org" <draft-ietf-ospf-segment-routing-extensions@ietf.org>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF-SR] Regarding graceful restart behavior with change in SR informaiotn carrying LSAs
Thread-Index: AdLYX5GxcNesv3fJR9CXqEVPe6G6dg==
Date: Mon, 29 May 2017 09:41:54 +0000
Message-ID: <73BFDDFFF499304EB26FE5FDEF20F788508BE111@blreml501-mbb>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.152.243]
Content-Type: multipart/alternative; boundary="_000_73BFDDFFF499304EB26FE5FDEF20F788508BE111blreml501mbb_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.592BECEC.0033, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 65c2ec0a5a080f9992fa136ca22d29bf
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/R1gpan-zwM6079gXX818l8xH0e8>
Subject: [OSPF] [OSPF-SR] Regarding graceful restart behavior with change in SR informaiotn carrying LSAs
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: Mon, 29 May 2017 09:42:08 -0000

Dear Authors,

In OSPFv2:
I am requesting for your clarification regarding  change in Opaque Type 7 and Opaque Type 8 LSAs (LSA origination/flush or modify)  need to consider for OSPFv2 GR exit case or not.
As per my understanding these LSAs will not be topology LSAs for OSPF, so it may not require to consider these LSAs for GR case.
I am requesting for your confirmation.

Also in OSPFv3:
SR information is carried in new extension LSAs, which can carry both topology and attribute information.
In this case, whether we need to consider LSA change for Graceful restart or not.
I am requesting for your confirmation.

Regards,
Veerendranath