From ops-nm-bounces@ietf.org Wed Jan 03 03:43:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H21i4-0000QZ-Lr; Wed, 03 Jan 2007 03:42:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H21i3-0000Pu-UN; Wed, 03 Jan 2007 03:42:55 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H21i0-0006Gw-8M; Wed, 03 Jan 2007 03:42:55 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l038girD007670; Wed, 3 Jan 2007 03:42:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Received: from 300216erh2.post.avaya.com ([198.152.7.49]) by
	IS0004AVEXU1.global.avaya.com with Microsoft
	SMTPSVC(5.0.2195.6713); Tue, 19 Dec 2006 09:54:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Received: from nj300815-ier2.net.avaya.com (nj300815-ier2.net.avaya.com
	[198.152.12.103]) by 300216erh2.post.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBJ9sjjv007652 for
	<dromasca@telaviv.exchange.avaya.com>;
	Tue, 19 Dec 2006 02:54:46 -0700
Received: from nj300815-nj-iereast.avaya.com (h198-152-12-104.avaya.com
	[198.152.12.104]) by nj300815-ier2.net.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBJ7WCMs013530 for
	<dromasca@avaya.com>; Tue, 19 Dec 2006 02:54:47 -0500
Received: from bierator.ibr.cs.tu-bs.de ([134.169.34.9]) by
	nj300815-nj-iereast.avaya.com with ESMTP; 19 Dec 2006 02:53:32 -0500
Received: from bierator.ibr.cs.tu-bs.de (list@localhost [127.0.0.1]) by
	bierator.ibr.cs.tu-bs.de (8.13.4/8.13.4/Debian-3sarge3) with
	ESMTP id kBJ7s3F0016453; Tue, 19 Dec 2006 08:54:08 +0100
Received: from nj300815-ier2.net.avaya.com (nj300815-ier2.net.avaya.com
	[198.152.12.103]) by bierator.ibr.cs.tu-bs.de
	(8.13.4/8.13.4/Debian-3sarge3) with ESMTP id kBJ7rsAG016433
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168
	verify=NOT) for <nmrg@ibr.cs.tu-bs.de>;
	Tue, 19 Dec 2006 08:54:00 +0100
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51]) by nj300815-ier2.net.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBJ7rqKT024301 for
	<nmrg@ibr.cs.tu-bs.de>; Tue, 19 Dec 2006 02:53:53 -0500
Received: from 300815erh2.post.avaya.com ([198.152.6.49]) by
	IS0004AVEXU1.global.avaya.com with Microsoft
	SMTPSVC(5.0.2195.6713); Mon, 18 Dec 2006 21:32:37 +0200
Received: from co300216-ier2.net.avaya.com (co300216-ier2.net.avaya.com
	[198.152.13.103]) by 300815erh2.post.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIJWa1g000326 for
	<dromasca@telaviv.exchange.avaya.com>;
	Mon, 18 Dec 2006 14:32:36 -0500
Received: from co300216-co-ierwest.avaya.com (h198-152-13-104.avaya.com
	[198.152.13.104]) by co300216-ier2.net.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIJRLYO001667 for
	<dromasca@avaya.com>; Mon, 18 Dec 2006 14:32:30 -0500
