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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 29 October 2018 00:21 UTC

Return-Path: <ketant@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 BF31212872C for <lsr@ietfa.amsl.com>; Sun, 28 Oct 2018 17:21:42 -0700 (PDT)
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_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, 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 9wwzRvYQQdJC for <lsr@ietfa.amsl.com>; Sun, 28 Oct 2018 17:21:40 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58BC01274D0 for <lsr@ietf.org>; Sun, 28 Oct 2018 17:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10752; q=dns/txt; s=iport; t=1540772500; x=1541982100; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ENT4ZmIYuipqnGtU7l3s30/ITrTFt2RZhR5DU4l0iB8=; b=lVBXhGACrxf0Rn6yRpvnGwReq3acXVsN6j0hmPOQFFE0e362YDJc6oZM VSA0F4ZDVXPf1UaRRvQuRd4gNuA/DRiEGYYMUcG85Cz78dTSDSyYCiTLv HXAhwN7v9cXhOTCkBjzy/C2JdDx76bKWXT7Qwi9/4IZYKSmDNcPpdlRkB 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ANAADJUdZb/4MNJK1ZChkBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQEBgVEEAQEBAQELAYFVL2Z/KAqDa4gYjiODQIVAjiCBegs?= =?us-ascii?q?BARgLhEkCF4MBITQNDQEDAQECAQECbRwMhToBAQEDAQEBGwYROgsMBAIBBgI?= =?us-ascii?q?RBAEBAQICHwQDAgICHwYLFAEICAIEAQ0FCIMagWkDDQgPiwebToEuhD5AgnA?= =?us-ascii?q?NghMFgQuKXBeBQT+BEAGCZC6CVkUBAQMBgTJCD4JeglcCnlsuCQKGaIMhg1K?= =?us-ascii?q?DHyCBUoR3iX6CaYoHf4YGgwACERSBJh04QYEUcBU7gmyCJhcSiEqFPm+MBIE?= =?us-ascii?q?fAQE?=
X-IronPort-AV: E=Sophos;i="5.54,438,1534809600"; d="scan'208";a="387952394"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Oct 2018 00:21:39 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id w9T0Lc3O022137 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 29 Oct 2018 00:21:39 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 28 Oct 2018 19:21:38 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1395.000; Sun, 28 Oct 2018 19:21:38 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "Anton Smirnov (asmirnov)" <asmirnov@cisco.com>, Alexander Okonnikov <alexander.okonnikov@gmail.com>
CC: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt
Thread-Index: AQHUalYXl2Z4skvnDEu/Rd//ZGkJo6UuJ/bggAJeuoCAAElgAIABfSOAgAMW1UA=
Date: Mon, 29 Oct 2018 00:21:38 +0000
Message-ID: <d8b732b965984aff8545556e7d0a3f06@XCH-ALN-008.cisco.com>
References: <1E930DB6-2ED9-43A3-8EC7-338DAD1C3803@cisco.com> <a0d5bee9e8f34f2683f60a3d368b1d96@XCH-ALN-008.cisco.com> <2687ff55-16c4-d6f8-ecb9-3a0db154c28e@cisco.com> <DCEC0D5D-4716-47CD-8FA6-0414A6A2F578@gmail.com> <b92e376e-a244-a683-a8bb-d4c03fd9414a@cisco.com>
In-Reply-To: <b92e376e-a244-a683-a8bb-d4c03fd9414a@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.137.48.161]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/4vaxKcnNLLFqedb56K6IkR5u7ZU>
Subject: Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt
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, 29 Oct 2018 00:21:43 -0000

Agree with Anton on the use of Node IPvX Local Address sub-TLVs as it provides the flexibility to advertise more/other addresses. If we were to use IPvX Router Address TLVs then we could only do one per node.

My comment was that in most cases, advertising just that one IPvX address (generally equivalent to what would have been put in IPvX Router Address TLV) is sufficient and that this it should be a MUST (instead of SHOULD). Other addresses may be optional as indicated in the draft.

Thanks,
Ketan

-----Original Message-----
From: Anton Smirnov (asmirnov) 
Sent: 27 October 2018 07:04
To: Alexander Okonnikov <alexander.okonnikov@gmail.com>;
Cc: Ketan Talaulikar (ketant) <ketant@cisco.com>;; Acee Lindem (acee) <acee@cisco.com>;; lsr@ietf.org
Subject: Re: [Lsr] OSPF Routing with Cross-Address Family Traffic Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt

    Hi Alexander,

 > I tend to agree with Ketan, but with slightly different proposal. Would  > not it be simpler to advertise IPv6 Router Address TLV (TLV type 3) by  > OSPFv2 Opaque LSA (in addition to advertising of Router Address TLV) and  > to advertise Router Address TLV (TLV type 1) by OSPFv3 Intra-Area-TE-LSA  > (in addition to advertising IPv6 Router Address TLV)? In this case we  > can identify the same router represented by OSPFv2 and OSPFv3 and don't  > need the extension provided by the draft.

    What you are suggesting is essentially the same sort of information propagated in different TE TLV. So basically except for TLV type rest of of procedures won't change.
    When writing the first revision of the draft we did consider doing what you are proposing but finally Node IPvX Local Address sub-TLV looked like a better match to what we intend to advertise.
    Per RFC 5786 Node IPvX Local Address sub-TLV is used to advertise additional addresses local to the router. And that is exactly what we use it for, to advertise additional router's addresses.

    As for the other Ketan's comment - as I already wrote, we will try to address it in the next document revision.

