From ops-area-bounces@ietf.org  Wed Jul  2 05:30:47 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 B35C03A6C78;
	Wed,  2 Jul 2008 05:30:47 -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 DD8103A6C77;
	Wed,  2 Jul 2008 05:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.42
X-Spam-Level: 
X-Spam-Status: No, score=-2.42 tagged_above=-999 required=5 tests=[AWL=0.179, 
	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 xOocelkGhdko; Wed,  2 Jul 2008 05:30:45 -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 773103A6867;
	Wed,  2 Jul 2008 05:30:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,737,1204520400"; d="scan'208";a="133852851"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 02 Jul 2008 08:30:55 -0400
X-IronPort-AV: E=Sophos;i="4.27,737,1204520400"; d="scan'208";a="221001947"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	02 Jul 2008 08:30:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 2 Jul 2008 14:30:52 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of Multiprotocol Label Switching (mpls) 
Thread-Index: AcjcHDtgrlQyhkApTHeBg+ZEoMo3owAIvYyw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>,
	<ops-area@ietf.org>
Subject: [OPS-AREA] FW: WG Review: Recharter of Multiprotocol Label
	Switching (mpls)
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
The IESG
Sent: Tuesday, July 01, 2008 11:45 PM
To: ietf-announce@ietf.org
Cc: mpls@lists.ietf.org
Subject: WG Review: Recharter of Multiprotocol Label Switching (mpls) 

A modified charter has been submitted for the Multiprotocol Label
Switching working group in the in the Routing 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 Tuesday, July 8,
2008.

This is an update to the MPLS charter in order to cover the MPLS-TP
work.

Multiprotocol Label Switching (mpls)
---------------------------------------------------
Last Modified: 2008-06-13

Current Status: Active Working Group

Chair(s):

    George Swallow <swallow@cisco.com> 
    Loa Andersson <loa@pi.nu> 

Routing Area Director(s):

    Ross Callon <rcallon@juniper.net> 
    David Ward <dward@cisco.com> 

Routing Area Advisor:

    Ross Callon <rcallon@juniper.net> 

Mailing Lists:

    General Discussion: mpls@lists.ietf.org
    To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls
    Archive:
http://www.ietf.org/mail-archive/web/mpls/current/maillist.html

Description of Working Group:

The MPLS working group is responsible for standardizing a base
technology for using label switching and for the implementation of
label-switched paths over various packet based link-level technologies,
such as Packet-over-Sonet, Frame Relay, ATM, and LAN technologies (e.g.
all forms of Ethernet, Token Ring, etc.).
This includes procedures and protocols for the distribution of labels
between routers and encapsulation.

The working group is also responsible for specifying the necessary
management objects (e.g. as part of MIB modules) and OAM techniques for
the functionality specified in the base MPLS technology.

The first generation of the MPLS standards are largely complete, and the
current WG work items are:

 - Define requirements, mechanisms and protocol extensions for
point-to-multipoint (P2MP) MPLS

 - Define requirements, mechanisms and protocol extensions for traffic
engineered point-to-multipoint (P2MP) MPLS, including soft preemption

 - Define requirements and mechanisms for MPLS OAM

 - Define an overall OAM framework for MPLS applications

 - MPLS-specific aspects of traffic engineering for multi-areas/multi-AS
in cooperation with the CCAMP WG

 - Determine (with CCAMP) what procedures are appropriate for evaluating
proposals to extend the MPLS and GMPLS protocols, and document these

 - Document current implementation practices for MPLS load sharing

 - Include extensions to the MPLS WG protocols and RFCs necessary to
create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP will
be coordinated between the working groups (eg, MPLS, CCAMP, PWE3, and
L2PVN) that are chartered to do MPLS TP work.

The Working Group chairs tracking of the working group documents can be
viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm

Goals and Milestones:

Done  Submit documents from original MPLS effort to IESG 

Done  Framework for IP multicast over label-switched paths ready for
advancement. 

Done  LDP fault tolerance specification ready for advancement to
Proposed Standard. 

Done  Submit Definitions of Managed Objects for MultoiProtocol Label
Switching, Label Distribution Protocol (LDP) to the IESG for publication
as Proposed Standards 

Done  Specification for MPLS-specific recovery ready for advancement. 

Done  Submit Multiprotocol Label Switching (MPLS) Forward Equivalency
Class-To-Next Hop Label Forwarding Entry Management Information Base to
the IESG for publication as Proposed Standards 

Done  Submit Multiprotocol Label Switching (MPLS) Label Switching Router
(LSR), Management Information Base to the IESG for publication as
Proposed Standards 

Done  Submit Multiprotocol Label Switching (MPLS) Management Overview to
the IESG for publication as Proposed Standards 

Done  Submit Definitions of Textual Conventions for Multiprotocol Label
Switching (MPLS) Management to the IESG for publication as Proposed
Standards 

Done  Submit Multiprotocol Label Switching (MPLS) Traffic Engineering
Management Information Base to the IESG for publication as Proposed
Standards 

Done  Submit the Traffic Engineering Link MIB to the IESG for as a
Proposed Standard 

Done  Submit a specification on Encapsulations to carry MPLS over IP and
GRE to the IESG for as a Proposed Standard 

Done  Submit specification on LSP Ping to the IESG for publication as a
Proposed Standard 

Done  Submit a document defining the scope, requirements, and issues to
resolve for setup of P2MP TE LSPs (MPLS and GMPLS) 

Done  Submit an OAM Framework Document to the IESG for publication as an
Informational RFC 

Done  Submit a BCP on MPLS load sharing to the IESG 

Done  Submit specification on LSR Self Test to the IESG for publication
as a Proposed Standard 

Done  Submit document(s) specifying protocol extensions, enhancements
and mechanisms for setup of P2MP TE LSPs 

Done  Submit point to multipoint TE MIB to IESG as proposed standard

Jun 2009  Submit requirements for point-to-multipoint extensions to LDP 

Jan 2009  Submit LDP extensions for P2MP LSPs 

Dec 2008  Submit a specification on Soft Pre-emption of LSP Tunnels to
the IESG for publication as a Proposed Standard 

Mar 2009  Submit MPLS security framework for publication as an
informational RFC 

Nov 2008  Submit EXP field clarification document to IESG as proposed
standard

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


From ops-area-bounces@ietf.org  Wed Jul  2 09:48: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 DFE4C3A6C08;
	Wed,  2 Jul 2008 09:48: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 6EF253A67EC;
	Wed,  2 Jul 2008 09:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.483
X-Spam-Level: 
X-Spam-Status: No, score=-6.483 tagged_above=-999 required=5 tests=[AWL=0.116, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id rT5qjvf9ESok; Wed,  2 Jul 2008 09:48:10 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167])
	by core3.amsl.com (Postfix) with ESMTP id 283BC3A6C08;
	Wed,  2 Jul 2008 09:48:08 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob107.postini.com
	([64.18.6.12]) with SMTP; Wed, 02 Jul 2008 09:48:01 PDT
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Jul 2008 09:48:10 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by emailwf1.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 2 Jul 2008 12:48:05 -0400
Received: from [172.23.1.187] ([172.23.1.187] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 2 Jul 2008 12:47:12 -0400
Message-ID: <486BB10C.8070406@juniper.net>
Date: Wed, 02 Jul 2008 12:47:08 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 02 Jul 2008 16:47:12.0341 (UTC)
	FILETIME=[468A7050:01C8DC63]
Cc: ops-dir@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [OPS-DIR] FW: WG Review: Recharter of Multiprotocol
 Label Switching (mpls)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Folks,

Has anyone else had problems with the current MPLS MIBs? A while back I 
tried to implement RFC 3814 and was underwhelmed.

Maybe we should ask the WG to revisit their MIBs.

                                    Ron
                                    /as individual contributor


Romascanu, Dan (Dan) wrote:
>  
> 
> -----Original Message-----
> From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
> The IESG
> Sent: Tuesday, July 01, 2008 11:45 PM
> To: ietf-announce@ietf.org
> Cc: mpls@lists.ietf.org
> Subject: WG Review: Recharter of Multiprotocol Label Switching (mpls) 
> 
> A modified charter has been submitted for the Multiprotocol Label
> Switching working group in the in the Routing 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 Tuesday, July 8,
> 2008.
> 
> This is an update to the MPLS charter in order to cover the MPLS-TP
> work.
> 
> Multiprotocol Label Switching (mpls)
> ---------------------------------------------------
> Last Modified: 2008-06-13
> 
> Current Status: Active Working Group
> 
> Chair(s):
> 
>     George Swallow <swallow@cisco.com> 
>     Loa Andersson <loa@pi.nu> 
> 
> Routing Area Director(s):
> 
>     Ross Callon <rcallon@juniper.net> 
>     David Ward <dward@cisco.com> 
> 
> Routing Area Advisor:
> 
>     Ross Callon <rcallon@juniper.net> 
> 
> Mailing Lists:
> 
>     General Discussion: mpls@lists.ietf.org
>     To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls
>     Archive:
> http://www.ietf.org/mail-archive/web/mpls/current/maillist.html
> 
> Description of Working Group:
> 
> The MPLS working group is responsible for standardizing a base
> technology for using label switching and for the implementation of
> label-switched paths over various packet based link-level technologies,
> such as Packet-over-Sonet, Frame Relay, ATM, and LAN technologies (e.g.
> all forms of Ethernet, Token Ring, etc.).
> This includes procedures and protocols for the distribution of labels
> between routers and encapsulation.
> 
> The working group is also responsible for specifying the necessary
> management objects (e.g. as part of MIB modules) and OAM techniques for
> the functionality specified in the base MPLS technology.
> 
> The first generation of the MPLS standards are largely complete, and the
> current WG work items are:
> 
>  - Define requirements, mechanisms and protocol extensions for
> point-to-multipoint (P2MP) MPLS
> 
>  - Define requirements, mechanisms and protocol extensions for traffic
> engineered point-to-multipoint (P2MP) MPLS, including soft preemption
> 
>  - Define requirements and mechanisms for MPLS OAM
> 
>  - Define an overall OAM framework for MPLS applications
> 
>  - MPLS-specific aspects of traffic engineering for multi-areas/multi-AS
> in cooperation with the CCAMP WG
> 
>  - Determine (with CCAMP) what procedures are appropriate for evaluating
> proposals to extend the MPLS and GMPLS protocols, and document these
> 
>  - Document current implementation practices for MPLS load sharing
> 
>  - Include extensions to the MPLS WG protocols and RFCs necessary to
> create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP will
> be coordinated between the working groups (eg, MPLS, CCAMP, PWE3, and
> L2PVN) that are chartered to do MPLS TP work.
> 
> The Working Group chairs tracking of the working group documents can be
> viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm
> 
> Goals and Milestones:
> 
> Done  Submit documents from original MPLS effort to IESG 
> 
> Done  Framework for IP multicast over label-switched paths ready for
> advancement. 
> 
> Done  LDP fault tolerance specification ready for advancement to
> Proposed Standard. 
> 
> Done  Submit Definitions of Managed Objects for MultoiProtocol Label
> Switching, Label Distribution Protocol (LDP) to the IESG for publication
> as Proposed Standards 
> 
> Done  Specification for MPLS-specific recovery ready for advancement. 
> 
> Done  Submit Multiprotocol Label Switching (MPLS) Forward Equivalency
> Class-To-Next Hop Label Forwarding Entry Management Information Base to
> the IESG for publication as Proposed Standards 
> 
> Done  Submit Multiprotocol Label Switching (MPLS) Label Switching Router
> (LSR), Management Information Base to the IESG for publication as
> Proposed Standards 
> 
> Done  Submit Multiprotocol Label Switching (MPLS) Management Overview to
> the IESG for publication as Proposed Standards 
> 
> Done  Submit Definitions of Textual Conventions for Multiprotocol Label
> Switching (MPLS) Management to the IESG for publication as Proposed
> Standards 
> 
> Done  Submit Multiprotocol Label Switching (MPLS) Traffic Engineering
> Management Information Base to the IESG for publication as Proposed
> Standards 
> 
> Done  Submit the Traffic Engineering Link MIB to the IESG for as a
> Proposed Standard 
> 
> Done  Submit a specification on Encapsulations to carry MPLS over IP and
> GRE to the IESG for as a Proposed Standard 
> 
> Done  Submit specification on LSP Ping to the IESG for publication as a
> Proposed Standard 
> 
> Done  Submit a document defining the scope, requirements, and issues to
> resolve for setup of P2MP TE LSPs (MPLS and GMPLS) 
> 
> Done  Submit an OAM Framework Document to the IESG for publication as an
> Informational RFC 
> 
> Done  Submit a BCP on MPLS load sharing to the IESG 
> 
> Done  Submit specification on LSR Self Test to the IESG for publication
> as a Proposed Standard 
> 
> Done  Submit document(s) specifying protocol extensions, enhancements
> and mechanisms for setup of P2MP TE LSPs 
> 
> Done  Submit point to multipoint TE MIB to IESG as proposed standard
> 
> Jun 2009  Submit requirements for point-to-multipoint extensions to LDP 
> 
> Jan 2009  Submit LDP extensions for P2MP LSPs 
> 
> Dec 2008  Submit a specification on Soft Pre-emption of LSP Tunnels to
> the IESG for publication as a Proposed Standard 
> 
> Mar 2009  Submit MPLS security framework for publication as an
> informational RFC 
> 
> Nov 2008  Submit EXP field clarification document to IESG as proposed
> standard
> 
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed Jul  2 11:22:41 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 19BC23A697E;
	Wed,  2 Jul 2008 11:22:41 -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 48E643A687E;
	Wed,  2 Jul 2008 11:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.428
X-Spam-Level: 
X-Spam-Status: No, score=-2.428 tagged_above=-999 required=5 tests=[AWL=0.171, 
	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 TrnRv+hv3hZL; Wed,  2 Jul 2008 11:22:38 -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 C852A3A6980;
	Wed,  2 Jul 2008 11:22:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,738,1204520400"; d="scan'208";a="133909948"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 02 Jul 2008 14:22:40 -0400
X-IronPort-AV: E=Sophos;i="4.27,738,1204520400"; d="scan'208";a="221201454"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	02 Jul 2008 14:22:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 2 Jul 2008 20:22:38 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04D93B5E@307622ANEX5.global.avaya.com>
In-Reply-To: <486BB10C.8070406@juniper.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-DIR] FW: WG Review: Recharter of Multiprotocol Label
	Switching (mpls)
Thread-Index: AcjcY3fLc0UISLPRRhC9FHFCJ/WN9gADQz+A
References: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
	<486BB10C.8070406@juniper.net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Ron Bonica" <rbonica@juniper.net>
Cc: ops-dir@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [OPS-DIR] FW: WG Review: Recharter of Multiprotocol
	Label Switching (mpls)
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

Can you spell a little bit 'underwhelmed'? 

Dan
 

> -----Original Message-----
> From: Ron Bonica [mailto:rbonica@juniper.net] 
> Sent: Wednesday, July 02, 2008 7:47 PM
> To: Romascanu, Dan (Dan)
> Cc: ops-dir@ietf.org; ops-area@ietf.org
> Subject: Re: [OPS-DIR] FW: WG Review: Recharter of 
> Multiprotocol Label Switching (mpls)
> 
> Folks,
> 
> Has anyone else had problems with the current MPLS MIBs? A 
> while back I tried to implement RFC 3814 and was underwhelmed.
> 
> Maybe we should ask the WG to revisit their MIBs.
> 
>                                     Ron
>                                     /as individual contributor
> 
> 
> Romascanu, Dan (Dan) wrote:
> >  
> > 
> > -----Original Message-----
> > From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] 
> On Behalf 
> > Of The IESG
> > Sent: Tuesday, July 01, 2008 11:45 PM
> > To: ietf-announce@ietf.org
> > Cc: mpls@lists.ietf.org
> > Subject: WG Review: Recharter of Multiprotocol Label 
> Switching (mpls)
> > 
> > A modified charter has been submitted for the Multiprotocol Label 
> > Switching working group in the in the Routing 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 
> Tuesday, July 8, 
> > 2008.
> > 
> > This is an update to the MPLS charter in order to cover the MPLS-TP 
> > work.
> > 
> > Multiprotocol Label Switching (mpls)
> > ---------------------------------------------------
> > Last Modified: 2008-06-13
> > 
> > Current Status: Active Working Group
> > 
> > Chair(s):
> > 
> >     George Swallow <swallow@cisco.com> 
> >     Loa Andersson <loa@pi.nu>
> > 
> > Routing Area Director(s):
> > 
> >     Ross Callon <rcallon@juniper.net> 
> >     David Ward <dward@cisco.com>
> > 
> > Routing Area Advisor:
> > 
> >     Ross Callon <rcallon@juniper.net>
> > 
> > Mailing Lists:
> > 
> >     General Discussion: mpls@lists.ietf.org
> >     To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls
> >     Archive:
> > http://www.ietf.org/mail-archive/web/mpls/current/maillist.html
> > 
> > Description of Working Group:
> > 
> > The MPLS working group is responsible for standardizing a base 
> > technology for using label switching and for the implementation of 
> > label-switched paths over various packet based link-level 
> > technologies, such as Packet-over-Sonet, Frame Relay, ATM, 
> and LAN technologies (e.g.
> > all forms of Ethernet, Token Ring, etc.).
> > This includes procedures and protocols for the distribution 
> of labels 
> > between routers and encapsulation.
> > 
> > The working group is also responsible for specifying the necessary 
> > management objects (e.g. as part of MIB modules) and OAM techniques 
> > for the functionality specified in the base MPLS technology.
> > 
> > The first generation of the MPLS standards are largely 
> complete, and 
> > the current WG work items are:
> > 
> >  - Define requirements, mechanisms and protocol extensions for 
> > point-to-multipoint (P2MP) MPLS
> > 
> >  - Define requirements, mechanisms and protocol extensions 
> for traffic 
> > engineered point-to-multipoint (P2MP) MPLS, including soft 
> preemption
> > 
> >  - Define requirements and mechanisms for MPLS OAM
> > 
> >  - Define an overall OAM framework for MPLS applications
> > 
> >  - MPLS-specific aspects of traffic engineering for 
> > multi-areas/multi-AS in cooperation with the CCAMP WG
> > 
> >  - Determine (with CCAMP) what procedures are appropriate for 
> > evaluating proposals to extend the MPLS and GMPLS protocols, and 
> > document these
> > 
> >  - Document current implementation practices for MPLS load sharing
> > 
> >  - Include extensions to the MPLS WG protocols and RFCs 
> necessary to 
> > create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP 
> > will be coordinated between the working groups (eg, MPLS, 
> CCAMP, PWE3, 
> > and
> > L2PVN) that are chartered to do MPLS TP work.
> > 
> > The Working Group chairs tracking of the working group 
> documents can 
> > be viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm
> > 
> > Goals and Milestones:
> > 
> > Done  Submit documents from original MPLS effort to IESG
> > 
> > Done  Framework for IP multicast over label-switched paths 
> ready for 
> > advancement.
> > 
> > Done  LDP fault tolerance specification ready for advancement to 
> > Proposed Standard.
> > 
> > Done  Submit Definitions of Managed Objects for 
> MultoiProtocol Label 
> > Switching, Label Distribution Protocol (LDP) to the IESG for 
> > publication as Proposed Standards
> > 
> > Done  Specification for MPLS-specific recovery ready for 
> advancement. 
> > 
> > Done  Submit Multiprotocol Label Switching (MPLS) Forward 
> Equivalency 
> > Class-To-Next Hop Label Forwarding Entry Management 
> Information Base 
> > to the IESG for publication as Proposed Standards
> > 
> > Done  Submit Multiprotocol Label Switching (MPLS) Label Switching 
> > Router (LSR), Management Information Base to the IESG for 
> publication 
> > as Proposed Standards
> > 
> > Done  Submit Multiprotocol Label Switching (MPLS) 
> Management Overview 
> > to the IESG for publication as Proposed Standards
> > 
> > Done  Submit Definitions of Textual Conventions for Multiprotocol 
> > Label Switching (MPLS) Management to the IESG for publication as 
> > Proposed Standards
> > 
> > Done  Submit Multiprotocol Label Switching (MPLS) Traffic 
> Engineering 
> > Management Information Base to the IESG for publication as Proposed 
> > Standards
> > 
> > Done  Submit the Traffic Engineering Link MIB to the IESG for as a 
> > Proposed Standard
> > 
> > Done  Submit a specification on Encapsulations to carry 
> MPLS over IP 
> > and GRE to the IESG for as a Proposed Standard
> > 
> > Done  Submit specification on LSP Ping to the IESG for 
> publication as 
> > a Proposed Standard
> > 
> > Done  Submit a document defining the scope, requirements, 
> and issues 
> > to resolve for setup of P2MP TE LSPs (MPLS and GMPLS)
> > 
> > Done  Submit an OAM Framework Document to the IESG for 
> publication as 
> > an Informational RFC
> > 
> > Done  Submit a BCP on MPLS load sharing to the IESG
> > 
> > Done  Submit specification on LSR Self Test to the IESG for 
> > publication as a Proposed Standard
> > 
> > Done  Submit document(s) specifying protocol extensions, 
> enhancements 
> > and mechanisms for setup of P2MP TE LSPs
> > 
> > Done  Submit point to multipoint TE MIB to IESG as proposed standard
> > 
> > Jun 2009  Submit requirements for point-to-multipoint extensions to 
> > LDP
> > 
> > Jan 2009  Submit LDP extensions for P2MP LSPs
> > 
> > Dec 2008  Submit a specification on Soft Pre-emption of LSP 
> Tunnels to 
> > the IESG for publication as a Proposed Standard
> > 
> > Mar 2009  Submit MPLS security framework for publication as an 
> > informational RFC
> > 
> > Nov 2008  Submit EXP field clarification document to IESG 
> as proposed 
> > standard
> > 
> > _______________________________________________
> > OPS-DIR mailing list
> > OPS-DIR@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-dir
> > 
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Wed Jul  2 12:16: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 063863A6774;
	Wed,  2 Jul 2008 12:16: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 9D9E83A6774;
	Wed,  2 Jul 2008 12:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level: 
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[AWL=0.558, 
	BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id MGjsIi1bfMoO; Wed,  2 Jul 2008 12:15:56 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249])
	by core3.amsl.com (Postfix) with ESMTP id C70443A6767;
	Wed,  2 Jul 2008 12:15:55 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m62JFiIG031473; Wed, 2 Jul 2008 20:15:46 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com
	[81.140.15.32]) (authenticated bits=0)
	by asmtp2.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m62JFfIW031417; Wed, 2 Jul 2008 20:15:44 +0100
Message-ID: <06c501c8dc78$0352bf80$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Ron Bonica" <rbonica@juniper.net>,
	"Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
	<486BB10C.8070406@juniper.net>
Date: Wed, 2 Jul 2008 20:15:29 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Cc: ops-dir@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [OPS-DIR] FW: WG Review: Recharter of Multiprotocol
	Label Switching (mpls)
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi Ron,

I have implemented several of the MIB modules (3812, 3813) several times and 
also the GMPLS extensions.

I am not sure whether you are tarring all the MPLS MIB modules with the 3814 
brush. Perhaps we can get wider feedback.

But surely asking the MPLS WG to revisit the MIBs will not necessarily get 
anything done. But, if someone who had just found implementing them a pain 
was to produce a bis, I'm sure the WG would consider it.

Cheers,

Adrian
----- Original Message ----- 
From: "Ron Bonica" <rbonica@juniper.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Cc: <ops-dir@ietf.org>; <ops-area@ietf.org>
Sent: Wednesday, July 02, 2008 5:47 PM
Subject: Re: [OPS-AREA] [OPS-DIR] FW: WG Review: Recharter of Multiprotocol 
Label Switching (mpls)


> Folks,
>
> Has anyone else had problems with the current MPLS MIBs? A while back I 
> tried to implement RFC 3814 and was underwhelmed.
>
> Maybe we should ask the WG to revisit their MIBs.
>
>                                    Ron
>                                    /as individual contributor
>
>
> Romascanu, Dan (Dan) wrote:
>>  -----Original Message-----
>> From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] On Behalf Of
>> The IESG
>> Sent: Tuesday, July 01, 2008 11:45 PM
>> To: ietf-announce@ietf.org
>> Cc: mpls@lists.ietf.org
>> Subject: WG Review: Recharter of Multiprotocol Label Switching (mpls) A 
>> modified charter has been submitted for the Multiprotocol Label
>> Switching working group in the in the Routing 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 Tuesday, July 8,
>> 2008.
>>
>> This is an update to the MPLS charter in order to cover the MPLS-TP
>> work.
>>
>> Multiprotocol Label Switching (mpls)
>> ---------------------------------------------------
>> Last Modified: 2008-06-13
>>
>> Current Status: Active Working Group
>>
>> Chair(s):
>>
>>     George Swallow <swallow@cisco.com> Loa Andersson <loa@pi.nu> Routing 
>> Area Director(s):
>>
>>     Ross Callon <rcallon@juniper.net> David Ward <dward@cisco.com> 
>> Routing Area Advisor:
>>
>>     Ross Callon <rcallon@juniper.net> Mailing Lists:
>>
>>     General Discussion: mpls@lists.ietf.org
>>     To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls
>>     Archive:
>> http://www.ietf.org/mail-archive/web/mpls/current/maillist.html
>>
>> Description of Working Group:
>>
>> The MPLS working group is responsible for standardizing a base
>> technology for using label switching and for the implementation of
>> label-switched paths over various packet based link-level technologies,
>> such as Packet-over-Sonet, Frame Relay, ATM, and LAN technologies (e.g.
>> all forms of Ethernet, Token Ring, etc.).
>> This includes procedures and protocols for the distribution of labels
>> between routers and encapsulation.
>>
>> The working group is also responsible for specifying the necessary
>> management objects (e.g. as part of MIB modules) and OAM techniques for
>> the functionality specified in the base MPLS technology.
>>
>> The first generation of the MPLS standards are largely complete, and the
>> current WG work items are:
>>
>>  - Define requirements, mechanisms and protocol extensions for
>> point-to-multipoint (P2MP) MPLS
>>
>>  - Define requirements, mechanisms and protocol extensions for traffic
>> engineered point-to-multipoint (P2MP) MPLS, including soft preemption
>>
>>  - Define requirements and mechanisms for MPLS OAM
>>
>>  - Define an overall OAM framework for MPLS applications
>>
>>  - MPLS-specific aspects of traffic engineering for multi-areas/multi-AS
>> in cooperation with the CCAMP WG
>>
>>  - Determine (with CCAMP) what procedures are appropriate for evaluating
>> proposals to extend the MPLS and GMPLS protocols, and document these
>>
>>  - Document current implementation practices for MPLS load sharing
>>
>>  - Include extensions to the MPLS WG protocols and RFCs necessary to
>> create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP will
>> be coordinated between the working groups (eg, MPLS, CCAMP, PWE3, and
>> L2PVN) that are chartered to do MPLS TP work.
>>
>> The Working Group chairs tracking of the working group documents can be
>> viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm
>>
>> Goals and Milestones:
>>
>> Done  Submit documents from original MPLS effort to IESG Done  Framework 
>> for IP multicast over label-switched paths ready for
>> advancement. Done  LDP fault tolerance specification ready for 
>> advancement to
>> Proposed Standard. Done  Submit Definitions of Managed Objects for 
>> MultoiProtocol Label
>> Switching, Label Distribution Protocol (LDP) to the IESG for publication
>> as Proposed Standards Done  Specification for MPLS-specific recovery 
>> ready for advancement. Done  Submit Multiprotocol Label Switching (MPLS) 
>> Forward Equivalency
>> Class-To-Next Hop Label Forwarding Entry Management Information Base to
>> the IESG for publication as Proposed Standards Done  Submit Multiprotocol 
>> Label Switching (MPLS) Label Switching Router
>> (LSR), Management Information Base to the IESG for publication as
>> Proposed Standards Done  Submit Multiprotocol Label Switching (MPLS) 
>> Management Overview to
>> the IESG for publication as Proposed Standards Done  Submit Definitions 
>> of Textual Conventions for Multiprotocol Label
>> Switching (MPLS) Management to the IESG for publication as Proposed
>> Standards Done  Submit Multiprotocol Label Switching (MPLS) Traffic 
>> Engineering
>> Management Information Base to the IESG for publication as Proposed
>> Standards Done  Submit the Traffic Engineering Link MIB to the IESG for 
>> as a
>> Proposed Standard Done  Submit a specification on Encapsulations to carry 
>> MPLS over IP and
>> GRE to the IESG for as a Proposed Standard Done  Submit specification on 
>> LSP Ping to the IESG for publication as a
>> Proposed Standard Done  Submit a document defining the scope, 
>> requirements, and issues to
>> resolve for setup of P2MP TE LSPs (MPLS and GMPLS) Done  Submit an OAM 
>> Framework Document to the IESG for publication as an
>> Informational RFC Done  Submit a BCP on MPLS load sharing to the IESG 
>> Done  Submit specification on LSR Self Test to the IESG for publication
>> as a Proposed Standard Done  Submit document(s) specifying protocol 
>> extensions, enhancements
>> and mechanisms for setup of P2MP TE LSPs Done  Submit point to multipoint 
>> TE MIB to IESG as proposed standard
>>
>> Jun 2009  Submit requirements for point-to-multipoint extensions to LDP 
>> Jan 2009  Submit LDP extensions for P2MP LSPs Dec 2008  Submit a 
>> specification on Soft Pre-emption of LSP Tunnels to
>> the IESG for publication as a Proposed Standard Mar 2009  Submit MPLS 
>> security framework for publication as an
>> informational RFC Nov 2008  Submit EXP field clarification document to 
>> IESG as proposed
>> standard
>>
>> _______________________________________________
>> OPS-DIR mailing list
>> OPS-DIR@ietf.org
>> https://www.ietf.org/mailman/listinfo/ops-dir
>>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


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


From ops-area-bounces@ietf.org  Wed Jul  2 12:22:30 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 867993A690C;
	Wed,  2 Jul 2008 12:22:30 -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 061253A690C;
	Wed,  2 Jul 2008 12:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.491
X-Spam-Level: 
X-Spam-Status: No, score=-6.491 tagged_above=-999 required=5 tests=[AWL=0.108, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 0242m915lYag; Wed,  2 Jul 2008 12:22:27 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7ob116.obsmtp.com [64.18.2.218])
	by core3.amsl.com (Postfix) with ESMTP id 34DCA3A6905;
	Wed,  2 Jul 2008 12:22:26 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob116.postini.com
	([64.18.6.12]) with SMTP; Wed, 02 Jul 2008 12:22:34 PDT
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emsmtp03.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 2 Jul 2008 12:21:58 -0700
Received: from pi-smtp.jnpr.net ([10.10.2.36]) by p-emlb02-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Jul 2008 12:21:57 -0700
Received: from proton.jnpr.net ([10.10.2.37]) by pi-smtp.jnpr.net with
	Microsoft SMTPSVC(5.0.2195.6713); Wed, 2 Jul 2008 15:21:56 -0400
Received: from [172.23.1.187] ([172.23.1.187] RDNS failed) by proton.jnpr.net
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 2 Jul 2008 15:21:55 -0400
Message-ID: <486BD54A.7070208@juniper.net>
Date: Wed, 02 Jul 2008 15:21:46 -0400
From: Ron Bonica <rbonica@juniper.net>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
References: <EDC652A26FB23C4EB6384A4584434A04D93A6F@307622ANEX5.global.avaya.com>
	<486BB10C.8070406@juniper.net>
	<EDC652A26FB23C4EB6384A4584434A04D93B5E@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04D93B5E@307622ANEX5.global.avaya.com>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 02 Jul 2008 19:21:55.0754 (UTC)
	FILETIME=[E3E2D8A0:01C8DC78]
Cc: ops-dir@ietf.org, ops-area@ietf.org
Subject: Re: [OPS-AREA] [OPS-DIR] FW: WG Review: Recharter of Multiprotocol
 Label Switching (mpls)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi Dan,

Sure. RFC 3814 defines three tables. These are:

- mplsFTNPerfTable
- mplsFTNMapTable
- mplsFTNPerfTable

The mplsFTNPerfTable is useful, but poorly formed. Each table entry 
represents a forwarding equivalence class (FEC) and associates that FEC 
to an LSP. If it were indexed well, it would be indexed by some 
combination of fields that identify the FEC. Unfortunately, it is 
indexed by INDEX. So, I can't ask a question of the following form:

- over which LSP would a packet bound for 10.1.1.1 be routed

I have to ask questions like the following:

- show me the 142nd entry in the forwarding table (whatever that might be!)

Since I generally have no idea where the entry that I care about is 
located, I have to walk the entire table. Typically, it is huge.

The mplsFTNPerfTable has some other oddities. For example, rather than 
using the address/mask strategy that other MIBs use, they talk about the 
high and low members of an address range.

The mplsFTNMapTable maps mapping rules to particular interfaces. It is 
only interesting on boxes that maintain a separate routing table per 
interface.

The mplsFTNPerfTable maintains performance statistics per FEC/Interface. 
  I don't know of any forwarding platforms that maintain such statistics.

                                     Ron



Romascanu, Dan (Dan) wrote:
> Can you spell a little bit 'underwhelmed'? 
> 
> Dan
>  
> 
>> -----Original Message-----
>> From: Ron Bonica [mailto:rbonica@juniper.net] 
>> Sent: Wednesday, July 02, 2008 7:47 PM
>> To: Romascanu, Dan (Dan)
>> Cc: ops-dir@ietf.org; ops-area@ietf.org
>> Subject: Re: [OPS-DIR] FW: WG Review: Recharter of 
>> Multiprotocol Label Switching (mpls)
>>
>> Folks,
>>
>> Has anyone else had problems with the current MPLS MIBs? A 
>> while back I tried to implement RFC 3814 and was underwhelmed.
>>
>> Maybe we should ask the WG to revisit their MIBs.
>>
>>                                     Ron
>>                                     /as individual contributor
>>
>>
>> Romascanu, Dan (Dan) wrote:
>>>  
>>>
>>> -----Original Message-----
>>> From: iesg-bounces@iesg.org [mailto:iesg-bounces@iesg.org] 
>> On Behalf 
>>> Of The IESG
>>> Sent: Tuesday, July 01, 2008 11:45 PM
>>> To: ietf-announce@ietf.org
>>> Cc: mpls@lists.ietf.org
>>> Subject: WG Review: Recharter of Multiprotocol Label 
>> Switching (mpls)
>>> A modified charter has been submitted for the Multiprotocol Label 
>>> Switching working group in the in the Routing 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 
>> Tuesday, July 8, 
>>> 2008.
>>>
>>> This is an update to the MPLS charter in order to cover the MPLS-TP 
>>> work.
>>>
>>> Multiprotocol Label Switching (mpls)
>>> ---------------------------------------------------
>>> Last Modified: 2008-06-13
>>>
>>> Current Status: Active Working Group
>>>
>>> Chair(s):
>>>
>>>     George Swallow <swallow@cisco.com> 
>>>     Loa Andersson <loa@pi.nu>
>>>
>>> Routing Area Director(s):
>>>
>>>     Ross Callon <rcallon@juniper.net> 
>>>     David Ward <dward@cisco.com>
>>>
>>> Routing Area Advisor:
>>>
>>>     Ross Callon <rcallon@juniper.net>
>>>
>>> Mailing Lists:
>>>
>>>     General Discussion: mpls@lists.ietf.org
>>>     To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls
>>>     Archive:
>>> http://www.ietf.org/mail-archive/web/mpls/current/maillist.html
>>>
>>> Description of Working Group:
>>>
>>> The MPLS working group is responsible for standardizing a base 
>>> technology for using label switching and for the implementation of 
>>> label-switched paths over various packet based link-level 
>>> technologies, such as Packet-over-Sonet, Frame Relay, ATM, 
>> and LAN technologies (e.g.
>>> all forms of Ethernet, Token Ring, etc.).
>>> This includes procedures and protocols for the distribution 
>> of labels 
>>> between routers and encapsulation.
>>>
>>> The working group is also responsible for specifying the necessary 
>>> management objects (e.g. as part of MIB modules) and OAM techniques 
>>> for the functionality specified in the base MPLS technology.
>>>
>>> The first generation of the MPLS standards are largely 
>> complete, and 
>>> the current WG work items are:
>>>
>>>  - Define requirements, mechanisms and protocol extensions for 
>>> point-to-multipoint (P2MP) MPLS
>>>
>>>  - Define requirements, mechanisms and protocol extensions 
>> for traffic 
>>> engineered point-to-multipoint (P2MP) MPLS, including soft 
>> preemption
>>>  - Define requirements and mechanisms for MPLS OAM
>>>
>>>  - Define an overall OAM framework for MPLS applications
>>>
>>>  - MPLS-specific aspects of traffic engineering for 
>>> multi-areas/multi-AS in cooperation with the CCAMP WG
>>>
>>>  - Determine (with CCAMP) what procedures are appropriate for 
>>> evaluating proposals to extend the MPLS and GMPLS protocols, and 
>>> document these
>>>
>>>  - Document current implementation practices for MPLS load sharing
>>>
>>>  - Include extensions to the MPLS WG protocols and RFCs 
>> necessary to 
>>> create an MPLS Transport Profile (MPLS TP). The work on the MPLS TP 
>>> will be coordinated between the working groups (eg, MPLS, 
>> CCAMP, PWE3, 
>>> and
>>> L2PVN) that are chartered to do MPLS TP work.
>>>
>>> The Working Group chairs tracking of the working group 
>> documents can 
>>> be viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm
>>>
>>> Goals and Milestones:
>>>
>>> Done  Submit documents from original MPLS effort to IESG
>>>
>>> Done  Framework for IP multicast over label-switched paths 
>> ready for 
>>> advancement.
>>>
>>> Done  LDP fault tolerance specification ready for advancement to 
>>> Proposed Standard.
>>>
>>> Done  Submit Definitions of Managed Objects for 
>> MultoiProtocol Label 
>>> Switching, Label Distribution Protocol (LDP) to the IESG for 
>>> publication as Proposed Standards
>>>
>>> Done  Specification for MPLS-specific recovery ready for 
>> advancement. 
>>> Done  Submit Multiprotocol Label Switching (MPLS) Forward 
>> Equivalency 
>>> Class-To-Next Hop Label Forwarding Entry Management 
>> Information Base 
>>> to the IESG for publication as Proposed Standards
>>>
>>> Done  Submit Multiprotocol Label Switching (MPLS) Label Switching 
>>> Router (LSR), Management Information Base to the IESG for 
>> publication 
>>> as Proposed Standards
>>>
>>> Done  Submit Multiprotocol Label Switching (MPLS) 
>> Management Overview 
>>> to the IESG for publication as Proposed Standards
>>>
>>> Done  Submit Definitions of Textual Conventions for Multiprotocol 
>>> Label Switching (MPLS) Management to the IESG for publication as 
>>> Proposed Standards
>>>
>>> Done  Submit Multiprotocol Label Switching (MPLS) Traffic 
>> Engineering 
>>> Management Information Base to the IESG for publication as Proposed 
>>> Standards
>>>
>>> Done  Submit the Traffic Engineering Link MIB to the IESG for as a 
>>> Proposed Standard
>>>
>>> Done  Submit a specification on Encapsulations to carry 
>> MPLS over IP 
>>> and GRE to the IESG for as a Proposed Standard
>>>
>>> Done  Submit specification on LSP Ping to the IESG for 
>> publication as 
>>> a Proposed Standard
>>>
>>> Done  Submit a document defining the scope, requirements, 
>> and issues 
>>> to resolve for setup of P2MP TE LSPs (MPLS and GMPLS)
>>>
>>> Done  Submit an OAM Framework Document to the IESG for 
>> publication as 
>>> an Informational RFC
>>>
>>> Done  Submit a BCP on MPLS load sharing to the IESG
>>>
>>> Done  Submit specification on LSR Self Test to the IESG for 
>>> publication as a Proposed Standard
>>>
>>> Done  Submit document(s) specifying protocol extensions, 
>> enhancements 
>>> and mechanisms for setup of P2MP TE LSPs
>>>
>>> Done  Submit point to multipoint TE MIB to IESG as proposed standard
>>>
>>> Jun 2009  Submit requirements for point-to-multipoint extensions to 
>>> LDP
>>>
>>> Jan 2009  Submit LDP extensions for P2MP LSPs
>>>
>>> Dec 2008  Submit a specification on Soft Pre-emption of LSP 
>> Tunnels to 
>>> the IESG for publication as a Proposed Standard
>>>
>>> Mar 2009  Submit MPLS security framework for publication as an 
>>> informational RFC
>>>
>>> Nov 2008  Submit EXP field clarification document to IESG 
>> as proposed 
>>> standard
>>>
>>> _______________________________________________
>>> OPS-DIR mailing list
>>> OPS-DIR@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-dir
>>>
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Thu Jul  3 02:44:30 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 8E3FC3A6A50;
	Thu,  3 Jul 2008 02:44:30 -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 9E7F53A6908;
	Thu,  3 Jul 2008 02:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167, 
	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 kgBaa7q-gs3u; Thu,  3 Jul 2008 02:44:28 -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 52F9D3A6975;
	Thu,  3 Jul 2008 02:44:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,742,1204520400"; d="scan'208";a="113529663"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	03 Jul 2008 05:44:32 -0400
X-IronPort-AV: E=Sophos;i="4.27,742,1204520400"; d="scan'208";a="228457836"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	03 Jul 2008 05:44:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 3 Jul 2008 11:44:29 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04D93C7B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of Benchmarking Methodology Working Group
	(bmwg) 
Thread-Index: AcjciuoOaaj+G7U6REehhFrZONCq5wAZnOeQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>,
	<ops-area@ietf.org>
Subject: [OPS-AREA] FW: WG Review: Recharter of Benchmarking Methodology
	Working Group (bmwg)
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: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: Thursday, July 03, 2008 12:30 AM
To: ietf-announce@ietf.org
Cc: acmorton@att.com; bmwg@ietf.org
Subject: WG Review: Recharter of Benchmarking Methodology Working Group
(bmwg) 

A modified charter has been submitted for the Benchmarking Methodology
Working Group (bmwg) 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
Wednesday, July 9, 2008.

Benchmarking Methodology Working Group (bmwg)
=====================================
Last Modified: 2008-06-13  

Current Status: Active Working Group  

Chair(s):
    Al Morton <acmorton@att.com>   

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

Operations and Management Area Advisor:     
    Ronald Bonica <rbonica@juniper.net>   

Mailing Lists:     
    General Discussion: bmwg@ietf.org
    In Body: subscribe your_email_address
    Archive: http://www.ietf.org/mail-archive/web/bmwg/index.html   

Description of Working Group:

The major goal of the Benchmarking Methodology Working Group is to make
a series of recommendations concerning the measurement of the
performance characteristics of various internetworking technologies;
further, these recommendations may focus on the systems or services that
are built from these technologies.

Each recommendation will describe the class of equipment, system, or
service being addressed; discuss the performance characteristics that
are pertinent to that class; clearly identify a set of metrics that aid
in the description of those characteristics; specify the methodologies
required to collect said metrics; and lastly, present the requirements
for the common, unambiguous reporting of benchmarking results.

To better distinguish the BMWG from other measurement initiatives in the
IETF, the scope of the BMWG is limited to technology characterization
using simulated stimuli in a laboratory environment.
Said differently, the BMWG does not attempt to produce benchmarks for
live, operational networks. Moreover, the benchmarks produced by this WG
shall strive to be vendor independent or otherwise have universal
applicability to a given technology class.

Because the demands of a particular technology may vary from deployment
to deployment, a specific non-goal of the Working Group is to define
acceptance criteria or performance requirements.

An ongoing task is to provide a forum for discussion regarding the
advancement of measurements designed to provide insight on the operation
inter-networking technologies.

In addition to its current work plan, the BMWG is explicitly tasked to
develop benchmarks and methodologies for the following technologies:

* MPLS Forwarding: Develop specific methods to characterize the latency
and forwarding performance of MPLS devices, extending the fundamental
recommendations of RFC 1242 and RFC 2544 to this networking technology.

* SIP Networking Devices: Develop new terminology and methods to
characterize the key performance aspects of network devices using SIP,
including the signaling plane scale and service rates while considering
load conditions on both the signaling and media planes. This work will
be harmonized with related SIP performance metric definitions prepared
by the PMOL working group.

Goals and Milestones:

