Re: [RTG-DIR] [Lsr] RtgDir review: draft-ietf-ospf-ospfv3-segment-routing-extensions-17.txt

Peter Psenak <ppsenak@cisco.com> Wed, 14 November 2018 13:59 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FDC5130E8E; Wed, 14 Nov 2018 05:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 TJMlqVpvNmMP; Wed, 14 Nov 2018 05:59:50 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5C37130E7B; Wed, 14 Nov 2018 05:59:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1356; q=dns/txt; s=iport; t=1542203990; x=1543413590; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Sbr9QIUSAUDwOAB8Jwzjgq3IGZDjNcGCCVwIAMkjg/4=; b=Cm14iMCjnL4D+r62QsQuiYRgXYnY8/lr+x4ZjqfRoX0RDIXKvk4N+Myz zfQaIM1qwppUKzUb5LKRcVWRlCCLYtHwIOXx++5kQfzpoXKAX6IQDehh/ W3XZlzLa3u1cJAf5RTwDHB6uICLNrlrhi4CgiGbFuT061eWP+PGbwbSai Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DKAgAAKexb/xbLJq1iHAEBAQQBAQc?= =?us-ascii?q?EAQGBZYM5IRKNFo0pmTANhGwCg2k4FgEDAQECAQECbSiFOgEBAQMBOEABEAs?= =?us-ascii?q?YCRYPCQMCAQIBRQYNAQcBAYUXCKkoDoVBhGuMHIFAP4ERgxKKWQKPTJASCZE?= =?us-ascii?q?iGIFYhQWCfIccmAGBXCGBVTMaCBsVgyiCT44LPgOOFwEB?=
X-IronPort-AV: E=Sophos;i="5.56,232,1539648000"; d="scan'208";a="8041348"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2018 13:59:47 +0000
Received: from [10.147.24.43] ([10.147.24.43]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id wAEDxlYg003057; Wed, 14 Nov 2018 13:59:47 GMT
Message-ID: <5BEC2A52.7050207@cisco.com>
Date: Wed, 14 Nov 2018 14:59:46 +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: Erik Auerswald <auerswald@fg-networking.de>
CC: Tomonori Takeda <takeda.tomonori@lab.ntt.co.jp>, rtg-ads@ietf.org, rtg-dir@ietf.org, draft-ietf-ospf-ospfv3-segment-routing-extensions.all@ietf.org, lsr@ietf.org
References: <42c3e097-9789-49d4-cf15-c3713f4a1c0b@lab.ntt.co.jp> <5BEC1F81.9080103@cisco.com> <20181114132416.js5len3zao4bitkg@fg-networking.de>
In-Reply-To: <20181114132416.js5len3zao4bitkg@fg-networking.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.147.24.43, [10.147.24.43]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/1mX4sr-ar7oUt5qnq-ULPm6oZUU>
Subject: Re: [RTG-DIR] [Lsr] RtgDir review: draft-ietf-ospf-ospfv3-segment-routing-extensions-17.txt
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2018 13:59:53 -0000

Hi Erik,

On 14/11/18 14:24 , Erik Auerswald wrote:
> Hi Peter,
>
> please see inline (I have kept just the relevant part):
>
> On Wed, Nov 14, 2018 at 02:13:37PM +0100, Peter Psenak wrote:
>> On 14/11/18 12:49 , Tomonori Takeda wrote:
>>> [...]
>>> 1) Flooding Scope of SR-Algorithm TLV
>>> In Section 4.1, it says:
>>>
>>>     "If the SR-Algorithm TLV appears in
>>>      multiple OSPFv3 Router Information Opaque LSAs that have different
>>>      flooding scopes, the SR-Algorithm TLV in the OSPFv3 Router
>>>      Information Opaque LSA with the area-scoped flooding scope MUST be
>>>      used."
>>>
>>> At the same time, it say:
>>>
>>>     "For the purpose of SR-Algorithm TLV advertisement, area-
>>>      scoped flooding is REQUIRED."
>>>
>>> So, does it mean a) a router MUST use area-scoped flooding for sending,
>>> and
>>
>> no. It says that that for the purpose of the SR-Algorithm TLV area scope is
>> required. That means it cannot be link-scope, but it can be
>> autonomous-system scope, because that is also covering the area-scope.
>
> May I suggest to add the words "at least" to make the wording more
> explicit?
>
>      "For the purpose of SR-Algorithm TLV advertisement, at least
>       area-scoped flooding is REQUIRED."

sure, will do that.

thanks,
Peter

>
> Thanks,
> Erik
> .
>