Received: from lists.ietf.org (HELO megatron.ietf.org) ([156.154.16.145]) by
	co300216-co-ierwest.avaya.com with ESMTP; 18 Dec 2006 14:31:38 -0500
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by
	megatron.ietf.org with esmtp (Exim 4.43) id 1GwOCk-00055A-Iu;
	Mon, 18 Dec 2006 14:31:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with
	esmtp (Exim 4.43) id 1GwOCj-00054X-Hm;
	Mon, 18 Dec 2006 14:31:17 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103]) by
	ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwOCh-0001Sr-2S;
	Mon, 18 Dec 2006 14:31:17 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51]) by nj300815-ier2.net.avaya.com
	(Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIJVBEC009649;
	Mon, 18 Dec 2006 14:31:14 -0500
content-class: urn:content-classes:message
Date: Wed, 3 Jan 2007 10:42:43 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C08CAF8@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPS Area BOFs in Prague
Thread-Index: AcccV6ii14zulLX7R3CFlQvi3jCmlA==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <ops-nm@ietf.org>,
	"MIB Doctors" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	"DNS Directorate" <dns-dir@ops.ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: nmrg@ibr.cs.tu-bs.de
Subject: [OPS-NM] OPS Area BOFs in Prague
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

=20
Happy New Year!

This is a final reminder that we shall schedule for the Prague IETF a
number of BOFs or mini-BOFs in the OPS area meeting slots with the
intention to bring to attention new ideas in the operations and
management area and discuss which of those are worth becoming subject
for future standardization, research or prototyping work. We (David and
Dan) will be meeting by the end of the month to discuss the proposed BOF
subjects, please send your proposals as soon as you can, but not later
than January 24. Any of the lists in the area would do, but
ops-area@ietf.org would probably be the best.=20

Note that if you intent to ask for a separate and dedicated BOF session
rather than for a mini-BOF in the OPS area meeting slots the deadline
for submitting a BOF request is January 15.=20


David and Dan


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Fri Jan 05 01:29:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2iZ0-0002MO-Pd; Fri, 05 Jan 2007 01:28:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2iYz-0002HJ-J6; Fri, 05 Jan 2007 01:28:25 -0500
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H2iYx-0006v7-5i; Fri, 05 Jan 2007 01:28:25 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l056SCUX020603; Fri, 5 Jan 2007 01:28:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 5 Jan 2007 08:28:11 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C0C7AF8@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for January 11, 2007 Telechat 
Thread-Index: AccwVVOQ6AXq2LcyTfSZHh6Xl9jynQAPNhBg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>,
	"MIB Doctors" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Cc: 
Subject: [OPS-NM] FW: PRELIMINARY Agenda and Package for January 11,
	2007 Telechat 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

=20
Please find below the preliminary agenda of the January 11, 2007 IESG
meeting. Please let me know if you have any comments or concerns related
to the documents brought to the approval of the IESG until January 10,
2007 COB the latest.=20

Thanks and Regards,

Dan




INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the January 11, 2007 IESG Teleconference

=20

     =20
2. Protocol Actions
	Reviews should focus on these questions: "Is this document a
	reasonable basis on which to build the salient part of the
Internet
	infrastructure? If not, what changes would make it so?"


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-ccamp-automesh-03.txt
    Routing extensions for discovery of Multiprotocol (MPLS) Label
Switch

    Router (LSR) Traffic Engineering (TE) mesh membership (Proposed
Standard) -=20
    1 of 10=20
    Token: Ross Callon
  o draft-ietf-dkim-base-07.txt
    DomainKeys Identified Mail (DKIM) Signatures (Proposed Standard) - 2
of 10=20
    Token: Russ Housley
  o draft-ietf-dhc-timezone-option-05.txt
    A Timezone Option for DHCP (Proposed Standard) - 3 of 10=20
    Token: Jari Arkko
  o draft-narten-ipr-3979-3rd-party-fix-00.txt
    Clarification of the 3rd Party Disclosure procedure in RFC 3979
(BCP)
- 4=20
    of 10=20
    Note: Update to BCP 79. Document shepherd is Harald Alvestrand. It
is
an=20
    IPR WG draft.=20
    Token: Brian Carpenter
  o Two-document ballot:  - 5 of 10
     - draft-ietf-kitten-gssapi-domain-based-names-03.txt
       GSS-API Domain-Based Service Names and Name Type (Proposed
Standard)=20
       Note: Proto Shepherd: jaltman@secure-endpoints.com=20
     - draft-ietf-kitten-krb5-gssapi-domain-based-names-03.txt
       GSS-API Domain-Based Service Names Mapping for the Kerberos V GSS

       Mechanism (Proposed Standard)=20
    Token: Sam Hartman
  o draft-ietf-pkix-srvsan-04.txt
    Internet X.509 Public Key Infrastructure Subject Alternative Name
for

    expression of service name (Proposed Standard) - 6 of 10=20
    Token: Russ Housley
  o draft-ietf-rohc-sigcomp-impl-guide-10.txt
    Implementer's Guide for SigComp (Proposed Standard) - 7 of 10=20
    Token: Magnus Westerlund
  o draft-ietf-rohc-formal-notation-13.txt
    Formal Notation for Robust Header Compression (ROHC-FN) (Proposed
Standard)=20
    - 8 of 10=20
    Token: Magnus Westerlund
  o draft-ietf-radext-filter-06.txt
    RADIUS Filter Rule Attribute (Proposed Standard) - 9 of 10=20
    Note: Note: David Nelson is the Document Shepherd=20
    Token: David Kessens
  o rfc3989.txt
    MIDCOM Protocol Semantics (BCP) - 10 of 10=20
    Token: Magnus Westerlund

2.1.2 Returning Item
  o draft-ietf-mip6-ikev2-ipsec-08.txt
    Mobile IPv6 Operation with IKEv2 and the revised IPsec Architecture=20
    (Proposed Standard) - 1 of 1=20
    Note: PROTO Shepherd is Basavaraj Patil
<basavaraj.patil@nokia.com>=20
    Token: Jari Arkko


2.2 Individual Submissions
2.2.1 New Item
  o draft-andersson-rtg-gmpls-change-07.txt
    Change Process for Multiprotocol Label Switching (MPLS) and
Generalized=20
    MPLS (GMPLS) Protocols and Procedures (BCP) - 1 of 2=20
    Note: Brian shepherds on behalf of the Routing ADs=20
    Token: Brian Carpenter
  o draft-housley-aaa-key-mgmt-06.txt
    Guidance for AAA Key Management (BCP) - 2 of 2=20
    Token: Sam Hartman

2.2.2 Returning Item
NONE
2.2.3 For Action
  o draft-diao-eipv4-01.txt
    Source Route Based Extensible IP Network (EIPv4) (Proposed Standard)
-
1 of=20
    1=20
    Note: Instructed author to participate in ID-Loc split design in RAM

    Token: Jari Arkko

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-dna-link-information-05.txt
    Link-layer Event Notifications for Detecting Network Attachments=20
    (Informational) - 1 of 1=20
    Token: Jari Arkko

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-snell-atompub-feed-license-10.txt
    Atom License Extension (Experimental) - 1 of 1=20
    Token: Lisa Dusseault

3.2.2 Returning Item
  o draft-klensin-norm-ref-02.txt
    A Process Experiment in Normative Reference Handling (Experimental)
-
1 of=20
    1=20
    Note: RFC 3933 process experiment, substantially reduced in scope in
02=20
    version.=20
    Token: Brian Carpenter



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Wed Jan 10 06:31:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4bf9-00026O-JE; Wed, 10 Jan 2007 06:30:35 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4bf8-00025P-Ke; Wed, 10 Jan 2007 06:30:34 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1H4bf6-00012I-AV; Wed, 10 Jan 2007 06:30:34 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0ABUULQ024088; Wed, 10 Jan 2007 06:30:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
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 Jan 2007 13:30:29 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C13410E@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPS Area Open Hours
Thread-Index: Acc0qrsbrZp9CZTtRDuogWddSosg9Q==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>,
	"MIB Doctors" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<ietfmibs@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: IESG <iesg@ietf.org>
Subject: [OPS-NM] OPS Area Open Hours
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org


David Kessens and Dan Romascanu are holding Open Hours to discuss issues
related to the IETF Operations and Management Area on the first and
third Tuesday of each month at 10-11AM PT / 1-2PM ET / 7-8PM CET. The
series of calls starts on 1/16, and the other open hours slots until the
Prague IETF meeting are 2/6, 2/20, 3/6.=20

All WG chairs, document editors, contributors, participants and in
general all interested to talk with us about the area and IETF business
are invited to ask for a meeting slot using the OPS Area wiki
http://www1.tools.ietf.org/area/ops/trac/wiki/WikiStart, and/or to write
us directly at david.kessens@nokia.com or dromasca@avaya.com. An e-mail
will be sent in response to acknowledge the time slot and provide a
telephone bridge number to be used in the call.=20

David and Dan
=20


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Tue Jan 16 10:30:22 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6qG8-0005Ie-0R; Tue, 16 Jan 2007 10:30:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H6qG6-0005D0-7M; Tue, 16 Jan 2007 10:29:58 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H6qG4-0001Kz-UA; Tue, 16 Jan 2007 10:29:58 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0GFTnwY023963; Tue, 16 Jan 2007 10:29:49 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
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 Jan 2007 17:29:48 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C1E1B20@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: draft-heard-rfc4181-update (RFC 4181 Update to
	Recognize the IETF Trust) to BCP 
Thread-Index: Acc5gsj5tf+QpATrRkK+efYbYZeRmwAAETSA
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>, <ops-chairs@ietf.org>, 
	"MIB Doctors" <mib-doctors@ietf.org>, <ietfmibs@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [OPS-NM] FW: Last Call: draft-heard-rfc4181-update (RFC 4181 Update
	to Recognize the IETF Trust) to BCP 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

=20


=20

-----Original Message-----
From: The IESG [mailto:iesg-secretary@ietf.org]=20
Sent: Tuesday, January 16, 2007 5:22 PM
To: IETF-Announce
Subject: Last Call: draft-heard-rfc4181-update (RFC 4181 Update to
Recognize the IETF Trust) to BCP=20

The IESG has received a request from an individual submitter to consider
the following document:

- 'RFC 4181 Update to Recognize the IETF Trust '
   <draft-heard-rfc4181-update-00.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-02-13. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-heard-rfc4181-update-00.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dview_id&dTag=
=3D
15574&rfc_flag=3D0


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


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Fri Jan 19 01:53:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7nbZ-0007ZV-2i; Fri, 19 Jan 2007 01:52:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7nbX-0007Yw-AU; Fri, 19 Jan 2007 01:52:03 -0500
Received: from 103.13.152.198.in-addr.arpa ([198.152.13.103]
	helo=co300216-ier2.net.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H7nbV-00050k-Rk; Fri, 19 Jan 2007 01:52:03 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0J6pxJb003631; Fri, 19 Jan 2007 01:52:00 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 19 Jan 2007 08:51:59 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C210417@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Documents on IESG Telechat Agenda for January 25, 2007
Thread-Index: Acc7jq6aVbChUbQjQvuAVDiYPlES2wAB1a8w
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<ops-nm@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: 
Subject: [OPS-NM] FW: Documents on IESG Telechat Agenda for January 25, 2007
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

=20


Please see below for all documents on the agenda for the next IESG
telechat.

I would appreciate if you can send me your issues and comments by Wed
January 24, 2007 COB

Dan

This agenda was generated at 18:0:57 EDT, January 18, 2007 Web version
of this agenda can be found at:
http://www.ietf.org/IESG/agenda.html

2. Protocol Actions
	Reviews should focus on these questions: "Is this document a
	reasonable basis on which to build the salient part of the
Internet
	infrastructure? If not, what changes would make it so?"


2.1 WG Submissions
2.1.1 New Item
  o Two-document ballot:  - 1 of 7
     - draft-ietf-ips-iwarp-da-05.txt
       Datamover Architecture for iSCSI (DA) (Informational)=20
       Note: PROTO Document Shepherd: David Black (black_david@emc.com)=20
     - draft-ietf-ips-iser-06.txt
       iSCSI Extensions for RDMA Specification (Proposed Standard)=20
       Note: Document Shepherd: David Black (black_david@emc.com)=20
    Token: Lars Eggert
  o draft-ietf-ccamp-rsvp-restart-ext-07.txt
    Extensions to GMPLS RSVP Graceful Restart (Proposed Standard) - 2 of
7=20
    Token: Ross Callon
  o draft-ietf-pim-mib-v2-09.txt
    Protocol Independent Multicast MIB (Proposed Standard) - 3 of 7=20
    Token: Bill Fenner
  o draft-ietf-crisp-iris-common-transport-04.txt
    A Common Schema for Internet Registry Information Service Transfer=20
    Protocols (Proposed Standard) - 4 of 7=20
    Token: Ted Hardie
  o draft-ietf-crisp-iris-lwz-07.txt
    A Lightweight UDP Transfer Protocol for the the Internet Registry=20
    Information Service (Proposed Standard) - 5 of 7=20
    Token: Ted Hardie
  o draft-ietf-crisp-iris-xpc-05.txt
    XML Pipelining with Chunks for the Information Registry Information
Service=20
    (Proposed Standard) - 6 of 7=20
    Token: Ted Hardie
  o draft-ietf-lemonade-compress-07.txt
    The IMAP COMPRESS Extension (Proposed Standard) - 7 of 7=20
    Note: Eric Burger is the Shepherd for this document.=20
    Token: Ted Hardie

2.1.2 Returning Item
  o draft-ietf-tsvwg-tcp-mib-extension-14.txt
    TCP Extended Statistics MIB (Proposed Standard) - 1 of 2=20
    Note: PROTO Document Shepherd: James Polk. MIB Doctors: Dan
Romascanu, Bert=20
    Wijnen=20
    Token: Lars Eggert
  o rfc3989.txt
    MIDCOM Protocol Semantics (BCP) - 2 of 2=20
    Token: Magnus Westerlund


2.2 Individual Submissions
2.2.1 New Item
  o draft-bonica-internet-icmp-14.txt
    Modifying ICMP to Support Multi-part Messages (Proposed Standard) -
1 of 4=20
    Token: Jari Arkko
  o draft-manral-ipsec-rfc4305-bis-errata-03.txt
    Cryptographic Algorithm Implementation Requirements for
Encapsulating=20
    Security Payload (ESP) and Authentication Header (AH) (Proposed
Standard) -=20
    2 of 4=20
    Token: Russ Housley
  o draft-solinas-ui-suites-01.txt
    Suite B Cryptographic Suites for IPsec (Proposed Standard) - 3 of 4=20
    Token: Russ Housley
  o draft-daigle-unaptr-01.txt
    Domain-based Application Service Location Using URIs and the Dynamic

    Delegation Discovery Service (DDDS) (Proposed Standard) - 4 of 4=20
    Token: Ted Hardie

2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-widex-requirements-04.txt
    Widget Description Exchange Service (WIDEX) Requirements
(Informational) -=20
    1 of 1=20
    Token: Lisa Dusseault

3.1.2 Returning Item
NONE

3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-cam-winget-eap-fast-06.txt
    The Flexible Authentication via Secure Tunneling Extensible
Authentication=20
    Protocol Method (EAP-FAST) (Informational) - 1 of 3=20
    Token: Russ Housley
  o draft-conboy-mime-opf-00.txt
    Media Type Registrations for OEBPS Package File (OPF)
(Informational) - 2=20
    of 3=20
    Note: Sent to ietf-types in October of 2006=20
    Token: Ted Hardie
  o draft-irtf-dtnrg-arch-08.txt
    Delay-Tolerant Networking Architecture (Informational) - 3 of 3=20
    Note: Advancing according to: draft-irtf-rfcs-00.txt. Document
Shepherd:=20
    Stephen Farrell (stephen.farrell@cs.tcd.ie)=20
    Token: Lars Eggert

3.2.2 Returning Item
NONE
3.3 Individual Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG
approval.
=20

	Other matters may be recorded in comments to be passed on
	to the RFC Editor as community review of the document.


3.3.1 New Item
NONE
3.3.2 Returning Item
  o draft-deoliveira-diff-te-preemption-06.txt
    LSP Preemption Policies for MPLS Traffic Engineering (Informational)
- 1 of=20
    2=20
    Token: Ross Callon
  o draft-zorn-radius-keywrap-12.txt
    RADIUS Attributes for the Delivery of Keying Material
(Informational) - 2=20
    of 2=20
    Token: Russ Housley

3.3.3 For Action
  o draft-burke-vxml-02.txt
    SIP Interface to VoiceXML Media Services (Informational) - 1 of 1=20
    Token: Cullen Jennings



_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Sat Jan 20 13:03:28 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H8KXa-00058X-W0; Sat, 20 Jan 2007 13:02:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H8KXZ-00058M-Jp
	for ops-nm@ietf.org; Sat, 20 Jan 2007 13:02:09 -0500
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H8KXV-0004kl-8o
	for ops-nm@ietf.org; Sat, 20 Jan 2007 13:02:09 -0500
Received: from [128.96.58.98] (vpntnlA98.research.telcordia.com [128.96.58.98])
	by thumper.research.telcordia.com (8.13.6/8.13.5) with ESMTP id
	l0KI220g025011
	for <ops-nm@ietf.org>; Sat, 20 Jan 2007 13:02:02 -0500 (EST)
Message-ID: <45B25916.7050801@research.telcordia.com>
Date: Sat, 20 Jan 2007 13:01:58 -0500
From: Sanjai Narain <narain@research.telcordia.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: ops-nm@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by
	thumper.research.telcordia.com id l0KI220g025011
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Subject: [OPS-NM] SIGCOMM Workshop on Internet Network Management
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please consider submitting to this workshop. -- Sanjai

INM=9207 (Five 9=92s)
Workshop on Designing and Managing High Availability Internet Services

Date: Friday, August 31, 2007
Place: Kyoto, Japan
In conjunction with ACM SIGCOMM

The design goal for voice networks is traditionally 99.999% or *five
9=92s* of availability. Though the Internet Protocol was designed to
provide *best effort* service, IP networks are now an essential part
of our communications infrastructure, with corresponding expectations
of high availability. Yet, in many ways, management of IP networks
remains a challenge, based more on ad-hoc tools than well-established
principles. IP networks are prone to failures not only as a result of
hardware faults, but also due to software bugs, misconfiguration,
human errors, malicious users, and inadequate network management
tools, exacerbated by the huge scale and diversity of the networks. In
addition, with the growth of IP overlay applications, service
providers must take into account both the health of the network and
that of the (typically) distributed applications infrastructure,
raising the ante from *simple* network management to end-to-end
service management. As a result, while IP networks and applications
generally work well, the *last 9* is an elusive goal and the
challenges continue to increase. This workshop broadens the theme of
INM=9206 to explore both network and application service management, in
the context of user expectations of high availability. The scope
ranges from large scale backbone networks to end-to-end application
performance and availability.

We are interested in questions such as the following: What metrics
should be used to measure network and service availability and
performance? How can overlay applications be designed to be resilient
to failures, or to be managed effectively in the presence of failures?
Given that routers and servers fail and are taken out of service
periodically, what techniques for planned maintenance, redundancy and
fail-over can be used, and what is their performance? What approaches
are needed for network and software configuration given the thousands
of elements and software modules that must be patched and updated in a
live network? Given the large volumes of *telemetry* data that is
available from networks and servers, what tools can be used to
facilitate rapid fault detection, isolation and remediation? Topics
for consideration include:

* measurement of and metrics for service availability and performance;
* designing reliable systems from unreliable components;
* the cost of building available systems;
* analysis of network-wide and systems configuration issues;
* system design, specification, and validation techniques;
* fault and performance management;
* control plane stability and failure resilience;
* data plane performance, availability and management;
* management of distributed application overlays;
* resilient protocols and applications;
* survivability modeling tools and approaches;
* impact of security on availability;
* adaptive networks.

The workshop solicits papers on completed work, position papers,
and/or work-in-progress papers on the challenges raised above. Papers
that bring out new and interesting approaches at an early stage of
their development are very welcome.

Submission guidelines Submissions must be no greater than 6 pages in
length, must be a pdf file, and must follow the formatting guidelines
at http://www.sigcomm.org/sigcomm2007/workshoppsg.html. Submissions
that deviate from these guidelines will be rejected without
consideration. Reviews will be single-blind: authors name and
affiliation should be included in the submission. Papers may be
submitted at the following URL: to-be-announced. Authors of accepted
papers are expected to present their papers at the workshop.
Submissions must be original work not under review at any other
workshop, conference, or journal.

Dates
* Abstract Registration Deadline: 26 April 2007
* Paper Submission Deadline: 3 May 2007
* Notification of Acceptance: 31 May 2007
* Camera Ready Deadline: 13 June 2007
* Workshop Date: 31 August 2007

INM=9207 Co-chairs
* Chuck Kalmanek (AT&T Labs)
* Richard Mortier (Microsoft Research)
* Geoffrey Xie (Naval Postgraduate Institute)

INM =9207 Technical Program Committee
* Eugene Ng (Rice University)
* Nick Feamster (Georgia Tech)
* Yin Zhang (UT Austin)
* Gianluca Iannaccone (Intel Research)
* Farnam Jahanian (University of Michigan)
* Patrick McDaniel (Pennsylvania State University)
* Rolf Stadler (KTH)
* Dah Ming Chiu (Chinese Univ. HK)
* Chuanyi Ji (George Tech)
* Sanjai Narain (Telcordia)
* Keisuke Ishibashi (NTT)
* Jennifer Rexford (Princeton University)
* Peter Sewell (Cambridge University)
* Sanjay Rao (Purdue University)
* Ken Calvert (University of Kentucky)
* Sue Moon (KAIST)
* Divesh Verma (IBM)
* Ran Atkinson (Extreme Networks)
* Emre Kiciman (Microsoft Research)
* Nick Duffield (AT&T Labs)
* Tim Griffin (Cambridge University)
* Ehab El-Shaer (DePaul University)

--=20
Sanjai Narain, Ph.D.
Senior Research Scientist
Information Assurance and Security Department
Telcordia Technologies, Inc.=20
1 Telcordia Drive, Room 1N-375
Piscataway, NJ 08854
732 699 2806 (T)
908 337 3636 (M)
narain@research.telcordia.com


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Tue Jan 23 19:06:13 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Ve4-0001Fd-R3; Tue, 23 Jan 2007 19:05:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H9Ve3-0001El-Du; Tue, 23 Jan 2007 19:05:43 -0500
Received: from nj300815-ier2.net.avaya.com ([198.152.12.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H9Ve1-0007Ju-DN; Tue, 23 Jan 2007 19:05:42 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0O05X24005036; Tue, 23 Jan 2007 19:05:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 24 Jan 2007 02:05:33 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C28A407@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LAST REMINDER: OPS Area mini-BOFs in Prague
Thread-Index: Acc0gtyrABLFfwSZQwe7EkhqqrpLqwGUzm1Q
References: <459B763C.1000600@alaxala.net> <45A445ED.9070509@hitachi.com>
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>, <aaa-doctors@ietf.org>, 
	"MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>, <ietfmibs@ietf.org>,
	<nmrg@ibr.cs.tu-bs.de>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
Subject: [OPS-NM] LAST REMINDER: OPS Area mini-BOFs in Prague
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

To all contributors who intend to present in Prague - If you did not do
it yet, please confirm the submissions for a mini-BOF slot at the OPS
Area meetings in Prague and send us the following information: .=20

- short technical scope description (not much more than one paragraph)
- goals of the proposal, where this can lead: e.g. new protocol or
extension of an existing protocol, standard, BCP or Informational RFC,
formation of a WG or individual submission, other
- estimation of time you will need in Prague including Q&A
- whether there is an Internet-Draft or you intent to submit one before
the Prague IETF

Please send us this information until 1/25 the latest. David and me will
meet on 1/26 and will communicate the finalized agenda shortly after.=20

Thanks and Regards,

Dan


=20
=20


_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Mon Jan 29 09:07:15 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBXA8-0006nl-KL; Mon, 29 Jan 2007 09:07:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBXA6-0006mh-Rs; Mon, 29 Jan 2007 09:07:10 -0500
Received: from co300216-ier2.net.avaya.com ([198.152.13.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HBXA5-0007qw-C2; Mon, 29 Jan 2007 09:07:10 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0TE76eB020529; Mon, 29 Jan 2007 09:07:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Jan 2007 16:07:06 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C310DB4@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPS Area Meetings and mini-BOFs: Preliminary Agenda for Prague
	(corrected date) 
Thread-Index: AcdDrpqUSwS6PSnaQHKopeF9pnPMag==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>, <ops-dir@ops.ietf.org>, 
	<aaa-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>,
	<nmrg@ibr.cs.tu-bs.de>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: 
Subject: [OPS-NM] OPS Area Meetings and mini-BOFs: Preliminary Agenda for
	Prague (corrected date) 
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please find below the preliminary agenda of the meetings in Prague, as
well as the list of mini-BOFs that David and myself have approved for
Prague. We were not able to grant to everybody the time that you
requested - please be prepared to adjust and manage your time
accordingly. Also note that there still may be changes in the dates and
time of the meting slots as result of IESG-Secretary changes.=20

Please comment on the agenda items and mini-BOF proposals.=20

We are looking forward to see you all in Prague.=20

Dan



=20
     Operations and Management (OPS) Area AGENDA

     Meeting : IETF68, Monday March 19, 2007 and Thursday March 22, 2007
     Location: Prague, Congress II, Monday March 19, 2007 15:20 to 17:20
and Grand Ballroom Thursday March 22, 2007 9:00 to 11:30
     Chairs  : David Kessens (david.kessens@nokia.com) and Dan Romascanu
(dromasca@avaya.com)=20
     Jabber  : ops@jabber.ietf.org
     URL     : http://www.ops.ietf.org/
     Agenda  : version 0.1 (draft)
     =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Meeting 1 - Monday March 19, 2007 15:20 to 17:20

1. Meeting Administrivia                 ADs        (total: 5 min)
        - Mailing list and URL
        - Minutes Scribe
        - Jabber Scribe
        - Blue Sheets

2. Mini-BOF A: COPS push mode policy configuration - Tom Taylor and Tina
Tsou (total: 30 min)

This mini-BOF is requested to gain comments on a technical proposal to
reduce the number of messages required when COPS is used to support push
mode policy configuration, where each request-state corresponds to an
user session. The essence of this proposal is to allow the PDP to
request the opening of a new request-state in the same message that
sends down policy to be stored against this request-state. At the other
end of the session life cycle, allow the PDP to delete a request-state.=20
The proposed extensions to COPS could save two to three messages per
session, depending on the details that are finally agreed.

I-D:  to be submitted=20

3. Mini-BOF B: - Manageability and Operational Guidelines - David
Harrington (total: 30 min)

We need to develop multi-protocol manageability and operational
guidelines for developers of protocols in the IETF. An internet-draft
has been published that summarizes previous work on this goal as a
starting point. This work would lead to either a WG, if enough people
want to be involved, or a design team to get the document finished. If
we can get enough feedback from operators and from protocol designers,
this could lead to a BCP; with limited input it would lead to an
Informational RFC instead.=20

I-D: to be submitted

4. Mini-BOF C: Best Current Practices in Operations and Management -
David Harrington (total: 20 min)

This would be an effort to get operators together in a WG to develop a
set of best current practices, and a description of supporting
technologies, for manageability and operations, similar to the work done
in the OpSec WG. There will not be an internet-draft published prior to
ietf68. A WG should be created for operators to do this work.

5. Improved Efficiency of the OPS Area - proposal for the formation of a
OPS Area WG - ADs (total: 20 min)

6. Open Microphone - 15 min


Meeting 2 - Thursday March 22, 2007 - 9:00 to 11:30AM

1. Meeting Administrivia                 ADs        (total: 5 min)
        - Mailing list and URL
        - Minutes Scribe
        - Jabber Scribe
        - Blue Sheets

2. Mini-BOF D: NE/facilities/lines/protocols/services data modeling -
Michael Alexander (total: 40 min)

Network Management (NM) standards have traditionally been focused on
protocols, such as pertaining to configuration management and discovery.
Yet, all areas of Network Management, ranging from Element Management
(EM) to Network Management Systems (NMS) and Service Management Systems
have in common that they critically rely on underlying data structures
describing devices and services being managed. Network elements (NE)
frequently spawn ten thousands of managed objects, such as for a
multiservice switch...Traditionally, standardization of access-methods
(protocols), discovery, etc. have received most attention, while the
more heterogeneous data models and data modeling per saw comparatively
less. As there are real possibilities to standardize underlying and
universal commonalities in EMS/NMS/Service Management Systems on the one
side and managed attributes of NEs, protocols, transmission facilities,
lines and services on the other, the two distributions should be closer
aligned. Despite the complexity, it is possible to identify and define
frameworks and meta models of each constituent and their relation to
each other, that would substantially ease the management of present and
future devices, networks and services.

I-D:=20

3. Mini-BOF E: MIB module editing in XML : Emile Stephan (total: 20 min)

Present the state of the art of editing MIB module in XML; Introduce a
basic template to edit SMI items in pure XML instead of in raw text;
Propose a simple XML template for SMI items; discuss the connections
with XML schema and network management protocols.

I-D: draft-stephan-ops-xml-mib-module-template-00 (under edition to be
submitted before mid February)

4. Mini-BOF F: Japanese Data Model Standards: Tomoyuki Iijima (total: 20
min)

 I'd like to show the data model examples we developed and was adopted
in the Japanese Standard body.

We developed data models of VLAN, Filter (Access Control List), and so
on and those data models were adopted by Japanese standardization body
called INTAP/OSMIC as standard data models. I'd like to make our data
model examples be adopted as an Informational RFC.

I-D: to be submitted

5. Mini-BOF G: OWL techniques for MIB to XML documents and schema
translation - Bob Natale (total: 40 min)

Specification of a standard methodology for translating SNMP MIBs into
outputs more directly usable by emerging SOA/web services management
tools, and specification of a standard methodology for validating those
translations.  Appropriate translation outputs are TBD by the WG, but
can be expected to include one or more of the following: XML, RDF, WSDL,
WS-Policy, WS-Event/Notification, Ontology.  The translation output(s)
should allow for extension of the respective managed element data model
in the native SOA/web services environment.  Because of the
extensibility objective, reverse translation back into SNMP MIB format
is a non-goal of the WG, but the possibility should be considered when
weighing alternatives.

I-D: to be submitted

6. Open microphone (total: 25 min)



=20




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



From ops-nm-bounces@ietf.org Mon Jan 29 09:07:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBX99-0006Dl-Iw; Mon, 29 Jan 2007 09:06:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBX98-0006Co-7l; Mon, 29 Jan 2007 09:06:10 -0500
Received: from [198.152.12.103] (helo=nj300815-ier2.net.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HBX95-0007li-Qx; Mon, 29 Jan 2007 09:06:10 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by nj300815-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP
	id l0TE61YF032141; Mon, 29 Jan 2007 09:06:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Jan 2007 16:06:00 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C310DAE@is0004avexu1.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPS Area Meetings and mini-BOFs: Preliminary Agenda for Prague
Thread-Index: AcdDrpqUSwS6PSnaQHKopeF9pnPMag==
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "OPS Area" <ops-area@ietf.org>, <ops-nm@ietf.org>, <ops-dir@ops.ietf.org>, 
	<aaa-doctors@ietf.org>, "MIB Doctors \(E-mail\)" <mib-doctors@ietf.org>,
	<nmrg@ibr.cs.tu-bs.de>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: 
Subject: [OPS-NM] OPS Area Meetings and mini-BOFs: Preliminary Agenda for
	Prague
X-BeenThere: ops-nm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area NM e-mail list <ops-nm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-nm>
List-Post: <mailto:ops-nm@ietf.org>
List-Help: <mailto:ops-nm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-nm>,
	<mailto:ops-nm-request@ietf.org?subject=subscribe>
Errors-To: ops-nm-bounces@ietf.org

Please find below the preliminary agenda of the meetings in Prague, as
well as the list of mini-BOFs that David and myself have approved for
Prague. We were not able to grant to everybody the time that you
requested - please be prepared to adjust and manage your time
accordingly. Also note that there still may be changes in the dates and
time of the meting slots as result of IESG-Secretary changes.=20

Please comment on the agenda items and mini-BOF proposals.=20

We are looking forward to see you all in Prague.=20

Dan



=20
     Operations and Management (OPS) Area AGENDA

     Meeting : IETF68, Monday March 19, 2007 and Thursday March 22, 2007
     Location: Prague, Congress II, Monday March 19, 2007 15:20 to 17:20
and Grand Ballroom Thursday March 22, 2007 9:00 to 11:30
     Chairs  : David Kessens (david.kessens@nokia.com) and Dan Romascanu
(dromasca@avaya.com)=20
     Jabber  : ops@jabber.ietf.org
     URL     : http://www.ops.ietf.org/
     Agenda  : version 0.1 (draft)
     =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Meeting 1 - Monday March 19, 2007 15:20 to 17:20

1. Meeting Administrivia                 ADs        (total: 5 min)
        - Mailing list and URL
        - Minutes Scribe
        - Jabber Scribe
        - Blue Sheets

2. Mini-BOF A: COPS push mode policy configuration - Tom Taylor and Tina
Tsou (total: 30 min)

This mini-BOF is requested to gain comments on a technical proposal to
reduce the number of messages required when COPS is used to support push
mode policy configuration, where each request-state corresponds to an
user session. The essence of this proposal is to allow the PDP to
request the opening of a new request-state in the same message that
sends down policy to be stored against this request-state. At the other
end of the session life cycle, allow the PDP to delete a request-state.=20
The proposed extensions to COPS could save two to three messages per
session, depending on the details that are finally agreed.

I-D:  to be submitted=20

3. Mini-BOF B: - Manageability and Operational Guidelines - David
Harrington (total: 30 min)

We need to develop multi-protocol manageability and operational
guidelines for developers of protocols in the IETF. An internet-draft
has been published that summarizes previous work on this goal as a
starting point. This work would lead to either a WG, if enough people
want to be involved, or a design team to get the document finished. If
we can get enough feedback from operators and from protocol designers,
this could lead to a BCP; with limited input it would lead to an
Informational RFC instead.=20

I-D: to be submitted

4. Mini-BOF C: Best Current Practices in Operations and Management -
David Harrington (total: 20 min)

This would be an effort to get operators together in a WG to develop a
set of best current practices, and a description of supporting
technologies, for manageability and operations, similar to the work done
in the OpSec WG. There will not be an internet-draft published prior to
ietf68. A WG should be created for operators to do this work.

5. Improved Efficiency of the OPS Area - proposal for the formation of a
OPS Area WG - ADs (total: 20 min)

6. Open Microphone - 15 min


Meeting 2 - Monday March 19, 2007 - 9:00 to 11:30AM

1. Meeting Administrivia                 ADs        (total: 5 min)
        - Mailing list and URL
        - Minutes Scribe
        - Jabber Scribe
        - Blue Sheets

2. Mini-BOF D: NE/facilities/lines/protocols/services data modeling -
Michael Alexander (total: 40 min)

Network Management (NM) standards have traditionally been focused on
protocols, such as pertaining to configuration management and discovery.
Yet, all areas of Network Management, ranging from Element Management
(EM) to Network Management Systems (NMS) and Service Management Systems
have in common that they critically rely on underlying data structures
describing devices and services being managed. Network elements (NE)
frequently spawn ten thousands of managed objects, such as for a
multiservice switch...Traditionally, standardization of access-methods
(protocols), discovery, etc. have received most attention, while the
more heterogeneous data models and data modeling per saw comparatively
less. As there are real possibilities to standardize underlying and
universal commonalities in EMS/NMS/Service Management Systems on the one
side and managed attributes of NEs, protocols, transmission facilities,
lines and services on the other, the two distributions should be closer
aligned. Despite the complexity, it is possible to identify and define
frameworks and meta models of each constituent and their relation to
each other, that would substantially ease the management of present and
future devices, networks and services.

I-D:=20

3. Mini-BOF E: MIB module editing in XML : Emile Stephan (total: 20 min)

Present the state of the art of editing MIB module in XML; Introduce a
basic template to edit SMI items in pure XML instead of in raw text;
Propose a simple XML template for SMI items; discuss the connections
with XML schema and network management protocols.

I-D: draft-stephan-ops-xml-mib-module-template-00 (under edition to be
submitted before mid February)

4. Mini-BOF F: Japanese Data Model Standards: Tomoyuki Iijima (total: 20
min)

 I'd like to show the data model examples we developed and was adopted
in the Japanese Standard body.

We developed data models of VLAN, Filter (Access Control List), and so
on and those data models were adopted by Japanese standardization body
called INTAP/OSMIC as standard data models. I'd like to make our data
model examples be adopted as an Informational RFC.

I-D: to be submitted

5. Mini-BOF G: OWL techniques for MIB to XML documents and schema
translation - Bob Natale (total: 40 min)

Specification of a standard methodology for translating SNMP MIBs into
outputs more directly usable by emerging SOA/web services management
tools, and specification of a standard methodology for validating those
translations.  Appropriate translation outputs are TBD by the WG, but
can be expected to include one or more of the following: XML, RDF, WSDL,
WS-Policy, WS-Event/Notification, Ontology.  The translation output(s)
should allow for extension of the respective managed element data model
in the native SOA/web services environment.  Because of the
extensibility objective, reverse translation back into SNMP MIB format
is a non-goal of the WG, but the possibility should be considered when
weighing alternatives.

I-D: to be submitted

6. Open microphone (total: 25 min)



=20




_______________________________________________
OPS-NM mailing list
OPS-NM@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-nm



