Re: [Lsr] "OSPF Routing with Cross-Address Family Traffic Engineering Tunnels" - draft-ietf-ospf-xaf-te-05

2019-02-27 Thread Anton Smirnov
Hi Alexander, see some answers inline. --- Anton On 02/08/19 11:25, Alexander Okonnikov wrote: Hi Acee, For me current version doesn't change the solution. My comments are follow: 1.  Introduction "TE Extensions to OSPFv2 [RFC3630] and OSPFv3 [RFC5329] have been described to support

Re: [Lsr] I-D Action: draft-ietf-ospf-xaf-te-05.txt

2018-12-10 Thread Anton Smirnov
Hello all, the new revision addresses 3 comments raised during the LC discussion. --- Anton Smirnov On 12/10/18 17:40, internet-dra...@ietf.org wrote: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Link State Routing WG

Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

2018-10-26 Thread Anton Smirnov
h that SPF for one AF can utilise LSPs as shortcuts, created for other AF. My understanding that these two tasks need to be discussed separately. It could be two different documents, or two different sections of the same one. Thank you. 25 окт. 2018 г., в 19:57, Anton Smirnov <mailto:asmir.

Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

2018-10-25 Thread Anton Smirnov
   Hi Ketan, 1. I am not sure I understood the question. Your example says "using the TE topology from OSPFv2 to compute a tunnel". In that case TE router ID is an IPv4 address. So no, advertising IPv6 address won't help to identify the tunnel. 2. my opinion (not discussed with other

Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

2018-10-25 Thread Anton Smirnov
   Hi Gunter,    we agree with the proposed change and will make it in the next revision, probably even rephrase this sentence. --- Anton On 10/24/18 12:59, Van De Velde, Gunter (Nokia - BE/Antwerp) wrote: Looks fine. One item I would like to see changed (or at least discussed) I have a

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

2018-04-24 Thread Anton Smirnov
functionality. Thanks, Acee *From: *Lsr <lsr-boun...@ietf.org> on behalf of Acee Lindem <a...@cisco.com> *Date: *Thursday, April 19, 2018 at 5:29 PM *To: *"Anton Smirnov (asmirnov)" <asmir...@cisco.com>, "draft-ietf-ospf-xaf...@ietf.org" <draft-ietf-ospf-xa

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

2018-04-20 Thread Anton Smirnov
w author Alvaro (of OSPF TTZ fame) could help with some generic text preceding the specific IGP Shortcut use case. Let me see if I can massage the backward compatibility text. I’m requested a Routing Directorate review and I’m going to start the LSR WG last call shortly. Thanks, Acee *From:

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

2018-04-19 Thread Anton Smirnov
if answers in my previous email didn't clarify your questions/concerns. --- Anton On 04/07/18 23:06, Acee Lindem (acee) wrote: Hi Anton, On 4/6/18, 7:33 AM, "Anton Smirnov (asmirnov)" <asmir...@cisco.com> wrote:     Hi Acee,     my answers below (I didn't vet

Re: [Lsr] OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels

2018-04-06 Thread Anton Smirnov
Hi Acee, my answers below (I didn't vet them with other authors, so they may express different opinions). > 1. Have you considered a shorter name for the RFC? For example: “OSPF > Cross Address Family Traffic Engineering Tunnels”? Your proposed variant drops two pieces: "Routing