IETF Logo Mail Archive

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

Peter Psenak <ppsenak@cisco.com> Mon, 18 February 2019 13:19 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F120D130EFC for <lsr@ietfa.amsl.com>; Mon, 18 Feb 2019 05:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 mEY5ugMN1NUb for <lsr@ietfa.amsl.com>; Mon, 18 Feb 2019 05:19:02 -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 143E1130EF2 for <lsr@ietf.org>; Mon, 18 Feb 2019 05:19:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1905; q=dns/txt; s=iport; t=1550495942; x=1551705542; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=csnpYg35zVZgVhbXDU2ZUCZ9kDA92JktytWpejX/2DA=; b=kcRqTYUelC3m2W5MSHLUJt9TMG8jyV6n0ybWzQ/FcyB5FhUQ7lp4YlDU cOfu9wvqbQUz4sMi8fyA3miiFdDKzjjI6tszeUYVyLXgBfAiO1V+HWVtO t0hqM+zXyBk6lTjx3+sHDqjrQ7Q9B0JwLMBqjdCXEHFHHwsRnQ9mZJ9nr I=;
X-IronPort-AV: E=Sophos;i="5.58,384,1544486400"; d="scan'208";a="10204110"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Feb 2019 13:19:00 +0000
Received: from [10.147.24.16] ([10.147.24.16]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTP id x1IDIx3a026334; Mon, 18 Feb 2019 13:18:59 GMT
To: "Goethals, Dirk (Nokia - BE/Antwerp)" <dirk.goethals@nokia.com>, "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
References: <A4351C7F-183D-4490-BD3C-5ADC5C087F84@cisco.com> <f21041a1-62df-4f6e-6353-46986569bdcc@nokia.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <5b1be003-eaf2-768f-bb0e-ac949df40665@cisco.com>
Date: Mon, 18 Feb 2019 14:18:59 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <f21041a1-62df-4f6e-6353-46986569bdcc@nokia.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.147.24.16, [10.147.24.16]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/6AE7zWGvkIjzDlO2YWhQwhWoSgs>
Subject: Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 13:19:05 -0000

Hi Dirk,

On 18/02/2019 09:31 , Goethals, Dirk (Nokia - BE/Antwerp) wrote:
> support +1
>
> 1 question:
>
>> When S1 in another area receives such LSA, it then can learn that
>>    prefix Lt1 is associated with node T1, check the ELC, ERLD, or MSD
>>    value according to its necessity, and construct the right label stack
>>    at the ingress node S1 for the traffic destined to Lt1.
>
> How is S1 going to know the "ELC, ERLD, or MSD" of  node T1?
> I guess, T1 will need to send an AS-scoped router info LSA?

yes, that is a possibility.

>
> If so, should T1 be ASBR as to be able to send this AS-scoped LSA?

I would not think so.


> I guess it was needed before as to enforce  the ABR to create the T4 LSAs,
> so that others can learn which ABR to use to reach T4, but I guess
> it's not needed anymore when this draft is implemented.

not sure how you reached the above conclusion. Can you please clarify?

thanks,
Peter



>
> Regards,
> Dirk
>
>
> On 2/13/2019 14:25, Acee Lindem (acee) wrote:
>>
>> This begins a two week adoption poll for the subject draft. Please
>> send your comments to this list before 12:00 AM UTC on Thursday,
>> February 28^th , 2019.
>>
>>
>>
>> All authors have responded to the IPR poll and there is one
>> <https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-wang-lsr-ospf-prefix-originator-ext> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-wang-lsr-ospf-prefix-originator-ext
>>
>> It is listed multiple times but references the same CN201810650141.
>>
>>
>>
>> Thanks,
>>
>> Acee
>>
>>
>>
>>
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org
>> https://www.ietf.org/mailman/listinfo/lsr
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>

v2.23.0 | Report a Bug | By Email