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

"Bhatia, Manav \(Manav\)" <manav@lucent.com> Fri, 17 November 2006 09:02 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gkzc5-0007bA-DP; Fri, 17 Nov 2006 04:02:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gkzc3-0007ae-QS for ospf@ietf.org; Fri, 17 Nov 2006 04:02:19 -0500
Received: from ihemail1.lucent.com ([135.245.0.33]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gkzbz-0000lp-Tt for ospf@ietf.org; Fri, 17 Nov 2006 04:02:17 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id kAH92Etk027338; Fri, 17 Nov 2006 03:02:14 -0600 (CST)
Received: from inexp01.in.lucent.com ([135.254.223.65]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 17 Nov 2006 03:02:13 -0600
Received: from INEXC1U01.in.lucent.com ([135.254.223.25]) by inexp01.in.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 17 Nov 2006 14:31:25 +0530
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Fri, 17 Nov 2006 14:31:24 +0530
Message-ID: <6D26D1FE43A66F439F8109CDD42419651210D1@INEXC1U01.in.lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
Thread-Index: AccJlzpElgH+Mi0rTSuqxTpmNFJkpAAjNS9w
From: "Bhatia, Manav \(Manav\)" <manav@lucent.com>
To: "Phil Cowburn" <phil.cowburn@gmail.com>, "Acee Lindem" <acee@cisco.com>
X-OriginalArrivalTime: 17 Nov 2006 09:01:25.0467 (UTC) FILETIME=[F5F222B0:01C70A26]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: OSPF List <ospf@ietf.org>
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org

Hi Phil,

> >    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!

We had posted the revised text based on the comments that we had
received both on the list and offline and there was quite a discussion
that followed!

http://www1.ietf.org/mail-archive/web/ospf/current/mail6.html

The consensus that we all had reached on was that before this draft one
could only have a key mismatch. From this draft onwards we will have a
key/algorithm mismatch.

[clipped]

> 
> >
> 
> 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?

Yes we would like to progress these drafts as a WG items. 

Cheers,
Manav

_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf