Document Action: 'Operational Security Current Practices' to Informational RFC

The IESG <iesg-secretary@ietf.org> Tue, 24 October 2006 14:21 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcNAA-0001c2-RG; Tue, 24 Oct 2006 10:21:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcNA8-0001Ys-EW for ietf-announce@ietf.org; Tue, 24 Oct 2006 10:21:52 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcN9v-0007OK-Ro for ietf-announce@ietf.org; Tue, 24 Oct 2006 10:21:52 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id C8EE326E15; Tue, 24 Oct 2006 14:21:39 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GcN9v-0002Um-N9; Tue, 24 Oct 2006 10:21:39 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1GcN9v-0002Um-N9@stiedprstage1.ietf.org>
Date: Tue, 24 Oct 2006 10:21:39 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: Internet Architecture Board <iab@iab.org>, opsec chair <opsec-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Document Action: 'Operational Security Current Practices' to Informational RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

The IESG has approved the following document:

- 'Operational Security Current Practices '
   <draft-ietf-opsec-current-practices-07.txt> as an Informational RFC

This document is the product of the Operational Security Capabilities 
for IP Network Infrastructure Working Group. 

The IESG contact persons are David Kessens and Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsec-current-practices-07.txt

Technical Summary
 
 This document is a survey of the current practices used in today's
 large ISP operational networks to secure layer 2 and layer 3
 infrastructure devices.  The information listed here is the result of
 information gathered from people directly responsible for defining
 and implementing secure infrastructures in Internet Service Provider
 environments.

Working Group Summary
 
 This document is a product of the opsec working group.
 
Protocol Quality
 
 David Kessens reviewed this document for the IESG. In addition to 
 careful review by the opsec working group, this document also received 
 considerable review from the operator community.

Note to RFC Editor

 Change the title:

 OLD:

  Operational Security Current Practices

 NEW:

  Current Operational Security Practices in Internet Service Provider
  Environments

 In section 1.2., paragraph 5:

   ...
   resent at later time).  A message can also be inserted with any of
   the fields in the message being OspoofedO, such as IP
   addresses, port
   ...

  s/OspoofedO,/spoofed,/

 In section 2.2.3., paragraph 4:
   
   ...    
   internal system.  Also, using SSH for device access ensures that
   noone can spoof the traffic during the SSH session.
   ...

  s/noone/no one/

 In section '2.4.2.  Security Practices':

   ...
   Some large ISPs require that routes be registered in an Internet
   Routing Registry [IRR] which can then be part of the RADB - a public
   registry of routing information for networks in the Internet that can
   be used to generate filter lists.
   ...

  s/[IRR]/(IRR)/

   ...
   registry of routing information for networks in the Internet
   that can be used to generate filter lists.  Some ISPs, especially in
   europe,
   ...

  s/europe,/Europe,/

 In section 5., paragraph 1:
  
   ...  
   Jones, who has been instrumental in providing guidance and
   direction for this document and the insighful comments from Ross
   Callon, Ron
   ...

  s/insighful/insightful/

 In section '6.1.  Normative References':

  Remove reference to 'RFC2119'


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce