Re: [OSPF] Fw: New Version Notification for draft-manjuldtv-ospf-sequence-number-00.txt

"Acee Lindem (acee)" <acee@cisco.com> Wed, 11 May 2016 15:19 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747CA12DB40 for <ospf@ietfa.amsl.com>; Wed, 11 May 2016 08:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 tyVhzuMsr5rL for <ospf@ietfa.amsl.com>; Wed, 11 May 2016 08:19:31 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA71812DB47 for <ospf@ietf.org>; Wed, 11 May 2016 08:19:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3828; q=dns/txt; s=iport; t=1462979971; x=1464189571; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=7SncMqokwZeonYtQ+Y/2RsfEdnTxsHnNqD9/Y76gIEI=; b=lQFPGrePKp3LqFB4iNyLIug1KWbLiA7v2blGBsCtce7bQAkhb3VpDpud bT9gur+NDL9Pi2Vt87caGcl43pDgL3f2jNtMMFzZVpY2t+r2GeFBQ/nlw FGXET7y5CA0MtPj2aI67i1Uf1Y/NDkjR61AOlSAgJkfQtDMFBVo7D/pJZ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D5AQD9TDNX/4MNJK1dgzhVfQa5KQENgXYXDYVsHoEcOBQBAQEBAQEBZSeEQgEBAQQBAQEgEToJAhIBCBEEAQEDAiYCBCULFQgKBAENBYgvDqgckHABAQEBAQEBAQEBAQEBAQEBAQEBAQEVfIlwhD+DAIJZBY1fikgBhX2IIIFpToQBgyqFN49AAR4BAUKCNoE1bogLfwEBAQ
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="271581744"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2016 15:19:30 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u4BFJUeo017709 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 15:19:30 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 11:19:29 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1104.009; Wed, 11 May 2016 11:19:29 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Manjul Khandelwal <manjul@nivettisystems.com>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [OSPF] Fw: New Version Notification for draft-manjuldtv-ospf-sequence-number-00.txt
Thread-Index: AQHRq5iDI45ZmPCOekqfeZl/Lp+NDg==
Date: Wed, 11 May 2016 15:19:29 +0000
Message-ID: <D358C4E4.607A9%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <49693EB87A4DBE47857FF338C6CE1413@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/ZbyxKevp_1u3Hk97mv_jzJxIeSw>
Cc: Ramakrishna DTV <ramakrishnadtv@nivettisystems.com>
Subject: Re: [OSPF] Fw: New Version Notification for draft-manjuldtv-ospf-sequence-number-00.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 11 May 2016 15:19:38 -0000

Hi Manjul, 

Would it be possible to succinctly describe these “certain security
attacks” in the draft rather than expecting everyone to read the
referenced paper? 

Thanks,
Acee 

On 5/11/16, 10:19 AM, "OSPF on behalf of Manjul Khandelwal"
<ospf-bounces@ietf.org on behalf of manjul@nivettisystems.com> wrote:

>Hi,
>
>We have recently submitted a draft which deals with OSPF LS sequence
>number
>generation mechanism.
>
>Abstract of the draft:
>   The mechanism for LS sequence number generation as specified in RFC
>   2328 and RFC 5340 is completely predictable.  This makes it prone to
>   certain security attacks which exploit the predictable nature of LS
>   sequence numbers.  This draft updates the RFC 2328 to make LS
>   sequence number generation an implementation choice rather than a
>   fixed increment by 1 for successive LSAs.
>
>https://datatracker.ietf.org/doc/draft-manjuldtv-ospf-sequence-number/
>
>We solicit feedback/comments on the draft and request for adoption by the
>OSPF working group.
>
>Regards,
>Manjul Khandelwal
>DTV Ramakrishna Rao
>________________________________________
>From: internet-drafts@ietf.org <internet-drafts@ietf.org>
>Sent: Monday, May 9, 2016 7:22 PM
>To: Manjul Khandelwal; Ramakrishna DTV
>Subject: New Version Notification for
>draft-manjuldtv-ospf-sequence-number-00.txt
>
>A new version of I-D, draft-manjuldtv-ospf-sequence-number-00.txt
>has been successfully submitted by Manjul Khandelwal and posted to the
>IETF repository.
>
>Name:           draft-manjuldtv-ospf-sequence-number
>Revision:       00
>Title:          OSPF LSA sequence number generation
>Document date:  2016-05-09
>Group:          Individual Submission
>Pages:          10
>URL:            
>https://www.ietf.org/internet-drafts/draft-manjuldtv-ospf-sequence-number-
>00.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-manjuldtv-ospf-sequence-number/
>Htmlized:       
>https://tools.ietf.org/html/draft-manjuldtv-ospf-sequence-number-00
>
>
>Abstract:
>   The mechanism for LS sequence number generation as specified in RFC
>   2328 and RFC 5340 is completely predictable.  This makes it prone to
>   certain security attacks which exploit the predictable nature of LS
>   sequence numbers.  This draft updates the RFC 2328 to make LS
>   sequence number generation an implementation choice rather than a
>   fixed increment by 1 for successive LSAs.
>
>
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf