[OPSEC] Routing Crypto drafts ..
"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> Wed, 16 December 2009 02:09 UTC
Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DAAB3A68B0 for <opsec@core3.amsl.com>; Tue, 15 Dec 2009 18:09:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level:
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.375, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zriNh0i4Hy7r for <opsec@core3.amsl.com>; Tue, 15 Dec 2009 18:09:03 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id AF3923A68A0 for <opsec@ietf.org>; Tue, 15 Dec 2009 18:09:03 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id nBG28k6t010506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <opsec@ietf.org>; Tue, 15 Dec 2009 20:08:48 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/ICT) with ESMTP id nBG28j6X018318 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <opsec@ietf.org>; Wed, 16 Dec 2009 07:38:45 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.56]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 16 Dec 2009 07:38:45 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: opsec wg mailing list <opsec@ietf.org>
Date: Wed, 16 Dec 2009 07:38:41 +0530
Thread-Topic: Routing Crypto drafts ..
Thread-Index: Acp99LAoivFkr+ytTe++5mJSSBojZg==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350AB3287303@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.250.11.33
Subject: [OPSEC] Routing Crypto drafts ..
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Dec 2009 02:09:04 -0000
Hi Joel, What are the next steps for draft-ietf-opsec-routing-protocols-crypto-issues-02.txt - "Issues with existing Cryptographic Protection Methods for Routing Protocols"? There is considerable interest in this work. Do you think we are in a position where we can move this forward? And what about for "Cryptographic Authentication Algorithm Implementation Best Practices for Routing Protocols" (http://tools.ietf.org/html/draft-bhatia-manral-igp-crypto-requirements-04)? The language and the tone in the draft has been changed based on the feedback that we received from the WG. Cheers, Manav -- Manav Bhatia, IP Division, Alcatel-Lucent, Bangalore - India
- [OPSEC] Routing Crypto drafts .. Bhatia, Manav (Manav)
- Re: [OPSEC] Routing Crypto drafts .. Glen Kent
- Re: [OPSEC] Routing Crypto drafts .. Bhatia, Manav (Manav)