Re: [OSPF] [Adj-SID Flags] Regarding newly added 'P' flag
Peter Psenak <ppsenak@cisco.com> Thu, 02 March 2017 09:26 UTC
Return-Path: <ppsenak@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 ECCF41294BD; Thu, 2 Mar 2017 01:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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, 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 rMEmYCXLs9kY; Thu, 2 Mar 2017 01:26:13 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 334FA129459; Thu, 2 Mar 2017 01:26:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=754; q=dns/txt; s=iport; t=1488446772; x=1489656372; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=NIxA5zguS+kYYM8MG4IhCl3MFyyGDka9cY/J3EWtjK0=; b=K45maM1TSaxZEzL1O33glGrYFzuM8VRfFSgSdzPu6f2s8VuK3mdMfgYK laxKevrGo2eb7nDG/TNcJ8PHpoeTsszW235Vb8/27O+SmoI1Xva2qNq8k JaZ1hOPWDnv30G6vzJW8JuyiLanqxnfdCOrpWbg7We8JVxNVWxH2GCRZI g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D1BAAP5LdY/xbLJq1dGQEBAQEBAQEBAQEBBwEBAQEBhDSPYJB0l0KGHQMCAoMBFAECAQEBAQEBAWIohHABAQEDAQwmAQVAARALGAkWDwkDAgECAUUGDQEHAQGJbgizVRKLGAEBAQEBAQEBAQEBAQEBAQEBASCGTIRvijkBBJwpkjKBe4UigzGGUZM3NiGBASEUCBcVhQ0dgWI/ijMBAQE
X-IronPort-AV: E=Sophos;i="5.35,230,1484006400"; d="scan'208";a="692644845"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2017 09:26:10 +0000
Received: from [10.60.140.55] (ams-ppsenak-nitro6.cisco.com [10.60.140.55]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v229Q9fm008374; Thu, 2 Mar 2017 09:26:10 GMT
Message-ID: <58B7E531.8060103@cisco.com>
Date: Thu, 02 Mar 2017 10:26:09 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>, "draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org" <draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org>
References: <73BFDDFFF499304EB26FE5FDEF20F7885087843A@blreml501-mbx>
In-Reply-To: <73BFDDFFF499304EB26FE5FDEF20F7885087843A@blreml501-mbx>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/ySES7bxHUQu6ji-4J3kfQD3oQ_s>
Cc: "draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] [Adj-SID Flags] Regarding newly added 'P' flag
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: Thu, 02 Mar 2017 09:26:14 -0000
Hi Veerendranath, On 02/03/17 05:53 , Veerendranatha Reddy Vallem wrote: > Dear Authors, > > As per my understanding ‘P’ flag is used to avoid Adj-SID value change > in forwarding plane and during segment routing path calculation by > controller for interface flapping or switch over cases. for any case, even for router reload, etc. > > The Adj-SID value may change if adjacency gone down for longer period > (say 10 min) and come up, even P flag is set in previous advertisement. no. If the P flag is set, the Adj-SID should never change, unless specifically requested by the operator. thanks, Peter > > Please help me to know if any other use cases for setting P flag in Adj-SID > > Regards, > > Veerendranath >
- [OSPF] [Adj-SID Flags] Regarding newly added 'P' … Veerendranatha Reddy Vallem
- Re: [OSPF] [Adj-SID Flags] Regarding newly added … Peter Psenak