IETF Logo Mail Archive

Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB)

"A S Kiran Koushik" <kkoushik@cisco.com> Thu, 28 June 2007 22:16 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I42HZ-0002dY-Lu; Thu, 28 Jun 2007 18:16:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I42HZ-0002dS-1Z for pce@ietf.org; Thu, 28 Jun 2007 18:16:09 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I42HT-0002XK-Eb for pce@ietf.org; Thu, 28 Jun 2007 18:16:09 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 28 Jun 2007 18:16:03 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAP7Pg0ZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,472,1175486400"; d="scan'208"; a="124828359:sNHT39708264"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5SMG3K2020896; Thu, 28 Jun 2007 18:16:03 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5SMG3ZF008248; Thu, 28 Jun 2007 22:16:03 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:16:03 -0400
Received: from kkoushikwxp ([64.101.185.227]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jun 2007 18:16:02 -0400
Message-ID: <05fc01c7b9d1$ea3c6b00$6b10590a@apac.cisco.com>
From: A S Kiran Koushik <kkoushik@cisco.com>
To: Meral Shirazipour <meral.shirazipour@polymtl.ca>
References: <4682A0D1.4050904@grotto-networking.com> <048d01c7b921$4c998fa0$6b10590a@apac.cisco.com> <1183039913.4683c1a9722c8@www.imp.polymtl.ca>
Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB)
Date: Thu, 28 Jun 2007 17:16:02 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"; reply-type="original"
Content-Transfer-Encoding: 7bit
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.3138
X-OriginalArrivalTime: 28 Jun 2007 22:16:02.0539 (UTC) FILETIME=[E9D03BB0:01C7B9D1]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2175; t=1183068963; x=1183932963; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kkoushik@cisco.com; z=From:=20=22A=20S=20Kiran=20Koushik=22=20<kkoushik@cisco.com> |Subject:=20Re=3A=20[Pce]=20draft-kkoushik-pce-pcep-mib-00.txt=20(PCE-PCE P-DRAFT-MIB) |Sender:=20 |To:=20=22Meral=20Shirazipour=22=20<meral.shirazipour@polymtl.ca>; bh=7Xv+3K57PG9Cy/R+ap1KJ22Wos103u4yOoFj6Fv4C4E=; b=Xts7Xy+DG35Gs3VMYNDWFPW6zDwqgITAOTx77IOHZTCzGTXf4rWtgBCyw3z3hgDRwhdLrGEL uLuysFKR1hxTUZ/Zpj4yJ7a597OIM3FJCW84Md+tXVmk5f8l6aeJxxdw;
Authentication-Results: rtp-dkim-1; header.From=kkoushik@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: pce@ietf.org, jpv@cisco.com
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi Meral,
We have divided the organization of PCE management MIBs
as below:
MIB module               WG draft name
================================================
PCE-DISC-DRAFT-MIB         draft-ietf-pce-disc-mib
 -- PCE discovery MIB.

PCE-PCEP-DRAFT-MIB         draft-ietf-pce-pcep-mib
 -- PCE communication protocol MIB

PCE-PCC-DRAFT-MIB          draft-ietf-pce-pcc-mib
 -- Path Computation Client MIB

PCE-TC-DRAFT-MIB           draft-ietf-pce-tc-mib
 -- PCE Textual conventions MIB.

The information you are referring to below will be contained as a
part of draft-ietf-pce-pcc-mib which is yet to be started.

Regards,
Kiran.

----- Original Message ----- 
From: "Meral Shirazipour" <meral.shirazipour@polymtl.ca>
To: "A S Kiran Koushik" <kkoushik@cisco.com>
Cc: <pce@ietf.org>; <jpv@cisco.com>
Sent: Thursday, June 28, 2007 9:11 AM
Subject: Re: [Pce] draft-kkoushik-pce-pcep-mib-00.txt (PCE-PCEP-DRAFT-MIB)


> Hi,
>   I have a question regarding page 3, section 4:
> "The PCEP MIB will contain the following information:
>   a. PCEP client configuration and status."
>
> Does the "status" here also represent the previous/ongoing path computation
> requests?
> I am referring to Section 6.8.  Stateful versus Stateless PCEs in RFC4655; 
> would
> the information related to a stateful PCE be stored in the described MIB ?
>
> Best regards,
> Meral
>
>
> Selon A S Kiran Koushik <kkoushik@cisco.com>:
>
>> Hi pce-team,
>> We are working on updating the PCE-PCEP-DRAFT-MIB
>> (PCE communication protocol MIB) with some editorial changes.
>> http://tools.ietf.org/id/draft-kkoushik-pce-pcep-mib-00.txt
>>
>> Can some of you kindly review the existing draft and let us know of any
>> comments/suggestions. That way we can fix them by the deadline.
>>
>> Also we are planning to request this to be a working group document.
>> If there are any objections to this, please let us know and we will work
>> on fixing them.
>>
>> Thanks,
>> Kiran and Emile.
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/pce
>>
> 

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

v2.23.0 | Report a Bug | By Email