Re: [Lsr] OSPF TE Link Local TLV

Alexander Okonnikov <alexander.okonnikov@gmail.com> Tue, 05 February 2019 19:40 UTC

Return-Path: <alexander.okonnikov@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 2AA19131205; Tue, 5 Feb 2019 11:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 DJZ9eT0tCbFo; Tue, 5 Feb 2019 11:40:51 -0800 (PST)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 A185B1311FC; Tue, 5 Feb 2019 11:40:50 -0800 (PST)
Received: by mail-lf1-x12d.google.com with SMTP id z26so3560572lfj.6; Tue, 05 Feb 2019 11:40:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=x6XQ0RJkdkwXPDwuebezgmZgdUMvtJLaNrxtd848bMk=; b=XagD4WbOxIYm6CVff//VyPIOlAoayQwFxBdHAf/e5hFm76IELyABoIOB4kec+LCwiK 8V00g0gMjgo8kqVBIA0fUkK/KjXMTMLVVvkB44DhjrS6nHDc6wXsDtG+es4vwHD1UPss yw0FsUvx7cR1nQB7ASLdtdcABbZoynbBdD5VZAxTWtE2qa841PpB8VeIs968Xx/N4eMh b2A6NvnpBGeN1czPkiiUTSutrnELwmmdp5L2aL1XsZENVbZQqKmWF41qvI4UvpdXaJ+h PSuOprSM+5muLteSmP77C2WZ31vaw82da0IC0Uw+TrMhGb3+/x1/50UADx3ixeOj514m nbOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=x6XQ0RJkdkwXPDwuebezgmZgdUMvtJLaNrxtd848bMk=; b=G+zCno2wXm3E+ns8rn3+xcIgWgZBtwXt+hWJ6Y5W4+29Xrhyo+zej8ZTDZQ5iefX/P 9V6Rehn+WE/zXdM+W2GXhPfsOuy50tfaRXrpDAEJI58/bbxXR5MK60StOIJYDr36ah+F TDrwUN6UweYLz3zFyIkv1BGXt+vSnnWZX5VHS4VttKeaYH17H7cYga6Wh+e6oPcnYSNL EnVZnBEdMlbA2d+E9BDWhr0ylXxAKWwbYCc69DTGrrAaZyM31zKZy4S1XoxHvUMqyFGi F/UKMaXx82h3HSo/6BCXmWHBJn5pFvUMg/TJrbGx1qfM7EZUaEwVt8LT0kpY2j4WEBeL i4lg==
X-Gm-Message-State: AHQUAuYHXMe16AOl8dI6tTsKj4hXNrt9qqe9JvK5MOyBgMBh6G16HGaW uD7UV8e1XvPmrJH++ZB4Ad8=
X-Google-Smtp-Source: AHgI3IbO1A0bQGfBPesgranylBXWn3xGiGXIb2EFZwkvLfrVUhbce6LW94NOBcDy8N13/fLrF0svNQ==
X-Received: by 2002:a19:ab09:: with SMTP id u9mr4059302lfe.149.1549395648713; Tue, 05 Feb 2019 11:40:48 -0800 (PST)
Received: from [10.0.1.2] ([88.201.167.54]) by smtp.gmail.com with ESMTPSA id p14sm310105lfk.16.2019.02.05.11.40.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Feb 2019 11:40:48 -0800 (PST)
From: Alexander Okonnikov <alexander.okonnikov@gmail.com>
Message-Id: <8085D050-8FF9-4E93-8218-802ED36C6481@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7612AE11-1B16-4D0A-8F4B-84DA97FDE92E"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 05 Feb 2019 22:40:46 +0300
In-Reply-To: <CD275F53-6376-4848-B9EB-F422FB00BF6E@cisco.com>
Cc: "ccamp@ietf.org" <ccamp@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
To: "Acee Lindem (acee)" <acee@cisco.com>
References: <DE0E4808-0C9A-415B-9D96-85B75A385B84@gmail.com> <12BF6AD3-674E-47F5-BD05-040B33DD0354@cisco.com> <DB7PR04MB4521A0C4B0E14DEE4572C84BA86E0@DB7PR04MB4521.eurprd04.prod.outlook.com> <CD275F53-6376-4848-B9EB-F422FB00BF6E@cisco.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/pxbWNWP9Ep20PmusRf-IzvCdouc>
Subject: Re: [Lsr] OSPF TE Link Local TLV
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: Tue, 05 Feb 2019 19:40:53 -0000

