
From dromasca@avaya.com  Wed Feb  3 01:26:54 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 866D63A6AE4 for <ops-area@core3.amsl.com>; Wed,  3 Feb 2010 01:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 f2OqhsRnjUUb for <ops-area@core3.amsl.com>; Wed,  3 Feb 2010 01:26:53 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 5B4D23A6ADE for <ops-area@ietf.org>; Wed,  3 Feb 2010 01:26:53 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,397,1262581200"; d="scan'208";a="175061064"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Feb 2010 04:27:32 -0500
X-IronPort-AV: E=Sophos;i="4.49,397,1262581200"; d="scan'208";a="442013385"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 03 Feb 2010 04:27:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 3 Feb 2010 10:27:30 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401ED2C75@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Agenda Items for the OPSAREA Meeting in Anaheim
Thread-Index: AcqksxuCdzQYqyOPSKubA1BBWoVjJw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] Agenda Items for the OPSAREA Meeting in Anaheim
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2010 09:26:54 -0000

We have requested a two hours slot for the OPSAREA meeting in Anaheim.
Please send your proposals for items that you would like to be discussed
in the meeting.=20

Thanks and Regards,

Ron and Dan

From dromasca@avaya.com  Sun Feb  7 00:41:27 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99EA43A6840; Sun,  7 Feb 2010 00:41:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  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 pjP1QFcQhAgJ; Sun,  7 Feb 2010 00:41:26 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 8FC753A67A2; Sun,  7 Feb 2010 00:41:26 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,421,1262581200"; d="scan'208";a="204050855"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Feb 2010 03:42:23 -0500
X-IronPort-AV: E=Sophos;i="4.49,421,1262581200"; d="scan'208";a="428931213"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Feb 2010 03:41:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 7 Feb 2010 09:41:29 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Outcomes wiki
Thread-Index: Acqn0VfhCrQbwmaJQPa+cUbUaWHfxQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Cc: ops-chairs@ietf.org
Subject: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 08:41:27 -0000

For folks who are not aware, a set of wikipages on the outcomes of the
IETF work, successes and failures was started at
http://trac.tools.ietf.org/misc/outcomes/ with per areas views that
include OPS -
http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations=20

The wiki is out there to be discussed and improved. Maybe it's a good
item to discuss shortly also in the OPSAREA meeting at IETF77.=20

Dan

From bertietf@bwijnen.net  Sun Feb  7 03:26:41 2010
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F11D23A71AC for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 03:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.354
X-Spam-Level: *
X-Spam-Status: No, score=1.354 tagged_above=-999 required=5 tests=[AWL=-0.063,  BAYES_20=-0.74, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 Rjhy7O9-o35I for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 03:26:41 -0800 (PST)
Received: from relay.versatel.net (relay56.tele2.vuurwerk.nl [62.250.3.56]) by core3.amsl.com (Postfix) with ESMTP id E8A3F3A71A3 for <ops-area@ietf.org>; Sun,  7 Feb 2010 03:26:39 -0800 (PST)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1Ne5Id-0006XL-Fp for ops-area@ietf.org; Sun, 07 Feb 2010 12:27:35 +0100
Message-ID: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "ops-area \(IETF\)" <ops-area@ietf.org>
Date: Sun, 7 Feb 2010 12:26:58 +0100
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0CA5_01CAA7F0.D76328B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
Subject: [OPS-AREA] Fw: IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 11:26:42 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0CA5_01CAA7F0.D76328B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Wow... sofar that does not look so good for the OPS area.
Only a couple of protocols that we did in the late 80s (so even before I
participated... or maybe just because of that :-() seem to have good
adoption.

Bert
  ----- Original Message -----=20
  From: Romascanu, Dan (Dan)=20
  To: ops-area@ietf.org=20
  Cc: ops-chairs@ietf.org=20
  Sent: Sunday, February 07, 2010 9:41 AM
  Subject: IETF Outcomes wiki


  For folks who are not aware, a set of wikipages on the outcomes of the
  IETF work, successes and failures was started at
  http://trac.tools.ietf.org/misc/outcomes/ with per areas views that
  include OPS -
  http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations=20

  The wiki is out there to be discussed and improved. Maybe it's a good
  item to discuss shortly also in the OPSAREA meeting at IETF77.=20

  Dan
------=_NextPart_000_0CA5_01CAA7F0.D76328B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18882">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Wow... sofar that does not look so good for the OPS=20
area.</FONT></DIV>
<DIV><FONT size=3D2>Only a couple of protocols that we did in the late =
80s (so=20
even before I</FONT></DIV>
<DIV><FONT size=3D2>participated... or maybe just because of that :-() =
seem to=20
have good</FONT></DIV>
<DIV><FONT size=3D2>adoption.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Bert</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Ddromasca@avaya.com =
href=3D"mailto:dromasca@avaya.com">Romascanu, Dan=20
  (Dan)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dops-area@ietf.org=20
  href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dops-chairs@ietf.org=20
  href=3D"mailto:ops-chairs@ietf.org">ops-chairs@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, February 07, 2010 =
9:41=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> IETF Outcomes =
wiki</DIV>
  <DIV><BR></DIV>For folks who are not aware, a set of wikipages on the =
outcomes=20
  of the<BR>IETF work, successes and failures was started at<BR><A=20
  =
href=3D"http://trac.tools.ietf.org/misc/outcomes/">http://trac.tools.ietf=
.org/misc/outcomes/</A>=20
  with per areas views that<BR>include OPS -<BR><A=20
  =
href=3D"http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations">htt=
p://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations</A>=20
  <BR><BR>The wiki is out there to be discussed and improved. Maybe it's =
a=20
  good<BR>item to discuss shortly also in the OPSAREA meeting at IETF77. =

  <BR><BR>Dan</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0CA5_01CAA7F0.D76328B0--


From bwijnen@bwijnen.net  Sun Feb  7 02:56:02 2010
Return-Path: <bwijnen@bwijnen.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B01243A7040; Sun,  7 Feb 2010 02:56:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.972
X-Spam-Level: *
X-Spam-Status: No, score=1.972 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 bOWnzJYn1U+x; Sun,  7 Feb 2010 02:56:01 -0800 (PST)
Received: from relay.versatel.net (relay56.tele2.vuurwerk.nl [62.250.3.56]) by core3.amsl.com (Postfix) with ESMTP id 674133A7058; Sun,  7 Feb 2010 02:56:00 -0800 (PST)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bwijnen@bwijnen.net>) id 1Ne4oz-0002ED-Bk; Sun, 07 Feb 2010 11:56:57 +0100
Message-ID: <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop>
From: "Bert Wijnen" <bwijnen@bwijnen.net>
To: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>, <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>
Date: Sun, 7 Feb 2010 11:55:51 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C43_01CAA7EC.7EBE4680"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
X-Mailman-Approved-At: Sun, 07 Feb 2010 05:42:05 -0800
Cc: ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 10:56:02 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0C43_01CAA7EC.7EBE4680
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Wow... sofar that does not look so good for the OPS area.
Only a couple of protocols that we did in the late 80s (so even before I
participated... or maybe just because of that :-() seem to have good
adoption.

Bert
  ----- Original Message -----=20
  From: Romascanu, Dan (Dan)=20
  To: ops-area@ietf.org=20
  Cc: ops-chairs@ietf.org=20
  Sent: Sunday, February 07, 2010 9:41 AM
  Subject: IETF Outcomes wiki


  For folks who are not aware, a set of wikipages on the outcomes of the
  IETF work, successes and failures was started at
  http://trac.tools.ietf.org/misc/outcomes/ with per areas views that
  include OPS -
  http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations=20

  The wiki is out there to be discussed and improved. Maybe it's a good
  item to discuss shortly also in the OPSAREA meeting at IETF77.=20

  Dan



-------------------------------------------------------------------------=
-----



  Geen virus gevonden in het binnenkomende-bericht.
  Gecontroleerd door AVG - www.avg.com=20
  Versie: 9.0.733 / Virusdatabase: 271.1.1/2672 - datum van uitgifte: =
02/06/10 20:35:00

------=_NextPart_000_0C43_01CAA7EC.7EBE4680
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18882">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Wow... sofar that does not look so good for the OPS=20
area.</FONT></DIV>
<DIV><FONT size=3D2>Only a couple of protocols that we did in the late =
80s (so=20
even before I</FONT></DIV>
<DIV><FONT size=3D2>participated... or maybe just because of that :-() =
seem to=20
have good</FONT></DIV>
<DIV><FONT size=3D2>adoption.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Bert</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Ddromasca@avaya.com =
href=3D"mailto:dromasca@avaya.com">Romascanu, Dan=20
  (Dan)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dops-area@ietf.org=20
  href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dops-chairs@ietf.org=20
  href=3D"mailto:ops-chairs@ietf.org">ops-chairs@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, February 07, 2010 =
9:41=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> IETF Outcomes =
wiki</DIV>
  <DIV><BR></DIV>For folks who are not aware, a set of wikipages on the =
outcomes=20
  of the<BR>IETF work, successes and failures was started at<BR><A=20
  =
href=3D"http://trac.tools.ietf.org/misc/outcomes/">http://trac.tools.ietf=
.org/misc/outcomes/</A>=20
  with per areas views that<BR>include OPS -<BR><A=20
  =
href=3D"http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations">htt=
p://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations</A>=20
  <BR><BR>The wiki is out there to be discussed and improved. Maybe it's =
a=20
  good<BR>item to discuss shortly also in the OPSAREA meeting at IETF77. =

  <BR><BR>Dan<BR>
  <P>
  <HR>

  <P></P><BR>Geen virus gevonden in het =
binnenkomende-bericht.<BR>Gecontroleerd=20
  door AVG - <A href=3D"http://www.avg.com">www.avg.com</A> <BR>Versie: =
9.0.733 /=20
  Virusdatabase: 271.1.1/2672 - datum van uitgifte: 02/06/10=20
20:35:00<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0C43_01CAA7EC.7EBE4680--


From dromasca@avaya.com  Sun Feb  7 06:45:22 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2A6628C0DE; Sun,  7 Feb 2010 06:45:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 kO0mJ0o3uZD5; Sun,  7 Feb 2010 06:45:20 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 2C0153A7209; Sun,  7 Feb 2010 06:45:19 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,422,1262581200";  d="scan'208,217";a="204063778"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Feb 2010 09:46:17 -0500
X-IronPort-AV: E=Sophos;i="4.49,422,1262581200";  d="scan'208,217";a="428969019"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Feb 2010 09:45:46 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAA804.2F1E6E41"
Date: Sun, 7 Feb 2010 15:45:25 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0D9B3@307622ANEX5.global.avaya.com>
In-Reply-To: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] Fw: IETF Outcomes wiki
Thread-Index: Acqn6JYfeUEfBU1vRu60XY9Bg8mOXQAG24uQ
References: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>, "ops-area (IETF)" <ops-area@ietf.org>
Cc: ops-chairs@ietf.org
Subject: Re: [OPS-AREA] Fw: IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 14:45:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CAA804.2F1E6E41
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It's a wiki - open for corrections and additions. Do you feel that they
are needed?=20
=20
Dan
=20


________________________________

	From: ops-area-bounces@ietf.org
[mailto:ops-area-bounces@ietf.org] On Behalf Of Bert Wijnen (IETF)
	Sent: Sunday, February 07, 2010 1:27 PM
	To: ops-area (IETF)
	Subject: [OPS-AREA] Fw: IETF Outcomes wiki
=09
=09
	Wow... sofar that does not look so good for the OPS area.
	Only a couple of protocols that we did in the late 80s (so even
before I
	participated... or maybe just because of that :-() seem to have
good
	adoption.
	=20
	Bert

		----- Original Message -----=20
		From: Romascanu, Dan (Dan) <mailto:dromasca@avaya.com> =20
		To: ops-area@ietf.org=20
		Cc: ops-chairs@ietf.org=20
		Sent: Sunday, February 07, 2010 9:41 AM
		Subject: IETF Outcomes wiki

		For folks who are not aware, a set of wikipages on the
outcomes of the
		IETF work, successes and failures was started at
		http://trac.tools.ietf.org/misc/outcomes/ with per areas
views that
		include OPS -
=09
http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations=20
	=09
		The wiki is out there to be discussed and improved.
Maybe it's a good
		item to discuss shortly also in the OPSAREA meeting at
IETF77.=20
	=09
		Dan


------_=_NextPart_001_01CAA804.2F1E6E41
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3660" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D921134414-07022010>It's a=20
wiki - open for corrections and additions. Do&nbsp;you feel that they =
are=20
needed? </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D921134414-07022010></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D921134414-07022010>Dan</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D921134414-07022010></SPAN></FONT>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ops-area-bounces@ietf.org=20
  [mailto:ops-area-bounces@ietf.org] <B>On Behalf Of </B>Bert Wijnen=20
  (IETF)<BR><B>Sent:</B> Sunday, February 07, 2010 1:27 PM<BR><B>To:</B> =

  ops-area (IETF)<BR><B>Subject:</B> [OPS-AREA] Fw: IETF Outcomes=20
  wiki<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT size=3D2>Wow... sofar that does not look so good for the =
OPS=20
  area.</FONT></DIV>
  <DIV><FONT size=3D2>Only a couple of protocols that we did in the late =
80s (so=20
  even before I</FONT></DIV>
  <DIV><FONT size=3D2>participated... or maybe just because of that :-() =
seem to=20
  have good</FONT></DIV>
  <DIV><FONT size=3D2>adoption.</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>Bert</FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
    <A title=3Ddromasca@avaya.com =
href=3D"mailto:dromasca@avaya.com">Romascanu, Dan=20
    (Dan)</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dops-area@ietf.org=20
    href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dops-chairs@ietf.org=20
    href=3D"mailto:ops-chairs@ietf.org">ops-chairs@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, February 07, =
2010 9:41=20
    AM</DIV>
    <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> IETF Outcomes =
wiki</DIV>
    <DIV><BR></DIV>For folks who are not aware, a set of wikipages on =
the=20
    outcomes of the<BR>IETF work, successes and failures was started =
at<BR><A=20
    =
href=3D"http://trac.tools.ietf.org/misc/outcomes/">http://trac.tools.ietf=
.org/misc/outcomes/</A>=20
    with per areas views that<BR>include OPS -<BR><A=20
    =
href=3D"http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations">htt=
p://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations</A>=20
    <BR><BR>The wiki is out there to be discussed and improved. Maybe =
it's a=20
    good<BR>item to discuss shortly also in the OPSAREA meeting at =
IETF77.=20
    <BR><BR>Dan</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01CAA804.2F1E6E41--

From dhc2@dcrocker.net  Sun Feb  7 08:04:29 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6A0A3A6C15 for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 08:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bz5jGorZOl5k for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 08:04:28 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id C92393A6920 for <ops-area@ietf.org>; Sun,  7 Feb 2010 08:04:28 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o17G5JvV003604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Feb 2010 08:05:25 -0800
Message-ID: <4B6EE4BF.6040208@dcrocker.net>
Date: Sun, 07 Feb 2010 08:05:19 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop>
In-Reply-To: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10363/Sun Feb 7 05:50:54 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 07 Feb 2010 08:05:25 -0800 (PST)
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Fw: IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 16:04:29 -0000

On 2/7/2010 3:26 AM, Bert Wijnen (IETF) wrote:
> Wow... sofar that does not look so good for the OPS area.
> Only a couple of protocols that we did in the late 80s (so even before I
> participated... or maybe just because of that :-() seem to have good
> adoption.


For the initial version of the wiki, we did not try to be complete and we were 
not all that systematic.  It was a case of what examples some of us thought of. 
The most interesting choices were ones tested the limits of the wiki's template 
format, so we could consider enhancements to the form of the wiki.

As Dan's notes suggests, the nice thing about a wiki is that any of you (with an 
IETF tools login) can add to it or fix errors.

Please do!

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ietfdbh@comcast.net  Sun Feb  7 08:08:01 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E64273A7234 for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 08:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 iPtGt-hDSr93 for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 08:08:00 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id 7460D3A7019 for <ops-area@ietf.org>; Sun,  7 Feb 2010 08:08:00 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta05.westchester.pa.mail.comcast.net with comcast id f2mV1d0091ei1Bg554889r; Sun, 07 Feb 2010 16:08:08 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta24.westchester.pa.mail.comcast.net with comcast id f4AA1d00S284sdk3k4AA6g; Sun, 07 Feb 2010 16:10:10 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>
Date: Sun, 7 Feb 2010 11:08:58 -0500
Message-ID: <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>
Thread-Index: Acqn0VfhCrQbwmaJQPa+cUbUaWHfxQAM45MQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: ietf-outcomes@ietf.org, ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 16:08:02 -0000

Hi,

I think this results table an interesting idea, but I have some
concerns.

1) My first concern is about the clarity of adoption ratings.
SNMPv1 was obviously widely adopted. 
But a recent survey shared by Bert showed 14% using SNMPv1, 65% using
SNMPv2, and 12% using SNMPv3. Yet SNMPv1 is listed as massive
adoption, SNMPv2 is listed as some adoption, and SNMPv3 as complete
failure. 

Obviously, the adoption rates in the table differ from the survey
results quite a bit. Whose measurements should we use to declare
adoption rates?

If 12% adoption is complete failure, how do we score something like
SNMPCONF, or the EOS or SMING efforts?

2) I have concerns about IETF Origin.
IPFIX is classified as IETF Origin, but the ipfix WG actually started
when companies contributed their proprietary flow accounting protocol
designs, combined with requests from flow accounting users, to develop
a standard. IPFIX is very largely based on Netflow (chosen after a
bakeoff), coupled with a TCP transport based on Cabletron's
lightweight flow accounting protocol, and features from SFLOW(?), and
elements of CRANE from (NetApp?). And it built atop aspects of the
IETF RTFM standard. 

ipfix did not start out as an IETF design; I think an analysis of IPR
disclosures would certainly reflect that; the ipfix WG just developed
existing work into a standard. 

What criteria should be used for this binary decision?

3) I have concerns about whether "adoption" is historical adoption or
current adoption.
At what point in time is adoption measured? Is netconf a complete
failure because it has not been widely adopted yet? Was SNMPv1
massively adopted in 1990? Maybe the chart should have adoption
ratings at 2 years, 5 years, 10 years, and 15+ to get a better idea of
adoption trends. 

SNMPv3 is judged as a complete failure, but it has far more adoption
than netconf at this point. We certainly do not want to discourage
people from adopting Netconf because so far it has not achieved
massive adoption. Yet this chart could do that if the timeline of
availability versus adoption isn't represented.

4) I have concerns about "adoption" when it relates to extensions
versus the base technology. SNMPv2 and SNMPv3 build upon the base SNMP
design. What has been adopted widely in SNMPv2? Is it the operations
(getBulk), or is it SMIv2 extensions (Counter64)? 

SNMPv2 added very little to SNMPv1; SNMPv3 added a huge number of
extensions, with new varbind formats, different transports, detailed
authentication and integrity checking, per-user authorizations,
standardized notification configurations, proxy, etc. The costs
associated with adopting a huge extension compared to a small
extension is not reflected in the table. Yet certainly that has an
impact on adoption.

SNMPv2 and SNMPv3 still use the base protocol features, such as GETs
and SETs, traps and request/responses, and so on. That doesn't really
get reflected in this table. 

MIB-2 achieved wide adoption, but many later MIB modules achieved much
less adoption.

I notice Diameter is listed as a separate protocol from RADIUS, but
isn't Diameter really RADIUS v2? Diameter has been adopted by the
telecom/service provider segment, but it has been largely rejected by
the enterprise segment who prefer the simplicity of RADIUS. But
adoption by some market segements and not others certainly doesn't get
reflected in this table.

I would be interested in seeing the adoption trends for other
protocols and later versions or their extensions, like DHCP and TLS
and RADIUS and ipfix and IPv4/IPv6. I suspect the massively adopted
protocols really solve massive basic operational problems, whereas
extensions to those protocols solve problems with dramatically less
operational demand, because the base protocol already solved most of
the problem.

5) I am concerned about incomplete information, especially concerning
area production. 

Bert's response was "wow. we haven't achieved much". But we haven't
listed most of the work that has occurred in the OPS area. Where is
SMIv1, SMIv2, MIB-2, and all the MIB modules that have been massively
adopted? The bulk of the work done in the OPS area since 1990 has
probably been MIB module development. Where is capwap, disman,
snmpconf, eos, sming, and a wide range of others? If people, even
Bert, look at this and think it is in any way a reflection of what OPS
has contributed to the IETF in the last ten years, then this table is
highly misleading.

6) I am concerned about statistics without analysis. The info
presented has no analysis with it. I think it could be tremedously
useful to understand that, as documented in rfc 1052, the SNMP suite
started with a cintributed data modeling language (which became SMIv1)
and a common information model (which became the MIB), then added two
protocols - one long-term (CMIP) and one a simple, temporary protocol
to use until the long-term protocol was ready (SNMP). I believe the
SNMP suite achieved fairly quick adoption because of its relative
simplicity, but also because MIB-1 and MIB-2 defined a standard
information model so there was something to actually manage - and it
was relatively simple, providing counters for things like packets in
and packets out for core protocols like IP, UDP, TCP, etc. 

I am especially concerned because I see many efforts that try to build
the pieces separately. For example, netconf was published two years
ago, but the data modeling language is still in development, and there
are no manageable data models available. Sip-clf is trying to build
just a data model without considering how protocols will need to work
to acheive the targeted use cases (and what effect that will have on
the information and data models).

--Summary--

I think this results chart is way too simplistic, and it can be very
misleading, and it could lead to bad decisions about how we should
develop protocols.

David Harrington
dbharrington@comcast.net
ietfdbh@comcast.net
dharrington@huawei.com


> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, February 07, 2010 3:41 AM
> To: ops-area@ietf.org
> Cc: ops-chairs@ietf.org
> Subject: [OPS-AREA] IETF Outcomes wiki
> 
> For folks who are not aware, a set of wikipages on the outcomes of
the
> IETF work, successes and failures was started at
> http://trac.tools.ietf.org/misc/outcomes/ with per areas views that
> include OPS -
> http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations 
> 
> The wiki is out there to be discussed and improved. Maybe it's a
good
> item to discuss shortly also in the OPSAREA meeting at IETF77. 
> 
> Dan
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


From dromasca@avaya.com  Sun Feb  7 08:51:02 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 831273A724A; Sun,  7 Feb 2010 08:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110,  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 wlLC0aHUgkED; Sun,  7 Feb 2010 08:51:01 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id E76B43A6DAC; Sun,  7 Feb 2010 08:51:00 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,422,1262581200"; d="scan'208";a="204068576"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Feb 2010 11:51:59 -0500
X-IronPort-AV: E=Sophos;i="4.49,422,1262581200"; d="scan'208";a="443296067"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 07 Feb 2010 11:51:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 7 Feb 2010 17:51:36 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0D9C9@307622ANEX5.global.avaya.com>
In-Reply-To: <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] IETF Outcomes wiki
Thread-Index: Acqn0VfhCrQbwmaJQPa+cUbUaWHfxQAM45MQAAPLTBA=
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "David Harrington" <ietfdbh@comcast.net>, <ops-area@ietf.org>
Cc: ietf-outcomes@ietf.org, ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 16:51:02 -0000

As I understand this - it's a wiki - so it's open for comments (as any
IETF work) and it's open for additions and corrections.=20

I have two comments to yours (to which I agree to a large extent):=20

- when talking about adoption, there is a certain period of time before
any judgment can be made. This may differ from area to area and from
types of protocols to other. For management protocols I think that the
level of adoption can be measured only after the basic pieces of the
management framework for the protocol are in place - these includes the
protocol itself and the associated data modeling language and security
framework. Of course, if any of these three elements is too late in
showing up the protocol can be declared a failure, but happens only
after a while. For NETCONF I believe we are in the situation that it's
far too early to make a judgment, as the work for its associated DML is
still in progress
- there are certainly many elements missing in the table, and I see this
only as a starting point, maybe intentionally filled in only with a few
rows to ignite discussion and invite the OPS community to contribute to
it filling the empty spaces. I would certainly add SMI and SMIv2 as
separate entries.=20

I agree about your observation concerning the DNA of IPFIX. On the other
hand I think that the later evolution shows that the industry did not
buy the Diameter is RADIUSv2 concept.

Dan


=20

> -----Original Message-----
> From: David Harrington [mailto:ietfdbh@comcast.net]=20
> Sent: Sunday, February 07, 2010 6:09 PM
> To: Romascanu, Dan (Dan); ops-area@ietf.org
> Cc: ops-chairs@ietf.org; ietf-outcomes@ietf.org
> Subject: RE: [OPS-AREA] IETF Outcomes wiki
>=20
> Hi,
>=20
> I think this results table an interesting idea, but I have=20
> some concerns.
>=20
> 1) My first concern is about the clarity of adoption ratings.
> SNMPv1 was obviously widely adopted.=20
> But a recent survey shared by Bert showed 14% using SNMPv1,=20
> 65% using SNMPv2, and 12% using SNMPv3. Yet SNMPv1 is listed=20
> as massive adoption, SNMPv2 is listed as some adoption, and=20
> SNMPv3 as complete failure.=20
>=20
> Obviously, the adoption rates in the table differ from the=20
> survey results quite a bit. Whose measurements should we use=20
> to declare adoption rates?
>=20
> If 12% adoption is complete failure, how do we score=20
> something like SNMPCONF, or the EOS or SMING efforts?
>=20
> 2) I have concerns about IETF Origin.
> IPFIX is classified as IETF Origin, but the ipfix WG actually=20
> started when companies contributed their proprietary flow=20
> accounting protocol designs, combined with requests from flow=20
> accounting users, to develop a standard. IPFIX is very=20
> largely based on Netflow (chosen after a bakeoff), coupled=20
> with a TCP transport based on Cabletron's lightweight flow=20
> accounting protocol, and features from SFLOW(?), and elements=20
> of CRANE from (NetApp?). And it built atop aspects of the=20
> IETF RTFM standard.=20
>=20
> ipfix did not start out as an IETF design; I think an=20
> analysis of IPR disclosures would certainly reflect that; the=20
> ipfix WG just developed existing work into a standard.=20
>=20
> What criteria should be used for this binary decision?
>=20
> 3) I have concerns about whether "adoption" is historical=20
> adoption or current adoption.
> At what point in time is adoption measured? Is netconf a=20
> complete failure because it has not been widely adopted yet?=20
> Was SNMPv1 massively adopted in 1990? Maybe the chart should=20
> have adoption ratings at 2 years, 5 years, 10 years, and 15+=20
> to get a better idea of adoption trends.=20
>=20
> SNMPv3 is judged as a complete failure, but it has far more=20
> adoption than netconf at this point. We certainly do not want=20
> to discourage people from adopting Netconf because so far it=20
> has not achieved massive adoption. Yet this chart could do=20
> that if the timeline of availability versus adoption isn't=20
> represented.
>=20
> 4) I have concerns about "adoption" when it relates to=20
> extensions versus the base technology. SNMPv2 and SNMPv3=20
> build upon the base SNMP design. What has been adopted widely=20
> in SNMPv2? Is it the operations (getBulk), or is it SMIv2=20
> extensions (Counter64)?=20
>=20
> SNMPv2 added very little to SNMPv1; SNMPv3 added a huge=20
> number of extensions, with new varbind formats, different=20
> transports, detailed authentication and integrity checking,=20
> per-user authorizations, standardized notification=20
> configurations, proxy, etc. The costs associated with=20
> adopting a huge extension compared to a small extension is=20
> not reflected in the table. Yet certainly that has an impact=20
> on adoption.
>=20
> SNMPv2 and SNMPv3 still use the base protocol features, such=20
> as GETs and SETs, traps and request/responses, and so on.=20
> That doesn't really get reflected in this table.=20
>=20
> MIB-2 achieved wide adoption, but many later MIB modules=20
> achieved much less adoption.
>=20
> I notice Diameter is listed as a separate protocol from=20
> RADIUS, but isn't Diameter really RADIUS v2? Diameter has=20
> been adopted by the telecom/service provider segment, but it=20
> has been largely rejected by the enterprise segment who=20
> prefer the simplicity of RADIUS. But adoption by some market=20
> segements and not others certainly doesn't get reflected in=20
> this table.
>=20
> I would be interested in seeing the adoption trends for other=20
> protocols and later versions or their extensions, like DHCP=20
> and TLS and RADIUS and ipfix and IPv4/IPv6. I suspect the=20
> massively adopted protocols really solve massive basic=20
> operational problems, whereas extensions to those protocols=20
> solve problems with dramatically less operational demand,=20
> because the base protocol already solved most of the problem.
>=20
> 5) I am concerned about incomplete information, especially=20
> concerning area production.=20
>=20
> Bert's response was "wow. we haven't achieved much". But we=20
> haven't listed most of the work that has occurred in the OPS=20
> area. Where is SMIv1, SMIv2, MIB-2, and all the MIB modules=20
> that have been massively adopted? The bulk of the work done=20
> in the OPS area since 1990 has probably been MIB module=20
> development. Where is capwap, disman, snmpconf, eos, sming,=20
> and a wide range of others? If people, even Bert, look at=20
> this and think it is in any way a reflection of what OPS has=20
> contributed to the IETF in the last ten years, then this=20
> table is highly misleading.
>=20
> 6) I am concerned about statistics without analysis. The info=20
> presented has no analysis with it. I think it could be=20
> tremedously useful to understand that, as documented in rfc=20
> 1052, the SNMP suite started with a cintributed data modeling=20
> language (which became SMIv1) and a common information model=20
> (which became the MIB), then added two protocols - one=20
> long-term (CMIP) and one a simple, temporary protocol to use=20
> until the long-term protocol was ready (SNMP). I believe the=20
> SNMP suite achieved fairly quick adoption because of its=20
> relative simplicity, but also because MIB-1 and MIB-2 defined=20
> a standard information model so there was something to=20
> actually manage - and it was relatively simple, providing=20
> counters for things like packets in and packets out for core=20
> protocols like IP, UDP, TCP, etc.=20
>=20
> I am especially concerned because I see many efforts that try=20
> to build the pieces separately. For example, netconf was=20
> published two years ago, but the data modeling language is=20
> still in development, and there are no manageable data models=20
> available. Sip-clf is trying to build just a data model=20
> without considering how protocols will need to work to=20
> acheive the targeted use cases (and what effect that will=20
> have on the information and data models).
>=20
> --Summary--
>=20
> I think this results chart is way too simplistic, and it can=20
> be very misleading, and it could lead to bad decisions about=20
> how we should develop protocols.
>=20
> David Harrington
> dbharrington@comcast.net
> ietfdbh@comcast.net
> dharrington@huawei.com
>=20
>=20
> > -----Original Message-----
> > From: ops-area-bounces@ietf.org
> > [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> > Sent: Sunday, February 07, 2010 3:41 AM
> > To: ops-area@ietf.org
> > Cc: ops-chairs@ietf.org
> > Subject: [OPS-AREA] IETF Outcomes wiki
> >=20
> > For folks who are not aware, a set of wikipages on the outcomes of
> the
> > IETF work, successes and failures was started at=20
> > http://trac.tools.ietf.org/misc/outcomes/ with per areas views that=20
> > include OPS -=20
> > http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations
> >=20
> > The wiki is out there to be discussed and improved. Maybe it's a
> good
> > item to discuss shortly also in the OPSAREA meeting at IETF77.=20
> >=20
> > Dan
> > _______________________________________________
> > OPS-AREA mailing list
> > OPS-AREA@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-area
> >=20
>=20
>=20

From dhc2@dcrocker.net  Sun Feb  7 11:35:26 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 648F33A692C for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 11:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xJa9XtTZCmU1 for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 11:35:24 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id AC6E83A682A for <ops-area@ietf.org>; Sun,  7 Feb 2010 11:35:24 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o17JaIB4018384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ops-area@ietf.org>; Sun, 7 Feb 2010 11:36:23 -0800
Message-ID: <4B6F1632.80105@dcrocker.net>
Date: Sun, 07 Feb 2010 11:36:18 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: "'OPS Area (E-mail)'" <ops-area@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10363/Sun Feb 7 05:50:54 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 07 Feb 2010 11:36:24 -0800 (PST)
Subject: [OPS-AREA] Fwd: Re: [ietf-outcomes]  IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 19:35:26 -0000

My response to David's focus' on his concerns ab out the nature of the wiki, 
rather than about ops-specific issues. So I've posted my reply on the 
ietf-outcomes mailing list and suggest that any discussion take place there:

    <http://www.ietf.org/mail-archive/web/ietf-outcomes>


d/

-------- Original Message --------
Subject: Re: [ietf-outcomes] [OPS-AREA] IETF Outcomes wiki
Date: Sun, 07 Feb 2010 10:00:17 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
To: David Harrington <ietfdbh@comcast.net>
CC: ietf-outcomes@ietf.org, ops-chairs@ietf.org, ops-area@ietf.org

Dave,

Thoughtful posting.  Thanks!

Responding only to the larger issues you raise (but hoping others will also
discuss the detail)...


On 2/7/2010 8:08 AM, David Harrington wrote:
> Hi,
>
> I think this results table an interesting idea, but I have some
> concerns.
>
> 1) My first concern is about the clarity of adoption ratings.
> SNMPv1 was obviously widely adopted.
> But a recent survey shared by Bert showed 14% using SNMPv1, 65% using
> SNMPv2, and 12% using SNMPv3. Yet SNMPv1 is listed as massive
> adoption, SNMPv2 is listed as some adoption, and SNMPv3 as complete
> failure.

The rating is like a 'best achieved' meter.  It pegs at the best value /ever/
achieved.  It's not designed to show reduced use over time.

Perhaps another column should be added, to distinguish between "best" and
"current"?  (Although that creates a serious challenge, for keeping the
'current' value, ummmmm... current.)

SNMPv1 was certainly massively successful... in its day.


> ipfix did not start out as an IETF design; I think an analysis of IPR
> disclosures would certainly reflect that; the ipfix WG just developed
> existing work into a standard.
>
> What criteria should be used for this binary decision?

Kernigan or Ritche defined "portable code" as needing less than 10% re-writing.
  Perhaps some similarly pragmatic definition should be developed for
determining whether something started "within" the IETF?

Since everything we define incorporates some details from outside, the right
choice here is probably something along the lines of "the ietf assembled or
invented all the pieces" vs. "the ietf made some changes to a pre-existing
spec".  But I'm just guessing.


> 3) I have concerns about whether "adoption" is historical adoption or
> current adoption.
> At what point in time is adoption measured? Is netconf a complete
> failure because it has not been widely adopted yet? Was SNMPv1
> massively adopted in 1990? Maybe the chart should have adoption
> ratings at 2 years, 5 years, 10 years, and 15+ to get a better idea of
> adoption trends.

You are raising a question that is clearly reasonable.  I don't know what my own
opinion about the particulars of the answer is.

However the one caution I will suggest is against trying to make this wiki
assert much "precision".  The method for developing entries is highly
subjective, and that means precision is extremely coarse.  It will be misleading
to represent more precision about community rough consensus than is warranted.

There is a natural tendency to want finer-grained resolution to information, but
we typically are not going to have assessment techniques that justify them, nor
will we find a compelling community /need/ for the effort to develop them.

To be pedantic about the precisions limitations when reporting assessment:  for
empirical efforts like this, the answer to 1.5 * 1.7 is not 2.55.  It's 2.6.


>       We certainly do not want to discourage
> people from adopting Netconf because so far it has not achieved
> massive adoption. Yet this chart could do that if the timeline of
> availability versus adoption isn't represented.

This is an interesting point:  To what extent can entries in this table
influence the use of the things being listed?

I had assumed that an assessment should only be listed after the value to use
(degree of success or failure) was quite clear to the community and that there
therefore was/is consensus about it.  Other than the "0" value (still pending),
of course.  I guess I could also imagine going from + to ++, or ++ to ++>, over
time.


> 4) I have concerns about "adoption" when it relates to extensions
> versus the base technology. SNMPv2 and SNMPv3 build upon the base SNMP
> design. What has been adopted widely in SNMPv2? Is it the operations
> (getBulk), or is it SMIv2 extensions (Counter64)?
...
> SNMPv2 and SNMPv3 still use the base protocol features, such as GETs
> and SETs, traps and request/responses, and so on. That doesn't really
> get reflected in this table.

Not sure what sort of "reflected" you are looking for.

Please note that the table is attempting to report on the utility of particular
a standards effort, not necessarily the functional relationship among different
effort.

That is, the bald form of the question is:  Was the incremental effort to
produce SNMPv2 worth the considerable effort?  Every standards effort is
enormously expensive.  Try calculating the aggregate cost of participant time
for even the smallest effort; it's intimidating.

(However Jon Callas commented to me that some efforts that are overtly a failure
do provide valuable learning for later efforts that succeed; and indeed,
capturing this is part of the goal in the "phases" idea, for efforts that have
to change direction.)


> I notice Diameter is listed as a separate protocol from RADIUS, but
> isn't Diameter really RADIUS v2?

This gets back to the notation question I raised separately, for such things as
phases.  It would be great if we could resolve this to cover such cases.

And this particular example can't reasonably be supported by the choice I had
stated a preference for, which is a version number in column 1, since the basic
name is different.


>  Diameter has been adopted by the
> telecom/service provider segment, but it has been largely rejected by
> the enterprise segment who prefer the simplicity of RADIUS. But
> adoption by some market segements and not others certainly doesn't get
> reflected in this table.

That's where the Target/Segment column helps.


> I would be interested in seeing the adoption trends for other
> protocols and later versions or their extensions, like DHCP and TLS
> and RADIUS and ipfix and IPv4/IPv6.

+1.


> 5) I am concerned about incomplete information, especially concerning
> area production.

The good news, is that you can directly remedy that deficiency....


> 6) I am concerned about statistics without analysis. The info
> presented has no analysis with it.

The right-most column is conveniently available for pointing to in-depth
information...  Discussion of history, core issues, and the like, is not the
goal of this wiki, but yes, it could be extremely helpful to develop that
information.


> I am especially concerned because I see many efforts that try to build
> the pieces separately. For example, netconf was published two years
> ago, but the data modeling language is still in development, and there
> are no manageable data models available. Sip-clf is trying to build
> just a data model without considering how protocols will need to work
> to acheive the targeted use cases (and what effect that will have on
> the information and data models).

Is there a way to depict this sort of issue in a table?  Can the wiki be
modified to support it?


> --Summary--
>
> I think this results chart is way too simplistic, and it can be very
> misleading, and it could lead to bad decisions about how we should
> develop protocols.

Your premise is that greater complexity will produce greater insight.

The cognitive reality is that there needs to be a balance between simplicity and
complexity.  Go too far in either direction and utility is lost.

Where the balance needs to be largely depends on the details of the target
population for consuming the wiki data.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
ietf-outcomes mailing list
ietf-outcomes@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-outcomes


From bertietf@bwijnen.net  Sun Feb  7 14:26:30 2010
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1C953A68AB for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 14:26:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.185
X-Spam-Level: *
X-Spam-Status: No, score=1.185 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_05=-1.11, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 f9jMapdscf9n for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 14:26:29 -0800 (PST)
Received: from relay.versatel.net (relay56.tele2.vuurwerk.nl [62.250.3.56]) by core3.amsl.com (Postfix) with ESMTP id 6E2173A67B4 for <ops-area@ietf.org>; Sun,  7 Feb 2010 14:26:27 -0800 (PST)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1NeFbC-0004Br-CX; Sun, 07 Feb 2010 23:27:26 +0100
Message-ID: <DEEFC07071B54587AF459A4E9F8C8499@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: <dcrocker@bbiw.net>
References: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop> <4B6EE4BF.6040208@dcrocker.net>
In-Reply-To: <4B6EE4BF.6040208@dcrocker.net>
Date: Sun, 7 Feb 2010 23:26:35 +0100
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0DC0_01CAA84C.FD105F90"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Fw: IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 22:26:30 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0DC0_01CAA84C.FD105F90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The real bad thing is that you now get news-articles like
     =
http://www.networkworld.com/news/2010/020410-ietf-turns-introspective-wit=
h-new.html

And so if the people who do not understand that this is really not =
reflecting the current
state at all..... they may get the complete wrong picture!!!!!!

Bert
  ----- Original Message -----=20
  From: Dave CROCKER=20
  To: Bert Wijnen (IETF)=20
  Cc: ops-area (IETF)=20
  Sent: Sunday, February 07, 2010 5:05 PM
  Subject: Re: [OPS-AREA] Fw: IETF Outcomes wiki




  On 2/7/2010 3:26 AM, Bert Wijnen (IETF) wrote:
  > Wow... sofar that does not look so good for the OPS area.
  > Only a couple of protocols that we did in the late 80s (so even =
before I
  > participated... or maybe just because of that :-() seem to have good
  > adoption.


  For the initial version of the wiki, we did not try to be complete and =
we were=20
  not all that systematic.  It was a case of what examples some of us =
thought of.=20
  The most interesting choices were ones tested the limits of the wiki's =
template=20
  format, so we could consider enhancements to the form of the wiki.

  As Dan's notes suggests, the nice thing about a wiki is that any of =
you (with an=20
  IETF tools login) can add to it or fix errors.

  Please do!

  d/
  --=20

     Dave Crocker
     Brandenburg InternetWorking
     bbiw.net



-------------------------------------------------------------------------=
-----



  Geen virus gevonden in het binnenkomende-bericht.
  Gecontroleerd door AVG - www.avg.com=20
  Versie: 9.0.733 / Virusdatabase: 271.1.1/2673 - datum van uitgifte: =
02/07/10 08:22:00

------=_NextPart_000_0DC0_01CAA84C.FD105F90
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18882">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>The real bad thing is that you now get news-articles =

like</FONT></DIV>
<DIV><FONT size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; <A=20
href=3D"http://www.networkworld.com/news/2010/020410-ietf-turns-introspec=
tive-with-new.html">http://www.networkworld.com/news/2010/020410-ietf-tur=
ns-introspective-with-new.html</A></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>And so if the people who do not understand that this =
is really=20
not reflecting the current</FONT></DIV>
<DIV><FONT size=3D2>state at all..... they may get the complete wrong=20
picture!!!!!!</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Bert</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Ddhc2@dcrocker.net href=3D"mailto:dhc2@dcrocker.net">Dave =
CROCKER</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dbertietf@bwijnen.net=20
  href=3D"mailto:bertietf@bwijnen.net">Bert Wijnen (IETF)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dops-area@ietf.org=20
  href=3D"mailto:ops-area@ietf.org">ops-area (IETF)</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, February 07, 2010 =
5:05=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [OPS-AREA] Fw: =
IETF Outcomes=20
  wiki</DIV>
  <DIV><BR></DIV><BR><BR>On 2/7/2010 3:26 AM, Bert Wijnen (IETF) =
wrote:<BR>&gt;=20
  Wow... sofar that does not look so good for the OPS area.<BR>&gt; Only =
a=20
  couple of protocols that we did in the late 80s (so even before =
I<BR>&gt;=20
  participated... or maybe just because of that :-() seem to have =
good<BR>&gt;=20
  adoption.<BR><BR><BR>For the initial version of the wiki, we did not =
try to be=20
  complete and we were <BR>not all that systematic.&nbsp; It was a case =
of what=20
  examples some of us thought of. <BR>The most interesting choices were =
ones=20
  tested the limits of the wiki's template <BR>format, so we could =
consider=20
  enhancements to the form of the wiki.<BR><BR>As Dan's notes suggests, =
the nice=20
  thing about a wiki is that any of you (with an <BR>IETF tools login) =
can add=20
  to it or fix errors.<BR><BR>Please do!<BR><BR>d/<BR>-- =
<BR><BR>&nbsp;&nbsp;=20
  Dave Crocker<BR>&nbsp;&nbsp; Brandenburg =
InternetWorking<BR>&nbsp;&nbsp;=20
  bbiw.net<BR>
  <P>
  <HR>

  <P></P><BR>Geen virus gevonden in het =
binnenkomende-bericht.<BR>Gecontroleerd=20
  door AVG - <A href=3D"http://www.avg.com">www.avg.com</A> <BR>Versie: =
9.0.733 /=20
  Virusdatabase: 271.1.1/2673 - datum van uitgifte: 02/07/10=20
08:22:00<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0DC0_01CAA84C.FD105F90--


From bertietf@bwijnen.net  Sun Feb  7 14:26:30 2010
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D24EE3A6B1E; Sun,  7 Feb 2010 14:26:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.413
X-Spam-Level: 
X-Spam-Status: No, score=0.413 tagged_above=-999 required=5 tests=[AWL=0.855,  BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 EqVhr2DoUTRO; Sun,  7 Feb 2010 14:26:30 -0800 (PST)
Received: from relay.versatel.net (relay56.tele2.vuurwerk.nl [62.250.3.56]) by core3.amsl.com (Postfix) with ESMTP id 05D5F3A6855; Sun,  7 Feb 2010 14:26:30 -0800 (PST)
Received: from [87.215.199.34] (helo=BertLaptop) by relay.versatel.net with smtp (Exim 4.69) (envelope-from <bertietf@bwijnen.net>) id 1NeFbC-0004Br-Pt; Sun, 07 Feb 2010 23:27:26 +0100
Message-ID: <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "David Harrington" <ietfdbh@comcast.net>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, "ops-area \(IETF\)" <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>
In-Reply-To: <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>
Date: Sun, 7 Feb 2010 23:26:50 +0100
Organization: Consultant
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0DCA_01CAA84D.062C5FC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
Cc: ietf-outcomes@ietf.org, ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 22:26:30 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0DCA_01CAA84D.062C5FC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dave...
  ----- Original Message -----=20
  From: David Harrington=20
  To: 'Romascanu, Dan (Dan)' ; ops-area@ietf.org=20
  Cc: ietf-outcomes@ietf.org ; ops-chairs@ietf.org=20
  Sent: Sunday, February 07, 2010 5:08 PM
  Subject: Re: [OPS-AREA] IETF Outcomes wiki


  Hi,

  Bert's response was "wow. we haven't achieved much".

I hope (assume/assumed) that you understand that I certainly also do not =
agree with
what is currently listed on the OPS outcomes page.

It is just that if you read that page.... one would have to come to that =
conclusion.

Bert
------=_NextPart_000_0DCA_01CAA84D.062C5FC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18882">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Dave...</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dietfdbh@comcast.net =
href=3D"mailto:ietfdbh@comcast.net">David=20
  Harrington</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Ddromasca@avaya.com=20
  href=3D"mailto:dromasca@avaya.com">'Romascanu, Dan (Dan)'</A> ; <A=20
  title=3Dops-area@ietf.org =
href=3D"mailto:ops-area@ietf.org">ops-area@ietf.org</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Dietf-outcomes@ietf.org=20
  href=3D"mailto:ietf-outcomes@ietf.org">ietf-outcomes@ietf.org</A> ; <A =

  title=3Dops-chairs@ietf.org=20
  href=3D"mailto:ops-chairs@ietf.org">ops-chairs@ietf.org</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, February 07, 2010 =
5:08=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [OPS-AREA] IETF =
Outcomes=20
  wiki</DIV>
  <DIV><FONT size=3D2></FONT><BR></DIV>
  <DIV>Hi,<BR><BR>Bert's response was "wow. we haven't achieved =
much".</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE>
<DIV><FONT size=3D2>I hope (assume/assumed) that you understand that I =
certainly=20
also do not agree with</FONT></DIV>
<DIV><FONT size=3D2>what is currently listed on the OPS outcomes=20
page.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>It is just that if you read that page.... one would =
have to=20
come to that conclusion.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Bert</FONT></DIV></BODY></HTML>

------=_NextPart_000_0DCA_01CAA84D.062C5FC0--


From dhc2@dcrocker.net  Sun Feb  7 16:11:29 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FB2D3A6F85 for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 16:11:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gdQyQgWiWd1M for <ops-area@core3.amsl.com>; Sun,  7 Feb 2010 16:11:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id A07D83A6EB1 for <ops-area@ietf.org>; Sun,  7 Feb 2010 16:11:26 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o180CJ68019598 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Feb 2010 16:12:24 -0800
Message-ID: <4B6F56E3.2090207@dcrocker.net>
Date: Sun, 07 Feb 2010 16:12:19 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <3FADB7DCE5AE42C2AD6BA1F81A46256B@BertLaptop> <4B6EE4BF.6040208@dcrocker.net> <DEEFC07071B54587AF459A4E9F8C8499@BertLaptop>
In-Reply-To: <DEEFC07071B54587AF459A4E9F8C8499@BertLaptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10363/Sun Feb 7 05:50:54 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 07 Feb 2010 16:12:25 -0800 (PST)
Cc: "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] Fw: IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 00:11:30 -0000

On 2/7/2010 2:26 PM, Bert Wijnen (IETF) wrote:
> The real bad thing is that you now get news-articles like
> http://www.networkworld.com/news/2010/020410-ietf-turns-introspective-with-new.html
> And so if the people who do not understand that this is really not
> reflecting the current
> state at all..... they may get the complete wrong picture!!!!!!


For any interesting population and any interesting topic, there is no "may" to 
worry about.  It is /certain/ that some people will entirely misunderstand one 
or another aspect.

At that, the reporter did an unusually good job of trying to ensure an accurate 
understand, by including:

    "Only a small portion of the many standards that IETF has created are now on 
the site, Crocker admitted. Any IETF member can edit the site, and Crocker is 
encouraging members to fill in details about their work."

and

    "A single snapshot in time was very useful, but we hope that watching this 
over a longer period will provide additional insights," Housley said."


In any event, I suspect the best way to deal with a concern for completeness is 
for us to get the wiki as complete as we think it should be...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mrm@vmware.com  Mon Feb  8 13:00:14 2010
Return-Path: <mrm@vmware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC3E328C191 for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 13:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 N5yMbzO2kIta for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 13:00:13 -0800 (PST)
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [65.115.85.73]) by core3.amsl.com (Postfix) with ESMTP id 5DC4B28C18C for <ops-area@ietf.org>; Mon,  8 Feb 2010 13:00:13 -0800 (PST)
Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id C593240054; Mon,  8 Feb 2010 13:01:16 -0800 (PST)
Received: from pa-exht02.vmware.com (pa-exht02.vmware.com [10.113.81.168]) by mailhost4.vmware.com (Postfix) with ESMTP id B07D1C9E3A; Mon,  8 Feb 2010 13:01:16 -0800 (PST)
Received: from EXCH-MBX-3.vmware.com ([10.113.81.228]) by pa-exht02.vmware.com ([10.113.81.168]) with mapi; Mon, 8 Feb 2010 13:00:50 -0800
From: Michael MacFaden <mrm@vmware.com>
To: Bert Wijnen <bwijnen@bwijnen.net>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "ops-area@ietf.org" <ops-area@ietf.org>
Date: Mon, 8 Feb 2010 13:01:16 -0800
Thread-Topic: [OPS-AREA] IETF Outcomes wiki
Thread-Index: Acqn+3pM1EGX3BVCRieqVntPDossiwBA0QWo
Message-ID: <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop>
In-Reply-To: <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop>
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
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 21:00:14 -0000

Regarding:

a) http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations
Need a legend for the values in the Adoption column no?

b) I don't see how one can compare the 80s to the 90s though, its not quite=
 fair comparison.
I see percentages floating about but didn't see where are the absolute numb=
ers in any of the links on trac.
I would have preferred to see numeric tables  as the overall pie's growth w=
as=20
nothing short of spectacular for those decades.

c) Think the SMI should be broken out of SNMP and given its due.
That we have for the large set pf core mib modules: (mib-2 and its progeny,=
 host-resources, entity,
some parts of rmon, and spawned a bazillion enterprise trap notifications),=
=20
it remains how systems are widely monitored for fault/performance=20
(but not configured).  A resounding success to me.

Add to that other standards orgs like IEEE that use or used to (not sure cu=
rrent state) define SMI mib modules
for technologies it develops, so then some credit is due to  SMI itself out=
side of the SNMP protocol. Modulo
some protocol limitations SMI has done quite well.  How's this for the sinc=
erest form of flattery:
http://www.vmware.com/support/developer/cim-sdk/smash/u2/ga/apirefdoc/CIM_E=
thernetPortStatistics.html


Mike MacFaden

________________________________________
From: ops-area-bounces@ietf.org [ops-area-bounces@ietf.org] On Behalf Of Be=
rt Wijnen [bwijnen@bwijnen.net]
Sent: Sunday, February 07, 2010 2:55 AM
To: Romascanu, Dan (Dan); ops-area@ietf.org
Cc: ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki

Wow... sofar that does not look so good for the OPS area.
Only a couple of protocols that we did in the late 80s (so even before I
participated... or maybe just because of that :-() seem to have good
adoption.

Bert
----- Original Message -----
From: Romascanu, Dan (Dan)<mailto:dromasca@avaya.com>
To: ops-area@ietf.org<mailto:ops-area@ietf.org>
Cc: ops-chairs@ietf.org<mailto:ops-chairs@ietf.org>
Sent: Sunday, February 07, 2010 9:41 AM
Subject: IETF Outcomes wiki

For folks who are not aware, a set of wikipages on the outcomes of the
IETF work, successes and failures was started at
http://trac.tools.ietf.org/misc/outcomes/ with per areas views that
include OPS -
http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations

The wiki is out there to be discussed and improved. Maybe it's a good
item to discuss shortly also in the OPSAREA meeting at IETF77.

Dan

________________________________

Geen virus gevonden in het binnenkomende-bericht.
Gecontroleerd door AVG - www.avg.com<http://www.avg.com>
Versie: 9.0.733 / Virusdatabase: 271.1.1/2672 - datum van uitgifte: 02/06/1=
0 20:35:00

From dhc2@dcrocker.net  Mon Feb  8 15:13:49 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CB3028C16E for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 lUUNQB5kYq9y for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:13:48 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 6AF8928C0EB for <ops-area@ietf.org>; Mon,  8 Feb 2010 15:13:48 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o18NEkJm019953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Feb 2010 15:14:52 -0800
Message-ID: <4B709AE5.8030203@dcrocker.net>
Date: Mon, 08 Feb 2010 15:14:45 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Michael MacFaden <mrm@vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop> <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>
In-Reply-To: <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10366/Mon Feb 8 08:41:04 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 08 Feb 2010 15:14:52 -0800 (PST)
Cc: "ops-area@ietf.org" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 23:13:49 -0000

On 2/8/2010 1:01 PM, Michael MacFaden wrote:
> a) http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations Need a legend
> for the values in the Adoption column no?

How about:

    <http://trac.tools.ietf.org/misc/outcomes/#Legend>

Come to think of it, the point ought to be on each page.  So I've added it.


> b) I don't see how one can compare the 80s to the 90s though, its not quite
> fair comparison. I see percentages floating about but didn't see where are
> the absolute numbers in any of the links on trac. I would have preferred to
> see numeric tables  as the overall pie's growth was nothing short of
> spectacular for those decades.

You want an empirical study with diligent methodology.  That would be nice, but
this is explicitly not that.

This is a rough consensus of subjective assessment.

In terms of assessing IETF productivity, the fact that something was a a huge
success is frankly more important than how large the market was.  What matters 
is that the IETF produced something that became popular.

The sort of adjustment based on age or market size could provide other sorts of 
useful insight, but the keyword is 'other'.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ietfdbh@comcast.net  Mon Feb  8 15:38:41 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 541A73A6F50 for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 ONG0Cg-iPWQM for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:38:40 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id 072AF3A6DE6 for <ops-area@ietf.org>; Mon,  8 Feb 2010 15:38:39 -0800 (PST)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta09.westchester.pa.mail.comcast.net with comcast id fV2h1d01B0cZkys59bfkfj; Mon, 08 Feb 2010 23:39:44 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta10.westchester.pa.mail.comcast.net with comcast id fbfj1d00C284sdk3Wbfjbn; Mon, 08 Feb 2010 23:39:44 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: <dcrocker@bbiw.net>, "'Michael MacFaden'" <mrm@vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop><35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com> <4B709AE5.8030203@dcrocker.net>
Date: Mon, 8 Feb 2010 18:39:42 -0500
Message-ID: <05ad01caa917$fd376b50$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <4B709AE5.8030203@dcrocker.net>
Thread-Index: AcqpFIdtQMlG2b8/T3CGEpZPkRlWyAAAsAdg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 23:38:41 -0000

Hi,

I wonder if "adoption" might not be broken into two parts, comparable
to the RFC2026 standards track:
implementations versus deployment.

Some standards, like BEEP or SCRIPT-MIB, never got much
implementation, so couldn't be deployed.
Others, like SNMPv3, have some implementation, but still don't get
deployed because they require too much work to configure.

dbh

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Dave CROCKER
> Sent: Monday, February 08, 2010 6:15 PM
> To: Michael MacFaden
> Cc: ops-area@ietf.org
> Subject: Re: [OPS-AREA] IETF Outcomes wiki
> 
> 
> 
> On 2/8/2010 1:01 PM, Michael MacFaden wrote:
> > a) 
> http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations 
> Need a legend
> > for the values in the Adoption column no?
> 
> How about:
> 
>     <http://trac.tools.ietf.org/misc/outcomes/#Legend>
> 
> Come to think of it, the point ought to be on each page.  So 
> I've added it.
> 
> 
> > b) I don't see how one can compare the 80s to the 90s 
> though, its not quite
> > fair comparison. I see percentages floating about but 
> didn't see where are
> > the absolute numbers in any of the links on trac. I would 
> have preferred to
> > see numeric tables  as the overall pie's growth was nothing short
of
> > spectacular for those decades.
> 
> You want an empirical study with diligent methodology.  That 
> would be nice, but
> this is explicitly not that.
> 
> This is a rough consensus of subjective assessment.
> 
> In terms of assessing IETF productivity, the fact that 
> something was a a huge
> success is frankly more important than how large the market 
> was.  What matters 
> is that the IETF produced something that became popular.
> 
> The sort of adjustment based on age or market size could 
> provide other sorts of 
> useful insight, but the keyword is 'other'.
> 
> d/
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