Done Expand the current Ethernet switch benchmarking methodology draft
to define the metrics and methodologies particular to the general class
of connectionless, LAN switches.

Done Edit the LAN switch draft to reflect the input from BMWG. Issue a
new version of document for comment. If appropriate, ascertain consensus
on whether to recommend the draft for consideration as an RFC.

Done Take controversial components of multicast draft to mailing list
for
 
discussion. Incorporate changes to draft and reissue appropriately.

Done Submit workplan for initiating work on Benchmarking Methodology for
LAN Switching Devices.

Done Submit workplan for continuing work on the Terminology for
Cell/Call
 
Benchmarking draft.

Done Submit initial draft of Benchmarking Methodology for LAN Switches.

Done Submit Terminology for IP Multicast Benchmarking draft for AD
Review.

Done Submit Benchmarking Terminology for Firewall Performance for AD
review

Done Progress ATM benchmarking terminology draft to AD review.

Done Submit Benchmarking Methodology for LAN Switching Devices draft for
AD review.

Done Submit first draft of Firewall Benchmarking Methodology.

Done First Draft of Terminology for FIB related Router Performance
Benchmarking.

Done First Draft of Router Benchmarking Framework

Done Progress Frame Relay benchmarking terminology draft to AD review.

Done Methodology for ATM Benchmarking for AD review.

Done Terminology for ATM ABR Benchmarking for AD review.

Done Terminology for FIB related Router Performance Benchmarking to AD
review.

Done Firewall Benchmarking Methodology to AD Review

Done First Draft of Methodology for FIB related Router Performance
Benchmarking.

Done First draft Net Traffic Control Benchmarking Methodology.

Done Methodology for IP Multicast Benchmarking to AD Review.

Done Resource Reservation Benchmarking Terminology to AD Review

Done First I-D on IPsec Device Benchmarking Terminology

Done EGP Convergence Benchmarking Terminology to AD Review

Done Resource Reservation Benchmarking Methodology to AD Review

Done Net Traffic Control Benchmarking Terminology to AD Review

Done IGP/Data-Plane Terminology I-D to AD Review

Done IGP/Data-Plane Methodology and Considerations I-Ds to AD Review

Done Hash and Stuffing I-D to AD Review

Done IPv6 Benchmarking Methodology to AD Review

REVISED
Sept 2008 IPsec Device Benchmarking Terminology to IESG Review Sept 2008
IPsec Device Benchmarking Methodology to IESG Review

Dec 2008 Net Traffic Control Benchmarking Methodology to AD Review.
Dec 2008 Router Accelerated Test Terminology to IESG Review Dec 2008
Router Accelerated Test Methodology to IESG Review


Dec 2009 Router Accelerated Test Method for EBGP to IESG Review Dec 2009
Router Acc. Test Method for Operational Security to IESG Review Feb 2009
Terminology For Protection Benchmarking to AD Review Feb 2009
Methodology For Protection Benchmarking to AD Review Jul 2010 Basic BGP
Convergence Benchmarking Methodology to AD Review.

NEW
April 2009 Methodology for MPLS Forwarding to AD Review.
June 2009 Terminology for SIP Device Benchmarking to IESG Review.
June 2009 Methodology for SIP Device Benchmarking to IESG Review.
_______________________________________________
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  Thu Jul 10 12:34: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 A89E03A6993;
	Thu, 10 Jul 2008 12:34: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 9729F3A6993;
	Thu, 10 Jul 2008 12:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5
	tests=[AWL=-0.300, 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 e0Ql57s1INtf; Thu, 10 Jul 2008 12:34:46 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id A98963A692A;
	Thu, 10 Jul 2008 12:34:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,339,1212379200"; d="scan'208";a="126842627"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 10 Jul 2008 15:35:00 -0400
X-IronPort-AV: E=Sophos;i="4.30,339,1212379200"; d="scan'208";a="226535090"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	10 Jul 2008 15:35:00 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Jul 2008 21:34:58 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04DD02F5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG Review: Recharter of Common Control and Measurement Plane
	(ccamp) 
Thread-Index: Acjira7s/Gks/UgFSOSqphjvzMjUFQAFk4kg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-dir@ietf.org>,
	<ops-area@ietf.org>
Subject: [OPS-AREA] FW: WG Review: Recharter of Common Control and
	Measurement Plane (ccamp)
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: Thursday, July 10, 2008 7:54 PM
To: new-work@ietf.org
Subject: WG Review: Recharter of Common Control and Measurement Plane
(ccamp) 


 A modified charter has been submitted for the Common Control and
Measurement Plane (ccamp) working group in the Routing 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 Thursday, July 17,
2008.

Common Control and Measurement Plane (ccamp)
--------------------------------------------

Last Modified: 2008-07-10

Current Status: Active Working Group

Chair(s):
    Adrian Farrel <adrian@olddog.co.uk> 
    Deborah Brungard <dbrungard@att.com> 

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

Routing Area Advisor:
    Ross Callon <rcallon@juniper.net> 

Technical Advisor(s):
    Lou Berger <lberger@labn.net> 

Mailing Lists:
    General Discussion: ccamp@ops.ietf.org
    To Subscribe: majordomo@ops.ietf.org
    In Body: subscribe ccamp
    Archive: https://ops.ietf.org/lists/ccamp


Description of Working Group:

Organizational Overview

The CCAMP working group coordinates the work within the IETF defining a
common control plane and a separate common measurement plane for
physical path and core tunneling technologies of Internet and telecom
service providers (ISPs and SPs), e.g. O-O and O-E-O optical switches,
TDM Switches, Ethernet Switches, ATM and Frame Relay switches, IP
encapsulation tunneling technologies, and MPLS in cooperation with the
MPLS WG.

In this context, measurement refers to the acquisition and distribution
of attributes relevant to the setting up of tunnels and paths.

CCAMP WG work scope includes:

- Definition of protocol-independent metrics and parameters
  (measurement attributes) for describing links and paths that are
  required for routing and signaling. These will be developed in
  conjunction with requests and requirements from other WGs to
  ensure overall usefulness.

- Definition of protocol(s) and extensions to them required for
  link and path attribute measurement. Link Management Protocol
  (LMP) is included here.

- Functional specification of extensions for routing (OSPF, ISIS)
  and signalling (RSVP-TE) required for path establishment.
  Protocol formats and procedures that embody these extensions will
  be done jointly with the WGs supervising those protocols.

- Definition of the mechanisms required to determine the route and
  properties of an established path (tunnel tracing).

- Definition of management objects (e.g. as part of MIB modules) and
  OAM techniques relevant to the protocols and extensions specified
  within the WG.

- Work on traffic-engineering GMPLS mechanisms and protocol
  extensions to support source-controlled and explicitly-routed
  Ethernet data paths for Ethernet data planes that are already
  approved by an Standards Development Organization (SDO) with
  responsibility for the Ethernet data plane. It is expected that the
  primary SDO in this case is the IEEE. Note that the specification or
  modification of Ethernet data planes is out of scope.
- Work on GMPLS mechanisms and protocol extensions to support the
  transport profile of MPLS (MPLS-TP) in cooperation with the MPLS,
  L2VPN, and PWE3 Working Group and in coordination with the
  requirements expressed jointly by the IETF and ITU-T.


CCAMP WG currently works on the following tasks:

- Define how the properties of network resources gathered by a
  measurement protocol can be distributed in existing routing
  protocols, such as OSPF and IS-IS. CCAMP defines the generic
  description of the properties and how they are distributed in
  OSPF. The specifics of distribution within IS-IS are being
  addressed in the ISIS WG.

- Define signaling and routing mechanisms and extensions to allow
  path and tunnel setup and maintenance across multiple domains,
  where a domain may be an IGP area, an Autonomous System, or any
  other region of topological visibility. To this end, work
  cooperatively with the PCE and MPLS WGs.

- Define abstract link and path properties needed for link and
  path protection. Specify signalling mechanisms for path
  protection, diverse routing and fast path restoration. Ensure
  that multi-layer path protection and restoration functions are
  achievable using the defined signalling, routing, and measurement
  protocols, either separately or in combination.

- Identify which requirements for signaling and routing for
  Automatically Switched Optical Network (ASON) are not currently met
  by protocols defined in CCAMP; based on these, define mechanisms to
  address these requirements.

- Produce extensions to the CCAMP WG protocols and RFCs necessary
  to create an MPLS Transport Profile (MPLS TP). The work on the
  MPLS TP will be coordinated between the MPLS, L2VPN, PWE3, and CCAMP
  working groups that are jointly chartered to do MPLS TP work.


In doing this work, the WG will work closely with at least the following
other WGs: MPLS, L2VPN, PWE3, ISIS, OSPF, IDR, L1VPN and PCE. 
The WG will also cooperate with the ITU-T and the IEEE 802.1.

Goals and Milestones:

Done    Post strawman WG goals and charter
Done    Identify and document a limited set of candidate solutions for 
        signalling and for measurement. Among candidate control
solutions

        to be considered are the existing GMPLS drafts.
Done    Build appropriate design teams
Done    Submit WG document defining path setup portions of common 
        control plane protocol
Done    Submit WG document defining common measurement plane protocol
Done    Submit LMP MIB to IESG
Done    Submit protection & restoration documents to IESG
Done    Submit ASON signaling requirements doc to IESG
Done    Submit GMPLS MIBs to IESG
Done    Produce CCAMP WG document for generic tunnel tracing protocol
Done    Produce CCAMP WG document for multi-area/AS signaling and 
        routing
Done    Submit ASON routing requirements doc to IESG
Done    Submit revised charter and milestones to IESG for IESG 
        consideration of more detailed deliverables and determination 
        of usefulness of continuation of WG
Done    First version WG I-D for Advertising TE Node Capabilities in 
        ISIS and OSPF
Done    First version WG I-D for Automatic discovery of MPLS-TE mesh 
        membership
Done    Submit ASON Routing evaluation I-D for IESG review
Done    Cross-WG review of I-D for Advertising TE Node Capabilities in 
        ISIS and OSPF
Done    First version WG I-D MPLS to GMPLS migration strategies
Done    First version WG I-D Requirements for Multi-Layer and Multi-
        Region Networks
Done    First version WG I-D for Evaluation of existing protocols for 
        MLN/MRN
Done    First version of WG I-D for ASON Routing solutions
Done    Submit RSVP-TE extensions for inter-domain signaling I-D for 
        IESG review
Done    Submit Per-domain path computation signaling I-D for IESG review
Done    First version of WG I-D for OSPF-TE/GMPLS MIB module
Done    Submit GMPLS signaling in support of Call Management I-D for 
        IESG review
Done    First version WG Informational I-D for Analysis of inter-domain 
        issues for disjoint and protected paths
Done    Submit I-D for Advertising TE Node Capabilities in ISIS and OSPF

        for IESG review
Done    First version WG I-D for Protocol solutions for MLN/MRN
Done    Submit GMPLS/ASON lexicography I-D for IESG review
Done    First version WG I-D MPLS-GMPLS interworking requirements and 
        solutions
Done    Submit LSP Stitching I-D for IESG review
Done    Submit I-D for Automatic discovery of MPLS-TE mesh membership 
        for IESG review
Done    First version WG I-D GMPLS OAM Requirements
Done    Submit GMPLS routing and signaling interoperability advice I-D 
        for IESG review
Done    Submit MPLS to GMPLS migration strategies I-D for IESG review
Done    Submit Requirements for Multi-Layer and Multi-Region Networks 
        I-D for IESG review
Done    Submit MPLS-GMPLS interworking requirements and solutions I-D 
        for IESG review
Done    Submit Evaluation of existing protocols for MLN/MRN for IESG 
        review
Done    First version WG I-Ds for GMPLS source-controlled and 
        explicitly-routed Ethernet networks
Done    Submit Informational I-D for Analysis of inter-domain issues for

        disjoint and protected paths for IESG review
Aug 2008    First version of Working Group draft providing Control Plane

            Framework for MPLS-TP
Sep 2008    Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG 
            review
Oct 2008    First version of Working Group draft defining RSVP-TE 
            extensions for MPLS-TP
Dec 2008    Submit GMPLS OAM Requirements I-D for IESG review
Dec 2008    Submit ASON Routing solutions I-D for IESG review
Jan 2009    Submit protocol extensions for GMPLS source-controlled and 
            explicitly-routed Ethernet networks for IESG review
Feb 2009    Submit Protocol solutions for MLN/MRN I-D for IESG review
Mar 2009    Submit Control Plane Framework for MPLS-TP for IESG review
Jun 2009    Submit RSVP-TE extensions for MPLS-TP for IESG review
Jun 2009    Recharter or close Working Group
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Thu Jul 17 07:54:56 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 A73843A6A08;
	Thu, 17 Jul 2008 07:54:56 -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 1C1433A69D6
	for <ops-area@core3.amsl.com>; Thu, 17 Jul 2008 07:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012, 
	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 tgrWce-S5iyV for <ops-area@core3.amsl.com>;
	Thu, 17 Jul 2008 07:54:54 -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 536A93A68A8
	for <ops-area@ietf.org>; Thu, 17 Jul 2008 07:54:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,204,1215403200"; d="scan'208";a="135838480"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 17 Jul 2008 10:55:25 -0400
X-IronPort-AV: E=Sophos;i="4.31,204,1215403200"; d="scan'208";a="230667669"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	17 Jul 2008 10:55:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 17 Jul 2008 16:55:23 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04DD10A3@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Preliminary Agenda for the Open OPS Area Meeting in Dublin
Thread-Index: AcjoHSM8pgENo30MTzyFY03BnZn8XA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] Preliminary Agenda for the Open OPS Area 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

The preliminary agenda for the Open OPS Area in Dublin can be found at
http://www.ietf.org/proceedings/08jul/agenda/opsarea.txt

We can still accommodate requests for other agenda items. 

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


From ops-area-bounces@ietf.org  Sun Jul 20 02:16:32 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 CDED13A6908;
	Sun, 20 Jul 2008 02:16:32 -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 EE7B23A684C
	for <ops-area@core3.amsl.com>; Sun, 20 Jul 2008 02:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010, 
	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 AjrlTKFuTiY4 for <ops-area@core3.amsl.com>;
	Sun, 20 Jul 2008 02:16:30 -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 C7EF63A6908
	for <ops-area@ietf.org>; Sun, 20 Jul 2008 02:16:29 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,218,1215403200"; d="scan'208";a="115324872"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	20 Jul 2008 05:17:04 -0400
X-IronPort-AV: E=Sophos;i="4.31,218,1215403200"; d="scan'208";a="232032698"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	20 Jul 2008 05:17:03 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 20 Jul 2008 11:16:59 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E0E8F3@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPSAREA Open Meeting - WG Status reports
Thread-Index: AcjqSV0kQXmNZy7XSqShyMXvlA82BA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Cc: ops-ads@tools.ietf.org
Subject: [OPS-AREA] OPSAREA Open Meeting - WG Status reports
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

Other areas in the IETF use part of their time in the open meeting for a
short round-up of reports from the WG chairs concerning the status of
each WG (charter changes, documents submitted to the IESG, documents
published, hot items, etc.) 

As the agenda for the Dublin OPSAREA meeting is relatively loose, I
would suggest that we try this as an experiment, allocating a max of 3
minutes for each WG for a short status report. I know that this is an
extra-task for WG chairs in a busy week, but I imagine that each of you
is capable of speaking about his WG status without too much special
preparation. If you want you can prepare one slide, but I would not make
this a mandatory requirements. Also, if there are WGs not meeting in
Dublin and no chair is present, the chairs still may send to the ADs a
short mail report or one slide to be presented in the meeting. 

Feedback is welcome, especially if you see a big problem in deciding
that late on this addition to the agenda.   

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 Jul 22 08:40:53 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 69E633A6AA3;
	Tue, 22 Jul 2008 08:40:53 -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 55B353A6AA3
	for <ops-area@core3.amsl.com>; Tue, 22 Jul 2008 08:40:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058, 
	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 xCO+X5dCmDF0 for <ops-area@core3.amsl.com>;
	Tue, 22 Jul 2008 08:40:51 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 411A33A6A9D
	for <ops-area@ietf.org>; Tue, 22 Jul 2008 08:40:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,232,1215403200"; d="scan'208";a="128208568"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 22 Jul 2008 11:41:30 -0400
X-IronPort-AV: E=Sophos;i="4.31,232,1215403200"; d="scan'208";a="233622626"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	22 Jul 2008 11:41:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Jul 2008 17:41:28 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E0EF79@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPSAREA Open Meeting Agenda - revised
Thread-Index: AcjsEWfPYrJORNzKTSiAy5wvU1P9PQ==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] OPSAREA Open Meeting Agenda - revised
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

A revised agenda of the OPSAREA open meeting is available at
http://www.ietf.org/proceedings/08jul/agenda/opsarea.txt 

It now includes WG chairs reports (3 min for each WG and chair who plans
to report)

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


From ops-area-bounces@ietf.org  Tue Jul 22 09:50:16 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 60DA628C11F;
	Tue, 22 Jul 2008 09:50:16 -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 37A7A3A683F;
	Tue, 22 Jul 2008 09:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.056, 
	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 RTUVDkpcSJtv; Tue, 22 Jul 2008 09:50:12 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 6803E3A6909;
	Tue, 22 Jul 2008 09:50:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,232,1215403200"; d="scan'208";a="128219266"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 22 Jul 2008 12:50:52 -0400
X-IronPort-AV: E=Sophos;i="4.31,232,1215403200"; d="scan'208";a="240479396"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	22 Jul 2008 12:50:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Jul 2008 18:50:33 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E0EFA1@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-opsawg-operations-and-management-04
Thread-Index: AcjsGw6G09XmP4sLQsmN0ooyuabwCA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <opsawg@ietf.org>
Cc: ops-area@ietf.org
Subject: [OPS-AREA] Comments on
	draft-ietf-opsawg-operations-and-management-04
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 find below my contributor comments on
draft-ietf-opsawg-operations-and-management-04. The comments are rather
in the text order than in importance. I tried to address also some of
the issues market for DISCUSS. 

1. Abstract - something is missing in the second phrase, maybe the word
'about' before 'covering aspects ...'

2. I would move to the introduction section some of the text in Section
5 or a clone of it. I believe it tells better about what this document
intents to be: 

  The purpose of this document is to provide guidance about what to
   consider when thinking about the management and deployment of a new
   protocol, and to provide guidance about documenting the
   considerations.  The following guidelines are designed to help
   writers provide a reasonably consistent format for such
   documentation.  Separate manageability and operational considerations
   sections are desirable in many cases, but their structure and
   location is a decision that can be made from case to case.

   We want to avoid seeming to impose a solution by putting in place a
   strict terminology - for example implying that a formal data model,
   or even using a management protocol is mandatory.  If protocol
   designers conclude that its technology can be managed solely by using
   proprietary CLIs, and no structured or standardized data model needs
   to be in place, this might be fine, but it is a decision that should
   be explicit in a manageability discussion, that this is how the
   protocol will need to be operated and managed.  Protocol designers
   should avoid having manageability pushed for a later/never phase of
   the development of the standard.

   Making a Management Considerations section a mandatory publication
   requirement for IETF documents is the responsibility of the IESG, or
   specific area directors, or working groups, and this document avoids
   recommending any mandatory publication requirements.  For a complex
   protocol, a completely separate draft on operations and management
   might be appropriate, or even a completely separate WG effort.

3. I would drop some of the existing text in the current introduction,
especially: 

   This document only provides guidelines; it does not specify how the
   guidelines provided should be used within the IETF.

4. Need to expand acronyms, even those who are very obvious in the
management community but may be obscure out of it like SMI or COPS-PR. 

5. the DISCUSS at page 6 - I would avoid giving more examples, lists of
protocols, etc. 

6. page 6 - I did not understand what is the intent of the paragraph
that mentions IPFIX

7. page 7 - [DISCUSS: would the
   example of inconsistency between MIB counters that cannot be reset
   and CLI counters that can be rest be useful here?] - yes, I think so

8. Section 3.3 - the second paragraph does not seem to deal with
protocols extensibility, but more to data models  and data model
languages design. I think that the protocol designers cannot do much
about this, and I would recommend to take this out. 

9. Section 3.4 - The example is from a functional component and not from
a protocol. I would emphasize the role of impact on functional elements
by saying s/document the requirements from other protocols/document the
requirements from other protocols and functional elements/ in the first
paragraph

10. page 9 - I believe that the content of the last paragraph in this
page is out of scope

11. Section 3.6 - we can add considering simple protocol status and
health indicators on network devices as a recommended mean to check
correct operation

12. Section 4 - We need some lose definition of what we mean by a
'service' (on the lines of network and operational functionality derived
from the implementation and deployment of a new protocol - or something
similar) 

13. page 11 - [DISCUSS: Is a section on P2P vs. central management
called for
   here?] - No, IMO

14, section 4.1 - when speaking about interoperability we should add the
management applications , emphasizing that interoperability allows for
usage or 3rd party applications and outsourcing of management services.

15. section 4.3 should start IMO with the need to document what are the
basic faults and health indicators that need to be instrumented for a
new protocol, as well as what alarms and events must be propagated to
management applications or exposed through a data model

16. page 14 - DISCUSS-what is reliable? The accurate delivery of the
event information is guaranteed within a given (high) margin of
confidence

17. 4.3.2 - the DISCUSSes go into too much details IMO 

18. 4.3.4 - same, I would consider taking out these section, they are
beyond protocol design and what is expected in protocol documents

19. Section 4.4 should start IMO with the need to document what are the
basic configuration parameters that need to be instrumented for a new
protocol, as well as default values and modes of operation

20. All the discussion in section 4.4 about backup configuration, gold
config, etc. seems to me to be out of scope - it is device centric and
is not covered in new protocol documents

21. Same with 4.4.1 - seems out of scope or mis-placed

22. page 19 -    What information should be maintained across reboots of
the device,  or restarts of the management system? - this is important
but mis-placed, should be in the configuration management section

23. DISCUSS: there are several parts to performance management.  Device
   monitoring (with the impact of the new protocol/service activation),
   protocol monitoring, and services monitoring.  This section might
   benefit from being broken into different pieces.] - 

   YES - maybe not breaking the section but mentioning the three
categories separately

24. The security management section may add a paragraph about security
threats that may be introduced by management operations. For example
CAPWAP breaks the structure of monolithic Access Points (AP) into Access
Controllers and Wireless Termination Points (WTP). By using a management
interface internal information that was previously not accessible is now
exposed over the network and to managers and my become a source of
potential security threats. 

25. I doubt that section A.1 is needed. In general I prefer that expert
reviews focus on expert information, while general reviews are left for
GenART

26. A2, first paragraph - add the question whether textual or graphical
UI are required, whether binary or text representation of management
information is preferred. 

27. add to A2 the question 'what is the minimal set of management
(configuration, faults, performance monitoring) objects that need to be
instrumented in order to manage the new protocol 

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 Jul 22 10:31: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 E073E3A695F;
	Tue, 22 Jul 2008 10:31: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 F40A23A6A07
	for <ops-area@core3.amsl.com>; Tue, 22 Jul 2008 10:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.473
X-Spam-Level: 
X-Spam-Status: No, score=-2.473 tagged_above=-999 required=5 tests=[AWL=0.126, 
	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 5egcYX08vXCB for <ops-area@core3.amsl.com>;
	Tue, 22 Jul 2008 10:31:36 -0700 (PDT)
Received: from QMTA02.emeryville.ca.mail.comcast.net
	(qmta02.emeryville.ca.mail.comcast.net [76.96.30.24])
	by core3.amsl.com (Postfix) with ESMTP id B64F03A67A2
	for <ops-area@ietf.org>; Tue, 22 Jul 2008 10:31:36 -0700 (PDT)
Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12])
	by QMTA02.emeryville.ca.mail.comcast.net with comcast
	id t0bn1Z00H0FhH24A25YJML; Tue, 22 Jul 2008 17:32:18 +0000
Received: from Harrington73653 ([24.128.66.199])
	by OMTA08.emeryville.ca.mail.comcast.net with comcast
	id t5YF1Z00J4HwxpC8U5YGLg; Tue, 22 Jul 2008 17:32:17 +0000
X-Authority-Analysis: v=1.0 c=1 a=ktf8BaHbQFsA:10 a=AKe0EMkaxvMA:10
	a=48vgC7mUAAAA:8 a=3Rx1Lpa4D8E9nPRrDUsA:9 a=i8ntdhcGUgJBpoNE038A:9
	a=7qh4-GwSPx5ON-m88_IA:7 a=0FSItxdcuyIse9JPMjV4-vVDDQkA:4
	a=lZB815dzVvQA:10 a=XF7b4UCPwd8A:10
From: "David Harrington" <ietfdbh@comcast.net>
To: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.com>,
	<opsawg@ietf.org>
References: <EDC652A26FB23C4EB6384A4584434A04E0EFA1@307622ANEX5.global.avaya.com>
Date: Tue, 22 Jul 2008 13:32:15 -0400
Message-ID: <01b401c8ec20$e2e69510$0600a8c0@china.huawei.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04E0EFA1@307622ANEX5.global.avaya.com>
Thread-Index: AcjsGw6G09XmP4sLQsmN0ooyuabwCAABcceQ
Cc: ops-area@ietf.org
Subject: Re: [OPS-AREA] [OPSAWG] Comments on
	draft-ietf-opsawg-operations-and-management-04
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 Dan,

I will incorporate these comments into the next revision.

dbh 

> -----Original Message-----
> From: opsawg-bounces@ietf.org 
> [mailto:opsawg-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Tuesday, July 22, 2008 12:51 PM
> To: opsawg@ietf.org
> Cc: ops-area@ietf.org
> Subject: [OPSAWG] Comments on 
> draft-ietf-opsawg-operations-and-management-04
> 
> Please find below my contributor comments on
> draft-ietf-opsawg-operations-and-management-04. The comments 
> are rather
> in the text order than in importance. I tried to address also some
of
> the issues market for DISCUSS. 
> 
> 1. Abstract - something is missing in the second phrase, 
> maybe the word
> 'about' before 'covering aspects ...'
> 
> 2. I would move to the introduction section some of the text 
> in Section
> 5 or a clone of it. I believe it tells better about what this
document
> intents to be: 
> 
>   The purpose of this document is to provide guidance about what to
>    consider when thinking about the management and deployment of a
new
>    protocol, and to provide guidance about documenting the
>    considerations.  The following guidelines are designed to help
>    writers provide a reasonably consistent format for such
>    documentation.  Separate manageability and operational 
> considerations
>    sections are desirable in many cases, but their structure and
>    location is a decision that can be made from case to case.
> 
>    We want to avoid seeming to impose a solution by putting in place
a
>    strict terminology - for example implying that a formal data
model,
>    or even using a management protocol is mandatory.  If protocol
>    designers conclude that its technology can be managed 
> solely by using
>    proprietary CLIs, and no structured or standardized data 
> model needs
>    to be in place, this might be fine, but it is a decision 
> that should
>    be explicit in a manageability discussion, that this is how the
>    protocol will need to be operated and managed.  Protocol
designers
>    should avoid having manageability pushed for a later/never phase
of
>    the development of the standard.
> 
>    Making a Management Considerations section a mandatory
publication
>    requirement for IETF documents is the responsibility of 
> the IESG, or
>    specific area directors, or working groups, and this 
> document avoids
>    recommending any mandatory publication requirements.  For a
complex
>    protocol, a completely separate draft on operations and
management
>    might be appropriate, or even a completely separate WG effort.
> 
> 3. I would drop some of the existing text in the current
introduction,
> especially: 
> 
>    This document only provides guidelines; it does not specify how
the
>    guidelines provided should be used within the IETF.
> 
> 4. Need to expand acronyms, even those who are very obvious in the
> management community but may be obscure out of it like SMI or 
> COPS-PR. 
> 
> 5. the DISCUSS at page 6 - I would avoid giving more 
> examples, lists of
> protocols, etc. 
> 
> 6. page 6 - I did not understand what is the intent of the paragraph
> that mentions IPFIX
> 
> 7. page 7 - [DISCUSS: would the
>    example of inconsistency between MIB counters that cannot be
reset
>    and CLI counters that can be rest be useful here?] - yes, 
> I think so
> 
> 8. Section 3.3 - the second paragraph does not seem to deal with
> protocols extensibility, but more to data models  and data model
> languages design. I think that the protocol designers cannot do much
> about this, and I would recommend to take this out. 
> 
> 9. Section 3.4 - The example is from a functional component 
> and not from
> a protocol. I would emphasize the role of impact on 
> functional elements
> by saying s/document the requirements from other 
> protocols/document the
> requirements from other protocols and functional elements/ in 
> the first
> paragraph
> 
> 10. page 9 - I believe that the content of the last paragraph in
this
> page is out of scope
> 
> 11. Section 3.6 - we can add considering simple protocol status and
> health indicators on network devices as a recommended mean to check
> correct operation
> 
> 12. Section 4 - We need some lose definition of what we mean by a
> 'service' (on the lines of network and operational 
> functionality derived
> from the implementation and deployment of a new protocol - or 
> something
> similar) 
> 
> 13. page 11 - [DISCUSS: Is a section on P2P vs. central management
> called for
>    here?] - No, IMO
> 
> 14, section 4.1 - when speaking about interoperability we 
> should add the
> management applications , emphasizing that interoperability allows
for
> usage or 3rd party applications and outsourcing of management 
> services.
> 
> 15. section 4.3 should start IMO with the need to document 
> what are the
> basic faults and health indicators that need to be instrumented for
a
> new protocol, as well as what alarms and events must be propagated
to
> management applications or exposed through a data model
> 
> 16. page 14 - DISCUSS-what is reliable? The accurate delivery of the
> event information is guaranteed within a given (high) margin of
> confidence
> 
> 17. 4.3.2 - the DISCUSSes go into too much details IMO 
> 
> 18. 4.3.4 - same, I would consider taking out these section, they
are
> beyond protocol design and what is expected in protocol documents
> 
> 19. Section 4.4 should start IMO with the need to document 
> what are the
> basic configuration parameters that need to be instrumented for a
new
> protocol, as well as default values and modes of operation
> 
> 20. All the discussion in section 4.4 about backup configuration,
gold
> config, etc. seems to me to be out of scope - it is device centric
and
> is not covered in new protocol documents
> 
> 21. Same with 4.4.1 - seems out of scope or mis-placed
> 
> 22. page 19 -    What information should be maintained across 
> reboots of
> the device,  or restarts of the management system? - this is
important
> but mis-placed, should be in the configuration management section
> 
> 23. DISCUSS: there are several parts to performance 
> management.  Device
>    monitoring (with the impact of the new protocol/service 
> activation),
>    protocol monitoring, and services monitoring.  This section might
>    benefit from being broken into different pieces.] - 
> 
>    YES - maybe not breaking the section but mentioning the three
> categories separately
> 
> 24. The security management section may add a paragraph about
security
> threats that may be introduced by management operations. For example
> CAPWAP breaks the structure of monolithic Access Points (AP) 
> into Access
> Controllers and Wireless Termination Points (WTP). By using a 
> management
> interface internal information that was previously not 
> accessible is now
> exposed over the network and to managers and my become a source of
> potential security threats. 
> 
> 25. I doubt that section A.1 is needed. In general I prefer 
> that expert
> reviews focus on expert information, while general reviews 
> are left for
> GenART
> 
> 26. A2, first paragraph - add the question whether textual or 
> graphical
> UI are required, whether binary or text representation of management
> information is preferred. 
> 
> 27. add to A2 the question 'what is the minimal set of management
> (configuration, faults, performance monitoring) objects that 
> need to be
> instrumented in order to manage the new protocol 
> 
> Thanks and Regards,
> 
> Dan
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 

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


From ops-area-bounces@ietf.org  Sun Jul 27 02:44:44 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 2E3D73A684B;
	Sun, 27 Jul 2008 02:44:44 -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 D2D3C3A6898
	for <ops-area@core3.amsl.com>; Sun, 27 Jul 2008 02:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74]
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 DYZbgG6sHTao for <ops-area@core3.amsl.com>;
	Sun, 27 Jul 2008 02:44:42 -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 B86823A67CF
	for <ops-area@ietf.org>; Sun, 27 Jul 2008 02:44:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,259,1215403200"; d="scan'208";a="116099211"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	27 Jul 2008 05:44:46 -0400
X-IronPort-AV: E=Sophos;i="4.31,259,1215403200"; d="scan'208";a="243410727"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	27 Jul 2008 05:44:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 27 Jul 2008 11:44:44 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E4BE8D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPS Area Open Hours
Thread-Index: AcjvzWYeF9ubTFeiRum6xVb5uJLeNg==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] OPS Area Open Hours
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

The OPS ADs will be holding Open Office hours as at each IETF meeting.
As the schedule at this IETF will be very busy with meeting slots for at
least each of us at any time, we need to split. So the schedule will be:


Tuesday July 29 13:00 to 15:20 - Dan
Tuesday July 29 15:00 to 17:20 - Ron

The breakout room will be announced later. 

Please come to talk with us on any issues related to the Operations and
Management Area or other IETF business. 

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  Mon Jul 28 05:45: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 B0B733A67AA;
	Mon, 28 Jul 2008 05:45: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 A3E7D3A67AA
	for <ops-area@core3.amsl.com>; Mon, 28 Jul 2008 05:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.292