Hi Acee,

Yes, RFC 8510 provides alternative mechanism, but link identifier discovery mechanism via link-local TE LSA is still valid. Hence, I think that early mentioned issues need to be addressed.

Thank you!

> 5 февр. 2019 г., в 21:29, Acee Lindem (acee) <acee@cisco.com> написал(а):
> 
> Hi Alex, 
>  
> From: Alexander Okonnikov <alexander.okonnikov@gmail.com <mailto:alexander.okonnikov@gmail.com>>
> Date: Tuesday, February 5, 2019 at 12:59 PM
> To: Acee Lindem <acee@cisco.com <mailto:acee@cisco.com>>, "ccamp@ietf.org <mailto:ccamp@ietf.org>" <ccamp@ietf.org <mailto:ccamp@ietf.org>>, "lsr@ietf.org <mailto:lsr@ietf.org>" <lsr@ietf.org <mailto:lsr@ietf.org>>
> Subject: Re: [Lsr] OSPF TE Link Local TLV
>  
> Hi Acee,
>  
> Per my understanding Link Local/Remote ID Sub-TLV is to be conveyed in area-scope LSA to uniquely identify link between pair of routers. For link-local scope another Sub-TLV was introduced, for discovery of link IDs by two neighbors.
>  
> The context is completely different – see https://www.rfc-editor.org/rfc/rfc8510.txt <https://www.rfc-editor.org/rfc/rfc8510.txt>
>  
> May be, it is possible to reuse Link Local/Remote ID Sub-TLV (with Remote ID = 0) of Link TLV in link-local scope LSA, but the RFC follows another approach - to use another Sub-TLV and another TLV. I am not sure that we needed dedicated top-level TLV, though idea to use separate Sub-TLV seems to be reasonable.
>  
> It is also possible to use a sledge hammer to crack a nut…. 
>  
> Acee 
>  
> Thank you!
>  
> Best regards,
> Alexander Okonnikov
>  
> От: Acee Lindem (acee) <acee@cisco.com <mailto:acee@cisco.com>>
> Отправлено: вторник, февраля 5, 2019 20:21
> Кому: Alexander Okonnikov; ccamp@ietf.org <mailto:ccamp@ietf.org>; lsr@ietf.org <mailto:lsr@ietf.org>
> Тема: Re: [Lsr] OSPF TE Link Local TLV 
>  
> Hi Alex, 
>  
>  
> From: Lsr <lsr-bounces@ietf.org <mailto:lsr-bounces@ietf.org>> on behalf of Alexander Okonnikov <alexander.okonnikov@gmail.com <mailto:alexander.okonnikov@gmail.com>>
> Date: Tuesday, February 5, 2019 at 7:48 AM
> To: "ccamp@ietf.org <mailto:ccamp@ietf.org>" <ccamp@ietf.org <mailto:ccamp@ietf.org>>, "lsr@ietf.org <mailto:lsr@ietf.org>" <lsr@ietf.org <mailto:lsr@ietf.org>>
> Subject: [Lsr] OSPF TE Link Local TLV
>  
> Hi,
>  
> I have question regarding RFC 4203, Section 3. That section introduces top-level TLV type 4 (Link Local TLV) and, at the same time, describes Link Local Identifier TLV. I guess that latter in fact is Sub-TLV of Link Local TLV. Also, IANA Considerations section doesn't mention that Sub-TLV, but only introduction of Link Local TLV. IANA has no corresponding registry  - "Types for Sub-TLVs of Link Local TLV (Value 4)".
>  
> I believe this example is actually wrong and section 3 should refer to the top-level Link TLV (value 2) defined in RFC 3630. The Link Local Identifier is the one advertised in Link Local/Remote Identifiers Sub-TLV (type 11) defined in RFC 4203 section 1.1. 
>  
> Hope this helps, 
> Acee
>  
> Thanks in advance.
>  
> Best regards,
> Alexander Okonnikov