Re: [Lsr] Link Data value for Multi-area links

Peter Psenak <ppsenak@cisco.com> Fri, 27 November 2020 11:50 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 3704C3A09B5 for <lsr@ietfa.amsl.com>; Fri, 27 Nov 2020 03:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.602
X-Spam-Level:
X-Spam-Status: No, score=-9.602 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, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, 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 wQEuRqQOwP5W for <lsr@ietfa.amsl.com>; Fri, 27 Nov 2020 03:50:35 -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 6F1C53A09AD for <lsr@ietf.org>; Fri, 27 Nov 2020 03:50:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=754; q=dns/txt; s=iport; t=1606477835; x=1607687435; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=DboiJzOLLl+ELtCihpWPBsWEObInYtETtgX+c/KX2+g=; b=PUjc+lepUuxdGa6tfb/qBKGd9TB/zRdglI+A7mTRIQI//40x+GKEgl0D c3HF3XxC0MiKtxCgDdn4KAKaovarKHkrRfw8/UZVK8lgLi5OtCumkf20D MyhzMQV/lFm/czxuL7mreMXvGCPrSDnvVAaULGnVLEORD6PyjYM/iIjKx I=;
X-IPAS-Result: A0BACgBS58Bf/xbLJq1iHgEBCxIMQIRuVgEgEi6EPYkFh3UvnDALAQEBDxgLDAQBAYRKAoIqJjgTAgMBAQEDAgMBAQEBBQEBAQIBBgRxhWEMhXIBAQEDAQEBIRU2GwsYAgImAgInMAYBDAYCAQGDIgGCZiAPrzN2gTKFV4NTgTwGgQ4qiS2ELoFBP4E4gkMuPoJdAQGEdoJfBJxgnAqCeYMdmAMFBwMfkmCPNB2TSKEWgW0jgVczGggbFTuCaVAZDZcmhUVAAzA3AgYKAQEDCY9aAQE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.78,374,1599523200"; d="scan'208";a="31454630"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Nov 2020 11:50:33 +0000
Received: from [10.60.140.52] (ams-ppsenak-nitro3.cisco.com [10.60.140.52]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id 0ARBoXZ5016992; Fri, 27 Nov 2020 11:50:33 GMT
To: Alexander Okonnikov <alexander.okonnikov@gmail.com>, lsr@ietf.org
References: <61201EB5-3F36-401A-9D39-FB0C577C7966@gmail.com>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <3d3d863b-3e1f-ea87-0c45-09e119aa7c8f@cisco.com>
Date: Fri, 27 Nov 2020 12:50:33 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <61201EB5-3F36-401A-9D39-FB0C577C7966@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.52, ams-ppsenak-nitro3.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/UMzbkJ4n2lvx2Ejp8w5ambmo6pY>
Subject: Re: [Lsr] Link Data value for Multi-area links
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: Fri, 27 Nov 2020 11:50:37 -0000

Alexander,

On 26/11/2020 17:58, Alexander Okonnikov wrote:
> Hi WG,
> 
> RFC 5185 says that Neighbor's IP address to be encoded into Link Data field. Per RFC 2328 router's own IP address to be encoded into Link Data. What is the reason to advertise neighbor's IP address for multi-area links and not local IP address? It seems like bug. Could someone comment on this?

Advertising a neighbor address/ifindex helps to eliminate ambiguity in 
case of parallel point-to-point adjacencies. It's not perfect, but 
that's how it was specified. So it's not a bug.

thanks,
Peter

> 
> Thanks in advance.
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
> 
>