From ops-area-bounces@ietf.org  Tue May  6 04:10:28 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6FE5E28C1C9;
	Tue,  6 May 2008 04:10:26 -0700 (PDT)
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 0634D28C34D
	for <ops-area@core3.amsl.com>; Tue,  6 May 2008 04:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[AWL=1.038, 
	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 pJpVOrpC-oin for <ops-area@core3.amsl.com>;
	Tue,  6 May 2008 04:09:53 -0700 (PDT)
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 EA6843A67B6
	for <ops-area@ietf.org>; Tue,  6 May 2008 04:09:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208";a="106078016"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	06 May 2008 07:09:49 -0400
X-IronPort-AV: E=Sophos;i="4.27,443,1204520400"; d="scan'208";a="191146928"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	06 May 2008 07:09:49 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 13:09:47 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BBC3F1@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cut-off Dates for WG meetings and BOF requests for the Dublin
	IETF
Thread-Index: AcivabI9QrXy4v3mTd2I2M7a+aGowA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] Cut-off Dates for WG meetings and BOF requests for the
	Dublin IETF
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Please be aware about the following cut-off dates for the Dublin IETF
meeting: 

> May 26, Monday - Cutoff date for requests to schedule Working Group 
> meetings and for preliminary BOF proposals to ADs at 17:00 PDT (24:00 
> UTC/GMT).
> June 9, Monday - Cutoff date for requests to Area Directors to 
> schedule BOFs at 17:00 PDT (24:00 UTC/GMT).
> June 16, Monday - Cutoff date for Area Directors to approve BOF 
> requests at 17:00 PDT (24:00 UTC/GMT).

WG chairs - please use the on-line tool to request meetings in Dublin
before 5/26

If you plan to request a BOF in the OPS area please send a preliminary
proposal to Ron and/or to me before 5/26. 

Thanks and Regards,

Dan
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Tue May 13 05:58:27 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8BAE43A67EA;
	Tue, 13 May 2008 05:58:27 -0700 (PDT)
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 190073A65A6
	for <ops-area@core3.amsl.com>; Tue, 13 May 2008 05:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5
	tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 MBVlzYvr3U9o for <ops-area@core3.amsl.com>;
	Tue, 13 May 2008 05:58:23 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 7F0423A67EA
	for <ops-area@ietf.org>; Tue, 13 May 2008 05:58:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,479,1204520400"; d="scan'208";a="126355521"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 13 May 2008 08:56:16 -0400
X-IronPort-AV: E=Sophos;i="4.27,479,1204520400"; d="scan'208";a="201203193"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	13 May 2008 08:56:15 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 13 May 2008 14:56:18 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BF9A84@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 72nd IETF - Working Group/BOF Scheduling - REMINDER 
Thread-Index: Aci0bLYBHLsAgwArTLq8YfiyXQXAmAAjAHPA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] FW: 72nd IETF - Working Group/BOF Scheduling - REMINDER
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IETF Agenda
Sent: Monday, May 12, 2008 11:14 PM
To: Working Group Chairs
Cc: irsg@isi.edu; bofchairs@ietf.org
Subject: 72nd IETF - Working Group/BOF Scheduling - REMINDER 

72nd IETF - Dublin, Ireland
Meeting Dates: July 27 - August 1, 2008
Host: Alcatel-Lucent


We are accepting scheduling requests for all Working Groups and BOFs.
The milestones and deadlines for scheduling-related activities are as
follows:


May 26, Monday - Cutoff date for requests to schedule Working Group
meetings and for preliminary BOF proposals to ADs at 17:00 PDT (24:00
UTC/GMT).
June 9, Monday - Cutoff date for requests to Area Directors to schedule
BOFs at 17:00 PDT (24:00 UTC/GMT).
June 16, Monday - Cutoff date for Area Directors to approve BOF requests
at 17:00 PDT (24:00 UTC/GMT).
June 20, Friday - Preliminary agenda published for comment.
July 2, Wednesday - Cutoff date for requests to reschedule Working Group
and BOF meetings 17:00 PDT (24:00 UTC/GMT) July 7, Monday - Final agenda
to be published.
July 16, Wednesday - Draft Working Group agendas due by 17:00 PDT (24:00
UTC/GMT).
July 21, Monday - Revised Working Group agendas due by 17:00 PDT (24:00
UTC/GMT).

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda@ietf.org. 
Please include the acronym of your BOF in the subject line of the
message, and include all of the information specified in item (4) of
"Requesting Meeting Sessions at IETF Meetings" in the body.  (This
document is included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, July 16 by 17:00 PDT (24:00
UTC/GMT).  Revised Working Group agendas are due no later than Monday,
July 23 at 17:00 PDT (24:00 UTC/GMT).  The proposed agenda for a BOF
session should be submitted along with your request for a session.
Please be sure to copy your Area Director on that message.

Please submit the agendas for your Working Group sessions using the
"IETF Meeting Materials Management Tool," a Web-based tool for making
your meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 72 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=72

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both
tools.
  If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting
sessions at IETF 72 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action@ietf.org.  If you are unable to use
the tool, then you may send your request via e-mail to agenda@ietf.org,
with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a
copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read
the BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt
before requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned,
based on availability, after Wednesday, July 2 at 17:00 PDT (24:00
UTC/GMT), the cut-off date for requests to reschedule a session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets: 

    b. AREA under which Working Group or BOF appears:

    c. CONFLICTS you wish to avoid, please be as specific as possible:

    d. Expected Attendance (figures from the 71st IETF meeting are
included at the end of this message):

    e. Special requests:

    f. Number of sessions:

    g. Length of session: 
       - 1 hour 
       - 2 hours 
       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions,
please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and
Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair
Russ Housley <housley@vigilsec.com>

Applications Area (app)
Lisa Dusseault <lisa@osafoundation.org>
Chris Newman <chris.newman@sun.com>

Internet Area (int)
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Operations & Management Area (ops)
Ronald Bonica <rbonica@juniper.net>
Dan Romascanu <dromasca@avaya.com>

Real-time Applications and Infrastructure Area (rai) Cullen Jennings
<fluffy@cisco.com> Jon Peterson <jon.peterson@neustar.biz>

Routing Area (rtg)
Ross Callon <rcallon@juniper.net>
David Ward <dward@cisco.com>

Security Area (sec)
Pasi Eronen <pasi.eronen@nokia.com>
Tim Polk <tim.polk@nist.gov>

Transport Area (tsv)
Lars Eggert <lars.eggert@nokia.com>
Magnus Westerlund <magnus.westerlund@ericsson.com>
===========================================================
71st IETF Meeting Attendance Number

16ng		36
6lowpan		33
6man		85
ancp		25
apparea (AG)	87
asrg		38
autoconf		71
avt		70
avt (2nd session)	28
behave		71
bliss		115
bmwg		28
calsify		21
canmod (BoF)	58
capwap		27
ccamp		91
ccamp (2nd session)	87
csi		29
dccp		22
dhc		97
dime		38
dkim		46
dna		32
dnsext		95
dnsop		103
dtnrg (RG)	46
eai		49
ecrit		85
emu		36
enum		84
esds (BoF)	64
fecframe	21
geopriv		76
grow		53
hiprg (RG)	48
hokey		39
iccrg (RG)	30
idn (BoF)	93
idr		69
intarea (AG)	141
ipfix		29
ippm		41
isis		36
keyprov		24
kitten		11
kmart (BoF)	102
krb-wg		27
l2vpn		88
l3vpn		78
lemonade	24
lemonade 2nd sess	20
ltans		13
manet		68
mboned		47
mediactrl	64
mext		85
mext - 2nd sess	62
mip4		26
mmusic		140
mpls		121
msec		22
nea (BOF)	33
netconf		50
netlmm		73
nfsv4		20
nmrg (RG)	18
nsis		27
ntp		25
opsarea (AG)	42
opsawg		41
ospf		40
p2psip		110
pana		48
pce		68
pcn		31
pcn - 2nd session	34
peppermint (Bof)	115
pim		33
pkix		60
pmol		25
pufi (BOF)	38
pwe3		110
radext		27
rtgarea (AG)	112+
rmt		15
roll		59
rrg (RG)		106
rrg - 2nd session	76
rucus (BoF)	127
saag (AG)	87
samrg (RG)	40
sasl		17
shim6		66
sidr		63
sieve		21
simple		65
sip		199
sipping		22
smime		24
softwire		50
speermint	102
tcpm		38
tictoc		59
tls		61
trill		54
tsvarea (AG)	132
tsvwg		90
v6ops		108
v6ops - 2nd session	88
vcarddav	24
xcon		44


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed May 14 04:58:08 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB9AD3A6960;
	Wed, 14 May 2008 04:58:08 -0700 (PDT)
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 47E353A6867;
	Wed, 14 May 2008 04:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091, 
	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 1+lf7ypen4Y9; Wed, 14 May 2008 04:58:02 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 0B6D83A67CC;
	Wed, 14 May 2008 04:58:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,486,1204520400"; d="scan'208";a="126524634"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 14 May 2008 07:54:41 -0400
X-IronPort-AV: E=Sophos;i="4.27,486,1204520400"; d="scan'208";a="201772032"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	14 May 2008 07:54:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 14 May 2008 13:54:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04BF9D85@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of RADIUS Extensions Working Group (radext)
Thread-Index: Aci1RLkjOAWzy9LnQUytN2wYUiVWLQAdIFGg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <radiusext@ops.ietf.org>, <ops-dir@ietf.org>, <aaa-doctors@ietf.org>,
	<ops-area@ietf.org>
Subject: [OPS-AREA] FW: WG Review: Recharter of RADIUS Extensions Working
	Group (radext)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IESG Secretary
Sent: Wednesday, May 14, 2008 1:00 AM
To: ietf-announce@ietf.org
Cc: Bernard_Aboba@hotmail.com; d.b.nelson@comcast.net;
radiusext@ops.ietf.org
Subject: WG Review: Recharter of RADIUS Extensions Working Group
(radext) 

A modified charter has been submitted for the RADIUS Extensions Working
Group in the Operations and Management Area of the IETF.  The IESG has
not made any determination as yet.  The modified charter is provided
below for informational purposes only.  Please send your comments to the
IESG mailing list (iesg@ietf.org) by May 20, 2008.


RADIUS Extensions Working Group (radext)
----------------------------------------
Last Modified: 2008-04-30

Current Status: Active Working Group

Chair(s):
*  Bernard Aboba <Bernard_Aboba@hotmail.com>
*  David Nelson <d.b.nelson@comcast.net> 


Operations and Management Area Director(s):
*  Dan Romascanu <dromasca@avaya.com> 
*  Ronald Bonica <rbonica@juniper.net> 


Operations and Management Area Advisor:
*  Dan Romascanu <dromasca@avaya.com> 


Technical Advisor(s):
*  Paul Congdon <paul.congdon@hp.com> 


Mailing Lists:
General Discussion: radiusext@ops.ietf.org
To Subscribe: radiusext-request@ops.ietf.org
In Body: In Body: subscribe
Archive: https://ops.ietf.org/lists/radiusext


Description of Working Group: 

The RADIUS Extensions Working Group will focus on extensions to the
RADIUS protocol required to define extensions to the standard
attribute space as well as to address cryptographic algorithm
agility and use over new transports. In addition, RADEXT will
work on RADIUS Design Guidelines and define new attributes for 
particular applications of authentication, authorization and 
accounting such as NAS management and local area network (LAN) usage. 

In order to enable interoperation of heterogeneous RADIUS/Diameter
deployments, all RADEXT WG work items MUST contain a Diameter
compatibility section, outlining how interoperability with
Diameter will be maintained.

Furthermore, to ensure backward compatibility with existing RADIUS
implementations, as well as compatibility between RADIUS and Diameter,
the following restrictions are imposed on extensions considered by the
RADEXT WG:

- All documents produced MUST specify means of interoperation with
legacy RADIUS implementations and, if possible, be backward 
compatible with existing RADIUS RFCs, including RFCs 2865-2869, 
3162, 3575, 3579, 3580, 4668-4673,4675, 5080, 5090 and 5176.
Transport profiles should, if possible, be compatible with RFC 3539. 

- All RADIUS work MUST be compatible with equivalent facilities in
Diameter. Where possible, new attributes should be defined so that
the same attribute can be used in both RADIUS and Diameter without
translation. In other cases a translation considerations
section should be included in the specification.


Work Items

The immediate goals of the RADEXT working group are to address the
following issues:

- RADIUS design guidelines. This document will provide guidelines for
design of RADIUS attributes. It will specifically consider how
complex data types may be introduced in a robust manner, maintaining
backwards compatibility with existing RADIUS RFCs, across all the
classes of attributes: Standard, Vendor-Specific and SDO-Specific.
In addition, it will review RADIUS data types and associated
backwards compatibility issues.

- RADIUS Management authorization. This document will define the
use of RADIUS for NAS management over IP. 

-RADIUS attribute space extension. The standard RADIUS attribute
space is currently being depleted. This document will provide
additional standard attribute space, while maintaining backward
compatibility with existing attributes.

-RADIUS Cryptographic Algorithm Agility. RADIUS has traditionally 
relied on MD5 for both per-packet integrity and authentication as well
as attribute confidentiality. Given the increasingly successful
attacks being mounted against MD5, the ability to support
alternative algorithms is required. This work item will
include documentation of RADIUS crypto-agility requirements,
as well as development of one or more Experimental RFCs providing
support for negotiation of alternative cryptographic algorithms
to protect RADIUS.

- IEEE 802 attributes. New attributes have been proposed to
support IEEE 802 standards for wired and wireless LANs. This
work item will support authentication, authorization and
accounting attributes needed by IEEE 802 groups including
IEEE 802.1, IEEE 802.11 and IEEE 802.16.

- New RADIUS transports. A reliable transport profile for
RADIUS will be developed, as well as specifications for 
Secure transports, including TCP/TLS (RADSEC) and UDP/DTLS.

- Documentation of Status-Server usage. A document
describing usage of the Status-Server facility will be
developed.

Goals and Milestones:

Jun 2008 RADIUS Design Guidelines submitted as a Best Current Practice
RFC
Jun 2008 RADIUS Management Authorization I-D submitted as a Proposed
Standard RFC
Sep 2008 RADIUS Crypto-agility Requirements submitted as an
Informational
RFC
Sep 2008 Extended Attributes I-D submitted as a Proposed Standard RFC
Dec 2008 IEEE 802 Attributes I-D submitted as a Proposed Standard RFC
Jan 2009 Reliable Transport Profile for RADIUS I-D submitted as a
Proposed
Standard RFC
Mar 2009 Status-Server I-D submitted as a Proposed Standard RFC
Mar 2009 RADSEC (RADIUS over TCP/TLS) draft submitted as an Experimental
RFC
June 2009 RADIUS over DTLS I-D submitted as an Experimental RFC
June 2009 RADIUS Cryptographic Algorithm Agility I-D submitted as an
Experimental RFC
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed May 21 01:51:48 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7F8053A69B3;
	Wed, 21 May 2008 01:51:48 -0700 (PDT)
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 017D53A68A2
	for <ops-area@core3.amsl.com>; Wed, 21 May 2008 01:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.969
X-Spam-Level: 
X-Spam-Status: No, score=-1.969 tagged_above=-999 required=5 tests=[AWL=0.630, 
	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 Bhn8w0f1YQWZ for <ops-area@core3.amsl.com>;
	Wed, 21 May 2008 01:51:47 -0700 (PDT)
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 4C6E33A68C7
	for <ops-area@ietf.org>; Wed, 21 May 2008 01:51:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,519,1204520400"; d="scan'208";a="108274407"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	21 May 2008 04:51:43 -0400
X-IronPort-AV: E=Sophos;i="4.27,519,1204520400"; d="scan'208";a="205237609"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	21 May 2008 04:51:42 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 May 2008 10:50:30 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C331F3@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPSAREA meeting in Dublin
Thread-Index: Aci7H7kqYsi0vwJEQSKFDfmdJp6G5g==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] OPSAREA meeting in Dublin
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

We will be holding an Operations and Management Area open meeting in
Dublin. 

Please send your proposals and requests for the agenda time.  

Thanks and Regards,

Ron and Dan


 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed May 21 09:58:57 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CEBC28C1FB;
	Wed, 21 May 2008 09:58:57 -0700 (PDT)
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 ECED628C103
	for <ops-area@core3.amsl.com>; Wed, 21 May 2008 09:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.068
X-Spam-Level: 
X-Spam-Status: No, score=-2.068 tagged_above=-999 required=5
	tests=[AWL=-0.069, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 zhZSylw3GhvV for <ops-area@core3.amsl.com>;
	Wed, 21 May 2008 09:58:54 -0700 (PDT)
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 1712F28C0FE
	for <ops-area@ietf.org>; Wed, 21 May 2008 09:58:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,521,1204520400"; d="scan'208";a="108342611"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	21 May 2008 12:58:55 -0400
X-IronPort-AV: E=Sophos;i="4.27,521,1204520400"; d="scan'208";a="205491126"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	21 May 2008 12:58:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 21 May 2008 18:58:50 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C33460@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BOFCHAIRS] 72nd IETF - Working Group/BOF Scheduling
Thread-Index: Aci7Xo7MBS2lroomTnCNW5RBod/N7wABVijQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] FW: [BOFCHAIRS] 72nd IETF - Working Group/BOF Scheduling
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IETF Agenda
Sent: Wednesday, May 21, 2008 7:20 PM
To: Working Group Chairs
Cc: bofchairs@ietf.org
Subject: [BOFCHAIRS] 72nd IETF - Working Group/BOF Scheduling

