IETF Logo Mail Archive

Re: [OPSEC] noted: draft-dugal-opsec-protect-control-plane-00

Rodney Dunn <rodunn@cisco.com> Mon, 11 January 2010 18:55 UTC

Return-Path: <rodunn@cisco.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 9A1083A6836 for <opsec@core3.amsl.com>; Mon, 11 Jan 2010 10:55:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 g9aNI083t4vc for <opsec@core3.amsl.com>; Mon, 11 Jan 2010 10:55:22 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by core3.amsl.com (Postfix) with ESMTP id AC66C3A63C9 for <opsec@ietf.org>; Mon, 11 Jan 2010 10:55:22 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o0BItIOO022870; Mon, 11 Jan 2010 13:55:18 -0500 (EST)
Received: from dhcp-64-102-157-217.cisco.com (dhcp-64-102-157-217.cisco.com [64.102.157.217]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id o0BItHEv007421; Mon, 11 Jan 2010 13:55:17 -0500 (EST)
Message-ID: <4B4B7415.1080204@cisco.com>
Date: Mon, 11 Jan 2010 13:55:17 -0500
From: Rodney Dunn <rodunn@cisco.com>
Organization: Cisco Systems Inc.
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0
MIME-Version: 1.0
To: Glen Kent <glen.kent@gmail.com>
References: <4B42CE9B.8070505@bogus.com> <92c950311001061023i39dd830eqd4fe2568f7106400@mail.gmail.com>
In-Reply-To: <92c950311001061023i39dd830eqd4fe2568f7106400@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: cpignata@cisco.com, "opsec@ietf.org" <opsec@ietf.org>
Subject: Re: [OPSEC] noted: draft-dugal-opsec-protect-control-plane-00
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: rodunn@cisco.com
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: Mon, 11 Jan 2010 18:55:23 -0000

Glen,

Thanks for reading through it. The consensus of the authors was that we 
would aim for an Informational draft
(http://tools.ietf.org/html/rfc1796) and the idea is that it helps 
support the Goals and Scope of OPSEC:

https://www.ietf.org/dyn/wg/charter/opsec-charter.html

Hopefully it raises the awareness of network operators to do more to 
protect the control plane of the network infrastructure devices.

Similar in concept to how RTBHF was highlighted via RFC 5635 to help in 
the data plane:

https://www.ietf.org/rfc/rfc5635.txt

Rodney



On 1/6/10 1:23 PM, Glen Kent wrote:
> I read the draft and i am not sure i understand the motivation of why
> this needs to get published as an IETF standard.
>
> Am i missing something here?
>
> Glen
>
> On Tue, Jan 5, 2010 at 11:01 AM, Joel Jaeggli<joelja@bogus.com>  wrote:
>> I notes with interest today the initial publication of:
>>
>> http://tools.ietf.org/html/draft-dugal-opsec-protect-control-plane-00
>>
>> for which I am certain review and feedback would be greatly appreciated.
>>
>> thanks
>>
>> joel
>> _______________________________________________
>> OPSEC mailing list
>> OPSEC@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsec
>>

v2.23.0 | Report a Bug | By Email