From mrm@vmware.com  Mon Feb  8 15:57:04 2010
Return-Path: <mrm@vmware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD93728C1C8 for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 PmRXILF8GEXJ for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 15:57:04 -0800 (PST)
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [65.115.85.73]) by core3.amsl.com (Postfix) with ESMTP id 0A95328C1C5 for <ops-area@ietf.org>; Mon,  8 Feb 2010 15:57:03 -0800 (PST)
Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 5A2721504B; Mon,  8 Feb 2010 15:58:08 -0800 (PST)
Received: from pa-exht01.vmware.com (pa-exht01.vmware.com [10.113.81.167]) by mailhost4.vmware.com (Postfix) with ESMTP id 51A71C9F7D; Mon,  8 Feb 2010 15:58:08 -0800 (PST)
Received: from EXCH-MBX-3.vmware.com ([10.113.81.228]) by pa-exht01.vmware.com ([10.113.81.167]) with mapi; Mon, 8 Feb 2010 15:58:08 -0800
From: Michael MacFaden <mrm@vmware.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Date: Mon, 8 Feb 2010 15:58:08 -0800
Thread-Topic: [OPS-AREA] IETF Outcomes wiki
Thread-Index: AcqpFIXYIsGimLoARwqe613UnxRL7wAAnx4I
Message-ID: <35203D411DF5144CACC340A56A90E564965BA498@EXCH-MBX-3.vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop> <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>, <4B709AE5.8030203@dcrocker.net>
In-Reply-To: <4B709AE5.8030203@dcrocker.net>
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
Cc: "ops-area@ietf.org" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2010 23:57:04 -0000

>Come to think of it, the point ought to be on each page.  So I've added it=
.

Nice. thanks.

>This is a rough consensus of subjective assessment.

>In terms of assessing IETF productivity, the fact that something was a a h=
uge
>success is frankly more important than how large the market was.  What mat=
ters
>is that the IETF produced something that became popular.
>The sort of adjustment based on age or market size could provide other sor=
ts of
>useful insight, but the keyword is 'other'.

Good to know, would be useful to update the legend with how the values
were/are being defined.=20

If the size  or kind of market isn't defined in the table, then
the subjective value given is even less useful  to come to a common underst=
anding.

ie What part of the elephant are you touching anyway?

afaik,  SNMPv3 has 100% adoption (nay popular) rate in [Euro-]DOCSIS=20
based cable modem market, something less in US Gov't/Federal markets, and=20
tiny in enterprise markets. Financial markets being the one wanting better
security.

Mike  MacFaden


From dhc2@dcrocker.net  Mon Feb  8 17:05:06 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 635A13A74DD for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 17:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 GKwjXJfQa0+i for <ops-area@core3.amsl.com>; Mon,  8 Feb 2010 17:05:04 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 98EDA3A6F89 for <ops-area@ietf.org>; Mon,  8 Feb 2010 17:05:03 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o19161Il027216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Feb 2010 17:06:07 -0800
Message-ID: <4B70B4F8.1050508@dcrocker.net>
Date: Mon, 08 Feb 2010 17:06:00 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Michael MacFaden <mrm@vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop> <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>, <4B709AE5.8030203@dcrocker.net> <35203D411DF5144CACC340A56A90E564965BA498@EXCH-MBX-3.vmware.com>
In-Reply-To: <35203D411DF5144CACC340A56A90E564965BA498@EXCH-MBX-3.vmware.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10366/Mon Feb 8 08:41:04 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 08 Feb 2010 17:06:07 -0800 (PST)
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ops-area@ietf.org" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 01:05:06 -0000

On 2/8/2010 3:58 PM, Michael MacFaden wrote:
> Good to know, would be useful to update the legend with how the values
> were/are being defined.

Reasonable idea.  I look forward to your wordsmithing...


> If the size  or kind of market isn't defined in the table, then
> the subjective value given is even less useful  to come to a common understanding.

That depends on what understanding is being sought.

The community might decide to take the wiki in the direction you have in mind, 
but the 'understanding' that motivated my developing the wiski was simply "what 
succeeded?"  The answer to that question does not depend on market size, nor the 
year of the success.

Since you are being tenacious about the importance of the size of the market in 
which the success take place, I'll ask you to elaborate:  How does it matter? 
Specifically, what should the IETF learn from that distinction, about the 
utility of its work or how it should do things differently?



> afaik,  SNMPv3 has 100% adoption (nay popular) rate in [Euro-]DOCSIS
> based cable modem market, something less in US Gov't/Federal markets, and
> tiny in enterprise markets. Financial markets being the one wanting better
> security.

Ahhh.  That's not about market size or year.  That's about the /type/ of market 
and its a distinction that led to the Target Segment column.

Your observation suggests that there is perhaps a different value, depending on 
the Target Segment.  Looks like perhaps ++ for DOCSIS and maybe Gov't, and - in 
Enterprise.

First question is whether those differential values match other people's assessment?

Second is whether they want the wiki to differentiate this, and why that's 
important.

Third, is what annotation should be used, to indicate differential success?

But this really is a topic for the Outcomes list.  Can we move this over there?

d/

--

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From joelja@bogus.com  Mon Feb  8 21:47:19 2010
Return-Path: <joelja@bogus.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77A273A6C3C; Mon,  8 Feb 2010 21:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  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 91yqEGcY+IDr; Mon,  8 Feb 2010 21:47:18 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [147.28.0.81]) by core3.amsl.com (Postfix) with ESMTP id 9EBE73A68D6; Mon,  8 Feb 2010 21:47:18 -0800 (PST)
Received: from [192.168.1.151] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.3/8.14.3) with ESMTP id o195mBAM029013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Feb 2010 05:48:15 GMT (envelope-from joelja@bogus.com)
Message-ID: <4B70F71B.7080804@bogus.com>
Date: Mon, 08 Feb 2010 21:48:11 -0800
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>
In-Reply-To: <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Tue, 09 Feb 2010 05:48:16 +0000 (UTC)
X-Mailman-Approved-At: Tue, 09 Feb 2010 04:04:02 -0800
Cc: ops-chairs@ietf.org, "ops-area \(IETF\)" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 05:47:19 -0000

Bert Wijnen (IETF) wrote:
> 
> I hope (assume/assumed) that you understand that I certainly also do not
> agree with
> what is currently listed on the OPS outcomes page.
>  
> It is just that if you read that page.... one would have to come to that
> conclusion.

One might also conclude that appart from some rather obvious successes,
that attempting to determine if something is a success or failure as
part of the outcomes exercise is a fools errand. Although as with many
IETF exercises if enough fools work hard enough you might luck out and
end up with something useful.

> Bert

From bernard_aboba@hotmail.com  Mon Feb  8 22:45:15 2010
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C94B28C10F; Mon,  8 Feb 2010 22:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level: 
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=0.565,  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 acYvOwG7kR7V; Mon,  8 Feb 2010 22:45:13 -0800 (PST)
Received: from blu0-omc3-s21.blu0.hotmail.com (blu0-omc3-s21.blu0.hotmail.com [65.55.116.96]) by core3.amsl.com (Postfix) with ESMTP id 997D428C18A; Mon,  8 Feb 2010 22:45:13 -0800 (PST)
Received: from BLU137-DS5 ([65.55.116.74]) by blu0-omc3-s21.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Feb 2010 22:46:18 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS5E874A567D6039C93F14793500@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: "'Joel Jaeggli'" <joelja@bogus.com>, "'Bert Wijnen \(IETF\)'" <bertietf@bwijnen.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop> <4B70F71B.7080804@bogus.com>
In-Reply-To: <4B70F71B.7080804@bogus.com>
Date: Mon, 8 Feb 2010 22:46:58 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqpS7ImPHNuBip2QICb6W0CPSfbGgABvqdA
Content-Language: en-us
X-OriginalArrivalTime: 09 Feb 2010 06:46:18.0732 (UTC) FILETIME=[95658AC0:01CAA953]
X-Mailman-Approved-At: Tue, 09 Feb 2010 04:04:02 -0800
Cc: ops-chairs@ietf.org, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 06:45:15 -0000

I'd argue that the wiki is not using the same definition of "success" =
that we used in RFC 5218.=20

If the data shows that 85 percent of the original implementers of SNMPv1 =
went on to implement
SNMPv2 at some point, then if SNMPv1 was a success under the RFC 5218 =
criteria, then SNMPv2
would also have to be judged a success.=20

In fact, using the RFC 5218 criteria, SNMPv1/v2 might also be judged as =
a "wild success"
in that it was used more widely and for things beyond what the creators =
envisaged.=20

Note that the RFC 5218 criteria explicitly include the original scope in =
the definition of
"success".  For example, if a protocol was deployed for its original =
purpose in the originally
envisaged use, that is success.=20

So a protocol such as Kerberos can be judged a "success" even though it =
is not used in
consumer scenarios in the same manner as say, SSL/TLS. =20





-----Original Message-----
From: Joel Jaeggli [mailto:joelja@bogus.com]=20
Sent: Monday, February 08, 2010 9:48 PM
To: Bert Wijnen (IETF)
Cc: David Harrington; 'Romascanu, Dan (Dan)'; ops-area (IETF); =
ops-chairs@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki

Bert Wijnen (IETF) wrote:
>=20
> I hope (assume/assumed) that you understand that I certainly also do =
not
> agree with
> what is currently listed on the OPS outcomes page.
> =20
> It is just that if you read that page.... one would have to come to =
that
> conclusion.

One might also conclude that appart from some rather obvious successes,
that attempting to determine if something is a success or failure as
part of the outcomes exercise is a fools errand. Although as with many
IETF exercises if enough fools work hard enough you might luck out and
end up with something useful.

> Bert


From dhc2@dcrocker.net  Tue Feb  9 07:09:57 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5557D3A71DC; Tue,  9 Feb 2010 07:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 EVRzFZYCAQlf; Tue,  9 Feb 2010 07:09:56 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 6A10A3A6C7F; Tue,  9 Feb 2010 07:09:56 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o19FApqk029033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 07:10:57 -0800
Message-ID: <4B717AF8.8050209@dcrocker.net>
Date: Tue, 09 Feb 2010 07:10:48 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Bernard Aboba <bernard_aboba@hotmail.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>	<048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>	<E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>	<4B70F71B.7080804@bogus.com> <BLU137-DS5E874A567D6039C93F14793500@phx.gbl>
In-Reply-To: <BLU137-DS5E874A567D6039C93F14793500@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10371/Tue Feb 9 05:33:13 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Feb 2010 07:10:57 -0800 (PST)
Cc: 'Joel Jaeggli' <joelja@bogus.com>, ops-chairs@ietf.org, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 15:09:57 -0000

please, can we move this thread to the Outcomes list?

You guys are posting interesting stuff.

d/

On 2/8/2010 10:46 PM, Bernard Aboba wrote:
> I'd argue that the wiki is not using the same definition of "success" that we used in RFC 5218.
>

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ietfdbh@comcast.net  Tue Feb  9 07:52:06 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CD0028C207 for <ops-area@core3.amsl.com>; Tue,  9 Feb 2010 07:52:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 q02c24aUpeyM for <ops-area@core3.amsl.com>; Tue,  9 Feb 2010 07:52:05 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by core3.amsl.com (Postfix) with ESMTP id 291E328C11E for <ops-area@ietf.org>; Tue,  9 Feb 2010 07:52:05 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta12.westchester.pa.mail.comcast.net with comcast id fpUK1d0041uE5Es5CrtCKc; Tue, 09 Feb 2010 15:53:12 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta16.westchester.pa.mail.comcast.net with comcast id frun1d00E284sdk3crunUf; Tue, 09 Feb 2010 15:54:48 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'ops-area \(IETF\)'" <ops-area@ietf.org>, <ietf-outcomes@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop> <4B70F71B.7080804@bogus.com> <BLU137-DS5E874A567D6039C93F14793500@phx.gbl>
Date: Tue, 9 Feb 2010 10:53:11 -0500
Message-ID: <064301caa99f$fb5f6e30$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <BLU137-DS5E874A567D6039C93F14793500@phx.gbl>
Thread-Index: AcqpS7ImPHNuBip2QICb6W0CPSfbGgABvqdAABMzafA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 15:52:06 -0000

Hi,

I think it would be good to set success and failure to match rfc 5218,
and have the legends page provide brief descriptions of the
categories, and reference RFC 5218 for more details.

dbh

> -----Original Message-----
> From: Bernard Aboba [mailto:bernard_aboba@hotmail.com] 
> Sent: Tuesday, February 09, 2010 1:47 AM
> To: 'Joel Jaeggli'; 'Bert Wijnen (IETF)'
> Cc: 'David Harrington'; 'Romascanu, Dan (Dan)'; 'ops-area 
> (IETF)'; ops-chairs@ietf.org
> Subject: RE: [OPS-AREA] IETF Outcomes wiki
> 
> I'd argue that the wiki is not using the same definition of 
> "success" that we used in RFC 5218. 
> 
> If the data shows that 85 percent of the original 
> implementers of SNMPv1 went on to implement
> SNMPv2 at some point, then if SNMPv1 was a success under the 
> RFC 5218 criteria, then SNMPv2
> would also have to be judged a success. 
> 
> In fact, using the RFC 5218 criteria, SNMPv1/v2 might also be 
> judged as a "wild success"
> in that it was used more widely and for things beyond what 
> the creators envisaged. 
> 
> Note that the RFC 5218 criteria explicitly include the 
> original scope in the definition of
> "success".  For example, if a protocol was deployed for its 
> original purpose in the originally
> envisaged use, that is success. 
> 
> So a protocol such as Kerberos can be judged a "success" even 
> though it is not used in
> consumer scenarios in the same manner as say, SSL/TLS.  
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Joel Jaeggli [mailto:joelja@bogus.com] 
> Sent: Monday, February 08, 2010 9:48 PM
> To: Bert Wijnen (IETF)
> Cc: David Harrington; 'Romascanu, Dan (Dan)'; ops-area 
> (IETF); ops-chairs@ietf.org
> Subject: Re: [OPS-AREA] IETF Outcomes wiki
> 
> Bert Wijnen (IETF) wrote:
> > 
> > I hope (assume/assumed) that you understand that I 
> certainly also do not
> > agree with
> > what is currently listed on the OPS outcomes page.
> >  
> > It is just that if you read that page.... one would have to 
> come to that
> > conclusion.
> 
> One might also conclude that appart from some rather obvious 
> successes,
> that attempting to determine if something is a success or failure as
> part of the outcomes exercise is a fools errand. Although as with
many
> IETF exercises if enough fools work hard enough you might luck out
and
> end up with something useful.
> 
> > Bert
> 
> 