---
Anton


On 10/25/18 23:19, Alexander Okonnikov wrote:
> Hi Anton,
> 
> I tend to agree with Ketan, but with slightly different proposal. 
> Would not it be simpler to advertise IPv6 Router Address TLV (TLV type 
> 3) by
> OSPFv2 Opaque LSA (in addition to advertising of Router Address TLV) 
> and to advertise Router Address TLV (TLV type 1) by OSPFv3 
> Intra-Area-TE-LSA (in addition to advertising IPv6 Router Address 
> TLV)? In this case we can identify the same router represented by 
> OSPFv2 and OSPFv3 and don't need the extension provided by the draft.
> 
> Regarding calculation of LSPs towards non-TE addresses - head-end uses 
> non-TE address in order to determine TE Router ID of the tail-end 
> (which holds that non-TE address); then head-end uses TE RID in CSPF 
> calculation (though it will, probably, use that non-TE address as a 
> destination in RSVP-TE signaling). Hence, head-end can hold mapping of 
> destination IP of an LSP to corresponding TE RID of tail-end. Then, if 
> the same head-end attempts to calculate LSP using TEDB from OSPFv3 
> (OSPFv2), it will be able to determine whether LSP already have been 
> signaled using OSPFv2 (OSPFv3) TEDB.
> 
> Also, the draft several times says about using TEDB(s) for calculation 
> of LSPs and, on the other hand, for using LSPs for calculation of OSPF 
> routes. Per my understanding these are two different independent tasks 
> - calculation of LSPs and their usage. The second task is what defined 
> by RFC 3906, and you want to extend it such 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 <asmirnov@cisco.com 
>> <mailto:asmirnov@cisco.com>> написал(а):
>>
>>    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 authors): RFC 3906 is 
>> Informational RFC, so it is not mandatory for implementation to 
>> follow. I think we can insert mention to that RFC somewhere in the 
>> Introduction but wording should be sufficiently weak (like "one 
>> possible example of route computation algorithm...").
>>
>> ---
>> Anton
>>
>> On 10/24/18 12:06, Ketan Talaulikar (ketant) wrote:
>>>
>>> Hello All,
>>>
>>> I support this simple but important extension.
>>>
>>> A couple of minor comments on the draft:
>>>
>>> 1)Sec 3 says
>>>
>>>    A node that implements X-AF routing SHOULD advertise, in the
>>>    corresponding Node Local Address sub-TLV, all X-AF IPv4 and IPv6
>>>    addresses local to the router that can be used by Constrained SPF
>>>    (CSPF) to calculate MPLS TE LSPs.  In general, OSPF SHOULD 
>>> advertise
>>>    the IP address listed in the Router Address TLV [RFC3630 
>>> <https://tools.ietf.org/html/rfc3630>] [RFC5329 
>>> <https://tools.ietf.org/html/rfc5329>]
>>>    of the X-AF instance maintaining the MPLS TE database, plus any
>>>    additional local addresses advertised by the X-AF OSPF instance 
>>> in
>>>    its Node Local Address sub-TLVs.  An implementation MAY advertise
>>>    other local X-AF addresses.
>>>
>>> Generally speaking, should the IP address (TE router ID in common
>>> terms) which is candidate for inclusion in the Router Address TLV 
>>> not be a MUST candidate for X-AF advertisement?
>>>
>>> I also have a question about the first statement with the SHOULD in 
>>> it. Consider we are using the TE topology from OSPFv2 to compute a 
>>> tunnel for use with OSPFv3. Any IPv6 addresses associated with the
>>> OSPFv3 instance on a router would be advertised as a Node attribute 
>>> and would not help identify a specific link. So practically, if any
>>> IPv6 addresses (if at all) were to be used for CSPF then it would 
>>> just identify the node – in this case, isn’t advertising the IPv6 
>>> address (TE router ID used in Router Address TLV) sufficient?
>>>
>>> For practical deployment, it think it would help if this was 
>>> clarified that we really need only the TE Router ID Address to go 
>>> X-AF in most/general cases and not the others?
>>>
>>> 2)Isn’t the mapping algorithm in Sec 3 actually going to be used for 
>>> IGP short-cut use-case with its reference to the IGP cost of the 
>>> tunnel? If so, would a reference to rfc3906 be helpful in this document.
>>>
>>> Thanks,
>>>
>>> Ketan
>>>
>>> *From:*Lsr <lsr-bounces@ietf.org>; *On Behalf Of *Acee Lindem (acee)
>>> *Sent:* 23 October 2018 03:55
>>> *To:* lsr@ietf.org
>>> *Subject:* [Lsr] OSPF Routing with Cross-Address Family Traffic 
>>> Engineering Tunnels - draft-ietf-ospf-xaf-te-04.txt
>>>
>>> This begins an LSR WG last call for the subject draft. Please send 
>>> your comments to this list prior to 12:00 AM GMT, November 13^th , 
>>> 2018. While its only an 8 page document, I added an extra week due 
>>> to the IETF. Please let me know if anyone needs any more time.
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-ospf-xaf-te/
>>>
>>> Thanks,
>>> Acee
>>>
>>>
>>>
>>> _______________________________________________
>>> Lsr mailing list
>>> Lsr@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lsr
>>
>> _______________________________________________
>> Lsr mailing list
>> Lsr@ietf.org <mailto:Lsr@ietf.org>
>> https://www.ietf.org/mailman/listinfo/lsr
>