REMINDER: The cutoff date for requesting a working group session and for
preliminary BOF proposals to ADs is Monday, May 26 at 17:00 PDT (24:00
UTC/GMT).

-----------------------------------------------------------------
72nd IETF - Dublin, Ireland
Meeting Dates: July 27 - August 1, 2008
Host: Alcatel-Lucent
-----------------------------------------------------------------
We are currently accepting scheduling requests for all Working Groups
and BOFs.  The milestones and deadlines for scheduling-related
activities are as follows:

May 26, Monday - Cutoff date for requests to schedule Working Group
meetings and for preliminary BOF proposals to ADs at 17:00 PDT (24:00
UTC/GMT).
June 9, Monday - Cutoff date for requests to Area Directors to schedule
BOFs at 17:00 PDT (24:00 UTC/GMT).
June 16, Monday - Cutoff date for Area Directors to approve BOF requests
at 17:00 PDT (24:00 UTC/GMT).
June 20, Friday - Preliminary agenda published for comment.
July 2, Wednesday - Cutoff date for requests to reschedule Working Group
and BOF meetings 17:00 PDT (24:00 UTC/GMT) July 7, Monday - Final agenda
to be published.
July 16, Wednesday - Draft Working Group agendas due by 17:00 PDT (24:00
UTC/GMT).
July 21, Monday - Revised Working Group agendas due by 17:00 PDT (24:00
UTC/GMT).

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda@ietf.org. 
Please include the acronym of your BOF in the subject line of the
message, and include all of the information specified in item (4) of
"Requesting Meeting Sessions at IETF Meetings" in the body.  (This
document is included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, July 16 by 17:00 PDT (24:00
UTC/GMT).  Revised Working Group agendas are due no later than Monday,
July 23 at 17:00 PDT (24:00 UTC/GMT).  The proposed agenda for a BOF
session should be submitted along with your request for a session.
Please be sure to copy your Area Director on that message.

Please submit the agendas for your Working Group sessions using the
"IETF Meeting Materials Management Tool," a Web-based tool for making
your meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 72 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=72

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both
tools.
  If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action@ietf.org.
===============================================================
For your convenience, comprehensive information on requesting meeting
sessions at IETF 72 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action@ietf.org.  If you are unable to use
the tool, then you may send your request via e-mail to agenda@ietf.org,
with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda@ietf.org with a
copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read
the BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt
before requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned,
based on availability, after Wednesday, July 2 at 17:00 PDT (24:00
UTC/GMT), the cut-off date for requests to reschedule a session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets: 

    b. AREA under which Working Group or BOF appears:

    c. CONFLICTS you wish to avoid, please be as specific as possible:

    d. Expected Attendance (figures from the 71st IETF meeting are
included at the end of this message):

    e. Special requests:

    f. Number of sessions:

    g. Length of session: 
       - 1 hour 
       - 2 hours 
       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions,
please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and
Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
===============================================================
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair
Russ Housley <housley@vigilsec.com>

Applications Area (app)
Lisa Dusseault <lisa@osafoundation.org>
Chris Newman <chris.newman@sun.com>

Internet Area (int)
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Operations & Management Area (ops)
Ronald Bonica <rbonica@juniper.net>
Dan Romascanu <dromasca@avaya.com>

Real-time Applications and Infrastructure Area (rai) Cullen Jennings
<fluffy@cisco.com> Jon Peterson <jon.peterson@neustar.biz>

Routing Area (rtg)
Ross Callon <rcallon@juniper.net>
David Ward <dward@cisco.com>

Security Area (sec)
Pasi Eronen <pasi.eronen@nokia.com>
Tim Polk <tim.polk@nist.gov>

Transport Area (tsv)
Lars Eggert <lars.eggert@nokia.com>
Magnus Westerlund <magnus.westerlund@ericsson.com>
===========================================================
71st IETF Meeting Attendance Number

16ng		36
6lowpan		33
6man		85
ancp		25
apparea (AG)	87
asrg		38
autoconf		71
avt		70
avt (2nd session)	28
behave		71
bliss		115
bmwg		28
calsify		21
canmod (BoF)	58
capwap		27
ccamp		91
ccamp (2nd session)	87
csi		29
dccp		22
dhc		97
dime		38
dkim		46
dna		32
dnsext		95
dnsop		103
dtnrg (RG)	46
eai		49
ecrit		85
emu		36
enum		84
esds (BoF)	64
fecframe	21
geopriv		76
grow		53
hiprg (RG)	48
hokey		39
iccrg (RG)	30
idn (BoF)	93
idr		69
intarea (AG)	141
ipfix		29
ippm		41
isis		36
keyprov		24
kitten		11
kmart (BoF)	102
krb-wg		27
l2vpn		88
l3vpn		78
lemonade	24
lemonade 2nd sess	20
ltans		13
manet		68
mboned		47
mediactrl	64
mext		85
mext - 2nd sess	62
mip4		26
mmusic		140
mpls		121
msec		22
nea (BOF)	33
netconf		50
netlmm		73
nfsv4		20
nmrg (RG)	18
nsis		27
ntp		25
opsarea (AG)	42
opsawg		41
ospf		40
p2psip		110
pana		48
pce		68
pcn		31
pcn - 2nd session	34
peppermint (Bof)	115
pim		33
pkix		60
pmol		25
pufi (BOF)	38
pwe3		110
radext		27
rtgarea (AG)	112+
rmt		15
roll		59
rrg (RG)		106
rrg - 2nd session	76
rucus (BoF)	127
saag (AG)	87
samrg (RG)	40
sasl		17
shim6		66
sidr		63
sieve		21
simple		65
sip		199
sipping		22
smime		24
softwire		50
speermint	102
tcpm		38
tictoc		59
tls		61
trill		54
tsvarea (AG)	132
tsvwg		90
v6ops		108
v6ops - 2nd session	88
vcarddav	24
xcon		44


_______________________________________________
BOFCHAIRS mailing list
BOFCHAIRS@ietf.org
https://www.ietf.org/mailman/listinfo/bofchairs
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Tue May 27 11:53:13 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 061A53A6C2E;
	Tue, 27 May 2008 11:53:13 -0700 (PDT)
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 866E23A6A88;
	Tue, 27 May 2008 11:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149, 
	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 NrDiChP5aJKT; Tue, 27 May 2008 11:53:10 -0700 (PDT)
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 601593A690D;
	Tue, 27 May 2008 11:53:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,549,1204520400"; d="scan'208";a="108995561"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	27 May 2008 14:52:57 -0400
X-IronPort-AV: E=Sophos;i="4.27,549,1204520400"; d="scan'208";a="208329312"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	27 May 2008 14:52:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 20:52:55 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C7166D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Protocol Action: 'Templates for Internet Drafts Containing MIB
	Modules' to BCP 
Thread-Index: AcjAJmnwVviV8zFTTyCY30xMKNl0oAABFbuw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>,
	"MIB Doctors" <mib-doctors@ietf.org>
Subject: [OPS-AREA] FW: Protocol Action: 'Templates for Internet Drafts
	Containing MIB Modules' to BCP
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Thanks and Congratulations to Dave Harrington for the approval of this
document. 

Dan

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: Tuesday, May 27, 2008 9:19 PM
To: IETF-Announce
Cc: Internet Architecture Board; RFC Editor
Subject: Protocol Action: 'Templates for Internet Drafts Containing MIB
Modules' to BCP 

The IESG has approved the following document:

- 'Templates for Internet Drafts Containing MIB Modules '
   <draft-harrington-text-mib-doc-template-06.txt> as a BCP

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-harrington-text-mib-doc-templa
te-06.txt

Technical Summary
 
   This memo contains two annotated templates for IETF documents that
   contain the definition of MIB modules.  It is intended to alleviate
   the work of the authors of such documents, making these more uniform
   and easier to read and review, thus furthering the quality of such
   documents and expediting their publication.

Working Group Summary
 
   This is an individual submission, which was reviewed by the MIB-
   DOCTORS team. Several suggestions that were made by the MIB-DOCTORS 
   and during the IETF Last Call were incorporated in the document. 
   
Protocol Quality
 
   Dan Romascanu reviewed the document for the IESG. Keith McCloghrie, 
   Bert Wijnen, Tom Petsch and other reviewed, commented and suggested 
   improvements. A small number of Internet-Drafts experimented with 
   different versions of the template.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed May 28 10:05:10 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 006773A6CA9;
	Wed, 28 May 2008 10:05:10 -0700 (PDT)
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 518A73A6AEA
	for <ops-area@core3.amsl.com>; Wed, 28 May 2008 10:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.456
X-Spam-Level: 
X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[AWL=0.143, 
	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 5XRG-IgPTj1G for <ops-area@core3.amsl.com>;
	Wed, 28 May 2008 10:05:01 -0700 (PDT)
Received: from co300216-co-outbound.avaya.com
	(co300216-co-outbound.net.avaya.com [198.152.13.100])
	by core3.amsl.com (Postfix) with ESMTP id 4FB3F28C120
	for <ops-area@ietf.org>; Wed, 28 May 2008 10:04:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,556,1204520400"; d="scan'208";a="128830913"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 28 May 2008 13:04:57 -0400
X-IronPort-AV: E=Sophos;i="4.27,556,1204520400"; d="scan'208";a="202056173"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	28 May 2008 13:04:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 28 May 2008 19:04:55 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04C7196A@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of EAP Method Update (emu) 
Thread-Index: AcjA5LKIxOSOtzVcQoK8p0E3zA8YjgAACZjQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>,
	<STDS-802-1-L@listserv.ieee.org>
Subject: [OPS-AREA] FW: WG Review: Recharter of EAP Method Update (emu)
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

 

-----Original Message-----
From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
IESG Secretary
Sent: Wednesday, May 28, 2008 8:00 PM
To: new-work@ietf.org
Subject: WG Review: Recharter of EAP Method Update (emu) 

A modified charter has been submitted for the EAP Method Update working
group in the Security Area of the IETF.  The IESG has not made any
determination as yet.  The modified charter is provided below for
informational purposes only.  Please send your comments to the IESG
mailing list (iesg@ietf.org) by Wednesday, June 4, 2008.

EAP Method Update (emu)
========================

Last Modified: 2008-05-22

Current Status: Active Working Group

Chair(s):
Joseph Salowey (jsalowey@cisco.com)
Alan DeKok (aland@deployingradius.com)

Security Area Director(s):
Tim Polk (tim.polk@nist.gov)
Pasi Eronen (pasi.eronen@nokia.com)


Security Area Advisor:
Pasi Eronen (pasi.eronen@nokia.com)


Mailing Lists:
General Discussion: emu@ietf.org
To Subscribe: https://www1.ietf.org/mailman/listinfo/emu
Archive: http://www.ietf.org/mail-archive/web/emu/current/index.html

Description of Working Group:

The Extensible Authentication Protocol (EAP) [RFC 3748] is a network
access authentication framework used in the PPP, 802.11, 802.16, VPN,
PANA, and in some functions in 3G networks. EAP itself is a simple
protocol and actual authentication happens in EAP methods.

Over 40 different EAP methods exist. Most of these methods are
proprietary methods, but some are documented in informational RFCs. In
the past the lack of documented, open specifications has been a
deployment and interoperability problem. There are currently only two
EAP methods in the standards track that implement features such as key
derivation that are required for many modern applications.
Authentication types and credentials continue to evolve as do
requirements for EAP methods.

This group is chartered to work on the following types of mechanisms to
meet requirements relevant to EAP methods in RFC 3748, RFC 4017, RFC
4962 and EAP Keying:

- A mechanism based on strong shared secrets. This mechanism should
strive to be simple and compact for implementation in resource
constrained environments.

- A document that defines EAP channel bindings and provides guidance for
establishing EAP channel bindings within EAP methods.

- Enable TLS-based EAP methods to support channel bindings. This item
will not generate a new method; rather, it will focus on adding support
for EAP channel bindings to the tunneled method (described below), and
if possible, other TLS-based EAP methods. Potential mechanisms for
adding channel binding support will be investigated, including tunneling
of channel binding parameters, or a TLS extension, or other standard TLS
mechanism

- A mechanism to support extensible communication within a TLS protected
tunnel. This mechanism will support meeting the requirements of an
enhanced TLS mechanism, a password based authentication mechanism, and
additional inner authentication mechanisms. It will also support channel
bindings (as described above) in order to meet RFC 4962 requirements.

- A mechanism that makes use of existing password databases such as AAA
databases. This item will be based on the above tunnel method.

Goals and Milestones:

Jun 2008 Submit Tunnel and Password Method requirements first Draft Sep
2008 Submit EAP Channel Bindings First Draft Sep 2008 Submit Tunnel
Method first draft Oct 2008 Submit TLS based method channel binding
first draft Oct 2008 Submit Password Method first draft Jan 2009 Send
EAP Channel Bindings to IESG Mar 2009 Send Tunnel Method to IESG Apr
2009 Send TLS based method channel binding to IESG Apr 2009 Send
Password based method to IESG
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed May 28 14:28:38 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A26AF3A6A38;
	Wed, 28 May 2008 14:28:38 -0700 (PDT)
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 BB2E83A6916
	for <ops-area@core3.amsl.com>; Wed, 28 May 2008 14:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[AWL=0.152, 
	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 kg8LF+MTaNZQ for <ops-area@core3.amsl.com>;
	Wed, 28 May 2008 14:28:37 -0700 (PDT)
Received: from QMTA08.westchester.pa.mail.comcast.net
	(qmta08.westchester.pa.mail.comcast.net [76.96.62.80])
	by core3.amsl.com (Postfix) with ESMTP id C1A913A6831
	for <ops-area@ietf.org>; Wed, 28 May 2008 14:28:36 -0700 (PDT)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35])
	by QMTA08.westchester.pa.mail.comcast.net with comcast
	id X9HR1Z0090ldTLk5801s00; Wed, 28 May 2008 21:28:44 +0000
Received: from Harrington73653 ([24.128.66.199])
	by OMTA04.westchester.pa.mail.comcast.net with comcast
	id X9Uf1Z0054HwxpC3Q00000; Wed, 28 May 2008 21:28:41 +0000
X-Authority-Analysis: v=1.0 c=1 a=MwdLkbQAy93gS2o36J8A:9
	a=5dGytZlial1wf2rNGDEH_NcJqm8A:4 a=si9q_4b84H0A:10 a=hPjdaMEvmhQA:10
	a=50e4U0PicR4A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: <ops-dir@ietf.org>,
	"'OPS Area'" <ops-area@ietf.org>
Date: Wed, 28 May 2008 17:28:39 -0400
Message-ID: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcjBCcspnqCTXpNTQEmOvSU1las4Ew==
Subject: [OPS-AREA] SNMP notification configuration
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi,

The ISMS WG could use some operator feedback.

We are developing the ability to use SSH to secure SNMP. Since
operators already use SSH to secure CLI shells and Xwindows and other
things, this is reasonably straightforward for SNMP request-response
traffic.

Question #1:
For SNMP notifications, the SNMP agent will need to act as an SSH
client, and the SNMP notification receivers will need to act as an SSH
server. Will operators find this objectionable?

Question #2:
Would operators prefer to modify their existing user and key
management solutions, such as implementation-dependent CLI scripts, to
configure SSH clients on devices where they may not be found now, or
would operators prefer to have the ISMS WG develop a standard MIB
module to configure and manage the SSH credentials needed to have SNMP
agents act as SSH clients?

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

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Thu May 29 07:45:12 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 067DA28C278;
	Thu, 29 May 2008 07:45:12 -0700 (PDT)
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 618D33A6803;
	Thu, 29 May 2008 07:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level: 
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, 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 AGw-KtpNGgkx; Thu, 29 May 2008 07:38:56 -0700 (PDT)
Received: from blu0-omc3-s10.blu0.hotmail.com (blu0-omc3-s10.blu0.hotmail.com
	[65.55.116.85])
	by core3.amsl.com (Postfix) with ESMTP id D08AB3A6B98;
	Thu, 29 May 2008 07:38:52 -0700 (PDT)
Received: from BLU137-W45 ([65.55.116.73]) by blu0-omc3-s10.blu0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 29 May 2008 07:38:52 -0700
Message-ID: <BLU137-W45C1225E37C03B1CCF5BAC93BF0@phx.gbl>
X-Originating-IP: [24.16.124.122]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: David Harrington <ietfdbh@comcast.net>, <ops-dir@ietf.org>, 'OPS Area'
	<ops-area@ietf.org>
Date: Thu, 29 May 2008 07:38:52 -0700
Importance: Normal
In-Reply-To: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
References: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 29 May 2008 14:38:52.0121 (UTC)
	FILETIME=[B6CE9C90:01C8C199]
X-Mailman-Approved-At: Thu, 29 May 2008 07:45:08 -0700
Subject: Re: [OPS-AREA] [OPS-DIR] SNMP notification configuration
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1959820757=="
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

--===============1959820757==
Content-Type: multipart/alternative;
	boundary="_745c3157-5c74-4cbc-af36-f7e692ad0ea0_"

--_745c3157-5c74-4cbc-af36-f7e692ad0ea0_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Comments below.=20

> From: ietfdbh@comcast.net
> To: ops-dir@ietf.org; ops-area@ietf.org
> Date: Wed, 28 May 2008 17:28:39 -0400
> Subject: [OPS-DIR] SNMP notification configuration
>=20
> Hi,
>=20
> The ISMS WG could use some operator feedback.
>=20
> We are developing the ability to use SSH to secure SNMP. Since
> operators already use SSH to secure CLI shells and Xwindows and other
> things, this is reasonably straightforward for SNMP request-response
> traffic.
>=20
> Question #1:
> For SNMP notifications, the SNMP agent will need to act as an SSH
> client, and the SNMP notification receivers will need to act as an SSH
> server. Will operators find this objectionable?

Assuming that the SNMP notification receivers are hosts running sshd,=20
this doesn't seem problematic. =20

> Question #2:
> Would operators prefer to modify their existing user and key
> management solutions, such as implementation-dependent CLI scripts, to
> configure SSH clients on devices where they may not be found now, or
> would operators prefer to have the ISMS WG develop a standard MIB
> module to configure and manage the SSH credentials needed to have SNMP
> agents act as SSH clients?

Personally, it seems a lot easier to deal with scripts than to attempt to c=
onfigure SSH via MIBs.=20

--_745c3157-5c74-4cbc-af36-f7e692ad0ea0_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class=3D'hmmessage'>
Comments below. <br><br>&gt; From: ietfdbh@comcast.net<br>&gt; To: ops-dir@=
ietf.org; ops-area@ietf.org<br>&gt; Date: Wed, 28 May 2008 17:28:39 -0400<b=
r>&gt; Subject: [OPS-DIR] SNMP notification configuration<br>&gt; <br>&gt; =
Hi,<br>&gt; <br>&gt; The ISMS WG could use some operator feedback.<br>&gt; =
<br>&gt; We are developing the ability to use SSH to secure SNMP. Since<br>=
&gt; operators already use SSH to secure CLI shells and Xwindows and other<=
br>&gt; things, this is reasonably straightforward for SNMP request-respons=
e<br>&gt; traffic.<br>&gt; <br>&gt; Question #1:<br>&gt; For SNMP notificat=
ions, the SNMP agent will need to act as an SSH<br>&gt; client, and the SNM=
P notification receivers will need to act as an SSH<br>&gt; server. Will op=
erators find this objectionable?<br><br>Assuming that the SNMP notification=
 receivers are hosts running sshd, <br>this doesn't seem problematic.&nbsp;=
 <br><br>&gt; Question #2:<br>&gt; Would operators prefer to modify their e=
xisting user and key<br>&gt; management solutions, such as implementation-d=
ependent CLI scripts, to<br>&gt; configure SSH clients on devices where the=
y may not be found now, or<br>&gt; would operators prefer to have the ISMS =
WG develop a standard MIB<br>&gt; module to configure and manage the SSH cr=
edentials needed to have SNMP<br>&gt; agents act as SSH clients?<br><br>Per=
sonally, it seems a lot easier to deal with scripts than to attempt to conf=
igure SSH via MIBs. <br></body>
</html>=

--_745c3157-5c74-4cbc-af36-f7e692ad0ea0_--

--===============1959820757==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area

--===============1959820757==--


From ops-area-bounces@ietf.org  Thu May 29 08:38:10 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 293A728C152;
	Thu, 29 May 2008 08:38:10 -0700 (PDT)
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 EC56B3A69CE;
	Thu, 29 May 2008 08:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611]
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 Fl9muqguVxkJ; Thu, 29 May 2008 08:38:07 -0700 (PDT)
Received: from wes.hardakers.net (dcn236-43.dcn.davis.ca.us [168.150.236.43])
	by core3.amsl.com (Postfix) with ESMTP id 94B7B3A694B;
	Thu, 29 May 2008 08:38:07 -0700 (PDT)
Received: from wes.hardakers.net (wlap.dyn.hardakers.net [127.0.0.1])
	by wes.hardakers.net (Postfix) with ESMTP id A33BF39A213;
	Thu, 29 May 2008 08:36:05 -0700 (PDT)
DKIM-Signature: v=0.5; a=rsa-sha1; c=relaxed; d=hardakers.net;
	h=received:from:to:cc:subject:organization:references:date:in-reply-to:message-id:user-agent:mime-version:content-type;
	q=dns/txt; s=wesmail; bh=9/yCw5CNw/0evmhuJ3GfMDSTlys=;
	b=gsRe3bPohwpL+c6T46hmkFLTSdAHS0vNTQUcbBTlW3xzJ9BPTbhMBNXiD4CCqzjhqJqrlk3G0MLkR/rBxevqezytg3Y5avsHcYhViRmArwAcQObP6Cfdolstbh6Bsr3zlRNNcG+FZP6OQeWCtMPpFtsaJ2Jl9IWBP3KvBzSLaQ4=
Received: by wes.hardakers.net (Postfix, from userid 274)
	id 646F039A214; Thu, 29 May 2008 08:36:05 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Organization: Sparta
References: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
	<BLU137-W45C1225E37C03B1CCF5BAC93BF0@phx.gbl>
Date: Thu, 29 May 2008 08:36:05 -0700
In-Reply-To: <BLU137-W45C1225E37C03B1CCF5BAC93BF0@phx.gbl> (Bernard Aboba's
	message of "Thu, 29 May 2008 07:38:52 -0700")
Message-ID: <sdiqwxw2ai.fsf@wes.hardakers.net>
User-Agent: Gnus/5.110007 (No Gnus v0.7) XEmacs/21.4.21 (linux, no MULE)
MIME-Version: 1.0
Cc: ops-dir@ietf.org, 'OPS Area' <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [OPS-DIR] SNMP notification configuration
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

>>>>> On Thu, 29 May 2008 07:38:52 -0700, Bernard Aboba <bernard_aboba@hotmail.com> said:

BA> Personally, it seems a lot easier to deal with scripts than to
BA> attempt to configure SSH via MIBs.

I think David's question was worded a bit oddly...  He wasn't saying it
was the only way to do things, the question is: should there be a way to
do it via MIBs so that a manager could be written to support assisted
configuration or would no one actually use that and want to use personal
scripts anyway (IE, would the effort to write a MIB be wasted and unused).
-- 
Wes Hardaker
Sparta, Inc.
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Fri May 30 00:37:02 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC68E3A6858;
	Fri, 30 May 2008 00:37:02 -0700 (PDT)
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 C18DA3A6844;
	Fri, 30 May 2008 00:37:01 -0700 (PDT)
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 VkAvfkA1k-9M; Fri, 30 May 2008 00:36:58 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1])
	by core3.amsl.com (Postfix) with ESMTP id D1FF23A6858;
	Fri, 30 May 2008 00:36:57 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id m4U7YFHZ022494;
	Fri, 30 May 2008 10:34:15 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m4U7YChQ022491;
	Fri, 30 May 2008 10:34:13 +0300
