Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended

"Phil Cowburn" <> Thu, 16 November 2006 15:42 UTC

Received: from [] ( by with esmtp (Exim 4.43) id 1GkjNV-0000PT-1T; Thu, 16 Nov 2006 10:42:13 -0500
Received: from [] ( by with esmtp (Exim 4.43) id 1GkjNT-0000PJ-Ij for; Thu, 16 Nov 2006 10:42:11 -0500
Received: from ([]) by with esmtp (Exim 4.43) id 1GkjNS-00050c-7V for; Thu, 16 Nov 2006 10:42:11 -0500
Received: by with SMTP id 72so426007ugd for <>; Thu, 16 Nov 2006 07:42:09 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fq0QzmtVYlXGucF/McQdWX1mfVucX4kK7QbckpFvh2o5mBRO2G6wfDXFWg24PMiLDg/m4+E9mrgueMrotP1TtM8GLlstLKdwZjIxjPUKCNr0Wc5zhUP719imIuuig3U6QSb498A69BUUP268DZVPeCvyoYSc/4ZsG4mtvJuqBYI=
Received: by with SMTP id s17mr689548hue.1163691728860; Thu, 16 Nov 2006 07:42:08 -0800 (PST)
Received: by with HTTP; Thu, 16 Nov 2006 07:42:08 -0800 (PST)
Message-ID: <>
Date: Thu, 16 Nov 2006 21:12:08 +0530
From: "Phil Cowburn" <>
To: "Acee Lindem" <>
Subject: Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: OSPF List <>
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>


> Presentation Michael Barnes : Crypto alg reqmts for OSPFv2
>    Some discussion on list already
>    Crypto - only md5 to date, can be attacked, some want stronger algs
>         perhaps should specify these
>    How - 2328 can add other algs w/o too much problem

Yes it does, but debugging would be a nightmare! :-)

Let me not trigger a discussion again, i am ok with using the existing
type code!

>    This draft - new algorithms should be used and won't change
>    proto fields, there is key-id field which can has an associated
>    algorithm as a property.
>    Adding crypto terms- SA's - will carry key/alg choice, fairly
>    straight forward approach - should not cause backwards compatibility
>    because no change to OSPF proto fields - it's mis-config if one peers
>    has a different algorithm.
>    Acee: IPSec for v3, once done, lacks replay and key dist issues
>    on lan - w/v2 these problems are solved mainly (seq#>=, not
>    monotonic incr). Vishwas present requirements in Paris in both
>    OSPF and RPSEC WGs.
>    Sandy Murphy, Sparta : what is manditory to implement?
>    Michael - Separate doc will discuss what is req'd (ala ISIS approach)
> Presentation: Manav Bhatia - Crypto Requirements Document
>    NULL, MS5, sha1, cryptographic - refs in this doc
>    more algorithms keep coming eg des was once must, now is should ot
>    What doc must, should, - running doc as algorithms come and go
>    uses 2119 terms should+ = should may become must
>    See slides and draft for specific requirements.
>    Acee: "should not" wording is problematic for NULL and other
>    existing requirements.
>    Russ white: shold may become a must vs. should+ (better to say
>         what is meant)

I dont see any show stopper comments, so what is the status of the
auth drafts? There was a discussion on these drafts some time back and
the consensus was that the drafts would not be changed and we would
reuse the existing type code for additional authentication types.

If there are no further comments then should these be taken up as a new items?

> Presentation Lou Berger: berger-ospf-rfc2370bis followon to ietf66 - opaque
>    LSA across areas - problem w/validation - so instead rev'd 2370


>    Acee wanted MAY or Should added
>    Acee: when we add new info to TE LSAs - scalability issues -
>          give priority to base ospf LSA over the opaque LSAs.
>    Lou: We should take to list whether MAY or SHOULD should be in
>         the final text.

SHOULD sounds too strong to me. This is an implementation specific
issue and not all implementations may be able to prioritize OSPF pkts.
In view of this, a MAY should be sufficient as a recommendation from
the WG. Lets not word it any stronger than this.

>    Acee: Will validate on list that this is to become a WG document.

I am in favor of this.


OSPF mailing list