Re: [Lsr] 答复: 答复: Regarding OSPF extension for inter-area topology retrieval

Tony Przygienda <tonysietf@gmail.com> Wed, 25 July 2018 06:09 UTC

Return-Path: <tonysietf@gmail.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 3C4EF130E3A for <lsr@ietfa.amsl.com>; Tue, 24 Jul 2018 23:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 FnNiuNXXHGdX for <lsr@ietfa.amsl.com>; Tue, 24 Jul 2018 23:09:07 -0700 (PDT)
Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B767B130DE2 for <lsr@ietf.org>; Tue, 24 Jul 2018 23:09:06 -0700 (PDT)
Received: by mail-ed1-x52f.google.com with SMTP id t2-v6so6182999edr.5 for <lsr@ietf.org>; Tue, 24 Jul 2018 23:09:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fD6b7+wQX736bb6gStEKR2S6cSeBxDmz/wy8VdoNiKo=; b=TgyfCoLlTKgH6C8z/WRJaYjvsZk/0PNOsZvPSTC6BjsBN/7iufIW6vEwJsBJLYXpv6 7JvHZ3rK+cHIN0ndrEmMwoz3vz8hu4YpNR6b9cPZnUw3moO99T6h/h3Na87enkM8K7Ee a3K+o5zXyznOx84r6JUKDbd3IlhQX+VYWNzVxXgcJAIO50SAnOgFRPV8O3/ihba9peTm nnLExtRp4OufLvY+V8zW9FHGY9cadYlu5uSAfyQG2Re11yE/jYZji9PUOT0co2p+NXHR KIqm/YrArwlyZHWIeBmHNBfsWRUOi7SeisuwiEQxsRLJTXxlw1qbvnwCjHHqNcu7srqs pcgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fD6b7+wQX736bb6gStEKR2S6cSeBxDmz/wy8VdoNiKo=; b=Di1oHUYAyhiqPhY9lw0F4pBiODc6as6yzYMD/gb7ib4dNcyAhDUj8apQAzUXibOqF8 cXyFE0chiVhupZSyNZifeiEljqJdTIMNZRf7ghDLaIsJOVDHFAeIK+CbCBu/hmmYqkdA IAJ0MnJ8ec4aQthBCTXEgXpBLB2UE1+l7t0/CLC3w6wM1EWtKpYOoLAzJP6zb1PJa/7L cB2Pstq4CZb7VajhGcwDq0KI/HsHnUGlt676iIM6SiYfoJjrhN/bPHIjSJb+z0SwNPwd HtNQ2V4W1x00XlQoooLeeGvRnKc5tjnmIqy2ikQQNQFsnqq6BBB05B+ftDOusyXQZNTi 91WA==
X-Gm-Message-State: AOUpUlHEBuOGJ50+FdNTNN+F+65hMvYAl9ZAesWpCniMow9E9ZhZ8yP6 Lcyz6+8qZpwk2SpPjfjimcHbpofb5h8Z81n5JJQ=
X-Google-Smtp-Source: AAOMgpe3lGIRnI98yQUM5463milkJJm1YDLz8yLL3nS0JGUVE4VWCnYWi4PLNaxfC3b2Q1o4mr8Ro8NZPcR1HpVkS9g=
X-Received: by 2002:a50:8141:: with SMTP id 59-v6mr21728585edc.156.1532498945341; Tue, 24 Jul 2018 23:09:05 -0700 (PDT)
MIME-Version: 1.0
References: <001601d42259$a860fff0$f922ffd0$@org.cn> <5B558E76.3010703@cisco.com> <003201d42265$cd011af0$670350d0$@org.cn> <5B55ABB5.60806@cisco.com> <003f01d42275$5ec00eb0$1c402c10$@org.cn> <5B55BC38.3050605@cisco.com> <CAHxMReYo_e+dDJ611X3eihV0WCToYqFDa2c+CLnfzhF8_L2YDA@mail.gmail.com>
In-Reply-To: <CAHxMReYo_e+dDJ611X3eihV0WCToYqFDa2c+CLnfzhF8_L2YDA@mail.gmail.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Wed, 25 Jul 2018 08:08:28 +0200
Message-ID: <CA+wi2hOs0qeZSOGQXSE+Ok_7YeqxyLnPDmDZ-r1YFsw=AS1haw@mail.gmail.com>
To: Rob Shakir <rjs@rob.sh>
Cc: ppsenak=40cisco.com@dmarc.ietf.org, "Dongjie (Jimmy)" <jie.dong@huawei.com>, Christian Hopps <chopps@chopps.org>, ketant@cisco.com, wangaijun@tsinghua.org.cn, lsr@ietf.org, "Acee Lindem (acee)" <acee@cisco.com>
Content-Type: multipart/alternative; boundary="000000000000417b780571ccb717"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/0xvfa3LVujCDvpdc2weRKCaeiCc>
Subject: Re: [Lsr] 答复: 答复: Regarding OSPF extension for inter-area topology retrieval
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 25 Jul 2018 06:09:10 -0000