Date: Fri, 30 May 2008 10:34:12 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: David Harrington <ietfdbh@comcast.net>
In-Reply-To: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
Message-ID: <alpine.LRH.1.10.0805301029530.22357@netcore.fi>
References: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.93/6816/Fri Apr 18 03:41:09 2008 on otso.netcore.fi
X-Virus-Status: Clean
Cc: ops-dir@ietf.org, 'OPS Area' <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [OPS-DIR] SNMP notification configuration
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

On Wed, 28 May 2008, David Harrington wrote:
> Question #1:
> For SNMP notifications, the SNMP agent will need to act as an SSH
> client, and the SNMP notification receivers will need to act as an SSH
> server. Will operators find this objectionable?

In our case, routers, switches, etc. are not allowed to log in (ssh 
allow_hosts, firewall rules in various places) to the management 
systems.  As a result this approach would require significant changes 
to ACL policies.

I'm not saying this is a show-stopper, but I suspect many (most?) 
other networks will require similar changes, and depending how easy 
for them it is to enumerate all the possible IP addresses or prefixes 
their SNMP-notifying equipment might use could be a challenge.

> Question #2:
> Would operators prefer to modify their existing user and key
> management solutions, such as implementation-dependent CLI scripts, to
> configure SSH clients on devices where they may not be found now, or
> would operators prefer to have the ISMS WG develop a standard MIB
> module to configure and manage the SSH credentials needed to have SNMP
> agents act as SSH clients?

I expects scripts to be used.  I would not expect SNMP (write) MIBs to 
be used.  It's possible that a MIB could be used in a read-only mode 
to verify configuration correctness, however.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Fri May 30 09:58:09 2008
Return-Path: <ops-area-bounces@ietf.org>
X-Original-To: ops-area-archive@optimus.ietf.org
Delivered-To: ietfarch-ops-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AD263A69EC;
	Fri, 30 May 2008 09:58:09 -0700 (PDT)
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 2435F3A684F;
	Thu, 29 May 2008 23:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311]
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 UT0vWfb3GnDI; Thu, 29 May 2008 23:23:23 -0700 (PDT)
Received: from lemland.kurtis.pp.se (lemland.kurtis.pp.se
	[IPv6:2001:670:87:2::25])
	by core3.amsl.com (Postfix) with ESMTP id B39203A6B60;
	Thu, 29 May 2008 23:23:16 -0700 (PDT)
Received: from [10.140.1.222] (rdcg01.wifihubtelecom.net [213.174.113.122])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(Client did not present a certificate)
	by lemland.kurtis.pp.se (Postfix) with ESMTP id F192D78C2B;
	Fri, 30 May 2008 09:23:12 +0300 (EEST)
Message-Id: <81227381-2502-4287-B35A-965F40096328@kurtis.pp.se>
From: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
To: Bernard Aboba <bernard_aboba@hotmail.com>
In-Reply-To: <BLU137-W45C1225E37C03B1CCF5BAC93BF0@phx.gbl>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Fri, 30 May 2008 08:23:11 +0200
References: <003101c8c109$cca067f0$0600a8c0@china.huawei.com>
	<BLU137-W45C1225E37C03B1CCF5BAC93BF0@phx.gbl>