From j.schoenwaelder@jacobs-university.de  Tue Feb  9 08:08:00 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDCBE3A73F5; Tue,  9 Feb 2010 08:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level: 
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 I0X1VcIlZyLU; Tue,  9 Feb 2010 08:08:00 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id DC4A53A73F3; Tue,  9 Feb 2010 08:07:59 -0800 (PST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 18BC6C0023; Tue,  9 Feb 2010 17:09:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id gvDFpVV+b9bC; Tue,  9 Feb 2010 17:09:05 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 54A1FC001E; Tue,  9 Feb 2010 17:09:05 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id DC42A1050C66; Tue,  9 Feb 2010 17:08:51 +0100 (CET)
Date: Tue, 9 Feb 2010 17:08:51 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Message-ID: <20100209160851.GA37892@elstar.local>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop> <4B70F71B.7080804@bogus.com> <BLU137-DS5E874A567D6039C93F14793500@phx.gbl> <4B717AF8.8050209@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B717AF8.8050209@dcrocker.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ops-chairs@ietf.org" <ops-chairs@ietf.org>, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 16:08:00 -0000

On Tue, Feb 09, 2010 at 04:10:48PM +0100, Dave CROCKER wrote:

> please, can we move this thread to the Outcomes list?
> 
> You guys are posting interesting stuff.

I only have one question: What is the process to create wiki pages on
the IETF site? I think I have some more cool wiki page ideas I like to
post on the IETF site and I am ready to create mailing lists for
people to join to discuss interesting stuff about the cool pages I
have created.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From dhc2@dcrocker.net  Tue Feb  9 08:23:02 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0269728C229 for <ops-area@core3.amsl.com>; Tue,  9 Feb 2010 08:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 w2jEF-zLQZmt for <ops-area@core3.amsl.com>; Tue,  9 Feb 2010 08:23:01 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 39FF128C21C for <ops-area@ietf.org>; Tue,  9 Feb 2010 08:23:01 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o19GO0Sg001783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 08:24:05 -0800
Message-ID: <4B718C1D.80008@dcrocker.net>
Date: Tue, 09 Feb 2010 08:23:57 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>	<048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>	<E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>	<4B70F71B.7080804@bogus.com>	<BLU137-DS5E874A567D6039C93F14793500@phx.gbl> <064301caa99f$fb5f6e30$0600a8c0@china.huawei.com>
In-Reply-To: <064301caa99f$fb5f6e30$0600a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10371/Tue Feb 9 05:33:13 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Feb 2010 08:24:05 -0800 (PST)
Cc: "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [ietf-outcomes]  IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 16:23:02 -0000

On 2/9/2010 7:53 AM, David Harrington wrote:
> I think it would be good to set success and failure to match rfc 5218,


My reply went to the ietf-outcomes list.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc2@dcrocker.net  Tue Feb  9 09:00:13 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACA7E28C203; Tue,  9 Feb 2010 09:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 aG7MqVZxAJ3b; Tue,  9 Feb 2010 09:00:12 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id E603F28C136; Tue,  9 Feb 2010 09:00:10 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o19H1Cs8004477 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 09:01:18 -0800
Message-ID: <4B7194D5.90405@dcrocker.net>
Date: Tue, 09 Feb 2010 09:01:09 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <048101caa80f$db2ee5a0$0600a8c0@china.huawei.com> <E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop> <4B70F71B.7080804@bogus.com> <BLU137-DS5E874A567D6039C93F14793500@phx.gbl> <4B717AF8.8050209@dcrocker.net> <20100209160851.GA37892@elstar.local>
In-Reply-To: <20100209160851.GA37892@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10371/Tue Feb 9 05:33:13 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Feb 2010 09:01:18 -0800 (PST)
Cc: "ops-chairs@ietf.org" <ops-chairs@ietf.org>, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 17:00:13 -0000

I approached the IETF Chair, who passed me to the IAB Chair, who passed me to 
the person on the IAB with some history in related work (Dave Thaler) who spent 
the next six months first asking the IAB if there were objections and then the 
IESG.

I hadn't heard back so I pressed a few times and finally was told there were no 
objections, and that the IETF Chair needed to authorize moving the wiki to the 
onto the site.  I queried the IETF Chair and we had it installed within 2 days 
after that.  (Henrik Levkowetz was the tools site contact and he's a very 
responsive guy!)

Note that the wiki already had a history and a small-but-real base of support. 
  I remain a fan of building a base of work and support, before worrying about 
going through the formalities.  It makes things much more concrete and 
demonstrates some degree of market validation.

d/

On 2/9/2010 8:08 AM, Juergen Schoenwaelder wrote:
> On Tue, Feb 09, 2010 at 04:10:48PM +0100, Dave CROCKER wrote:
>
>> please, can we move this thread to the Outcomes list?
>>
>> You guys are posting interesting stuff.
>
> I only have one question: What is the process to create wiki pages on
> the IETF site? I think I have some more cool wiki page ideas I like to
> post on the IETF site and I am ready to create mailing lists for
> people to join to discuss interesting stuff about the cool pages I
> have created.
>
> /js
>

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From bernard_aboba@hotmail.com  Tue Feb  9 12:26:18 2010
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CD823A7486; Tue,  9 Feb 2010 12:26:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558,  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 tRxARYZbqQA7; Tue,  9 Feb 2010 12:26:17 -0800 (PST)
Received: from blu0-omc4-s5.blu0.hotmail.com (blu0-omc4-s5.blu0.hotmail.com [65.55.111.144]) by core3.amsl.com (Postfix) with ESMTP id 60BE33A720D; Tue,  9 Feb 2010 12:26:17 -0800 (PST)
Received: from BLU137-DS4 ([65.55.111.136]) by blu0-omc4-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Feb 2010 12:27:24 -0800
X-Originating-IP: [24.19.160.219]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU137-DS4FD3AA173C43E69670B9A93500@phx.gbl>
From: "Bernard Aboba" <bernard_aboba@hotmail.com>
To: <dcrocker@bbiw.net>, "'David Harrington'" <ietfdbh@comcast.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>	<048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>	<E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>	<4B70F71B.7080804@bogus.com>	<BLU137-DS5E874A567D6039C93F14793500@phx.gbl>	<064301caa99f$fb5f6e30$0600a8c0@china.huawei.com> <4B718B7B.6000401@dcrocker.net>
In-Reply-To: <4B718B7B.6000401@dcrocker.net>
Date: Tue, 9 Feb 2010 12:28:04 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acqpo+bGRNswnBUGTq27qcxqjns3iAAIBjtg
Content-Language: en-us
X-OriginalArrivalTime: 09 Feb 2010 20:27:24.0812 (UTC) FILETIME=[4A44C4C0:01CAA9C6]
Cc: ietf-outcomes@ietf.org, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [ietf-outcomes]  IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 20:26:18 -0000

Dave Crocker said:

"This means that a protocol is a failure if it is widely used, but for
different 
purposes than it was intended."

[BA] If a protocol has been implemented, deployed and used, I don't think
that 
can qualify as a failure under the RFC 5218 definition. From 
Section 1.4:

"   Failure, or the lack of success, cannot be determined before allowing
   sufficient time to pass (e.g., 5-10 years for an average protocol).
   Failure criteria include:

   o  No mainstream implementations.  There is little or no support in
      hosts, routers, or other classes of relevant devices.

   o  No deployment.  Devices that support the protocol are not
      deployed, or if they are, then the protocol is not enabled.

   o  No use.  While the protocol may be deployed, there are no
      applications or scenarios that actually use the protocol."

Dave Crocker also said:

"Deployed" is also a problem, since there is a long track record of
industry's 
having deployed something but never actually using it very much.  I submit
all 
of OSI as a prime example.

These are the reasons the wiki was premised on the simple measure of use.

However I note that the column that lists degree of success only uses the
word 
'adoption'. However Target Segment uses 'use'."

[BA] I'd suggest that implementation, deployment and use are separate
stages,
worth documenting separately.  If that is done, we may learn 
something about the characteristics that affect success at each stage. 

One aspect that bothers me about use is the definition of each category. 

Surely if almost nobody uses something, it is a "--" failure (e.g. IPsec
AH). 
But what if the protocol is used by the people it is designed for, but not
the vast majority of humanity? 

I use Kerberos all the time, but most people probably don't.  What category
does
this fall in?  Probably not "++" or "++>", but not "--" either.  So we're
left
with "-" and "+".  How are these categories defined?



From dromasca@avaya.com  Wed Feb 10 02:48:35 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48FD928C1C5; Wed, 10 Feb 2010 02:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  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 YvQNTQ2Dz7KC; Wed, 10 Feb 2010 02:48:34 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 5DCF528C11C; Wed, 10 Feb 2010 02:48:34 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,442,1262581200"; d="scan'208";a="204451209"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 10 Feb 2010 05:49:44 -0500
X-IronPort-AV: E=Sophos;i="4.49,442,1262581200"; d="scan'208";a="429870264"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Feb 2010 05:49:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 10 Feb 2010 11:49:26 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: again about ietf-outcomes
Thread-Index: AcqqPrbY8N2ZmCe9QxyRz7OMX58MBw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-chairs@ietf.org>
Subject: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 10:48:35 -0000

David Harrington put some work in improving the content of the wiki page
at http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations in what
concerns SNMP and SMI. It would be good if other folks have a look and
especially if they can spare some time adding more exact and detailed
information related to the other management protocols.=20

Dan

From ietfdbh@comcast.net  Wed Feb 10 05:32:48 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EE2E3A7570 for <ops-area@core3.amsl.com>; Wed, 10 Feb 2010 05:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 6PsNjQv7YRdE for <ops-area@core3.amsl.com>; Wed, 10 Feb 2010 05:32:47 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [76.96.62.24]) by core3.amsl.com (Postfix) with ESMTP id 81EB73A737D for <ops-area@ietf.org>; Wed, 10 Feb 2010 05:32:47 -0800 (PST)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta02.westchester.pa.mail.comcast.net with comcast id gCLB1d0081GhbT852DZy8C; Wed, 10 Feb 2010 13:33:58 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta07.westchester.pa.mail.comcast.net with comcast id gDZy1d005284sdk3TDZyMQ; Wed, 10 Feb 2010 13:33:58 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>, <ops-area@ietf.org>, <ops-chairs@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com>
Date: Wed, 10 Feb 2010 08:33:57 -0500
Message-ID: <072201caaa55$b25e3160$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com>
Thread-Index: AcqqPrbY8N2ZmCe9QxyRz7OMX58MBwAFqiLg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 13:32:48 -0000

Hi,

Be aware tyat if somebody edits it while you are editing it, your
edits might need to be discarded.
Work incrementally (i.e. save your changes often) to minimize the
chance of conflict.
Trac doesn't have a concept of locking work that is checked out.
I lost about an hour's worth of work when Dave Crocker added the link
to the legends page.

dbh

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Wednesday, February 10, 2010 5:49 AM
> To: ops-area@ietf.org; ops-chairs@ietf.org
> Subject: [OPS-AREA] again about ietf-outcomes
> 
> David Harrington put some work in improving the content of 
> the wiki page
> at 
> http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations in what
> concerns SNMP and SMI. It would be good if other folks have a look
and
> especially if they can spare some time adding more exact and
detailed
> information related to the other management protocols. 
> 
> Dan
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


From dhc@dcrocker.net  Tue Feb  9 08:20:21 2010
Return-Path: <dhc@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3514D3A73F5; Tue,  9 Feb 2010 08:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2FpXdgn-sHH9; Tue,  9 Feb 2010 08:20:20 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 3F7D43A73E9; Tue,  9 Feb 2010 08:20:20 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o19GLJeG001587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2010 08:21:24 -0800
Message-ID: <4B718B7B.6000401@dcrocker.net>
Date: Tue, 09 Feb 2010 08:21:15 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>	<048101caa80f$db2ee5a0$0600a8c0@china.huawei.com>	<E25EFA3754F74B2AB6D11BBA3685FD70@BertLaptop>	<4B70F71B.7080804@bogus.com>	<BLU137-DS5E874A567D6039C93F14793500@phx.gbl> <064301caa99f$fb5f6e30$0600a8c0@china.huawei.com>
In-Reply-To: <064301caa99f$fb5f6e30$0600a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10371/Tue Feb 9 05:33:13 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Feb 2010 08:21:24 -0800 (PST)
X-Mailman-Approved-At: Wed, 10 Feb 2010 06:47:30 -0800
Cc: ietf-outcomes@ietf.org, "'ops-area \(IETF\)'" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [ietf-outcomes]  IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 16:20:21 -0000

Dave,

On 2/9/2010 7:53 AM, David Harrington wrote:
> Hi,
>
> I think it would be good to set success and failure to match rfc 5218,
> and have the legends page provide brief descriptions of the
> categories, and reference RFC 5218 for more details.


The easy question is:  why?

The definition in RFC 5218 is:

      "we consider a successful protocol to be one that both meets its original
      goals and is widely deployed."

This means that a protocol is a failure if it is widely used, but for different 
purposes than it was intended.

"Deployed" is also a problem, since there is a long track record of industry's 
having deployed something but never actually using it very much.  I submit all 
of OSI as a prime example.

      These are the reasons the wiki was premised on the simple measure of use.

However I note that the column that lists degree of success only uses the word 
'adoption'. However Target Segment uses 'use'.

d/

ps.  I also note you've been busy updating net management-related entries.  Thanks!

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From wjhns1@hardakers.net  Wed Feb 10 07:04:41 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B18D3A771F; Wed, 10 Feb 2010 07:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 OTO2LhiwbfVS; Wed, 10 Feb 2010 07:04:40 -0800 (PST)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id 5AEBB3A73BC; Wed, 10 Feb 2010 07:04:40 -0800 (PST)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 98C829808F; Wed, 10 Feb 2010 07:05:50 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "David Harrington" <ietfdbh@comcast.net>
Organization: Sparta
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com> <072201caaa55$b25e3160$0600a8c0@china.huawei.com>
Date: Wed, 10 Feb 2010 07:05:50 -0800
In-Reply-To: <072201caaa55$b25e3160$0600a8c0@china.huawei.com> (David Harrington's message of "Wed, 10 Feb 2010 08:33:57 -0500")
Message-ID: <sd3a19cer5.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.4.22 (linux, no MULE)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ops-chairs@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 15:04:41 -0000

>>>>> On Wed, 10 Feb 2010 08:33:57 -0500, "David Harrington" <ietfdbh@comcast.net> said:

DH> I lost about an hour's worth of work when Dave Crocker added the link
DH> to the legends page.

With all group collaboration projects, frequent check-ins are
encouraged.

Good wiki software like mediawiki at least warns you about conflicts...
-- 
Wes Hardaker
Cobham Analytic Solutions

From wjhns1@hardakers.net  Wed Feb 10 07:07:53 2010
Return-Path: <wjhns1@hardakers.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8DF23A771F; Wed, 10 Feb 2010 07:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 g3tAUjwo1yRP; Wed, 10 Feb 2010 07:07:53 -0800 (PST)
Received: from mail.hardakers.net (hardaker-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::af]) by core3.amsl.com (Postfix) with ESMTP id CE9AB3A73BC; Wed, 10 Feb 2010 07:07:52 -0800 (PST)
Received: from localhost (wjh.hardakers.net [10.0.0.2]) by mail.hardakers.net (Postfix) with ESMTPSA id 31DF798095; Wed, 10 Feb 2010 07:09:03 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "Romascanu\, Dan \(Dan\)" <dromasca@avaya.com>
Organization: Sparta
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com>
Date: Wed, 10 Feb 2010 07:09:02 -0800
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com> (Dan Romascanu's message of "Wed, 10 Feb 2010 11:49:26 +0100")
Message-ID: <sdy6j1b01d.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110011 (No Gnus v0.11) XEmacs/21.4.22 (linux, no MULE)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ops-chairs@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 15:07:53 -0000

>>>>> On Wed, 10 Feb 2010 11:49:26 +0100, "Romascanu, Dan (Dan)" <dromasca@avaya.com> said:

DR> David Harrington put some work in improving the content of the wiki page
DR> at http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations in what
DR> concerns SNMP and SMI. It would be good if other folks have a look and
DR> especially if they can spare some time adding more exact and detailed
DR> information related to the other management protocols. 

Being the project leader of a major SNMP stack, I find it odd that we've
marked SNMPv3 as "poor adoption".  It's definitely deployed and adopted
from the perspective of what my users ask questions about.  It's
definitely confusing to many (or they wouldn't ask questions) and it's
definitely not as big of a percentage as we'd like (hence the need for
ISMS), but to say that it's "poor adoption" is a bit odd.  "Some" would
be a better marking, IMHO.  Definitely not "massive".  Unfortunately, we
don't have an "ehhh" marking.

-- 
Wes Hardaker
Cobham Analytic Solutions

From ietfdbh@comcast.net  Wed Feb 10 08:38:43 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2313428C1E2 for <ops-area@core3.amsl.com>; Wed, 10 Feb 2010 08:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 rXYc3Vp2OJ+7 for <ops-area@core3.amsl.com>; Wed, 10 Feb 2010 08:38:42 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [76.96.62.64]) by core3.amsl.com (Postfix) with ESMTP id 196BD3A7740 for <ops-area@ietf.org>; Wed, 10 Feb 2010 08:38:42 -0800 (PST)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta07.westchester.pa.mail.comcast.net with comcast id gC6G1d00A0vyq2s57GftUL; Wed, 10 Feb 2010 16:39:53 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta05.westchester.pa.mail.comcast.net with comcast id gGfs1d00N284sdk3RGftQA; Wed, 10 Feb 2010 16:39:53 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Wes Hardaker'" <wjhns1@hardakers.net>, "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com> <sdy6j1b01d.fsf@wjh.hardakers.net>
Date: Wed, 10 Feb 2010 11:39:51 -0500
Message-ID: <075101caaa6f$ab644f10$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <sdy6j1b01d.fsf@wjh.hardakers.net>
Thread-Index: AcqqYwB6SfDhjFjPRGOC2gZVY6SppwACm06w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: ops-chairs@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 16:38:43 -0000

Hi,

I didn't change the adoption column that was already set for snmpv3; I
have an obvious conflict of interest as snmpv3 wg chair. I would be
happy to see the ops area reach consensus on what the adoption column
should say.

I have discussed snmpv3 with a number of service provider operators
who tell me they definitely use snmpv3.

Here are my impressions, with very little evidence to support those
impressions:
There is the distinction between deployment and usage.
I believe snmpv3 is found in many devices. 
It had a slower adoption rate in NMS systems, but I think the major
NMS systems now support snmpv3. 
Many of the features are not used widely, and many are not used fully.
(I remember one case where VACM's per-user authorization was
supported, but they only allowed one user.)

Some environments are far more concerned about security than others,
and SNMPv3 gets used in security-conscious environments. 
Some environments have strict controls over management traffic using
techniques such as management VLANS, and operators for those networks
may feel that they have "enough" security using those approaches to
allow snmpv1/v2 to be used in a secure-enough manner, and they
obviously don't have demand for the additional features of SNMPv3.)

I would support "some adoption" with a target market of "environments
that require secure management".

dbh


> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Wes Hardaker
> Sent: Wednesday, February 10, 2010 10:09 AM
> To: Romascanu, Dan (Dan)
> Cc: ops-chairs@ietf.org; ops-area@ietf.org
> Subject: Re: [OPS-AREA] again about ietf-outcomes
> 
> >>>>> On Wed, 10 Feb 2010 11:49:26 +0100, "Romascanu, Dan 
> (Dan)" <dromasca@avaya.com> said:
> 
> DR> David Harrington put some work in improving the content 
> of the wiki page
> DR> at 
> http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations in what
> DR> concerns SNMP and SMI. It would be good if other folks 
> have a look and
> DR> especially if they can spare some time adding more exact 
> and detailed
> DR> information related to the other management protocols. 
> 
> Being the project leader of a major SNMP stack, I find it odd 
> that we've
> marked SNMPv3 as "poor adoption".  It's definitely deployed 
> and adopted
> from the perspective of what my users ask questions about.  It's
> definitely confusing to many (or they wouldn't ask questions) and
it's
> definitely not as big of a percentage as we'd like (hence the need
for
> ISMS), but to say that it's "poor adoption" is a bit odd.  
> "Some" would
> be a better marking, IMHO.  Definitely not "massive".  
> Unfortunately, we
> don't have an "ehhh" marking.
> 
> -- 
> Wes Hardaker
> Cobham Analytic Solutions
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


From dhc2@dcrocker.net  Wed Feb 10 09:58:57 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3798728C220; Wed, 10 Feb 2010 09:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 4cjn4CrJsZjB; Wed, 10 Feb 2010 09:58:56 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 40D2C28C159; Wed, 10 Feb 2010 09:58:56 -0800 (PST)
Received: from [192.168.1.68] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o1AHxtJt023694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Feb 2010 10:00:01 -0800
Message-ID: <4B72F419.5070801@dcrocker.net>
Date: Wed, 10 Feb 2010 09:59:53 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: David Harrington <ietfdbh@comcast.net>
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com> <072201caaa55$b25e3160$0600a8c0@china.huawei.com>
In-Reply-To: <072201caaa55$b25e3160$0600a8c0@china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10374/Tue Feb 9 23:05:12 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 10 Feb 2010 10:00:01 -0800 (PST)
Cc: ops-chairs@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 17:58:57 -0000

On 2/10/2010 5:33 AM, David Harrington wrote:
> Trac doesn't have a concept of locking work that is checked out.
> I lost about an hour's worth of work when Dave Crocker added the link
> to the legends page.

oh crap.  very sorry.  yeah, it's a limitation of this wiki software that it 
does not signal a conflict very well and doesn't retain the 'dropped' change. 
(If it any comfort, I've had major work also lost from this problem.)

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From fred@cisco.com  Wed Feb 10 10:03:13 2010
Return-Path: <fred@cisco.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5355128C24D; Wed, 10 Feb 2010 10:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Zu3zDhrrytlr; Wed, 10 Feb 2010 10:03:12 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 286C928C254; Wed, 10 Feb 2010 10:03:12 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAN+DckurRN+J/2dsb2JhbACaY3SlKJdphFUE
X-IronPort-AV: E=Sophos;i="4.49,445,1262563200"; d="scan'208";a="86311770"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 10 Feb 2010 18:04:23 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o1AI4Iqn005895; Wed, 10 Feb 2010 18:04:23 GMT
Message-Id: <A60278B8-6D6D-4484-9ACA-6F985BEF6D78@cisco.com>
From: Fred Baker <fred@cisco.com>
To: David Harrington <ietfdbh@comcast.net>
In-Reply-To: <075101caaa6f$ab644f10$0600a8c0@china.huawei.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 10 Feb 2010 10:04:17 -0800
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com> <sdy6j1b01d.fsf@wjh.hardakers.net> <075101caaa6f$ab644f10$0600a8c0@china.huawei.com>
X-Mailer: Apple Mail (2.936)
X-Mailman-Approved-At: Thu, 11 Feb 2010 03:39:29 -0800
Cc: ops-area@ietf.org, ops-chairs@ietf.org
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 18:03:13 -0000

Along the lines of "secure management", Cisco's Lawful Intercept  
offering is controlled using SNMPv3, so anyone that uses it has to  
deploy and use SNMPv3. There is a recent Black hat discussion  
regarding that, and US Cert is likely to come back to your working  
group with a request for a change in the access control procedure -  
the message responding to an accepted access is different than the  
response to a denied access, which reveals information to an attacker.

On Feb 10, 2010, at 8:39 AM, David Harrington wrote:

> Hi,
>
> I didn't change the adoption column that was already set for snmpv3; I
> have an obvious conflict of interest as snmpv3 wg chair. I would be
> happy to see the ops area reach consensus on what the adoption column
> should say.
>
> I have discussed snmpv3 with a number of service provider operators
> who tell me they definitely use snmpv3.
>
> Here are my impressions, with very little evidence to support those
> impressions:
> There is the distinction between deployment and usage.
> I believe snmpv3 is found in many devices.
> It had a slower adoption rate in NMS systems, but I think the major
> NMS systems now support snmpv3.
> Many of the features are not used widely, and many are not used fully.
> (I remember one case where VACM's per-user authorization was
> supported, but they only allowed one user.)
>
> Some environments are far more concerned about security than others,
> and SNMPv3 gets used in security-conscious environments.
> Some environments have strict controls over management traffic using
> techniques such as management VLANS, and operators for those networks
> may feel that they have "enough" security using those approaches to
> allow snmpv1/v2 to be used in a secure-enough manner, and they
> obviously don't have demand for the additional features of SNMPv3.)
>
> I would support "some adoption" with a target market of "environments
> that require secure management".
>
> dbh
>
>
>> -----Original Message-----
>> From: ops-area-bounces@ietf.org
>> [mailto:ops-area-bounces@ietf.org] On Behalf Of Wes Hardaker
>> Sent: Wednesday, February 10, 2010 10:09 AM
>> To: Romascanu, Dan (Dan)
>> Cc: ops-chairs@ietf.org; ops-area@ietf.org
>> Subject: Re: [OPS-AREA] again about ietf-outcomes
>>
>>>>>>> On Wed, 10 Feb 2010 11:49:26 +0100, "Romascanu, Dan
>> (Dan)" <dromasca@avaya.com> said:
>>
>> DR> David Harrington put some work in improving the content
>> of the wiki page
>> DR> at
>> http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations in what
>> DR> concerns SNMP and SMI. It would be good if other folks
>> have a look and
>> DR> especially if they can spare some time adding more exact
>> and detailed
>> DR> information related to the other management protocols.
>>
>> Being the project leader of a major SNMP stack, I find it odd
>> that we've
>> marked SNMPv3 as "poor adoption".  It's definitely deployed
>> and adopted
>> from the perspective of what my users ask questions about.  It's
>> definitely confusing to many (or they wouldn't ask questions) and
> it's
>> definitely not as big of a percentage as we'd like (hence the need
> for
>> ISMS), but to say that it's "poor adoption" is a bit odd.
>> "Some" would
>> be a better marking, IMHO.  Definitely not "massive".
>> Unfortunately, we
>> don't have an "ehhh" marking.
>>
>> -- 
>> Wes Hardaker
>> Cobham Analytic Solutions
>> _______________________________________________
>> OPS-AREA mailing list
>> OPS-AREA@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-area
>>
>

http://www.ipinc.net/IPv4.GIF


From mrm@vmware.com  Thu Feb 11 10:52:16 2010
Return-Path: <mrm@vmware.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DDD83A7875 for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 10:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 duawZrHNZJIT for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 10:52:15 -0800 (PST)
Received: from smtp-outbound-2.vmware.com (smtp-outbound-2.vmware.com [65.115.85.73]) by core3.amsl.com (Postfix) with ESMTP id CCDE23A7874 for <ops-area@ietf.org>; Thu, 11 Feb 2010 10:52:15 -0800 (PST)
Received: from mailhost3.vmware.com (mailhost3.vmware.com [10.16.27.45]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 789FF2904D for <ops-area@ietf.org>; Thu, 11 Feb 2010 10:53:31 -0800 (PST)
Received: from pa-excaht03.vmware.com (pa-excaht03.vmware.com [10.113.81.154]) by mailhost3.vmware.com (Postfix) with ESMTP id 71ED9CDA90 for <ops-area@ietf.org>; Thu, 11 Feb 2010 10:53:31 -0800 (PST)
Received: from EXCH-MBX-3.vmware.com ([10.113.81.228]) by pa-excaht03.vmware.com ([10.113.81.154]) with mapi; Thu, 11 Feb 2010 10:53:31 -0800
From: Michael MacFaden <mrm@vmware.com>
To: "ops-area@ietf.org" <ops-area@ietf.org>
Date: Thu, 11 Feb 2010 10:52:35 -0800
Thread-Topic: [OPS-AREA] IETF Outcomes wiki
Thread-Index: Acqn+3pM1EGX3BVCRieqVntPDossiwBA0QWoAJMoaug=
Message-ID: <35203D411DF5144CACC340A56A90E564965BA4C0@EXCH-MBX-3.vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com>, <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop>, <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com>
In-Reply-To: <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.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
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 18:52:16 -0000

To add to Fred's post, here was the discussion I saw on nanog list:
http://mailman.nanog.org/pipermail/nanog/2010-February/017900.html

Mike MacFaden

From j.schoenwaelder@jacobs-university.de  Thu Feb 11 11:17:05 2010
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CFEE28C208 for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 11:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.07
X-Spam-Level: 
X-Spam-Status: No, score=-2.07 tagged_above=-999 required=5 tests=[AWL=0.179,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 wKUWnJ7WDjEG for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 11:17:04 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by core3.amsl.com (Postfix) with ESMTP id 35DB03A7040 for <ops-area@ietf.org>; Thu, 11 Feb 2010 11:17:04 -0800 (PST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 25532C0033; Thu, 11 Feb 2010 20:18:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id w633VryDjCa2; Thu, 11 Feb 2010 20:18:18 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id BE8CDC0008; Thu, 11 Feb 2010 20:18:17 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 47BB5105CFEE; Thu, 11 Feb 2010 20:18:04 +0100 (CET)
Date: Thu, 11 Feb 2010 20:18:04 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Michael MacFaden <mrm@vmware.com>
Message-ID: <20100211191804.GB57728@elstar.local>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com> <14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop> <35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com> <35203D411DF5144CACC340A56A90E564965BA4C0@EXCH-MBX-3.vmware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <35203D411DF5144CACC340A56A90E564965BA4C0@EXCH-MBX-3.vmware.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ops-area@ietf.org" <ops-area@ietf.org>
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 19:17:05 -0000

On Thu, Feb 11, 2010 at 07:52:35PM +0100, Michael MacFaden wrote:
> 
> To add to Fred's post, here was the discussion I saw on nanog list:
> http://mailman.nanog.org/pipermail/nanog/2010-February/017900.html

Lots of talk but I did not see what the technical issue is. Does
anyone have a pointer to technical information?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From ietfdbh@comcast.net  Thu Feb 11 11:25:50 2010
Return-Path: <ietfdbh@comcast.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 541FA3A6926 for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 11:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 9TPkCxWmj7Im for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 11:25:48 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by core3.amsl.com (Postfix) with ESMTP id C68C13A746C for <ops-area@ietf.org>; Thu, 11 Feb 2010 11:25:47 -0800 (PST)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta05.westchester.pa.mail.comcast.net with comcast id gbZj1d0050vyq2s55jS5QH; Thu, 11 Feb 2010 19:26:05 +0000
Received: from Harrington73653 ([24.147.240.98]) by omta05.westchester.pa.mail.comcast.net with comcast id gjT31d002284sdk3RjT381; Thu, 11 Feb 2010 19:27:03 +0000
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Juergen Schoenwaelder'" <j.schoenwaelder@jacobs-university.de>, "'Michael MacFaden'" <mrm@vmware.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F0D8DA@307622ANEX5.global.avaya.com><14E08E4D45C940DCAAD6B16C39510F6E@BertLaptop><35203D411DF5144CACC340A56A90E564965BA495@EXCH-MBX-3.vmware.com><35203D411DF5144CACC340A56A90E564965BA4C0@EXCH-MBX-3.vmware.com> <20100211191804.GB57728@elstar.local>
Date: Thu, 11 Feb 2010 14:26:57 -0500
Message-ID: <086701caab50$2d354680$0600a8c0@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <20100211191804.GB57728@elstar.local>
Thread-Index: AcqrTvwrcK3HyGDFTnCcAx72UtT9wQAASwmg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] IETF Outcomes wiki
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 19:25:50 -0000

http://www.blackhat.com/presentations/bh-dc-10/Cross_Tom/BlackHat-DC-2
010-Cross-Attacking-LawfulI-Intercept-slides.pdf

dbh 

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Juergen
Schoenwaelder
> Sent: Thursday, February 11, 2010 2:18 PM
> To: Michael MacFaden
> Cc: ops-area@ietf.org
> Subject: Re: [OPS-AREA] IETF Outcomes wiki
> 
> On Thu, Feb 11, 2010 at 07:52:35PM +0100, Michael MacFaden wrote:
> > 
> > To add to Fred's post, here was the discussion I saw on nanog
list:
> > http://mailman.nanog.org/pipermail/nanog/2010-February/017900.html
> 
> Lots of talk but I did not see what the technical issue is. Does
> anyone have a pointer to technical information?
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


From dhc2@dcrocker.net  Thu Feb 11 12:39:16 2010
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 327283A6F19 for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 12:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9xkW8O2X7MbT for <ops-area@core3.amsl.com>; Thu, 11 Feb 2010 12:39:15 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 49D0E3A6926 for <ops-area@ietf.org>; Thu, 11 Feb 2010 12:39:15 -0800 (PST)
Received: from [192.168.1.43] (adsl-68-122-70-87.dsl.pltn13.pacbell.net [68.122.70.87]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id o1BKePe1026086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ops-area@ietf.org>; Thu, 11 Feb 2010 12:40:31 -0800
Message-ID: <4B746B34.6040308@dcrocker.net>
Date: Thu, 11 Feb 2010 12:40:20 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: ops-area@ietf.org
References: <EDC652A26FB23C4EB6384A4584434A0401F0E0A4@307622ANEX5.global.avaya.com>	<sdy6j1b01d.fsf@wjh.hardakers.net>	<075101caaa6f$ab644f10$0600a8c0@china.huawei.com> <A60278B8-6D6D-4484-9ACA-6F985BEF6D78@cisco.com>
In-Reply-To: <A60278B8-6D6D-4484-9ACA-6F985BEF6D78@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.92/10382/Thu Feb 11 10:54:02 2010 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 11 Feb 2010 12:40:31 -0800 (PST)
Subject: Re: [OPS-AREA] again about ietf-outcomes
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 20:39:16 -0000

On 2/10/2010 10:04 AM, Fred Baker wrote:
> Along the lines of "secure management", Cisco's Lawful Intercept
> offering is controlled using SNMPv3, so anyone that uses it has to
> deploy and use SNMPv3.

David H modified the wiki entry concerning this, but folks might want to take a 
look, and see whether they believe it needs more refinement:

    <http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations>

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From heard@pobox.com  Sun Feb 14 15:04:04 2010
Return-Path: <heard@pobox.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DC8B28C14F for <ops-area@core3.amsl.com>; Sun, 14 Feb 2010 15:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xg+0UC8yUPOI for <ops-area@core3.amsl.com>; Sun, 14 Feb 2010 15:04:03 -0800 (PST)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by core3.amsl.com (Postfix) with ESMTP id 9EA2128C151 for <ops-area@ietf.org>; Sun, 14 Feb 2010 15:04:03 -0800 (PST)
Received: (qmail 18974 invoked from network); 14 Feb 2010 15:05:31 -0800
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Feb 2010 15:05:31 -0800
X-Return-Path: <heard@pobox.com>
X-Delivered-To: 2-heard@mail4.bayarea.net
X-Received: (qmail 14753 invoked from network); 14 Feb 2010 11:32:28 -0800
X-Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Feb 2010 11:32:27 -0800
Date: Sun, 14 Feb 2010 11:32:27 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF Outcomes <ietf-outcomes@ietf.org>, OPS AREA <ops-area@ietf.org>
Message-ID: <Pine.LNX.4.64.1002141115190.6399@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
ReSent-Date: Sun, 14 Feb 2010 15:05:18 -0800 (PST)
ReSent-From: "C. M. Heard" <heard@pobox.com>
ReSent-To: OPS AREA <ops-area@ietf.org>
ReSent-Subject: Suggested corrections to OPS wiki page
ReSent-Message-ID: <Pine.LNX.4.64.1002141505180.15955@shell4.bayarea.net>
Subject: [OPS-AREA] Suggested corrections to OPS wiki page
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Feb 2010 23:04:04 -0000

Hello,

The first column of the following

http://trac.tools.ietf.org/misc/outcomes/wiki/IetfOperations

describes SMIv1.  In order for this to reflect the SMIv1 that was 
widely adopted and practiced (and the one listed under STD0016 and 
in our older MIB boilerplate), the RFCs column should show 1155, 
1212, and 1215, and the "Date Issued" should show 1991.  Also, the 
"Years to Develop" should be bumped from 2 to 3 (noting that RFC 
1065 was published in 1988, that may understate the development 
time, but I don't know enough of the history to be sure).

Also, would it be appropriate to show the '>' symbol ("prompted 
extensive derivative work") for both SMIv1 and SNMPv1, since these 
led directly to SMIv2 and SNMPv3 respectively?

Mike Heard

From dromasca@avaya.com  Tue Feb 16 02:25:43 2010
Return-Path: <dromasca@avaya.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 952383A7CBF; Tue, 16 Feb 2010 02:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073,  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 VLWBTkt3efc8; Tue, 16 Feb 2010 02:25:42 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id CD4B83A7CBD; Tue, 16 Feb 2010 02:25:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,483,1262581200"; d="scan'208";a="176587959"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2010 05:27:14 -0500
X-IronPort-AV: E=Sophos;i="4.49,483,1262581200"; d="scan'208";a="446158391"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Feb 2010 05:27:12 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Feb 2010 11:27:13 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401F492B5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Policy MIB stringprep profile
Thread-Index: Acqu8prf1vsdgQVsQYCutwEcVBLPhw==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, <ops-area@ietf.org>
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>, Peter Saint-Andre <stpeter@stpeter.im>, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: [OPS-AREA] FW: Policy MIB stringprep profile
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2010 10:25:43 -0000

Folks who participated in the Policy MIB work may be interested in this
discussion and can possibly help to answer the questions.=20

Dan


-----Original Message-----
From: Peter Saint-Andre [mailto:stpeter@stpeter.im]=20
Sent: Monday, February 15, 2010 4:35 AM
To: waldbusser@nextbeacon.com; saperia@jdscons.com;
hongal@riverstonenet.com
Cc: Marc Blanchet; Alexey.Melnikov@isode.com
Subject: Policy MIB stringprep profile

Gentlemen,

The IETF will hold a BoF at IETF 77 (in Anaheim the week of March 22)
about possible replacements for stringprep. I notice that you three
authored of one of the few stringprep profiles, for Policy MIB (RFC
4011). Marc Blanchet and I will be co-chairing the BoF, and we're
seeking input from authors of all stringprep profiles regarding the
possibility of pursuing new approaches to internationalized strings, as
has happened already for internationalized domain names through the
IDNAbis WG. A proposed charter for a "newprep" working group is here:

http://www.ietf.org/mail-archive/web/newprep/current/msg00000.html

See also subsequent discussion on the list:

https://www.ietf.org/mailman/listinfo/newprep

However, we don't necessarily wish to form yet another WG, and one
perfectly acceptable outcome of the BoF would be agreement to pursue any
needed work through independent submissions that update existing work in
this area.

As input to our thinking, would you perhaps have time to post to the
newprep list regarding industry experience with the Policy MIB profile?
We're especially interested in answers to the following questions:

* Approximately what percentage of relevant software has implemented and
deployed the profile?

* How have developers implemented the profile (e.g., by including or
wrapping an existing library such as libidn, or by writing an
independent implementation)?

* Have developers experienced any interoperability issues or other
problems with the profile?

* Might there be developer interest in migrating from the profile to an
approach that is less complex (e.g., by specifying a tiered model of
valid, disallowed, and unassigned characters as in IDNAbis) or more
flexible (e.g., by enabling the use of characters beyond Unicode 3.2 as
fixed by RFC 3454)?

[Alexey and Marc, feel free to modify or add to these questions.]

I plan to post to the newprep list soon regarding the XMPP experience
with stringprep, so perhaps you (or someone else in the network
management community) could take that as a bit of a template.

Any other feedback you might have would be much appreciated.

Thanks for your time.

Peter

--
Peter Saint-Andre
https://stpeter.im/




From hannu.hietalahti@nokia.com  Tue Feb 16 22:43:19 2010
Return-Path: <hannu.hietalahti@nokia.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2911D3A7E5F for <ops-area@core3.amsl.com>; Tue, 16 Feb 2010 22:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 LGr+x2LgWBiI for <ops-area@core3.amsl.com>; Tue, 16 Feb 2010 22:43:18 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 39AE23A7E5E for <ops-area@ietf.org>; Tue, 16 Feb 2010 22:43:16 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o1H6ioC7005465 for <ops-area@ietf.org>; Wed, 17 Feb 2010 08:44:51 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Feb 2010 08:44:45 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Feb 2010 08:44:40 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Wed, 17 Feb 2010 07:44:39 +0100
From: <hannu.hietalahti@nokia.com>
To: <ops-area@ietf.org>
Date: Wed, 17 Feb 2010 07:44:38 +0100
Thread-Topic: Updated 3GPP - IETF draft dependency list
Thread-Index: AcqvnKz3//UmB0pBQJGRjZGAMOV8SQ==
Message-ID: <15443028349C3C44BA819EB51B3B4F3C571F67B298@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_15443028349C3C44BA819EB51B3B4F3C571F67B298NOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Feb 2010 06:44:40.0416 (UTC) FILETIME=[AE19B600:01CAAF9C]
X-Nokia-AV: Clean
Subject: [OPS-AREA] Updated 3GPP - IETF draft dependency list
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2010 06:43:19 -0000

--_000_15443028349C3C44BA819EB51B3B4F3C571F67B298NOKEUMSG01mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear OPS,


please find the latest version of the 3GPP - IETF dependency document at ht=
tp://www.3gpp.org/IETF-Dependencies-and-Priorities

BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724



--_000_15443028349C3C44BA819EB51B3B4F3C571F67B298NOKEUMSG01mgd_
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"Arial, sans-serif" size=3D"2">
<div>Dear OPS,</div>
<div>&nbsp;</div>
<div style=3D"margin-top: 5pt; margin-bottom: 5pt; ">please find the latest=
 version of the 3GPP - IETF dependency document at <a href=3D"http://www.3g=
pp.org/IETF-Dependencies-and-Priorities"><font face=3D"Times New Roman, ser=
if" size=3D"3" color=3D"#0000FF"><u>http://www.3gpp.org/IETF-Dependencies-a=
nd-Priorities</u></font></a></div>
<div>&nbsp;</div>
<div>BR,</div>
<div>Hannu Hietalahti</div>
<div>3GPP TSG CT Chairman</div>
<div>tel: &#43;358 40 5021724</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_15443028349C3C44BA819EB51B3B4F3C571F67B298NOKEUMSG01mgd_--

From hannu.hietalahti@nokia.com  Fri Feb 19 04:24:23 2010
Return-Path: <hannu.hietalahti@nokia.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FCD03A7B18; Fri, 19 Feb 2010 04:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 shubR9rlkApA; Fri, 19 Feb 2010 04:24:09 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id E7D0F3A7855; Fri, 19 Feb 2010 04:24:07 -0800 (PST)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o1JCPoHp029660; Fri, 19 Feb 2010 14:25:51 +0200
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Feb 2010 14:25:50 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Feb 2010 14:25:45 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Fri, 19 Feb 2010 13:25:44 +0100
From: <hannu.hietalahti@nokia.com>
To: <int-area@ietf.org>, <rai@ietf.org>, <ops-area@ietf.org>
Date: Fri, 19 Feb 2010 13:25:43 +0100
Thread-Topic: Minutes of 3GPP - IETF teleconference 17th Feb 2010
Thread-Index: AcqxXqgKAtybxm3lSTWX4gFsQc6Qvg==
Message-ID: <15443028349C3C44BA819EB51B3B4F3C571F6C9057@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_15443028349C3C44BA819EB51B3B4F3C571F6C9057NOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Feb 2010 12:25:45.0263 (UTC) FILETIME=[A8ED0BF0:01CAB15E]
X-Nokia-AV: Clean
Subject: [OPS-AREA] Minutes of 3GPP - IETF teleconference 17th Feb 2010
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 12:24:23 -0000

--_000_15443028349C3C44BA819EB51B3B4F3C571F6C9057NOKEUMSG01mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,

please find below the meeting minutes from the 3GPP - IETF teleconference o=
n the 17th of February 2010. The same minutes are shared on four mailing li=
sts: 3GPP TSG CT, IETF RAI, INT, OPS.

Dependency document on 3GPP website will be updated soon for the coming Mar=
ch TSG plenaries.

Date: 17th Feb 2010
Time: 16:00 - 18:00 UTC
Venue: Phone conference
Participants:
Hannu Hietalahti (notetaker)
Milan Patel
Atle Monrad
Gonzalo Camarillo
Tom Tailor
Scott Lawrence
Hannes Tschofenig
Mary Barnes
Adam Roach
Jari Arkko
Ben Campbell
Julien Laganier
Spencer Dawkins
Ralph Droms
Marc Linsner

Agenda:
-------------
1. Roll call
2. Review of action points
3. Joint workshop on IPv6 in March 2010
4. IANA registrations
5. Emergency calls
6. Review of 3GPP IETF dependency document
7. Next meeting
8. AOB
9. Closing


1.      Roll call
All participants are listed above.

2.      REview of action points
AP      Title   Responsible     Status
1       Request expert comments on the best approach to IANA registration o=
f Service ID namespace assignment    Mary Barnes     Closed
2       Check the registration status of IANA registration of 3gpp-ims+xml =
     Cullen Jennings Closed
3       Provide a written explanation of why it could be considered that IA=
NA registration of feature tags g.3gpp.icsi and g.3gpp.iari could proceed a=
ccording to RFC 2506 without procedural change    Atle Monrad     Closed
4       Escalate the previous summary by Atle for RAI leadership review dur=
ing IETF #74 to find a recommended way forward       Cullen Jennings Closed
5       Report the SA3 meeting outcome to Jari Arkko    Valtteri Niemi  Clo=
sed
6       Arrange a telco on media security on Friday the 7th of Nov 2008 Val=
tteri Niemi  Closed
 7      Find the original 3gpp-ims+xml registration document and forward it=
 to Cullen   Hannu Hietalahti        Closed
8       Set up a meeting between 3GPP and IETF to agree how to proceed in t=
he IANA registration of feature tags g.3gpp.icsi and g.3gpp.iari     Gonzal=
o Camarillo       Closed
9       Check the real 3GPP need for draft-arkko-mext-rfc3775-altcoa-check =
     Raj Patil       Closed
10      Hannu to ask on CT1 mailing list if anyone knows any reason why pho=
nebcp -draft would not be applicable in cellular environment Hannu   Closed
        New APs assigned in this meeting
11      Check the status of IANA registration of EAP-AKA attributes require=
d by 3GPP    Jari Arkko      done
12      Jari Arkko as the sponsor of draft-das-mipshop-andsf-dhcp-options n=
eeds to know of any changes in the requirements from 3GPP side where the di=
scussion on the 3GPP TS 24.302 requirements for ANDSF discovery are still o=
ngoing. Hannu to inform Jari of 3GPP decisions in this area.   Hannu Hietal=
ahti        Open
13      The status of draft-mmusic-ice-tcp is marked dead in I-D Tracker, b=
ut a new version has been since then submitted. Hannu to find out from the =
responsible AD (Cullen) whether 3GPP should expect the draft to remain dead=
 or not?       Hannu Hietalahti        done
14


3.      Joint workshop in March 2010
The planning of IPv6 migration workshop in San Francisco on 1 - 2 March 201=
0 is well underway by the co-chairs Fred Baker and Balazs Bertenyi.

This workshop is informative and any agreements still need to be documented=
 according to normal working procedures in IETF or 3GPP or both, as applica=
ble.

4.      IANA registrations
All pending IANA registrations related with 3GPP work are expected to progr=
ess as part of the work when the related drafts become RFCs.

It was not known at the time of meeting whether there is an open item in IA=
NA registration of EAP-AKA attributes. Jari Arkko volunteered to check the =
status (AP 11).

5.      Emergency calls
Feedback mechanism via option tag has been discussed draft-patel-ecrit-sos-=
parameter to inform the UE whether the request was understood by the regist=
rar or not. The latest version does not add the option tag, but adds an exp=
lanation of why emergency registration is needed is added and what happens =
if the registrar does not support the URI parameter in registration request=
. This draft has been agreed to progress as AD sponsored document (Cullen J=
ennings)

Callback has also been discussed recently in ECRIT and the work is progress=
ing. Possible future work area may raise in non-voice emergency calls. The =
requirements need to be identified first and it was assumed (but not confir=
med during the meeting) that NENA would be liaising to 3GPP on non-voice em=
ergency calls.

Callback is removed from 3GPP Rel-9 requirements but this does not mean tha=
t 3GPP is abandoning that requirement. This decision should be considered a=
s commitment to use IETF based approach for callback indication and giving =
more time to get it completed.

6.      Review of 3GPP - IETF dependency document
The following new Rel-8 dependencies have been identified since the previou=
s update of the dependency document:
*       draft-ietf-sipcore-invfix
*       draft-ietf-sip-ipv6-abnf-fix
*       draft-ietf-mmusic-ice-tcp
*       draft-ietf-sipcore-keep
*       draft-ietf-mediactrl-vxml
*       draft-ietf-mediactrl-sip-control-framework
*       draft-ietf-mediactrl-ivr-control-package
*       draft-ietf-mediactrl-mixer-control-package
*       draft-kaplan-dispatch-session-id

draft-ietf-simple-xcap-diff: Waiting for AD go-ahead in Sep 2009 (Robert Sp=
arks) New version published in Jan 2010. It is being evaluated whether WG s=
till needs to re-review this draft.

draft-ietf-simple-common-policy-caps: The draft has expired, and is not goi=
ng to proceed to RFC. CT1 needs to take out the reference from 24.141

draft-ietf-sip-xcapevent and draft-sipping-config-framework: CT1 have repla=
ced their references to config-framework with refs to xcapevent. SA4 have a=
lso analysed their situation and intend to keep using config-framework in 3=
GPP TS 26.237.

draft-ietf-ipv6-abnf-fix will progress as AD sponsored draft (Robert Sparks=
).

draft-drage-sipping-rfc3455bis has expired but it will be needed by 3GPP. I=
t has been agreed to discuss among the interested people in San Francisco d=
uring CT1 #63 meeting week how to progress this work. The draft should prog=
ress as AD sponsored draft and further discussions on IETF side should take=
 place on SIPPING list.

draft-dime-qos-attributes is now an RFC.

draft-patel-dispatch-cpc-oli-parameter replaces draft-mahy-iptlel-cpc. This=
 work is expected to spin of a new mini-WG under DISPATCH.

draft-drage-sipping-service-identification has been in IESG evaluation sinc=
e September 2009 and revised draft is needed to handle the comments that ha=
ve been made.

draft-ietf-mmusic-sdp-capability-negotiation has been in IESG evaluation si=
nce June 2009, revised ID is needed and we are waiting for new version. New=
 version was submitted and it has been requested that this draft should go =
back to WG

draft-uy-tel-dai is indicated as dead in I-D tracker. There has been intent=
ion to submit a new version to DISPATCH, but that has not happened yet. New=
 version of the draft would need to be submitted.

draft-netlmm-pmip6-ipv4-support is in IESG evaluation since Nov 2009 and ha=
s received comments in IPSec area. Substantial re-write of the draft to add=
ress the comments has received rough consensus. AD review of the new versio=
n is still required before asking for IESG approval

draft-ietf-mip4-rfc3344bis has been revised to new draft version in Jan 201=
0. It is waiting for shepherd writeup. There has been very little activity =
in TSG CT on 24.304 recently as the latest versions do not require changes =
in 3GPP TSs, so CT1 is waiting for the draft to be completed.

draft-johnston-sipping-cc-uui has been revised to draft-johnston-dispatch-c=
c-uui. CT1 needs to update 24.229. It has been agreed to charter a new mini=
-WG to handle this draft.

draft-jesske-sipping-etsi-ngn-reason is replaced with draft-jesske-dispatch=
-reason-in-responses. The editor has been requested to split out the protoc=
ol changes from the use cases more clearly

draft-das-mipshop-andsf-dhcp-options proceeds as an AD sponsored draft (Jar=
i Arkko). MIPSHOP review was requested and that has now been passed. 3GPP n=
eeds to determine more precisely the use of the draft.

draft-vanelburg-sipping-private-network-indication has a new name under DIS=
PATCH WG and CT1 needs to check whether they have updated their specificati=
ons already. The authors need to drive this work in DISPATCH group.

draft-ietf-bliss-call-completion needs the editor to respond to technical i=
ssues that have been raised before the draft is ready for WG LC.

Two drafts have been merged to draft-dawes-sipping-debug and CT1 have alrea=
dy updated their specifications on this. It was agreed that the work on thi=
s draft will need to continue in DISPATCH.

draft-bakker-sipping-3gpp-ims-xml-body-handling will progress as AD sponsor=
ed draft (Cullen Jennings).

draft-mmusic-ice-tcp is marked as dead in IETF I-D tracker, but a new versi=
on has been distributed. 3GPP has got a reference towards this draft and ne=
eds to know whether the document is expected to progress or not.

7.      Next meeting
Hannu cannot participate IETF #77 so the next meeting was agreed to be a te=
lco on the last week of April 2010, with April 28 agreed as the tentative d=
ate.

8.      Any Other business
It was agreed to collect comments and revisions on these minutes until Frid=
ay the 19th of February 12:00 noon UTC so that Hannu can distribute the rev=
iewed and agreed version on 3GPP TSG CT mailing list and IETF RAI, INT and =
OPS mailing lists during the same day.

Jari Arkko gave the following comment via email after the meeting, to cover=
 his AP 11 from this meeting:

"IANA has an expert that reviews these requests (Vesa Lehtovirta). While he=
 was also specifying some of this work on the 3GPP side, in the IANA review=
 he did spot an issue in the way that the attribute bit fields are defined.=
 The issue is being rectified in CT1, they will handle a CR next week to fi=
x 24.302. Once this is approved, I think we are all set and the IANA alloca=
tion can be made."

Cullen Jennings made the following comment related with AP 13 on draft-mmus=
ic-ice-tcp from this meeting:

"This draft expired (no new version for 6 months) and for some reasons the =
idtracker moved it to dead when it expired. I'm not sure why this happened =
but I moved it back to AD-Watching. My understanding of the situation is th=
at the ietf community believes ice-tcp is needed and would like it to move =
forward but it needs a lot of work and the no one seems willing to put the =
time in to finish it. So with no one really moving ice-tcp forward, there i=
s not much happening on the SDP attributes for it. It is not making much fo=
rward progress right now."

9.      Closing
The meeting was closed at 17:50 UTC.



BR,
Hannu Hietalahti
3GPP TSG CT Chairman
tel: +358 40 5021724



--_000_15443028349C3C44BA819EB51B3B4F3C571F6C9057NOKEUMSG01mgd_
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"Arial, sans-serif" size=3D"2">
<div>Dear all,</div>
<div>&nbsp;</div>
<div>please find below the meeting minutes from the 3GPP - IETF teleconfere=
nce on the 17th of February 2010. The same minutes are shared on four maili=
ng lists: 3GPP TSG CT, IETF RAI, INT, OPS.</div>
<div>&nbsp;</div>
<div>Dependency document on 3GPP website will be updated soon for the comin=
g March TSG plenaries.</div>
<div>&nbsp;</div>
<div><font face=3D"Arial, sans-serif" size=3D"2"><b>Date:</b> 17<font size=
=3D"1"><sup>th</sup></font> Feb 2010</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2"><b>Time: </b>16:00 &#8211;=
 18:00 UTC</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2"><b>Venue:</b> Phone confer=
ence</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2"><b>Participants:</b></font=
></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Hannu Hietalahti (notetake=
r) </font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Milan Patel</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Atle Monrad</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Gonzalo Camarillo</font></=
div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Tom Tailor</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Scott Lawrence</font></div=
>
<div><font face=3D"Arial, sans-serif" size=3D"2">Hannes Tschofenig</font></=
div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Mary Barnes</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Adam Roach</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Jari Arkko</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Ben Campbell</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Julien Laganier</font></di=
v>
<div><font face=3D"Arial, sans-serif" size=3D"2">Spencer Dawkins</font></di=
v>
<div><font face=3D"Arial, sans-serif" size=3D"2">Ralph Droms</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Marc Linsner</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><b>Agenda:</b></font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">-------------</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">1. Roll call</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">2. Review of action points</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">3. Joint workshop on IPv6 in March 2010</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">4. IANA registrations</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">5. Emergency calls</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">6. Review of 3GPP IETF dependency document</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">7. Next meeting</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">8. AOB</font></div>
<div style=3D"padding-left: 36pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">9. Closing</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>1.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </b></span><span style=3D"text-transform: uppercase;"><b>Roll ca=
ll</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">All participants are liste=
d above.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>2.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; </b></span><span style=3D"text-transform: uppercase;"><b>REview =
of action points</b></span></font></div>
<table border=3D"1" width=3D"868" style=3D"border:1 solid; border-collapse:=
collapse; margin-left: -5pt; ">
<col width=3D"44">
<col width=3D"578">
<col width=3D"153">
<col width=3D"91">
<tr>
<td style=3D"background-color: #C0C0C0; "><font face=3D"Arial, sans-serif" =
size=3D"2"><b>AP</b></font></td>
<td style=3D"background-color: #C0C0C0; "><font face=3D"Arial, sans-serif" =
size=3D"2"><b>Title</b></font></td>
<td style=3D"background-color: #C0C0C0; "><font face=3D"Arial, sans-serif" =
size=3D"2"><b>Responsible</b></font></td>
<td style=3D"background-color: #C0C0C0; "><font face=3D"Arial, sans-serif" =
size=3D"2"><b>Status</b></font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">1</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Request expert comments on =
the best approach to IANA registration of Service ID namespace assignment</=
font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Mary Barnes</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">2</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Check the registration stat=
us of IANA registration of 3gpp-ims&#43;xml</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Cullen Jennings</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">3</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Provide a written explanati=
on of why it could be considered that IANA registration of feature tags g.3=
gpp.icsi and g.3gpp.iari could proceed according to RFC 2506 without proced=
ural change</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Atle Monrad</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">4</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Escalate the previous summa=
ry by Atle for RAI leadership review during IETF #74 to find a recommended =
way forward</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Cullen Jennings</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">5</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Report the SA3 meeting outc=
ome to Jari Arkko</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Valtteri Niemi</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">6</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Arrange a telco on media se=
curity on Friday the 7<font size=3D"1"><sup>th</sup></font> of Nov 2008</fo=
nt></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Valtteri Niemi</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2"> 7 </font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Find the original 3gpp-ims&=
#43;xml registration document and forward it to Cullen</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Hannu Hietalahti</font></td=
>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">8</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Set up a meeting between 3G=
PP and IETF to agree how to proceed in the IANA registration of feature tag=
s g.3gpp.icsi and g.3gpp.iari</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Gonzalo Camarillo</font></t=
d>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">9</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Check the real 3GPP need fo=
r draft-arkko-mext-rfc3775-altcoa-check</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Raj Patil</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">10</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Hannu to ask on CT1 mailing=
 list if anyone knows any reason why phonebcp &#8211;draft would not be app=
licable in cellular environment</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Hannu</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Closed</font></td>
</tr>
<tr>
<td style=3D"background-color: #B3B3B3; "><font face=3D"Arial, sans-serif" =
size=3D"2">&nbsp;</font></td>
<td style=3D"background-color: #B3B3B3; "><font face=3D"Arial, sans-serif" =
size=3D"2"><b>New APs assigned in this meeting</b></font></td>
<td style=3D"background-color: #B3B3B3; "><font face=3D"Arial, sans-serif" =
size=3D"2">&nbsp;</font></td>
<td style=3D"background-color: #B3B3B3; "><font face=3D"Arial, sans-serif" =
size=3D"2">&nbsp;</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">11</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Check the status of IANA re=
gistration of EAP-AKA attributes required by 3GPP</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Jari Arkko</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">done</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">12</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Jari Arkko as the sponsor o=
f draft-das-mipshop-andsf-dhcp-options needs to know of any changes in the =
requirements from 3GPP side where the discussion on the 3GPP TS 24.302 requ=
irements for ANDSF discovery are still
ongoing. Hannu to inform Jari of 3GPP decisions in this area.</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Hannu Hietalahti</font></td=
>
<td><font face=3D"Arial, sans-serif" size=3D"2">Open</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">13</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">The status of draft-mmusic-=
ice-tcp is marked dead in I-D Tracker, but a new version has been since the=
n submitted. Hannu to find out from the responsible AD (Cullen) whether 3GP=
P should expect the draft to remain
dead or not? </font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">Hannu Hietalahti</font></td=
>
<td><font face=3D"Arial, sans-serif" size=3D"2">done</font></td>
</tr>
<tr>
<td><font face=3D"Arial, sans-serif" size=3D"2">14</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></td>
<td><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></td>
</tr>
</table>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>3.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Joint work</b></span><span style=3D"text-transform: uppercase;">=
<b>shop in March 2010</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">The planning of IPv6 migra=
tion workshop in San Francisco on 1 <font face=3D"Times New Roman, serif">&=
#8211;</font> 2 March 2010 is well underway by the co-chairs Fred Baker and=
 Balazs Bertenyi.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">This workshop is informati=
ve and any agreements still need to be documented according to normal worki=
ng procedures in IETF or 3GPP or both, as applicable.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>4.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; IANA registrations</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">All pending IANA registrat=
ions related with 3GPP work are expected to progress as part of the work wh=
en the related drafts become RFCs.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">It was not known at the ti=
me of meeting whether there is an open item in IANA registration of EAP-AKA=
 attributes. Jari Arkko volunteered to check the status (AP 11).</font></di=
v>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>5.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Emergency calls</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Feedback mechanism via opt=
ion tag has been discussed draft-patel-ecrit-sos-parameter to inform the UE=
 whether the request was understood by the registrar or not. The latest ver=
sion does not add the option tag, but
adds an explanation of why emergency registration is needed is added and wh=
at happens if the registrar does not support the URI parameter in registrat=
ion request. This draft has been agreed to progress as AD sponsored documen=
t (Cullen Jennings)</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Callback has also been dis=
cussed recently in ECRIT and the work is progressing. Possible future work =
area may raise in non-voice emergency calls. The requirements need to be id=
entified first and it was assumed (but
not confirmed during the meeting) that NENA would be liaising to 3GPP on no=
n-voice emergency calls.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Callback is removed from 3=
GPP Rel-9 requirements but this does not mean that 3GPP is abandoning that =
requirement. This decision should be considered as commitment to use IETF b=
ased approach for callback indication
and giving more time to get it completed.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>6.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Review of 3GPP </b></span><span style=3D"text-transform: upperca=
se;"><b>&#8211; IETF dependency document</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">The following new Rel-8 de=
pendencies have been identified since the previous update of the dependency=
 document:</font></div>
<ul style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: 36pt; ">
<font face=3D"Arial, sans-serif" size=3D"2">
<li>draft-ietf-sipcore-invfix</li><li>draft-ietf-sip-ipv6-abnf-fix</li><li>=
draft-ietf-mmusic-ice-tcp</li><li>draft-ietf-sipcore-keep</li><li>draft-iet=
f-mediactrl-vxml</li><li>draft-ietf-mediactrl-sip-control-framework</li><li=
>draft-ietf-mediactrl-ivr-control-package</li><li>draft-ietf-mediactrl-mixe=
r-control-package</li><li>draft-kaplan-dispatch-session-id</li></font>
</ul>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-simple-xcap-dif=
f: Waiting for AD go-ahead in Sep 2009 (Robert Sparks) New version publishe=
d in Jan 2010. It is being evaluated whether WG still needs to re-review th=
is draft.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-simple-common-p=
olicy-caps: The draft has expired, and is not going to proceed to RFC. CT1 =
needs to take out the reference from 24.141</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-sip-xcapevent a=
nd draft-sipping-config-framework: CT1 have replaced their references to co=
nfig-framework with refs to xcapevent. SA4 have also analysed their situati=
on and intend to keep using config-framework
in 3GPP TS 26.237.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-ipv6-abnf-fix w=
ill progress as AD sponsored draft (Robert Sparks).</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-drage-sipping-rfc345=
5bis has expired but it will be needed by 3GPP. It has been agreed to discu=
ss among the interested people in San Francisco during CT1 #63 meeting week=
 how to progress this work. The draft
should progress as AD sponsored draft and further discussions on IETF side =
should take place on SIPPING list.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-dime-qos-attributes =
is now an RFC.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-patel-dispatch-cpc-o=
li-parameter replaces draft-mahy-iptlel-cpc. This work is expected to spin =
of a new mini-WG under DISPATCH.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-drage-sipping-servic=
e-identification has been in IESG evaluation since September 2009 and revis=
ed draft is needed to handle the comments that have been made.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-mmusic-sdp-capa=
bility-negotiation has been in IESG evaluation since June 2009, revised ID =
is needed and we are waiting for new version. New version was submitted and=
 it has been requested that this draft
should go back to WG</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-uy-tel-dai is indica=
ted as dead in I-D tracker. There has been intention to submit a new versio=
n to DISPATCH, but that has not happened yet. New version of the draft woul=
d need to be submitted.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-netlmm-pmip6-ipv4-su=
pport is in IESG evaluation since Nov 2009 and has received comments in IPS=
ec area. Substantial re-write of the draft to address the comments has rece=
ived rough consensus. AD review of the
new version is still required before asking for IESG approval</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-mip4-rfc3344bis=
 has been revised to new draft version in Jan 2010. It is waiting for sheph=
erd writeup. There has been very little activity in TSG CT on 24.304 recent=
ly as the latest versions do not require
changes in 3GPP TSs, so CT1 is waiting for the draft to be completed.</font=
></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-johnston-sipping-cc-=
uui has been revised to draft-johnston-dispatch-cc-uui. CT1 needs to update=
 24.229. It has been agreed to charter a new mini-WG to handle this draft. =
</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-jesske-sipping-etsi-=
ngn-reason is replaced with draft-jesske-dispatch-reason-in-responses. The =
editor has been requested to split out the protocol changes from the use ca=
ses more clearly</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-das-mipshop-andsf-dh=
cp-options proceeds as an AD sponsored draft (Jari Arkko). MIPSHOP review w=
as requested and that has now been passed. 3GPP needs to determine more pre=
cisely the use of the draft. </font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-vanelburg-sipping-pr=
ivate-network-indication has a new name under DISPATCH WG and CT1 needs to =
check whether they have updated their specifications already. The authors n=
eed to drive this work in DISPATCH group.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-ietf-bliss-call-comp=
letion needs the editor to respond to technical issues that have been raise=
d before the draft is ready for WG LC.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Two drafts have been merge=
d to draft-dawes-sipping-debug and CT1 have already updated their specifica=
tions on this. It was agreed that the work on this draft will need to conti=
nue in DISPATCH.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-bakker-sipping-3gpp-=
ims-xml-body-handling will progress as AD sponsored draft (Cullen Jennings)=
.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">draft-mmusic-ice-tcp is ma=
rked as dead in IETF I-D tracker, but a new version has been distributed. 3=
GPP has got a reference towards this draft and needs to know whether the do=
cument is expected to progress or not.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>7.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Next meeting</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Hannu cannot participate I=
ETF #77 so the next meeting was agreed to be a telco on the last week of Ap=
ril 2010, with April 28 agreed as the tentative date.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>8.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Any Other business</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">It was agreed to collect c=
omments and revisions on these minutes until Friday the 19<font size=3D"1">=
<sup>th</sup></font> of February 12:00 noon UTC so that Hannu can distribut=
e the reviewed and agreed version on 3GPP
TSG CT mailing list and IETF RAI, INT and OPS mailing lists during the same=
 day.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Jari Arkko gave the follow=
ing comment via email after the meeting, to cover his AP 11 from this meeti=
ng:</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&#8220;IANA has an expert =
that reviews these requests (Vesa Lehtovirta). While he was also specifying=
 some of this work on the 3GPP side, in the IANA review he did spot an issu=
e in the way that the attribute bit fields
are defined. The issue is being rectified in CT1, they will handle a CR nex=
t week to fix 24.302. Once this is approved, I think we are all set and the=
 IANA allocation can be made.&#8221;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">Cullen Jennings made the f=
ollowing comment related with AP 13 on draft-mmusic-ice-tcp from this meeti=
ng:</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&#8220;<font face=3D"Couri=
er New, monospace" size=3D"2">This draft expired (no new version for 6 mont=
hs) and for some reasons the idtracker moved it to dead when it expired. I'=
m not sure why this happened but I moved it back
to AD-Watching. My understanding of the situation is that the ietf communit=
y believes ice-tcp is needed and would like it to move forward but it needs=
 a lot of work and the no one seems willing to put the time in to finish it=
. So with no one really moving ice-tcp
forward, there is not much happening on the SDP attributes for it. It is no=
t making much forward progress right now.</font>&#8221;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div style=3D"margin-bottom: 11pt; "><font face=3D"Arial, sans-serif" size=
=3D"2"><span style=3D"text-transform: uppercase;"><b>9.&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; Closing</b></span></font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">The meeting was closed at =
17:50 UTC.</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div><font face=3D"Arial, sans-serif" size=3D"2">&nbsp;</font></div>
<div>BR,</div>
<div>Hannu Hietalahti</div>
<div>3GPP TSG CT Chairman</div>
<div>tel: &#43;358 40 5021724</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_15443028349C3C44BA819EB51B3B4F3C571F6C9057NOKEUMSG01mgd_--

From saperia@jdscons.com  Fri Feb 19 11:42:07 2010
Return-Path: <saperia@jdscons.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50FC13A7D2F; Fri, 19 Feb 2010 11:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 lLXpEGGm+vak; Fri, 19 Feb 2010 11:42:06 -0800 (PST)
Received: from rs40.luxsci.com (rs40.luxsci.com [65.61.166.82]) by core3.amsl.com (Postfix) with ESMTP id 1E7F83A7D7D; Fri, 19 Feb 2010 11:42:05 -0800 (PST)
Received: from [10.0.1.2] (c-98-229-133-101.hsd1.ma.comcast.net [98.229.133.101]) (authenticated bits=0) by rs40.luxsci.com (8.13.1/8.13.7) with ESMTP id o1JJhmRr028957 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 19 Feb 2010 13:43:49 -0600
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Jon Saperia <saperia@jdscons.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0401F492B5@307622ANEX5.global.avaya.com>
Date: Fri, 19 Feb 2010 14:43:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB91A970-F187-4C21-845F-410CE6C41A50@jdscons.com>
References: <EDC652A26FB23C4EB6384A4584434A0401F492B5@307622ANEX5.global.avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
X-Mailer: Apple Mail (2.1077)
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>, Marc Blanchet <marc.blanchet@viagenie.ca>, ops-area@ietf.org
Subject: Re: [OPS-AREA] FW: Policy MIB stringprep profile
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 19:42:07 -0000

Peter,

I am not aware of complete implementations so I do not have anything =
add.  I suspect some people on this list may have looked at =
implementation or attempted at least part of it.
/jon
On Feb 16, 2010, at 5:27 AM, Romascanu, Dan (Dan) wrote:

> Folks who participated in the Policy MIB work may be interested in =
this
> discussion and can possibly help to answer the questions.=20
>=20
> Dan
>=20
>=20
> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter@stpeter.im]=20
> Sent: Monday, February 15, 2010 4:35 AM
> To: waldbusser@nextbeacon.com; saperia@jdscons.com;
> hongal@riverstonenet.com
> Cc: Marc Blanchet; Alexey.Melnikov@isode.com
> Subject: Policy MIB stringprep profile
>=20
> Gentlemen,
>=20
> The IETF will hold a BoF at IETF 77 (in Anaheim the week of March 22)
> about possible replacements for stringprep. I notice that you three
> authored of one of the few stringprep profiles, for Policy MIB (RFC
> 4011). Marc Blanchet and I will be co-chairing the BoF, and we're
> seeking input from authors of all stringprep profiles regarding the
> possibility of pursuing new approaches to internationalized strings, =
as
> has happened already for internationalized domain names through the
> IDNAbis WG. A proposed charter for a "newprep" working group is here:
>=20
> http://www.ietf.org/mail-archive/web/newprep/current/msg00000.html
>=20
> See also subsequent discussion on the list:
>=20
> https://www.ietf.org/mailman/listinfo/newprep
>=20
> However, we don't necessarily wish to form yet another WG, and one
> perfectly acceptable outcome of the BoF would be agreement to pursue =
any
> needed work through independent submissions that update existing work =
in
> this area.
>=20
> As input to our thinking, would you perhaps have time to post to the
> newprep list regarding industry experience with the Policy MIB =
profile?
> We're especially interested in answers to the following questions:
>=20
> * Approximately what percentage of relevant software has implemented =
and
> deployed the profile?
>=20
> * How have developers implemented the profile (e.g., by including or
> wrapping an existing library such as libidn, or by writing an
> independent implementation)?
>=20
> * Have developers experienced any interoperability issues or other
> problems with the profile?
>=20
> * Might there be developer interest in migrating from the profile to =
an
> approach that is less complex (e.g., by specifying a tiered model of
> valid, disallowed, and unassigned characters as in IDNAbis) or more
> flexible (e.g., by enabling the use of characters beyond Unicode 3.2 =
as
> fixed by RFC 3454)?
>=20
> [Alexey and Marc, feel free to modify or add to these questions.]
>=20
> I plan to post to the newprep list soon regarding the XMPP experience
> with stringprep, so perhaps you (or someone else in the network
> management community) could take that as a bit of a template.
>=20
> Any other feedback you might have would be much appreciated.
>=20
> Thanks for your time.
>=20
> Peter
>=20
> --
> Peter Saint-Andre
> https://stpeter.im/
>=20
>=20
>=20
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
>=20


From randy_presuhn@mindspring.com  Fri Feb 19 15:54:41 2010
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E200B3A7B89; Fri, 19 Feb 2010 15:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.382
X-Spam-Level: 
X-Spam-Status: No, score=-2.382 tagged_above=-999 required=5 tests=[AWL=0.217,  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 1adB9EbHjETs; Fri, 19 Feb 2010 15:54:41 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id F33A03A7B1C; Fri, 19 Feb 2010 15:54:40 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=YtiqEWJYUOalsG5xl3P/SFwTgr936v3HwuBb8PlC4JkW/JDIrLoqgWlHTpteiRfj; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.60.27.76] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Nichw-0000Ib-UB; Fri, 19 Feb 2010 18:56:29 -0500
Message-ID: <000e01cab1bf$cd668b80$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, <ops-area@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A0401F492B5@307622ANEX5.global.avaya.com> <BB91A970-F187-4C21-845F-410CE6C41A50@jdscons.com>
Date: Fri, 19 Feb 2010 16:01:05 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888494b88d665f13b40f8302ce83fb5fdf72c62bb8676ddbcb6350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.60.27.76
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: [OPS-AREA] [MIB-DOCTORS]  FW: Policy MIB stringprep profile
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2010 23:54:42 -0000

Hi -

...
> On Feb 16, 2010, at 5:27 AM, Romascanu, Dan (Dan) wrote:
> 
> > Folks who participated in the Policy MIB work may be interested in this
> > discussion and can possibly help to answer the questions. 
> > 
> > Dan
> > 
> > 
> > -----Original Message-----
> > From: Peter Saint-Andre [mailto:stpeter@stpeter.im] 
> > Sent: Monday, February 15, 2010 4:35 AM
> > To: waldbusser@nextbeacon.com; saperia@jdscons.com;
> > hongal@riverstonenet.com
> > Cc: Marc Blanchet; Alexey.Melnikov@isode.com
> > Subject: Policy MIB stringprep profile
> > 
> > Gentlemen,
> > 
> > The IETF will hold a BoF at IETF 77 (in Anaheim the week of March 22)
> > about possible replacements for stringprep. I notice that you three
> > authored of one of the few stringprep profiles, for Policy MIB (RFC
> > 4011). Marc Blanchet and I will be co-chairing the BoF, and we're
> > seeking input from authors of all stringprep profiles regarding the
> > possibility of pursuing new approaches to internationalized strings, as
> > has happened already for internationalized domain names through the
> > IDNAbis WG. A proposed charter for a "newprep" working group is here:
...

As far as I can recall, for the Policy MIB the only reason stringprep specifically
was used to describe the desired behaviour  was that that was the preferred
solution at that time, and that "prohibition tables" C.2 through C.9 happened
to cover the things that we could reasonably constrain.  This fits in nicely
with the "exclusion" model, and made coming up with the profile straightforward.
In this particular case, an "inclusion" model would have been more difficult to use,
since the nature of this application put us in the position of wanting to include
everything except a few problematic cases.

This use of stringprep is perhaps a bit different from what was invisioned
by its authors, in that it really isn't about the Policy MIB per se, nor is it
about the protocol.  Rather, its an optional-to-use capability of the
programming language that the user of the MIB has at his/her disposal.
As such, it would perhaps have been more useful (or more over-engineered)
to be able to provide the stringprep profile (or equivalent) as a parameter to
the function, rather than hard-coding the profile in the programming
language's documentation.

Randy


From fluffy@cisco.com  Wed Feb 24 22:01:12 2010
Return-Path: <fluffy@cisco.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E60D3A8649; Wed, 24 Feb 2010 22:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.613
X-Spam-Level: 
X-Spam-Status: No, score=-110.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 GpQQlI+VX2Tb; Wed, 24 Feb 2010 22:01:07 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 45E813A863E; Wed, 24 Feb 2010 22:01:02 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACahhUurRN+K/2dsb2JhbACbFHOjLphRhHMEgxc
X-IronPort-AV: E=Sophos;i="4.49,537,1262563200"; d="scan'208";a="92323710"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 25 Feb 2010 06:03:11 +0000
Received: from dhcp-171-68-21-119.cisco.com (dhcp-171-68-21-119.cisco.com [171.68.21.119]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o1P63BJd028508; Thu, 25 Feb 2010 06:03:11 GMT
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <15443028349C3C44BA819EB51B3B4F3C571F6C9057@NOK-EUMSG-01.mgdnok.nokia.com>
Date: Wed, 24 Feb 2010 22:03:10 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFA1BBEB-6910-46D1-8498-9124789337A2@cisco.com>
References: <15443028349C3C44BA819EB51B3B4F3C571F6C9057@NOK-EUMSG-01.mgdnok.nokia.com>
To: "<hannu.hietalahti@nokia.com>" <hannu.hietalahti@nokia.com>
X-Mailer: Apple Mail (2.1077)
Cc: rai@ietf.org, int-area@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [RAI] Minutes of 3GPP - IETF teleconference 17th Feb 2010
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 06:01:12 -0000

On Feb 19, 2010, at 4:25 , <hannu.hietalahti@nokia.com> =
<hannu.hietalahti@nokia.com> wrote:

> =20
> draft-bakker-sipping-3gpp-ims-xml-body-handling will progress as AD =
sponsored draft (Cullen Jennings).

Could anyone clarify where this came from in the call?=20

Thanks, Cullen


From spencer@wonderhamster.org  Thu Feb 25 12:56:48 2010
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417593A8593; Thu, 25 Feb 2010 12:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 M7ElwAmRwns4; Thu, 25 Feb 2010 12:56:47 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 53E9D3A8584; Thu, 25 Feb 2010 12:56:47 -0800 (PST)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MQzYs-1OBbcT2kJi-00Tqdx; Thu, 25 Feb 2010 15:58:49 -0500
Message-ID: <EC146045408B478A8D400D849B05D8D4@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Cullen Jennings" <fluffy@cisco.com>, <hannu.hietalahti@nokia.com>
References: <15443028349C3C44BA819EB51B3B4F3C571F6C9057@NOK-EUMSG-01.mgdnok.nokia.com> <FFA1BBEB-6910-46D1-8498-9124789337A2@cisco.com>
Date: Thu, 25 Feb 2010 14:58:39 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1+ruH3SB8oIV+Xc3l6rzJcsiQ/HPl75KurDiXy N4jhh3qkpsgtKOSrs9ClZe+0rHVJ9JpH0zOgPiu+uhLNUh4wbL 9zKoWyFqHj8QkpjgI1N/Bb5TzpOIKsy51GvrFBF70c=
X-Mailman-Approved-At: Thu, 25 Feb 2010 13:14:01 -0800
Cc: int-area@ietf.org, rai@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [RAI] Minutes of 3GPP - IETF teleconference 17th Feb 2010
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 20:56:48 -0000

Hi, Cullen,

For what it's worth, my notes on this said

"bakker-sipping-3gpp-ims-xml-body-handling - never had a direct reference 
from 24.229, but specification is needed for IANA registration. Mary punted 
this to ADs last week. Need to ask if this needs expert review, if it's 
going to be AD-sponsored."

Spencer

>>
>> draft-bakker-sipping-3gpp-ims-xml-body-handling will progress as AD 
>> sponsored draft (Cullen Jennings).
>
> Could anyone clarify where this came from in the call?
>
> Thanks, Cullen 


From dean@av8.com  Thu Feb 25 14:25:58 2010
Return-Path: <dean@av8.com>
X-Original-To: ops-area@core3.amsl.com
Delivered-To: ops-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A779C3A8454; Thu, 25 Feb 2010 14:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level: 
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=0.295,  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 phHI7jAS44bX; Thu, 25 Feb 2010 14:25:57 -0800 (PST)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id 60B3E3A85D2; Thu, 25 Feb 2010 14:25:53 -0800 (PST)
Received: from citation2.av8.net (citation2.av8.net [130.105.12.10]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id o1PMS4Ju002458 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 25 Feb 2010 17:28:04 -0500
Date: Thu, 25 Feb 2010 17:28:03 -0500 (EST)
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: OPS AREA <ops-area@ietf.org>
In-Reply-To: <Pine.LNX.4.64.1002141115190.6399@shell4.bayarea.net>
Message-ID: <Pine.LNX.4.44.1002251727060.14339-100000@citation2.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF Outcomes <ietf-outcomes@ietf.org>
Subject: Re: [OPS-AREA] Suggested corrections to OPS wiki page
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ops-area>, <mailto:ops-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 22:25:58 -0000

The first page claims the IETF has operated in its current form since 
1989, but the ISOC was incorporated in 1992.  Please explain this.

		--Dean


-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 256 5494