X-Spam-Level: 
X-Spam-Status: No, score=-2.292 tagged_above=-999 required=5 tests=[AWL=0.307, 
	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 wp5npvw-B2q9 for <ops-area@core3.amsl.com>;
	Mon, 28 Jul 2008 05:45:46 -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 5FF2C3A63D3
	for <ops-area@ietf.org>; Mon, 28 Jul 2008 05:45:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,265,1215403200"; d="scan'208";a="137101939"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 28 Jul 2008 08:45:52 -0400
X-IronPort-AV: E=Sophos;i="4.31,265,1215403200"; d="scan'208";a="237283147"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	28 Jul 2008 08:45:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 28 Jul 2008 14:45:51 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E4C119@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Chairs: Helping out remote participants
Thread-Index: Acjwo840QueuVmImQ4WBC+ybForU3wAC7RNQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] FW: Chairs: Helping out remote participants
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

 OPS-Chairs,

Please take into account this request from a remote participant. 

Dan


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Philip Matthews
Sent: Monday, July 28, 2008 2:19 PM
To: IETF Discussion
Subject: Chairs: Helping out remote participants

Just a quick note on what chairs could do to help out remote
participants, from someone who is trying to participate remotely for the
first time this week.

In order of priority (most important first):

1) Ensure all meeting materials are uploaded before the session begins.
Ideally, the various presentations would be listed (on the meeting
materials page) in the same order as they appear in the agenda, but
otherwise they should have good names so  the correct presentation can
be easily found. [Following a presentation without seeing the slides can
be VERY difficult.]

2) Ensure everyone uses a microphone.

3) Ensure someone monitors the jabber chat room. If you cannot find a
scribe, at least have someone watching for questions, especially simple
questions like "what slide are we on now" or "who is that at the mic?".

4) Ensure all presentations have slide numbers and have the jabber
person type in slide changes. (It is often hard to tell from just audio
clues).


Thanks!

- Philip



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


From ops-area-bounces@ietf.org  Mon Jul 28 06:06:53 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 43E903A69C2;
	Mon, 28 Jul 2008 06:06:53 -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 D9B5D3A69C2
	for <ops-area@core3.amsl.com>; Mon, 28 Jul 2008 06:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.353
X-Spam-Level: 
X-Spam-Status: No, score=-2.353 tagged_above=-999 required=5 tests=[AWL=0.246, 
	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 HVoBXM9LQ4+p for <ops-area@core3.amsl.com>;
	Mon, 28 Jul 2008 06:06:48 -0700 (PDT)
Received: from nj300815-nj-outbound.avaya.com
	(nj300815-nj-outbound.net.avaya.com [198.152.12.100])
	by core3.amsl.com (Postfix) with ESMTP id 978933A691C
	for <ops-area@ietf.org>; Mon, 28 Jul 2008 06:06:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,265,1215403200"; d="scan'208";a="128846026"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 28 Jul 2008 09:06:56 -0400
X-IronPort-AV: E=Sophos;i="4.31,265,1215403200"; d="scan'208";a="237312374"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	28 Jul 2008 09:06:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 28 Jul 2008 15:06:50 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E4C12E@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A04E4BE8D@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [OPS-AREA] OPS Area Open Hours
Thread-Index: AcjvzWYeF9ubTFeiRum6xVb5uJLeNgA5Shmw
References: <EDC652A26FB23C4EB6384A4584434A04E4BE8D@307622ANEX5.global.avaya.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
	<ops-area@ietf.org>
Subject: Re: [OPS-AREA] OPS Area Open Hours
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

The meeting room will be the Swift Brook Suite. The time assignments
were slightly changed into:

Tuesday July 29 13:00 to 15:00 - Dan
Tuesday July 29 15:00 to 17:00 - Ron

Dan

 

> -----Original Message-----
> From: ops-area-bounces@ietf.org 
> [mailto:ops-area-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
> Sent: Sunday, July 27, 2008 12:45 PM
> To: ops-area@ietf.org
> Subject: [OPS-AREA] OPS Area Open Hours
> 
> The OPS ADs will be holding Open Office hours as at each IETF meeting.
> As the schedule at this IETF will be very busy with meeting 
> slots for at least each of us at any time, we need to split. 
> So the schedule will be:
> 
> 
> Tuesday July 29 13:00 to 15:20 - Dan
> Tuesday July 29 15:00 to 17:20 - Ron
> 
> The breakout room will be announced later. 
> 
> Please come to talk with us on any issues related to the 
> Operations and Management Area or other IETF business. 
> 
> Ron and Dan
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 
_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www.ietf.org/mailman/listinfo/ops-area


From ops-area-bounces@ietf.org  Mon Jul 28 07:44:21 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 084893A699C;
	Mon, 28 Jul 2008 07:44:21 -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 0B4DC3A695C
	for <ops-area@core3.amsl.com>; Mon, 28 Jul 2008 07:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level: 
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176, 
	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 L++pgwyZbJsh for <ops-area@core3.amsl.com>;
	Mon, 28 Jul 2008 07:44:13 -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 ECB3A3A6A9E
	for <ops-area@ietf.org>; Mon, 28 Jul 2008 07:44:12 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.31,266,1215403200"; d="scan'208";a="137121811"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by co300216-co-outbound.avaya.com with ESMTP; 28 Jul 2008 10:44:21 -0400
X-IronPort-AV: E=Sophos;i="4.31,266,1215403200"; d="scan'208";a="237441409"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	28 Jul 2008 10:44:21 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 28 Jul 2008 16:44:17 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04E4C1A6@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: GUINNESS AS YOU CAN (a.k.a. call for volunteers for OPSAREA open
	meeting note takers and jabber scribe)
Thread-Index: AcjwwGl3RX+Px7D4RyOL2AFJkEbQww==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
Subject: [OPS-AREA] GUINNESS AS YOU CAN (a.k.a. call for volunteers for
	OPSAREA open meeting note takers and jabber scribe)
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

Now that I got your attention - whoever is in Dublin and likes Guinness,
please step up and volunteer to be note takers and jabber proxies for
remote participants in the open area meeting tomorrow. 

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


From ops-area-bounces@ietf.org  Tue Jul 29 02:22:42 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 86C1D28C22D;
	Tue, 29 Jul 2008 02:22:42 -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 E1E7228C22D
	for <ops-area@core3.amsl.com>; Tue, 29 Jul 2008 02:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id Xr0SRU0beVgv for <ops-area@core3.amsl.com>;
	Tue, 29 Jul 2008 02:22:41 -0700 (PDT)
Received: from relay.versatel.net (relay.versatel.net [62.250.3.110])
	by core3.amsl.com (Postfix) with SMTP id C3FD628C22B
	for <ops-area@ietf.org>; Tue, 29 Jul 2008 02:22:40 -0700 (PDT)
Received: (qmail 16415 invoked from network); 29 Jul 2008 09:22:51 -0000
Received: from unknown (HELO BertLaptop) (87.215.199.34)
	by relay.versatel.net with SMTP; 29 Jul 2008 09:22:51 -0000
Message-ID: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
From: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>
To: "ops-area \(IETF\)" <ops-area@ietf.org>
Date: Tue, 29 Jul 2008 11:22:28 +0200
Organization: Consultant
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
Subject: [OPS-AREA] meeting materials MUST be online well BEFORE the session
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Being a jabber scribe for the OPS area, I clearly see how BAD it
is if slides are not ONLINE before the meeting starts.
Also... SLIDES MUST be numbers, and speakers should mention the
slide numbers.

I spend considerable amount of time typing slide titles after first having 
had
to email slides to remote participants from memory sticks.

Bert Wijnen 


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


From ops-area-bounces@ietf.org  Tue Jul 29 02:29:55 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 B3B9428C0F9;
	Tue, 29 Jul 2008 02:29:55 -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 844263A6B25
	for <ops-area@core3.amsl.com>; Tue, 29 Jul 2008 02:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.398
X-Spam-Level: 
X-Spam-Status: No, score=-1.398 tagged_above=-999 required=5 tests=[AWL=1.201, 
	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 a3kb-rXIRE0z for <ops-area@core3.amsl.com>;
	Tue, 29 Jul 2008 02:29:53 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248])
	by core3.amsl.com (Postfix) with ESMTP id 0B4473A6897
	for <ops-area@ietf.org>; Tue, 29 Jul 2008 02:29:52 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1])
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id
	m6T9TwIt018866; Tue, 29 Jul 2008 10:30:02 +0100
Received: from your029b8cecfe ([130.129.22.145]) (authenticated bits=0)
	by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id
	m6T9TkqE018669; Tue, 29 Jul 2008 10:29:55 +0100
Message-ID: <00a101c8f15d$a75335c0$91168182@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Bert Wijnen \(IETF\)" <bertietf@bwijnen.net>,
	"ops-area \(IETF\)" <ops-area@ietf.org>
References: <CB4A3CDA3EE44ECAB446F6D5A934EF1D@BertLaptop>
Date: Tue, 29 Jul 2008 10:29:34 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: Re: [OPS-AREA] meeting materials MUST be online well BEFORE the
	session
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Why don't we make the projector feed available on the Internet?

It's easy and its free.

Adrian
----- Original Message ----- 
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
To: "ops-area (IETF)" <ops-area@ietf.org>
Sent: Tuesday, July 29, 2008 10:22 AM
Subject: [OPS-AREA] meeting materials MUST be online well BEFORE the session


> Being a jabber scribe for the OPS area, I clearly see how BAD it
> is if slides are not ONLINE before the meeting starts.
> Also... SLIDES MUST be numbers, and speakers should mention the
> slide numbers.
>
> I spend considerable amount of time typing slide titles after first having 
> had
> to email slides to remote participants from memory sticks.
>
> Bert Wijnen
>
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area
> 


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


From ops-area-bounces@ietf.org  Wed Jul 30 05:31:46 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 A3AD628C2D5;
	Wed, 30 Jul 2008 05:31:46 -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 B435A28C2D5
	for <ops-area@core3.amsl.com>; Wed, 30 Jul 2008 05:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=0.079, 
	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 KiY1ugHvg3k3 for <ops-area@core3.amsl.com>;
	Wed, 30 Jul 2008 05:31:45 -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 732F128C1C8
	for <ops-area@ietf.org>; Wed, 30 Jul 2008 05:31:44 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1])
	by netcore.fi (8.13.8/8.13.8) with ESMTP id m6UCVsvY019822
	for <ops-area@ietf.org>; Wed, 30 Jul 2008 15:31:55 +0300
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m6UCVqjW019819
	for <ops-area@ietf.org>; Wed, 30 Jul 2008 15:31:54 +0300
Date: Wed, 30 Jul 2008 15:31:52 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: ops-area@ietf.org
Message-ID: <alpine.LRH.1.10.0807301529260.19753@netcore.fi>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.93.1/7882/Tue Jul 29 22:06:54 2008 on otso.netcore.fi
X-Virus-Status: Clean
Subject: [OPS-AREA] Adding accounting mechanisms in PIM
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ops-area-bounces@ietf.org
Errors-To: ops-area-bounces@ietf.org

Hi,

FYI, PIM WG has adopted a mechanism that adds certain accounting 
mechanisms to PIM routing protocol.  I want to bring this up because 
this seems to somewhat differ from typical management practises when 
designing protocols and their management:

http://tools.ietf.org/id/draft-ietf-pim-pop-count-00.txt

-- 
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