pretty obvious +1 here

--- tony

On Tue, Jul 24, 2018 at 3:41 AM Rob Shakir <rjs@rob.sh> wrote:

> +1 to Peter. We should not define fragile solutions within the IETF.
>
> There are also a multitude of other solutions here already:
>
> 1) IGP adjacency with one router in each area (at a minimum - probably two
> for a robust system) over a tunnel. Deployed in many networks for years.
> 2) BGP-LS to one router (ditto robustness comment) in each area.
> 3) streaming telemetry of the LSDB contents via gNMI.
>
> All these solutions exist in shipping implementations - please let’s not
> add to the system complexity of the IGP here.
>
> r.
> On Mon, Jul 23, 2018 at 12:30 Peter Psenak <ppsenak=
> 40cisco.com@dmarc.ietf.org> wrote:
>
>> Hi Aijun,
>>
>> On 23/07/18 13:07 , Aijun Wang wrote:
>> > Hi, Peter:
>> >
>> > For routers that connected by LAN, the router will establish adjacent
>> > neighbor with DR, but not only DR advertises the connected prefixes.
>>
>> only the Network LSA includes the network mask, other routers would
>> include the interface address only.
>>
>>
>> > DR and
>> > DRother will all advertise type 1 and type 2 LSA with each other, then
>> the
>> > process and proposal described in this draft will still work.
>> > We seldom use the ip unnumbered features in our network, can we ignore
>> it
>> > then? Or other persons has some idea on such situation?
>>
>> the fact that you do not use unnumbered is not really relevant. IETF
>> defines solutions that MUST work for all possible scenarios, not only
>> for a specific one.
>>
>> > Anycast prefixes are often /32 long, this can be easily filtered by SDN
>> > controller because the link prefixes between two routers will be no
>> larger
>> > than /32 for IPv4 network.
>>
>> protocol allows to advertise the same prefix with an arbitrary mask from
>> multiple routers without these routers being directly connected. Your
>> proposal is based on the assumptions that are incorrect.
>>
>> thanks,
>> Peter
>>
>> >
>> > Best Regards.
>> >
>> > Aijun Wang
>> > Network R&D and Operation Support Department
>> > China Telecom Corporation Limited Beijing Research Institute,Beijing,
>> China.
>> >
>> > -----邮件原件-----
>> > 发件人: Peter Psenak [mailto:ppsenak=40cisco.com@dmarc.ietf.org]
>> > 发送时间: 2018年7月23日 18:20
>> > 收件人: Aijun Wang; 'Peter Psenak'; chopps@chopps.org
>> > 抄送: lsr@ietf.org; 'Ketan Talaulikar (ketant)'; 'Acee Lindem (acee)';
>> > 'Dongjie (Jimmy)'
>> > 主题: Re: [Lsr] 答复: Regarding OSPF extension for inter-area topology
>> > retrieval
>> >
>> > Hi Aijun,
>> >
>> > On 23/07/18 11:16 , Aijun Wang wrote:
>> >> Hi, Peter:
>> >>
>> >> Actually, I consider mainly the point-to-point connection and the
>> >> numbered interface, which are normal in our network.
>> >> For the two situations that you mentioned, I will investigation the
>> >> possible solutions and feedback you later.
>> >>
>> >> For the point-to-point and numbered interface, do you have other
>> >> questions then?
>> >
>> > the fact that two routers announce the same subnet, does not mean they
>> are
>> > connected together by p2p link. Anycast prefix is an example.
>> >
>> > The idea you are proposing simply does not work.
>> >
>> > thanks,
>> > Peter
>> >
>> >
>> >>
>> >> Best Regards.
>> >>
>> >> Aijun Wang
>> >> Network R&D and Operation Support Department China Telecom Corporation
>> >> Limited Beijing Research Institute,Beijing, China.
>> >>
>> >> -----邮件原件-----
>> >> 发件人: Peter Psenak [mailto:ppsenak=40cisco.com@dmarc.ietf.org]
>> >> 发送时间: 2018年7月23日 16:15
>> >> 收件人: Aijun Wang; chopps@chopps.org
>> >> 抄送: lsr@ietf.org; 'Ketan Talaulikar (ketant)'; 'Acee Lindem (acee)';
>> >> 'Dongjie (Jimmy)'
>> >> 主题: Re: [Lsr] Regarding OSPF extension for inter-area topology
>> >> retrieval
>> >>
>> >> Hi Aijun,
>> >>
>> >> you are trying to reconstruct the topology of the remote area based on
>> >> the fact that two routers are connected to the same subnet. It does
>> >> not work
>> >> because:
>> >>
>> >> 1. connections between routers can be unnumbered 2. routers can be
>> >> connected via LAN, in which case only DR announces the prefix.
>> >>
>> >> In summary, what you propose does not work.
>> >>
>> >> thanks,
>> >> Peter
>> >>
>> >>
>> >>
>> >> On 23/07/18 09:49 , Aijun Wang wrote:
>> >>> (Sorry for my previous mail sent wrongly to the IDR mail list, please
>> >>> reply on this thread within the LSR wg)
>> >>>
>> >>> Hi, Peter:
>> >>>
>> >>> I am Aijun Wang from China Telecom, the author of draft about “OSPF
>> >>> extension for inter-area topology retrieval”
>> >>> <https://datatracker.ietf.org/doc/draft-wang-lsr-ospf-inter-area-topo
>> >>> l ogy-ext/>, which is presented by Mr.Jie Dong during the IETF102
>> >>> meeting.
>> >>>
>> >>> Thanks for your comments on the presentation material
>> >>>
>> >> <https://datatracker.ietf.org/meeting/102/materials/slides-102-lsr-osp
>> >> f-inte
>> >> r-area-topology-retrieval-00>.
>> >>>
>> >>> Below are my explanation that regarding to the question about “how it
>> >>> retrievals the inter-area topology based on the extension
>> information”:
>> >>>
>> >>> Let’s see the graph that illustrates in Fig.1 at section 3
>> >>> <https://tools.ietf.org/html/draft-wang-lsr-ospf-inter-area-topology-
>> >>> e xt-00#section-3> of the draft(I copy it also below for your
>> >>> conveniences ):
>> >>>
>> >>> Assuming we want to rebuild the connection between router S1 and
>> >>> router
>> >>> S2 that locates in area 1:
>> >>>
>> >>> 1)Normally, router S1 will advertise prefix N1 within its router LSA
>> >>>
>> >>> 2)When this router LSA reaches the ABR router R1, it will convert it
>> >>> into summary LSA, add the “Source Router Information”, which is
>> >>> router id of S1 in this example, as proposed in this draft.
>> >>>
>> >>> 3)R1 then floods this extension summary LSA to R0, which is running
>> >>> BGP-LS protocol with IP SDN Controller. The controller then knows the
>> >>> prefixes of N1 is from S1.
>> >>>
>> >>> 4)Router S2 will do the similar process, and the controller will also
>> >>> knows the prefixes N1 is also from S2
>> >>>
>> >>> 5)Then it can reconstruct the connection between S1 and S2, which
>> >>> prefix is N1. The topology within Area 1 can then be recovered
>> >> accordingly.
>> >>>
>> >>> Does the above explanation can answer your question. if so, I can add
>> >>> it into the context of this draft in updated version.
>> >>>
>> >>> Best Regards.
>> >>>
>> >>> Aijun Wang
>> >>>
>> >>> Network R&D and Operation Support Department
>> >>>
>> >>> China Telecom Corporation Limited Beijing Research Institute,Beijing,
>> >> China.
>> >>>
>> >>
>> >> _______________________________________________
>> >> 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
>> >>
>> >
>> > _______________________________________________
>> > 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
>>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>