home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
In-Reply-To: <8991B2517BA4384784708AFC7BA906AC02F2C377@CORMAIL1.ci.raleigh.nc.us> Cc: <nanog@merit.edu> From: Peter Schoenmaker <pds@lugs.com> Date: Thu, 26 Apr 2007 18:20:25 -0400 To: "Hess, DJ" <DJ.Hess@ci.raleigh.nc.us> Errors-To: owner-nanog@merit.edu There is a carriage return in the URL, try http://www.ietf.org/internet-drafts/draft-ietf-opsec-infrastructure-=20 security-01.txt peter On Apr 26, 2007, at 5:42 PM, Hess, DJ wrote: > The draft was not there? > > DJ Hess, CISSP, Information Security Administrator > > City of Raleigh Information Technology (CORIT) > Office Phone: (919) 890-3192 > > Cell: (919) 278-6132 > > dj.hess@ci.raleigh.nc.us > > > > > -----Original Message----- > From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On =20 > Behalf Of > Peter Schoenmaker > Sent: Thursday, April 26, 2007 2:58 PM > To: nanog@merit.edu > Subject: infrastructure security > > > Hi, > > My coauthors and I are looking for more input on a draft that we > wrote on infrastructure security. The draft is intended to document > methods that providers can refer to and implement to harden their > network. The draft is broken up into several different areas, Edge > Infrastructure ACLs, Edge rewriting/remarking, Device/element > protection, and Infrastructure hiding. We are very interested in > getting more feedback from network operators. > > The draft can be found at: > http://www.ietf.org/internet-drafts/draft-ietf-opsec-infrastructure- > security-01.txt > > Thanks > > Peter Schoenmaker > > > > > > > =93E-mail correspondence to and from this address may be subject to =20= > the North Carolina Public Records Law and may be disclosed to =20 > third parties by an authorized City or Law Enforcement official.=94
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |