IETF Logo Mail Archive

Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-prefix-link-attr-00.txt

"A. Przygienda" <prz@zeta2.ch> Wed, 03 September 2014 15:41 UTC

Return-Path: <prz@zeta2.ch>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78ABB1A03ED for <ospf@ietfa.amsl.com>; Wed, 3 Sep 2014 08:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level:
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_DYNAMIC=0.982] autolearn=no
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 OOyZjo5FA5wG for <ospf@ietfa.amsl.com>; Wed, 3 Sep 2014 08:41:25 -0700 (PDT)
Received: from zeta2.ch (zux172-086.adsl.green.ch [80.254.172.86]) by ietfa.amsl.com (Postfix) with ESMTP id E914C1A0466 for <ospf@ietf.org>; Wed, 3 Sep 2014 08:41:16 -0700 (PDT)
Received: from prz-workstation.zeta2.ch (108-228-12-76.lightspeed.sntcca.sbcglobal.net [108.228.12.76]) (Authenticated sender: prz) by zeta2.ch (Postfix) with ESMTPSA id F289812953; Wed, 3 Sep 2014 17:41:04 +0200 (CEST)
Message-ID: <5407368B.2050304@zeta2.ch>
Date: Wed, 03 Sep 2014 08:40:59 -0700
From: "A. Przygienda" <prz@zeta2.ch>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7
MIME-Version: 1.0
To: Hannes Gredler <hannes@juniper.net>
References: <20140812171918.31632.25544.idtracker@ietfa.amsl.com> <D010DA98.1B41%acee@cisco.com> <5404E67E.6050407@zeta2.ch> <20140902082342.GB39341@juniper.net>
In-Reply-To: <20140902082342.GB39341@juniper.net>
X-TagToolbar-Keys: D20140903084059313
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: F289812953.AA1F3
X-MailScanner: Found to be clean
X-MailScanner-From: prz@zeta2.ch
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/ZFNjJPGi-Rc_V-ZEDFAamHkcVKs
Cc: ospf@ietf.org
Subject: Re: [OSPF] FW: New Version Notification for draft-ietf-ospf-prefix-link-attr-00.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 15:41:28 -0000

On 09/02/2014 01:23 AM, Hannes Gredler wrote:
> hi tony,

Fuehrt' Di' Hannes ;-)
>
> requiring send-side ordering is certainly intended well,
> but that in itself does not guarantee ordered delivery
> at the receiving end :-/.

I think I pointed that out already below. full ack.
>
> IOW in case you have an application that needs both
> the 1) prefix-LSA and the 2) extended-prefix-LSA you need
> to have the logic that checks presence of 1)
> at the receiving end anyway.
>
> rather than doing things on the send-side let me suggest
> to check if you have got your act together during
> route-computation time. (this is a bit akin to
> IS-IS fragment zero handling - ala - if frag zero
> is not present then all non-zero
> frag content has to be disregarded).

That is required anyway, the ordering was meant as suggestion for
implementors but given what Peter/Acee write (extented can be sent
without the normal LSA, this makes no sense apparently).

--- tony

v2.23.0 | Report a Bug | By Email