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

Tomonori Takeda <takeda.tomonori@lab.ntt.co.jp> Thu, 15 November 2018 00:00 UTC

Return-Path: <takeda.tomonori@lab.ntt.co.jp>
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 44E09130DC9; Wed, 14 Nov 2018 16:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 Rmp6wMpKl4iA; Wed, 14 Nov 2018 16:00:07 -0800 (PST)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by ietfa.amsl.com (Postfix) with ESMTP id D55B81294D0; Wed, 14 Nov 2018 16:00:06 -0800 (PST)
Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id wAENxeI6028905; Thu, 15 Nov 2018 08:59:40 +0900
Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 56814EA7577; Thu, 15 Nov 2018 08:59:40 +0900 (JST)
Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 4BB7FEA751B; Thu, 15 Nov 2018 08:59:40 +0900 (JST)
Received: from [IPv6:::1] (unknown [129.60.13.98]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 450F0400AB9; Thu, 15 Nov 2018 08:59:40 +0900 (JST)
References: <42c3e097-9789-49d4-cf15-c3713f4a1c0b@lab.ntt.co.jp> <5BEC1F81.9080103@cisco.com> <20181114132416.js5len3zao4bitkg@fg-networking.de> <5BEC2A52.7050207@cisco.com>
From: Tomonori Takeda <takeda.tomonori@lab.ntt.co.jp>
Message-ID: <96563328-db52-0c31-78ea-2ff46436311e@lab.ntt.co.jp>
Date: Thu, 15 Nov 2018 08:59:17 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <5BEC2A52.7050207@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CC-Mail-RelayStamp: 1
To: Peter Psenak <ppsenak@cisco.com>, Erik Auerswald <auerswald@fg-networking.de>
Cc: rtg-ads@ietf.org, rtg-dir@ietf.org, draft-ietf-ospf-ospfv3-segment-routing-extensions.all@ietf.org, lsr@ietf.org, Tomonori Takeda <takeda.tomonori@lab.ntt.co.jp>
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/3PVjcfb_E71NSYpnlGy5KSGU998>
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: Thu, 15 Nov 2018 00:00:10 -0000

Hi Peter, Eric,

Thanks.
Proposed changes look good to me.

Tomonori


On 2018/11/14 22:59, Peter Psenak wrote:
> 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
>> .
>>
> 
> 
> 

-- 
Tomonori Takeda
NTT Network Service Systems Labs.
+81-422-59-7092