From: "BRUNGARD, DEBORAH A" <db3546@att.com>
To: "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: Update on draft-ietf-mpls-tp-oam-id-mib
Thread-Index: AdDhywgzTtgdRsqDTPiFgEWoPHWCpQ==
Date: Fri, 28 Aug 2015 19:52:13 +0000
Message-ID: <F64C10EAA68C8044B33656FA214632C852703BCF@MISOUT7MSGUSRDE.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
 boundary="_000_F64C10EAA68C8044B33656FA214632C852703BCFMISOUT7MSGUSRDE_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/5ucLDeAae5x6nFPjVPbU80j4Hok>
Cc: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>,
 "draft-ietf-mpls-tp-oam-id-mib@ietf.org"
 <draft-ietf-mpls-tp-oam-id-mib@ietf.org>
Subject: [mpls] Update on draft-ietf-mpls-tp-oam-id-mib
Precedence: list

--_000_F64C10EAA68C8044B33656FA214632C852703BCFMISOUT7MSGUSRDE_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

While this document was being last called, a mibs document in trill was bei=
ng reviewed by the IESG. The Security ADs commented that they needed to upd=
ate the security section. As our MPLS document is more or less a cut and pa=
ste of the trill security section, I've asked the authors to do a review an=
d update our document so as not to repeat the discussion. As it's only a co=
uple of sentences, I've place the document on next week's telechat as the a=
uthors promised a new version by Monday next week.

A heads-up for all of you, there is much more interest to ensure IETF's wor=
k on security is solid. Security sections which simply say "there is no new=
 security concerns" will not pass. Authors need to explain why there are no=
 new security concerns.

Thanks,
Deborah



--_000_F64C10EAA68C8044B33656FA214632C852703BCFMISOUT7MSGUSRDE_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi,</div>
<div>&nbsp;</div>
<div>While this document was being last called, a mibs document in trill wa=
s being reviewed by the IESG. The Security ADs commented that they needed t=
o update the security section. As our MPLS document is more or less a cut a=
nd paste of the trill security section,
I&#8217;ve asked the authors to do a review and update our document so as n=
ot to repeat the discussion. As it&#8217;s only a couple of sentences, I&#8=
217;ve place the document on next week&#8217;s telechat as the authors prom=
ised a new version by Monday next week.</div>
<div>&nbsp;</div>
<div>A heads-up for all of you, there is much more interest to ensure IETF&=
#8217;s work on security is solid. Security sections which simply say &#822=
0;there is no new security concerns&#8221; will not pass. Authors need to e=
xplain why there are no new security concerns.</div>
<div>&nbsp;</div>
<div>Thanks,</div>
<div>Deborah</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_F64C10EAA68C8044B33656FA214632C852703BCFMISOUT7MSGUSRDE_--