X-Mailer: Apple Mail (2.924)
X-Mailman-Approved-At: Fri, 30 May 2008 09:58:07 -0700
Cc: ops-dir@ietf.org, 'OPS Area' <ops-area@ietf.org>
Subject: Re: [OPS-AREA] [OPS-DIR] SNMP notification configuration
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org


On 29 maj 2008, at 16.38, Bernard Aboba wrote:

> > Question #1:
> > For SNMP notifications, the SNMP agent will need to act as an SSH
> > client, and the SNMP notification receivers will need to act as an  
> SSH
> > server. Will operators find this objectionable?
>
> Assuming that the SNMP notification receivers are hosts running sshd,
> this doesn't seem problematic.
>
> > Question #2:
> > Would operators prefer to modify their existing user and key
> > management solutions, such as implementation-dependent CLI  
> scripts, to
> > configure SSH clients on devices where they may not be found now, or
> > would operators prefer to have the ISMS WG develop a standard MIB
> > module to configure and manage the SSH credentials needed to have  
> SNMP
> > agents act as SSH clients?
>
> Personally, it seems a lot easier to deal with scripts than to  
> attempt to configure SSH via MIBs.


I would actually agree with Bernard. In addition, we have for years  
been trying to get more vendors to implement SSHv2 public key  
authentication, i.e no user/password login exactly to make it easier  
to script.

Best regards,

- kurtis -



_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


