From owner-te-wg@ops.ietf.org  Mon Aug 11 15:54:01 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02387
	for <tewg-archive@lists.ietf.org>; Mon, 11 Aug 2003 15:54:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19mIcq-000HOx-VV
	for te-wg-data@psg.com; Mon, 11 Aug 2003 19:46:40 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.20)
	id 19mIco-000HOl-08
	for te-wg@ops.ietf.org; Mon, 11 Aug 2003 19:46:38 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01404;
	Mon, 11 Aug 2003 15:46:32 -0400 (EDT)
Message-Id: <200308111946.PAA01404@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-mib-05.txt
Date: Mon, 11 Aug 2003 15:46:32 -0400
X-Spam-Status: No, hits=1.5 required=5.0
	tests=BAYES_30,MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Traffic Engineering Working Group of the IETF.

	Title		: A Traffic Engineering MIB
	Author(s)	: K. Kompella
	Filename	: draft-ietf-tewg-mib-05.txt
	Pages		: 38
	Date		: 2003-8-11
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Traffic Engineered
Tunnels, for example, Multi-Protocol Label Switched Paths.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-mib-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-tewg-mib-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-mib-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-11143325.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-mib-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tewg-mib-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-11143325.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Mon Aug 11 16:03:08 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03473
	for <tewg-archive@lists.ietf.org>; Mon, 11 Aug 2003 16:03:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19mIrX-000IOt-C6
	for te-wg-data@psg.com; Mon, 11 Aug 2003 20:01:51 +0000
Received: from [131.137.245.203] (helo=mx03.forces.gc.ca)
	by psg.com with esmtp (Exim 4.20)
	id 19mIrU-000IOL-CX
	for te-wg@ops.ietf.org; Mon, 11 Aug 2003 20:01:48 +0000
Received: from asgard.ietf.org (asgard.ietf.org [132.151.6.40])
	by mx03.forces.gc.ca (DND-Mailer) with ESMTP id 8F079206609
	for <Allan.JER@forces.gc.ca>; Mon, 11 Aug 2003 16:00:16 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14)
	id 19mId9-0007cz-EV
	for ietf-announce-list@asgard.ietf.org; Mon, 11 Aug 2003 15:46:59 -0400
Received: from ietf.org ([10.27.2.28])
	by asgard.ietf.org with esmtp (Exim 4.14)
	id 19mIco-0007XK-FA
	for all-ietf@asgard.ietf.org; Mon, 11 Aug 2003 15:46:38 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01404;
	Mon, 11 Aug 2003 15:46:32 -0400 (EDT)
Message-Id: <200308111946.PAA01404@ietf.org>
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-mib-05.txt
Date: Mon, 11 Aug 2003 15:46:32 -0400
MIME-Version: 1.0
Content-Type: Multipart/Mixed; boundary="MIMEStream=_0+36151_279936263610279_6791891987"
X-Spam-Status: No, hits=1.2 required=5.0
	tests=BAYES_30,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


--MIMEStream=_0+36151_279936263610279_6791891987

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Traffic Engineering Working Group of the IETF.

	Title		: A Traffic Engineering MIB
	Author(s)	: K. Kompella
	Filename	: draft-ietf-tewg-mib-05.txt
	Pages		: 38
	Date		: 2003-8-11
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Traffic Engineered
Tunnels, for example, Multi-Protocol Label Switched Paths.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-mib-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-tewg-mib-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-mib-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--MIMEStream=_0+36151_279936263610279_6791891987
Content-Type: Multipart/Alternative; boundary="MIMEStream=_1+29136_858703466811463_7057367189"


--MIMEStream=_1+29136_858703466811463_7057367189
Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-8-11143325.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-mib-05.txt

--MIMEStream=_1+29136_858703466811463_7057367189
Content-Type: Message/External-body; name="draft-ietf-tewg-mib-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-8-11143325.I-D@ietf.org>

--MIMEStream=_1+29136_858703466811463_7057367189--
--MIMEStream=_0+36151_279936263610279_6791891987--



From owner-te-wg@ops.ietf.org  Mon Aug 18 16:09:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02840
	for <tewg-archive@lists.ietf.org>; Mon, 18 Aug 2003 16:09:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19oqCI-000AsC-1l
	for te-wg-data@psg.com; Mon, 18 Aug 2003 20:01:46 +0000
Received: from [66.57.30.77] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.20)
	id 19oqCB-000As0-P6
	for te-wg@ops.ietf.org; Mon, 18 Aug 2003 20:01:39 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h7IJkFAY019144
	for <te-wg@ops.ietf.org>; Mon, 18 Aug 2003 15:46:20 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h7IJk8YZ019140
	for <te-wg@ops.ietf.org>; Mon, 18 Aug 2003 15:46:15 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 18 Aug 2003 15:46:08 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: WG Last Call: draft-ietf-tewg-mib-05.txt 
Message-ID: <Pine.LNX.4.44.0308181544050.8082-120000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; BOUNDARY="MIMEStream=_0+36151_279936263610279_6791891987"
Content-ID: <Pine.LNX.4.44.0308181544110.8082@fido.nc.rr.com>
X-Spam-Status: No, hits=-13.7 required=5.0
	tests=BAYES_01,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--MIMEStream=_0+36151_279936263610279_6791891987
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.44.0308181544111.8082@fido.nc.rr.com>


This message begins a WG last call for the TE-MIB, 

	draft-ietf-tewg-mib-05.txt

The last call will end 9/1/2003.

Thanks,

Jim

---------- Forwarded message ----------
Date: Mon, 11 Aug 2003 15:46:32 -0400
From: Internet-Drafts@ietf.org
To: IETF-Announce:  ;
Cc: te-wg@ops.ietf.org
Subject: I-D ACTION:draft-ietf-tewg-mib-05.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Traffic Engineering Working Group of the IETF.

	Title		: A Traffic Engineering MIB
	Author(s)	: K. Kompella
	Filename	: draft-ietf-tewg-mib-05.txt
	Pages		: 38
	Date		: 2003-8-11
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for Traffic Engineered
Tunnels, for example, Multi-Protocol Label Switched Paths.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-mib-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-tewg-mib-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-mib-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--MIMEStream=_0+36151_279936263610279_6791891987
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="MIMEStream=_1+29136_858703466811463_7057367189"
Content-ID: <Pine.LNX.4.44.0308181544112.8082@fido.nc.rr.com>
Content-Description: 

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--MIMEStream=_1+29136_858703466811463_7057367189
Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="mailserv@ietf.org"
Content-ID: <Pine.LNX.4.44.0308181544113.8082@fido.nc.rr.com>

--MIMEStream=_1+29136_858703466811463_7057367189
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="draft-ietf-tewg-mib-05.txt"; SITE="ftp.ietf.org"; ACCESS-TYPE=anon-ftp; DIRECTORY=internet-drafts
Content-ID: <Pine.LNX.4.44.0308181544114.8082@fido.nc.rr.com>

--MIMEStream=_1+29136_858703466811463_7057367189--
--MIMEStream=_0+36151_279936263610279_6791891987--



From owner-te-wg@ops.ietf.org  Tue Aug 19 01:22:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15180
	for <tewg-archive@lists.ietf.org>; Tue, 19 Aug 2003 01:22:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19oyt3-000EBk-At
	for te-wg-data@psg.com; Tue, 19 Aug 2003 05:18:29 +0000
Received: from [66.57.30.77] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.20)
	id 19oyt0-000EBT-5U
	for te-wg@ops.ietf.org; Tue, 19 Aug 2003 05:18:26 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h7J537AY019707
	for <te-wg@ops.ietf.org>; Tue, 19 Aug 2003 01:03:07 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h7J537ux019703
	for <te-wg@ops.ietf.org>; Tue, 19 Aug 2003 01:03:07 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 19 Aug 2003 01:03:06 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: How to progress DSTE, particularly p -> TE-Class[i] = {CT, p}
Message-ID: <Pine.LNX.4.44.0308190042180.8082-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-12.9 required=5.0
	tests=BAYES_10,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


One issue that draft-sivabalan-diff-te-bundling-02.txt highlights is that 
there may be text in existing RFCs and I-Ds for MPLS/TE which address how 
to support priority preemption between LSPs.  

draft-ietf-tewg-diff-te-proto-04.txt redefines the reservable bandwidth 
available at priority "p" to be the reservable bandwidth available for 
TE-Class "i" where that is defined as:

     TE-Class[i]  <-->  < CTc , preemption p >  

Where this mapping is defined locally.

This creates a problem, as improvements to the base of MPLS, for
instance bundled links refer to how to address the particulars of that
improvement with regards to priority, would also likely beof use e
might want to in a diff-serv TE environment as well.

It is obvious that one should assume that where one reads about "p" they 
should be thinking TE-Class[i], however it would be best for this to be 
explicitly stated somewhere.

Before the DSTE proto draft and the BC models progress to WG last call, 
I'd like to see this resolved.

There are 3 approaches that I've heard suggested.

1) Address this in the diff-te-proto draft. State that for the IGP and
RSVP RFCs, as well as technologies that improve upon them
(e.g. FA-LSP, link bundling, etc..), in order to be diff-serv TE
compliant, you need to map all references of "p" to TE-Class[i]

2) Address this in a parallel document to diff-te-proto, and let 
diff-te-proto progress to IESG before this is resolved.  This parallel 
document will somehow generalize "p" in base documents, and diff-te-proto 
will fit on-top of that (somehow)

3) Generalize "p" in the base documents, RFC3209, the igp-traffic drafts, 
all of the other MPLS/TE and GMPLS drafts as well.  For the record, I am 
not personally in favor of this approach.

Please advise how you propose we move forward with this,

thanks,

Jim




From owner-te-wg@ops.ietf.org  Wed Aug 20 09:15:24 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07655
	for <tewg-archive@lists.ietf.org>; Wed, 20 Aug 2003 09:15:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19pSda-0005o3-9L
	for te-wg-data@psg.com; Wed, 20 Aug 2003 13:04:30 +0000
Received: from [192.128.133.69] (helo=kcmso1.proxy.att.com)
	by psg.com with esmtp (Exim 4.20)
	id 19pSdX-0005no-5w
	for te-wg@ops.ietf.org; Wed, 20 Aug 2003 13:04:27 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h7KD3xTk000572
	for <te-wg@ops.ietf.org>; Wed, 20 Aug 2003 08:04:26 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3F307C6C003D2E20; Wed, 20 Aug 2003 09:04:10 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: How to progress DSTE, particularly p -> TE-Class[i] = {CT, p}
Date: Wed, 20 Aug 2003 08:04:19 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0201EE09@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: How to progress DSTE, particularly p -> TE-Class[i] = {CT, p}
Thread-Index: AcNmEoixtKRZVihFQditjQFhnSYQEgBBOtnQ
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.3 required=5.0
	tests=BAYES_20,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Jim,

> One issue that draft-sivabalan-diff-te-bundling-02.txt highlights is =
that=20
> there may be text in existing RFCs and I-Ds for MPLS/TE which address =
how=20
> to support priority preemption between LSPs. =20
>=20
> draft-ietf-tewg-diff-te-proto-04.txt redefines the reservable =
bandwidth=20
> available at priority "p" to be the reservable bandwidth available for =

> TE-Class "i" where that is defined as:
>=20
>      TE-Class[i]  <-->  < CTc , preemption p > =20
>=20
> Where this mapping is defined locally.
>=20
> This creates a problem, as improvements to the base of MPLS, for
> instance bundled links refer to how to address the particulars of that
> improvement with regards to priority, would also likely be of use
> might want to in a diff-serv TE environment as well.
>=20
> It is obvious that one should assume that where one reads about "p" =
they=20
> should be thinking TE-Class[i], however it would be best for this to =
be=20
> explicitly stated somewhere.
>=20
> Before the DSTE proto draft and the BC models progress to WG last =
call,=20
> I'd like to see this resolved.
>=20
> There are 3 approaches that I've heard suggested.
>=20
> 1) Address this in the diff-te-proto draft. State that for the IGP and
> RSVP RFCs, as well as technologies that improve upon them
> (e.g. FA-LSP, link bundling, etc..), in order to be diff-serv TE
> compliant, you need to map all references of "p" to TE-Class[i]
>=20
> 2) Address this in a parallel document to diff-te-proto, and let=20
> diff-te-proto progress to IESG before this is resolved.  This parallel =

> document will somehow generalize "p" in base documents, and =
diff-te-proto=20
> will fit on-top of that (somehow)
>=20
> 3) Generalize "p" in the base documents, RFC3209, the igp-traffic =
drafts,=20
> all of the other MPLS/TE and GMPLS drafts as well.  For the record, I =
am=20
> not personally in favor of this approach.
>=20
> Please advise how you propose we move forward with this.

I'd favor option 1, the issue relates directly to the proto spec and =
needs to be addressed there.  Option 2 is complicated, and only =
addresses the issue indirectly, the issue is left hanging until the =
'proto-2' draft is issued as an RFC.  Option 3 seems far too complex.

Hopefully we can move forward quickly to revise the proto draft, and =
finalize it.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Wed Aug 20 09:51:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09092
	for <tewg-archive@lists.ietf.org>; Wed, 20 Aug 2003 09:51:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19pTIa-000ARn-2p
	for te-wg-data@psg.com; Wed, 20 Aug 2003 13:46:52 +0000
Received: from [12.20.58.69] (helo=ckmso1.proxy.att.com)
	by psg.com with esmtp (Exim 4.20)
	id 19pTIX-000ARQ-DZ
	for te-wg@ops.ietf.org; Wed, 20 Aug 2003 13:46:49 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h7KDNN13009031
	for <te-wg@ops.ietf.org>; Wed, 20 Aug 2003 09:46:48 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3F307C6C003D74D5; Wed, 20 Aug 2003 09:46:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D ACTION:draft-ietf-tewg-measure-06.txt
Date: Wed, 20 Aug 2003 08:46:43 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0201EE0C@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-tewg-measure-06.txt
Thread-Index: AcNSAwntnVJHFebaQv+ERDUnKS2GTQAuRPfgBRjoYoA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.3 required=5.0
	tests=BAYES_20,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

> From: Lai, Wai S (Waisum), ALABS=20
> Sent: Monday, July 28, 2003 7:56 AM
> To: Wijnen, Bert (Bert); te-wg@ops.ietf.org
> Subject: RE: I-D ACTION:draft-ietf-tewg-measure-06.txt
>
> Bert and all,
>
> Many thanks for the AD review and the subsequent comments.
> We have now completed our revision of the TE Measurement draft
> based on your inputs.  The main body of document has been much
> shortened and streamlined - with requirements clearly identified.
> Supporting materials have been moved to Appendices.
> Please review.
>
> Thanks, Wai Sum

I think the 06-draft =
http://ietf.org/internet-drafts/draft-ietf-tewg-measure-06.txt well =
addresses Bert's comments:

'I would expect a CRISP set of "requirements for additional =
measurements, configurable/negotiable parameters/controls" ... but not =
the extensive exploration and text that I now see'.

The requirements are now clearly identified for additional measurements, =
configurable/negotiable parameters/controls, etc., and the main text has =
been greatly shortened.

It would be good to hear from Bert on this.  Can we now move forward and =
finalize?

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Fri Aug 22 09:25:35 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22723
	for <tewg-archive@lists.ietf.org>; Fri, 22 Aug 2003 09:25:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19qBnV-0008ud-9m
	for te-wg-data@psg.com; Fri, 22 Aug 2003 13:17:45 +0000
Received: from [209.171.43.51] (helo=relay0.netfirms.com)
	by psg.com with smtp (Exim 4.20)
	id 19qBmx-0008o9-0g
	for te-wg@ops.ietf.org; Fri, 22 Aug 2003 13:17:11 +0000
Received: (qmail 72245 invoked from network); 22 Aug 2003 13:15:44 -0000
Received: from du-069-0131.access.clara.net (HELO Puppy) (217.158.132.131)
  by 0 with SMTP; 22 Aug 2003 13:15:44 -0000
Message-ID: <017801c368af$7e6946e0$fc919ed9@Puppy>
Reply-To: "Adrian Farrel" <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: <te-wg@ops.ietf.org>
References: <Pine.LNX.4.44.0308181544050.8082-120000@fido.nc.rr.com>
Subject: Re: WG Last Call: draft-ietf-tewg-mib-05.txt 
Date: Fri, 22 Aug 2003 14:12:41 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0167_01C368B7.72ED3D00"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-15.4 required=5.0
	tests=BAYES_10,HTML_30_40,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,
	      REFERENCES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0167_01C368B7.72ED3D00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Kireeti,
Good job.=20

A few comments embedded in the extracted text of the draft below. Mainly =
typos.

But a couple of questions/issues first.

Cheers,
Adrian


1. Could you explicitly clarify in the introduction that the MIB applies
    only at the ingress of tunnels. That is that it cannot be used to
    monitor tunnels at transit nodes or at their egresses.

2. The introduction makes (correctly) much of the fact that the MIB
    module can be used to model and manage any tunnel. Yet when
    we get to teSignalingProto we discover that the options are only
    'other', rsvpte' and 'crldp'. This seems to make it very =
MPLS-centric.

    I appreciate that 'other' covers a lot of possibilities, but aren't =
there
    some other tunneling protocols/techniques you'd like to list here?

    In particular, I'd like to see 'none' added to the list to cover =
statically
    configured (unsignaled) tunnels.

3. teNextPathIndex seems to be in contradiction with the indexes to
    tePathTable.=20

    tePathTable has paths listed under the primary index of=20
    teTunnelIndex so that you can find all of the paths for a given
    tunnel. The secondary index is tePathIndex and is described as
    being unique within the context of a tunnel. The use of=20
    teNextPathIndex would give a tePathIndex value that was unique=20
    across the whole table.

    Admitedly one of these statements is a subset of the other, but
    it is not immediately clear how you expect teNextPathIndex to be=20
    used.

4.  Could you supply a means to enable/disable notifications?
     Something like...
     teNotificationEnable OBJECT-TYPE
        SYNTAX        TruthValue
        MAX-ACCESS    read-write
        STATUS        current
        DESCRIPTION
             "If this object is true, then it enables the generation of =
notifications
              from this MIB module. Otherwise notifications are not =
generated."
        DEFVAL { false }
        ::=3D { teMIBObjects 5 }

5. It is not clear (to me) how you activate a tunnel (i.e. cause it to =
begin to be
    signaled). I presume you use are using the rowStatus transitions to =
active
    event. Could you clarify this (and how to initiate tear-down) either =
in the
    description of teTunnelEntry or in the descriptive text before the =
MIB module
    definition.

Nits...

< 3. Overview of the MIB
> 3. Overview of the MIB Module

<   The Traffic Engineering MIB consists of four parts:
>   The Traffic Engineering MIB module consists of four parts:
      1) Traffic Engineering information;
      2) a table of Traffic Tunnels;
      3) a table of Paths that tunnels take;
      4) a table of Hops that make up a tunnel path.

<  The MIB also has statements for minimal and full compliance.
>  The MIB module also has statements for minimal and full compliance.


   teAdminGroupTable OBJECT-TYPE
       SYNTAX       SEQUENCE OF TeAdminGroupEntry
       MAX-ACCESS   not-accessible
       STATUS       current
       DESCRIPTION "A mapping of configured administrative groups.  Each
                    entry represents an Administrative Group, and
                    provides a name and index for the group.
                    Administrative groups are used to label links in the
                    Traffic Engineering topology in order to place
                    constraints (include and exclude) on Tunnel paths.

                    A groupName can only be linked to one group number.
                    The groupNumber is the number assigned to the
<                   administrative group which are used in constraints,
>                   administrative group which is used in constraints,
                    like tePathIncludeAny, tePathIncludeAll, etc.
                   "
       ::=3D { teInfo 9 }



   teTunnelIndex    OBJECT-TYPE
       SYNTAX       Unsigned32 (1..4294967295)
       MAX-ACCESS   not-accessible
       STATUS       current
       DESCRIPTION "A unique index that identifies a Tunnel.  This
                    index MUST be unique across Tunnels and interfaces
                    on this host.
# Unclear. Are you saying that a tunnel index must not have the same =
value as
# an interface index? Or are you saying "MUST be unique across Tunnels =
on all
# interfaces on this host"
                   "
       ::=3D { teTunnelEntry 1 }

   teTunnelName     OBJECT-TYPE
       SYNTAX       SnmpAdminString (SIZE (1..32))
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "Name of the Traffic Tunnel.

<                   Note that the name of a Tunnel must be unique.
>                   Note that the name of a Tunnel MUST be unique across
>                   all Tunnels on this host.
                    When a SET request contains a name that is already
                    in use for another entry, then the implementation
                    must return an inconsistentValue error.

                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::=3D { teTunnelEntry 2 }


   teTunnelSourceAddressType OBJECT-TYPE
       SYNTAX       TeHopAddressType
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Traffic Engineered Tunnel hop Address for the source
<                   this Tunnel.
>      DESCRIPTION "The type of the Traffic Engineered Tunnel hop =
address=20
>                   for the source this Tunnel.

                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::=3D { teTunnelEntry 5 }

   teTunnelSourceAddress OBJECT-TYPE
       SYNTAX       TeHopAddress
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Source Traffic Engineered Tunnel hop Address of
>      DESCRIPTION "Source Traffic Engineered Tunnel hop address of
                    this Tunnel.

                    The type of this address is determined by the value
                    of the corresponding teTunnelSourceAddressType.

                    Note that source and destination addresses of a
                    Tunnel can be different address types.

                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::=3D { teTunnelEntry 6 }

   teTunnelDestinationAddressType OBJECT-TYPE
       SYNTAX       TeHopAddressType
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "The type of Traffic Engineered Tunnel hop Address
>      DESCRIPTION "The type of Traffic Engineered Tunnel hop address
>                   for the destination of this Tunnel.

                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::=3D { teTunnelEntry 7 }

   teTunnelDestinationAddress OBJECT-TYPE
       SYNTAX       TeHopAddress
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Destination Traffic Engineered Tunnel hop Address
>      DESCRIPTION "Destination Traffic Engineered Tunnel hop address
                    of this Tunnel.

                    The type of this address is determined by the value
                    of the corresponding teTunnelDestinationAddressType.

                    Note that source and destination addresses of a
                    Tunnel can be different address types.

                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::=3D { teTunnelEntry 8 }


   teTunnelAge      OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
<      DESCRIPTION "The age (i.e., time from creation till now) of
<                   this Tunnel in hundredths of a second.
>      DESCRIPTION "The age (i.e., time from creation of this conceptual =

>                   row till now) of this Tunnel in hundredths of a=20
>                   second.
                   "
       ::=3D { teTunnelEntry 15 }


   teTunnelTransitions OBJECT-TYPE
       SYNTAX       Counter32
       MAX-ACCESS   read-only
       STATUS       current
<      DESCRIPTION "The number of state transitions (up -> down and
<                   down -> up) this Tunnel has undergone.
>      DESCRIPTION "The number of operational state transitions=20
>                   (up -> down and down -> up) this Tunnel has
>                   undergone.
                   "
       ::=3D { teTunnelEntry 18 }

   teTunnelLastTransition OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
       DESCRIPTION "The time in hundredths of a second since the last
<                   transition occurred on this Tunnel.
>                   operational state transition occurred on this=20
>                   Tunnel.
                   "
       ::=3D { teTunnelEntry 19 }


   teTunnelLastPathChange OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
       DESCRIPTION "The time in hundredths of a secondsince the last
<                   change occurred on this Tunnel.
>                   path change occurred on this Tunnel.
                   "
       ::=3D { teTunnelEntry 21 }


   tePathRowStatus  OBJECT-TYPE
       SYNTAX       RowStatus
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "The status of this conceptual row.

                    When the value of this object is 'active', then
                    the value of tePathName cannot be changed.  All
<                   other writable may be changed; however, these
<                   changes may affect traffic going over the TE
>                   other writable objects may be changed; however,=20
>                   these changes may affect traffic going over the TE
                    tunnel, or require the path to be computed and/or
                    re-signalled.
                   "
       ::=3D { tePathEntry 3 }

   tePathBandwidth  OBJECT-TYPE
       SYNTAX       Unsigned32
# You could use the MPLS TC MplsBitRate
       UNITS       "Kilobits per second"
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "The configured bandwidth for this Tunnel,
                    in units of thousands of bits per second (Kbps).
                   "
       DEFVAL      { 0 }
       ::=3D { tePathEntry 7 }


----- Original Message -----=20
From: "Jim Boyle" <jboyle@pdnets.com>
To: <te-wg@ops.ietf.org>
Sent: Monday, August 18, 2003 8:46 PM
Subject: WG Last Call: draft-ietf-tewg-mib-05.txt=20


>=20
> This message begins a WG last call for the TE-MIB,=20
>=20
> draft-ietf-tewg-mib-05.txt
>=20
> The last call will end 9/1/2003.
>=20
> Thanks,
>=20
> Jim
>=20

------=_NextPart_000_0167_01C368B7.72ED3D00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff background=3D"">
<DIV><FONT face=3DArial size=3D2>Kireeti,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Good job.&nbsp;<BR><BR>A few comments =
embedded in=20
the extracted text of the draft below. Mainly typos.<BR><BR>But a couple =
of=20
questions/issues first.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Cheers,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Adrian</DIV>
<DIV><BR><BR>1. Could you explicitly clarify in the introduction that =
the MIB=20
applies<BR>&nbsp;&nbsp;&nbsp; only at the ingress of tunnels. That is =
that it=20
cannot be used to</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; monitor tunnels at =
transit nodes=20
or at their egresses.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2. The introduction makes (correctly) =
much of the=20
fact that the MIB</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; module can be used =
to model and=20
manage any tunnel. Yet when</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; we get to =
teSignalingProto we=20
discover that the options are only</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; 'other', rsvpte' and =
'crldp'.=20
This seems to make it very MPLS-centric.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I appreciate that =
'other' covers=20
a lot of possibilities, but aren't there</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; some other tunneling =

protocols/techniques you'd like to list here?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; In particular, I'd =
like to see=20
'none' added to the list to cover statically</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; configured =
(unsignaled)=20
tunnels.</DIV>
<DIV>&nbsp;</DIV>
<DIV>3. teNextPathIndex seems to be in contradiction with the indexes =
to</DIV>
<DIV>&nbsp;&nbsp;&nbsp; tePathTable. </DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp; tePathTable has paths listed under the primary=20
index&nbsp;of </DIV>
<DIV>&nbsp;&nbsp;&nbsp; teTunnelIndex so that you can find all of the =
paths for=20
a given</DIV>
<DIV>&nbsp;&nbsp;&nbsp; tunnel. The secondary index is tePathIndex and =
is=20
described as</DIV>
<DIV>&nbsp;&nbsp;&nbsp; being unique within the context of a tunnel. The =
use of=20
</DIV>
<DIV>&nbsp;&nbsp;&nbsp; teNextPathIndex would give a tePathIndex value =
that was=20
unique </DIV>
<DIV>&nbsp;&nbsp;&nbsp; across the whole table.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp; Admitedly one of these statements is a subset of =
the=20
other, but</DIV>
<DIV>&nbsp;&nbsp;&nbsp; it is not immediately clear how you expect=20
teNextPathIndex to be </DIV>
<DIV>&nbsp;&nbsp;&nbsp; used.<BR><BR>4.&nbsp; Could you supply a means =
to=20
enable/disable notifications?<BR>&nbsp;&nbsp;&nbsp;&nbsp; Something=20
like...<BR>&nbsp;&nbsp;&nbsp;&nbsp; teNotificationEnable=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TruthValue<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;&nbsp;=20
read-write<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
DESCRIPTION<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp; "If this object is true, then it enables the generation of=20
notifications<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
from this MIB module. Otherwise notifications are not=20
generated."<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; DEFVAL { false=20
}<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ::=3D { teMIBObjects 5 =
}<BR></DIV>
<DIV>5. It is not clear (to me) how you activate a tunnel (i.e. cause it =
to=20
begin to be</DIV>
<DIV>&nbsp;&nbsp; &nbsp;signaled). I presume you use are using the =
rowStatus=20
transitions to active</DIV>
<DIV>&nbsp;&nbsp;&nbsp; event. Could you clarify this (and how to =
initiate=20
tear-down) either in the</DIV>
<DIV>&nbsp;&nbsp;&nbsp; description of teTunnelEntry or in the =
descriptive text=20
before the MIB module</DIV>
<DIV>&nbsp;&nbsp;&nbsp; definition.</DIV>
<DIV><BR>Nits...</DIV>
<DIV>&nbsp;</DIV>
<DIV>&lt; 3. Overview of the MIB<BR>&gt; 3. Overview of the MIB =
Module</DIV>
<DIV>&nbsp;</DIV>
<DIV>&lt;&nbsp;&nbsp; The Traffic Engineering MIB consists of four=20
parts:<BR>&gt;&nbsp;&nbsp; The Traffic Engineering MIB module consists =
of four=20
parts:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1) Traffic Engineering=20
information;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2) a table of Traffic=20
Tunnels;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) a table of Paths that =
tunnels=20
take;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4) a table of Hops that make up =
a tunnel=20
path.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&lt;&nbsp; The MIB also has statements for minimal and full=20
compliance.<BR>&gt;&nbsp; The MIB module also has statements for minimal =
and=20
full compliance.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teAdminGroupTable=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF=20
TeAdminGroupEntry<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
not-accessible<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "A mapping =
of=20
configured administrative groups.&nbsp;=20
Each<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
entry represents an Administrative Group,=20
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
provides a name and index for the=20
group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Administrative groups are used to label links in=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Traffic Engineering topology in order to place</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
constraints (include and exclude) on Tunnel paths.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
A groupName can only be linked to one group=20
number.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The groupNumber is the number assigned to=20
the<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
administrative group which are used in=20
constraints,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
administrative group which is used in=20
constraints,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
like tePathIncludeAny, tePathIncludeAll,=20
etc.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teInfo 9 }<BR></DIV>
<DIV><BR>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelIndex&nbsp;&nbsp;&nbsp;=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32=20
(1..4294967295)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
not-accessible<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "A unique =
index that=20
identifies a Tunnel.&nbsp;=20
This<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
index MUST be unique across Tunnels and=20
interfaces<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
on this host.<BR># Unclear. Are you saying that a tunnel index must not =
have the=20
same value as<BR># an interface index? Or are you saying "MUST be unique =
across=20
Tunnels on all<BR># interfaces on this=20
host"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 1 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelName&nbsp;&nbsp;&nbsp;&nbsp;=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SnmpAdminString (SIZE=20
(1..32))<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Name of the =
Traffic=20
Tunnel.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Note that the name of a Tunnel must be=20
unique.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Note that the name of a Tunnel MUST be unique=20
across<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
all Tunnels on this=20
host.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
When a SET request contains a name that is=20
already<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
in use for another entry, then the=20
implementation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
must return an inconsistentValue error.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The value of this object cannot be changed if=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if the value of the corresponding=20
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
object is=20
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 2 =
}<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelSourceAddressType=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TeHopAddressType<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Traffic =
Engineered=20
Tunnel hop Address for the=20
source<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
this Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The type =
of the=20
Traffic Engineered Tunnel hop address=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
for the source this Tunnel.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The value of this object cannot be changed if=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if the value of the corresponding=20
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
object is=20
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 5 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelSourceAddress=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TeHopAddress<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Source =
Traffic=20
Engineered Tunnel hop Address of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
DESCRIPTION "Source Traffic Engineered Tunnel hop address=20
of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
this Tunnel.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The type of this address is determined by the=20
value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
of the corresponding teTunnelSourceAddressType.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Note that source and destination addresses of=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Tunnel can be different address types.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The value of this object cannot be changed if=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if the value of the corresponding=20
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
object is 'active'.</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 6 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelDestinationAddressType=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TeHopAddressType<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The type of =
Traffic=20
Engineered Tunnel hop Address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION=20
"The type of Traffic Engineered Tunnel hop=20
address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
for the destination of this Tunnel.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The value of this object cannot be changed if=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if the value of the corresponding=20
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
object is=20
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 7 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelDestinationAddress=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TeHopAddress<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Destination =
Traffic=20
Engineered Tunnel hop Address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DESCRIPTION=20
"Destination Traffic Engineered Tunnel hop=20
address<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
of this Tunnel.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The type of this address is determined by the=20
value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
of the corresponding teTunnelDestinationAddressType.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Note that source and destination addresses of=20
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Tunnel can be different address types.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
The value of this object cannot be changed if=20
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
if the value of the corresponding=20
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
object is=20
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 8 =
}<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelAge&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The age =
(i.e., time=20
from creation till now)=20
of<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
this Tunnel in hundredths of a =
second.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
DESCRIPTION "The age (i.e., time from creation of this conceptual=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
row till now) of this Tunnel in hundredths of a=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
second.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 15 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelTransitions=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Counter32<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The number of =
state=20
transitions (up -&gt; down=20
and<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
down -&gt; up) this Tunnel has =
undergone.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
DESCRIPTION "The number of operational state transitions=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
(up -&gt; down and down -&gt; up) this Tunnel=20
has<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
undergone.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 18 =
}</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelLastTransition=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The time in =

hundredths of a second since the=20
last<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
transition occurred on this=20
Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
operational state transition occurred on this=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Tunnel.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 19 =
}<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; teTunnelLastPathChange=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The time in =

hundredths of a secondsince the=20
last<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
change occurred on this=20
Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
path change occurred on this=20
Tunnel.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 21 =
}<BR></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; tePathRowStatus&nbsp;=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
RowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The status =
of this=20
conceptual row.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
When the value of this object is 'active',=20
then<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
the value of tePathName cannot be changed.&nbsp;=20
All<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
other writable may be changed; however,=20
these<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
changes may affect traffic going over the=20
TE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
other writable objects may be changed; however,=20
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
these changes may affect traffic going over the=20
TE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
tunnel, or require the path to be computed=20
and/or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
re-signalled.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { tePathEntry 3 =
}<BR></DIV>
<DIV>&nbsp;&nbsp; tePathBandwidth&nbsp;=20
OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32<BR># You could use =
the=20
MPLS TC MplsBitRate<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
UNITS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Kilobits per=20
second"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp;=20
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The =
configured=20
bandwidth for this=20
Tunnel,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
in units of thousands of bits per second=20
(Kbps).<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DEFVAL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {=20
0 }<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { tePathEntry 7 =
}<BR></DIV>
<DIV><BR>----- Original Message ----- <BR>From: "Jim Boyle"=20
&lt;jboyle@pdnets.com&gt;<BR>To: &lt;te-wg@ops.ietf.org&gt;<BR>Sent: =
Monday,=20
August 18, 2003 8:46 PM<BR>Subject: WG Last Call: =
draft-ietf-tewg-mib-05.txt=20
<BR><BR><BR>&gt; <BR>&gt; This message begins a WG last call for the =
TE-MIB,=20
<BR>&gt; <BR>&gt; draft-ietf-tewg-mib-05.txt<BR>&gt; <BR>&gt; The last =
call will=20
end 9/1/2003.<BR>&gt; <BR>&gt; Thanks,<BR>&gt; <BR>&gt; Jim<BR>&gt;=20
<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0167_01C368B7.72ED3D00--




From owner-te-wg@ops.ietf.org  Mon Aug 25 15:48:49 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12844
	for <tewg-archive@lists.ietf.org>; Mon, 25 Aug 2003 15:48:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19rNE1-0006QF-5m
	for te-wg-data@psg.com; Mon, 25 Aug 2003 19:42:01 +0000
Received: from [171.71.177.238] (helo=sj-core-5.cisco.com)
	by psg.com with esmtp (Exim 4.20)
	id 19rNDP-0006HC-V9
	for te-wg@ops.ietf.org; Mon, 25 Aug 2003 19:41:23 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62])
	by sj-core-5.cisco.com (8.12.9/8.12.6) with ESMTP id h7PJfKDr016292;
	Mon, 25 Aug 2003 12:41:20 -0700 (PDT)
Received: from tnadeauw2k02 (che-vpn-cluster-2-20.cisco.com [10.86.242.20])
	by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ABU81233;
	Mon, 25 Aug 2003 15:41:18 -0400 (EDT)
Reply-To: <tnadeau@cisco.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
To: "'Adrian Farrel'" <adrian@olddog.co.uk>,
        "'Kireeti Kompella'" <kireeti@juniper.net>
Cc: <te-wg@ops.ietf.org>
Subject: RE: WG Last Call: draft-ietf-tewg-mib-05.txt 
Date: Mon, 25 Aug 2003 15:41:18 -0400
Organization: Cisco Systems, inc.
Message-ID: <000101c36b40$da707d30$6501a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0002_01C36B1F.535EDD30"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
Importance: Normal
In-Reply-To: <017801c368af$7e6946e0$fc919ed9@Puppy>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-Spam-Status: No, hits=-15.9 required=5.0
	tests=BAYES_20,HTML_40_50,HTML_FONT_COLOR_BLUE,IN_REP_TO,
	      ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0002_01C36B1F.535EDD30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

-----Original Message-----
From: owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] On
Behalf Of Adrian Farrel
Sent: Friday, August 22, 2003 9:13 AM
To: 'Kireeti Kompella'
Cc: te-wg@ops.ietf.org
Subject: Re: WG Last Call: draft-ietf-tewg-mib-05.txt 


Kireeti,
Good job. 

A few comments embedded in the extracted text of the draft below. Mainly
typos.

But a couple of questions/issues first.
 
Cheers,
Adrian


  1. Could you explicitly clarify in the introduction that the MIB
applies
    only at the ingress of tunnels. That is that it cannot be used to
    monitor tunnels at transit nodes or at their egresses.
 
2. The introduction makes (correctly) much of the fact that the MIB
    module can be used to model and manage any tunnel. Yet when
    we get to teSignalingProto we discover that the options are only
    'other', rsvpte' and 'crldp'. This seems to make it very
MPLS-centric.
 
    I appreciate that 'other' covers a lot of possibilities, but aren't
there
    some other tunneling protocols/techniques you'd like to list here?
 
    In particular, I'd like to see 'none' added to the list to cover
statically
    configured (unsignaled) tunnels. 
 
TOM:     When the type is set to 'other' you should also note clearly
which
            objects in the table do and do not apply. The same for when
the type
            is set to 'mpls' or 'crldp'.
 
 
3. teNextPathIndex seems to be in contradiction with the indexes to
    tePathTable. 
 
    tePathTable has paths listed under the primary index of 
    teTunnelIndex so that you can find all of the paths for a given
    tunnel. The secondary index is tePathIndex and is described as
    being unique within the context of a tunnel. The use of 
    teNextPathIndex would give a tePathIndex value that was unique 
    across the whole table.
 
    Admitedly one of these statements is a subset of the other, but
    it is not immediately clear how you expect teNextPathIndex to be 
    used.

4.  Could you supply a means to enable/disable notifications?
     Something like...
     teNotificationEnable OBJECT-TYPE
        SYNTAX        TruthValue
        MAX-ACCESS    read-write
        STATUS        current
        DESCRIPTION
             "If this object is true, then it enables the generation of
notifications
              from this MIB module. Otherwise notifications are not
generated."
        DEFVAL { false }
        ::= { teMIBObjects 5 } 
 
TOM:    You should also provide a means by which to specify a
            rate of notifications that the device should not exceed per
            second.  This allows implementations that can do
notification
            throttling to have a convienent place to have this
configured. 



    --Tom




5. It is not clear (to me) how you activate a tunnel (i.e. cause it to
begin to be
    signaled). I presume you use are using the rowStatus transitions to
active
    event. Could you clarify this (and how to initiate tear-down) either
in the
    description of teTunnelEntry or in the descriptive text before the
MIB module
    definition.

Nits...
 
< 3. Overview of the MIB
> 3. Overview of the MIB Module
 
<   The Traffic Engineering MIB consists of four parts:
>   The Traffic Engineering MIB module consists of four parts:
      1) Traffic Engineering information;
      2) a table of Traffic Tunnels;
      3) a table of Paths that tunnels take;
      4) a table of Hops that make up a tunnel path.
 
<  The MIB also has statements for minimal and full compliance.
>  The MIB module also has statements for minimal and full compliance.
 
 
   teAdminGroupTable OBJECT-TYPE
       SYNTAX       SEQUENCE OF TeAdminGroupEntry
       MAX-ACCESS   not-accessible
       STATUS       current
       DESCRIPTION "A mapping of configured administrative groups.  Each
                    entry represents an Administrative Group, and
                    provides a name and index for the group.
                    Administrative groups are used to label links in the
                    Traffic Engineering topology in order to place
                    constraints (include and exclude) on Tunnel paths.
 
                    A groupName can only be linked to one group number.
                    The groupNumber is the number assigned to the
<                   administrative group which are used in constraints,
>                   administrative group which is used in constraints,
                    like tePathIncludeAny, tePathIncludeAll, etc.
                   "
       ::= { teInfo 9 }


 
   teTunnelIndex    OBJECT-TYPE
       SYNTAX       Unsigned32 (1..4294967295)
       MAX-ACCESS   not-accessible
       STATUS       current
       DESCRIPTION "A unique index that identifies a Tunnel.  This
                    index MUST be unique across Tunnels and interfaces
                    on this host.
# Unclear. Are you saying that a tunnel index must not have the same
value as
# an interface index? Or are you saying "MUST be unique across Tunnels
on all
# interfaces on this host"
                   "
       ::= { teTunnelEntry 1 }
 
   teTunnelName     OBJECT-TYPE
       SYNTAX       SnmpAdminString (SIZE (1..32))
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "Name of the Traffic Tunnel.
 
<                   Note that the name of a Tunnel must be unique.
>                   Note that the name of a Tunnel MUST be unique across
>                   all Tunnels on this host.
                    When a SET request contains a name that is already
                    in use for another entry, then the implementation
                    must return an inconsistentValue error.
 
                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::= { teTunnelEntry 2 }

 
   teTunnelSourceAddressType OBJECT-TYPE
       SYNTAX       TeHopAddressType
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Traffic Engineered Tunnel hop Address for the source
<                   this Tunnel.
>      DESCRIPTION "The type of the Traffic Engineered Tunnel hop
address 
>                   for the source this Tunnel.
 
                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::= { teTunnelEntry 5 }
 
   teTunnelSourceAddress OBJECT-TYPE
       SYNTAX       TeHopAddress
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Source Traffic Engineered Tunnel hop Address of
>      DESCRIPTION "Source Traffic Engineered Tunnel hop address of
                    this Tunnel.
 
                    The type of this address is determined by the value
                    of the corresponding teTunnelSourceAddressType.
 
                    Note that source and destination addresses of a
                    Tunnel can be different address types.
 
                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::= { teTunnelEntry 6 }
 
   teTunnelDestinationAddressType OBJECT-TYPE
       SYNTAX       TeHopAddressType
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "The type of Traffic Engineered Tunnel hop Address
>      DESCRIPTION "The type of Traffic Engineered Tunnel hop address
>                   for the destination of this Tunnel.
 
                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::= { teTunnelEntry 7 }
 
   teTunnelDestinationAddress OBJECT-TYPE
       SYNTAX       TeHopAddress
       MAX-ACCESS   read-create
       STATUS       current
<      DESCRIPTION "Destination Traffic Engineered Tunnel hop Address
>      DESCRIPTION "Destination Traffic Engineered Tunnel hop address
                    of this Tunnel.
 
                    The type of this address is determined by the value
                    of the corresponding teTunnelDestinationAddressType.
 
                    Note that source and destination addresses of a
                    Tunnel can be different address types.
 
                    The value of this object cannot be changed if the
                    if the value of the corresponding teTunnelRowStatus
                    object is 'active'.
                   "
       ::= { teTunnelEntry 8 }

 
   teTunnelAge      OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
<      DESCRIPTION "The age (i.e., time from creation till now) of
<                   this Tunnel in hundredths of a second.
>      DESCRIPTION "The age (i.e., time from creation of this conceptual

>                   row till now) of this Tunnel in hundredths of a 
>                   second.
                   "
       ::= { teTunnelEntry 15 }
 
 
   teTunnelTransitions OBJECT-TYPE
       SYNTAX       Counter32
       MAX-ACCESS   read-only
       STATUS       current
<      DESCRIPTION "The number of state transitions (up -> down and
<                   down -> up) this Tunnel has undergone.
>      DESCRIPTION "The number of operational state transitions 
>                   (up -> down and down -> up) this Tunnel has
>                   undergone.
                   "
       ::= { teTunnelEntry 18 }
 
   teTunnelLastTransition OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
       DESCRIPTION "The time in hundredths of a second since the last
<                   transition occurred on this Tunnel.
>                   operational state transition occurred on this 
>                   Tunnel.
                   "
       ::= { teTunnelEntry 19 }

 
   teTunnelLastPathChange OBJECT-TYPE
       SYNTAX       TimeTicks
       MAX-ACCESS   read-only
       STATUS       current
       DESCRIPTION "The time in hundredths of a secondsince the last
<                   change occurred on this Tunnel.
>                   path change occurred on this Tunnel.
                   "
       ::= { teTunnelEntry 21 }

 
   tePathRowStatus  OBJECT-TYPE
       SYNTAX       RowStatus
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "The status of this conceptual row.
 
                    When the value of this object is 'active', then
                    the value of tePathName cannot be changed.  All
<                   other writable may be changed; however, these
<                   changes may affect traffic going over the TE
>                   other writable objects may be changed; however, 
>                   these changes may affect traffic going over the TE
                    tunnel, or require the path to be computed and/or
                    re-signalled.
                   "
       ::= { tePathEntry 3 }

   tePathBandwidth  OBJECT-TYPE
       SYNTAX       Unsigned32
# You could use the MPLS TC MplsBitRate
       UNITS       "Kilobits per second"
       MAX-ACCESS   read-create
       STATUS       current
       DESCRIPTION "The configured bandwidth for this Tunnel,
                    in units of thousands of bits per second (Kbps).
                   "
       DEFVAL      { 0 }
       ::= { tePathEntry 7 }


----- Original Message ----- 
From: "Jim Boyle" <jboyle@pdnets.com>
To: <te-wg@ops.ietf.org>
Sent: Monday, August 18, 2003 8:46 PM
Subject: WG Last Call: draft-ietf-tewg-mib-05.txt 


> 
> This message begins a WG last call for the TE-MIB, 
> 
> draft-ietf-tewg-mib-05.txt
> 
> The last call will end 9/1/2003.
> 
> Thanks,
> 
> Jim
> 



------=_NextPart_000_0002_01C36B1F.535EDD30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff background=3D"">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] <B>On =
Behalf Of=20
  </B>Adrian Farrel<BR><B>Sent:</B> Friday, August 22, 2003 9:13=20
  AM<BR><B>To:</B> 'Kireeti Kompella'<BR><B>Cc:</B>=20
  te-wg@ops.ietf.org<BR><B>Subject:</B> Re: WG Last Call:=20
  draft-ietf-tewg-mib-05.txt <BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Kireeti,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Good job.&nbsp;<BR><BR>A few comments =
embedded in=20
  the extracted text of the draft below. Mainly typos.<BR><BR>But a =
couple of=20
  questions/issues first.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Cheers,</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Adrian</DIV>
  <DIV><BR><BR><SPAN class=3D685563819-25082003>&nbsp;&nbsp;</SPAN>1. =
Could you=20
  explicitly clarify in the introduction that the MIB=20
  applies<BR>&nbsp;&nbsp;&nbsp; only at the ingress of tunnels. That is =
that it=20
  cannot be used to</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; monitor tunnels at =
transit=20
  nodes or at their egresses.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>2. The introduction makes (correctly) =
much of the=20
  fact that the MIB</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; module can be used =
to model=20
  and manage any tunnel. Yet when</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; we get to =
teSignalingProto we=20
  discover that the options are only</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; 'other', rsvpte' =
and 'crldp'.=20
  This seems to make it very MPLS-centric.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I appreciate that =
'other'=20
  covers a lot of possibilities, but aren't there</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; some other =
tunneling=20
  protocols/techniques you'd like to list here?</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; In particular, I'd =
like to see=20
  'none' added to the list to cover statically</FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2>&nbsp;&nbsp;&nbsp; configured =
(unsignaled)=20
  tunnels.<SPAN class=3D685563819-25082003><FONT=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D685563819-25082003></SPAN></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D685563819-25082003>TOM:=20
  &nbsp;&nbsp;&nbsp; When the type is set to 'other' you should also =
note=20
  clearly which</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  =
class=3D685563819-25082003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  objects in the table do and do not apply. The same for when the=20
  type</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  =
class=3D685563819-25082003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;=20
  is set to 'mpls' or 'crldp'.</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20
  class=3D685563819-25082003>&nbsp;</SPAN></FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>3. teNextPathIndex seems to be in =
contradiction=20
  with the indexes to</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; tePathTable. =
</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; tePathTable has =
paths listed=20
  under the primary index&nbsp;of </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; teTunnelIndex so =
that you can=20
  find all of the paths for a given</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; tunnel. The =
secondary index is=20
  tePathIndex and is described as</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; being unique =
within the=20
  context of a tunnel. The use of </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; teNextPathIndex =
would give a=20
  tePathIndex value that was unique </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; across the whole=20
  table.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; Admitedly one of =
these=20
  statements is a subset of the other, but</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; it is not =
immediately clear=20
  how you expect teNextPathIndex to be </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; =
used.<BR><BR>4.&nbsp; Could=20
  you supply a means to enable/disable=20
  notifications?<BR>&nbsp;&nbsp;&nbsp;&nbsp; Something=20
  like...<BR>&nbsp;&nbsp;&nbsp;&nbsp; teNotificationEnable=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TruthValue<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
  MAX-ACCESS&nbsp;&nbsp;&nbsp; read-write<BR>&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;=20
  DESCRIPTION<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  &nbsp;&nbsp; "If this object is true, then it enables the generation =
of=20
  =
notifications<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
  from this MIB module. Otherwise notifications are not=20
  generated."<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; DEFVAL { false=20
  }<BR>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; ::=3D { teMIBObjects 5 =
}<SPAN=20
  class=3D685563819-25082003><FONT =
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D685563819-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D685563819-25082003><FONT=20
  color=3D#0000ff>TOM:&nbsp;&nbsp;&nbsp;&nbsp;You should also provide a =
means by=20
  which to specify a</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  =
class=3D685563819-25082003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;<FONT=20
  color=3D#0000ff>rate of notifications&nbsp;that the device =
should&nbsp;not=20
  exceed&nbsp;per</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  =
class=3D685563819-25082003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;<FONT=20
  color=3D#0000ff>second.&nbsp; This allows implementations that can do=20
  notification</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  =
class=3D685563819-25082003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;<FONT=20
  color=3D#0000ff>throttling to have a convienent place to have this=20
  configured.</FONT>&nbsp;</SPAN></FONT></DIV><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D685563819-25082003><FONT =
color=3D#0000ff></FONT></SPAN></FONT></BLOCKQUOTE>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px"><FONT><SPAN=20
  class=3D685563819-25082003></SPAN>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D685563819-25082003><FONT=20
  color=3D#0000ff>&nbsp;&nbsp;&nbsp; =
--Tom</FONT></SPAN></FONT></FONT></DIV><FONT=20
  face=3DArial><FONT size=3D2><SPAN class=3D685563819-25082003><FONT=20
  color=3D#0000ff></FONT></SPAN></FONT></FONT></FONT></BLOCKQUOTE>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px"><FONT><FONT=20
  face=3DArial><FONT size=3D2><SPAN class=3D685563819-25082003></SPAN>
  <DIV><BR></DIV></FONT></FONT></FONT>
  <DIV><FONT face=3DArial size=3D2>5. It is not clear (to me) how you =
activate a=20
  tunnel (i.e. cause it to begin to be</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; &nbsp;signaled). I =
presume you use=20
  are using the rowStatus transitions to active</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; event. Could you =
clarify this=20
  (and how to initiate tear-down) either in the</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; description of =
teTunnelEntry=20
  or in the descriptive text before the MIB module</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; =
definition.</FONT></DIV>
  <DIV><BR><FONT face=3DArial size=3D2>Nits...</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&lt; 3. Overview of the MIB<BR>&gt; =
3. Overview=20
  of the MIB Module</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&lt;&nbsp;&nbsp; The Traffic =
Engineering MIB=20
  consists of four parts:<BR>&gt;&nbsp;&nbsp; The Traffic Engineering =
MIB module=20
  consists of four parts:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1) Traffic=20
  Engineering information;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2) a table =
of=20
  Traffic Tunnels;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3) a table of Paths =
that=20
  tunnels take;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4) a table of Hops =
that make=20
  up a tunnel path.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&lt;&nbsp; The MIB also has =
statements for=20
  minimal and full compliance.<BR>&gt;&nbsp; The MIB module also has =
statements=20
  for minimal and full compliance.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; teAdminGroupTable=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SEQUENCE OF=20
  TeAdminGroupEntry<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  MAX-ACCESS&nbsp;&nbsp; =
not-accessible<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "A mapping =
of=20
  configured administrative groups.&nbsp;=20
  =
Each<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  entry represents an Administrative Group,=20
  =
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  provides a name and index for the=20
  =
group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Administrative groups are used to label links in=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Traffic Engineering topology in order to place</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  constraints (include and exclude) on Tunnel paths.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  A groupName can only be linked to one group=20
  =
number.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The groupNumber is the number assigned to=20
  =
the<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  administrative group which are used in=20
  =
constraints,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  administrative group which is used in=20
  =
constraints,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  like tePathIncludeAny, tePathIncludeAll,=20
  =
etc.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teInfo 9 =
}<BR></FONT></DIV>
  <DIV><BR><FONT face=3DArial size=3D2>&nbsp;</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
teTunnelIndex&nbsp;&nbsp;&nbsp;=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32=20
  (1..4294967295)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  not-accessible<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "A unique =
index=20
  that identifies a Tunnel.&nbsp;=20
  =
This<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  index MUST be unique across Tunnels and=20
  =
interfaces<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  on this host.<BR># Unclear. Are you saying that a tunnel index must =
not have=20
  the same value as<BR># an interface index? Or are you saying "MUST be =
unique=20
  across Tunnels on all<BR># interfaces on this=20
  =
host"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 1 =
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
teTunnelName&nbsp;&nbsp;&nbsp;&nbsp;=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SnmpAdminString (SIZE=20
  (1..32))<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Name of =
the=20
  Traffic Tunnel.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note that the name of a Tunnel must be=20
  =
unique.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note that the name of a Tunnel MUST be unique=20
  =
across<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  all Tunnels on this=20
  =
host.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  When a SET request contains a name that is=20
  =
already<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  in use for another entry, then the=20
  =
implementation<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  must return an inconsistentValue error.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The value of this object cannot be changed if=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  if the value of the corresponding=20
  =
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  object is=20
  =
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 2=20
  }<BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
teTunnelSourceAddressType=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TeHopAddressType<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  MAX-ACCESS&nbsp;&nbsp; =
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Traffic =
Engineered=20
  Tunnel hop Address for the=20
  =
source<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  this Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The =
type of=20
  the Traffic Engineered Tunnel hop address=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for the source this Tunnel.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The value of this object cannot be changed if=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  if the value of the corresponding=20
  =
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  object is=20
  =
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 5 =
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; teTunnelSourceAddress=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TeHopAddress<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Source =
Traffic=20
  Engineered Tunnel hop Address of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  DESCRIPTION "Source Traffic Engineered Tunnel hop address=20
  =
of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  this Tunnel.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The type of this address is determined by the=20
  =
value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  of the corresponding teTunnelSourceAddressType.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note that source and destination addresses of=20
  =
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Tunnel can be different address types.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The value of this object cannot be changed if=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  if the value of the corresponding=20
  =
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  object is 'active'.</FONT></DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 6 =
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
teTunnelDestinationAddressType=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TeHopAddressType<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  MAX-ACCESS&nbsp;&nbsp; =
read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The type of =
Traffic=20
  Engineered Tunnel hop Address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  DESCRIPTION "The type of Traffic Engineered Tunnel hop=20
  =
address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  for the destination of this Tunnel.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The value of this object cannot be changed if=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  if the value of the corresponding=20
  =
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  object is=20
  =
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 7 =
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; =
teTunnelDestinationAddress=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TeHopAddress<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "Destination =
Traffic=20
  Engineered Tunnel hop Address<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  DESCRIPTION "Destination Traffic Engineered Tunnel hop=20
  =
address<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  of this Tunnel.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The type of this address is determined by the=20
  =
value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  of the corresponding teTunnelDestinationAddressType.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Note that source and destination addresses of=20
  =
a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Tunnel can be different address types.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  The value of this object cannot be changed if=20
  =
the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  if the value of the corresponding=20
  =
teTunnelRowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  object is=20
  =
'active'.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 8=20
  }<BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;=20
  teTunnelAge&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The age =
(i.e., time=20
  from creation till now)=20
  =
of<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  this Tunnel in hundredths of a =
second.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  DESCRIPTION "The age (i.e., time from creation of this conceptual=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  row till now) of this Tunnel in hundredths of a=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
second.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 15=20
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; teTunnelTransitions=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Counter32<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The number =
of state=20
  transitions (up -&gt; down=20
  =
and<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  down -&gt; up) this Tunnel has=20
  undergone.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The =
number of=20
  operational state transitions=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  (up -&gt; down and down -&gt; up) this Tunnel=20
  =
has<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
undergone.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 18=20
}</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; teTunnelLastTransition=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The time =
in=20
  hundredths of a second since the=20
  =
last<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  transition occurred on this=20
  =
Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  operational state transition occurred on this=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Tunnel.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 19=20
  }<BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; teTunnelLastPathChange=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  TimeTicks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The time =
in=20
  hundredths of a secondsince the=20
  =
last<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  change occurred on this=20
  =
Tunnel.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  path change occurred on this=20
  =
Tunnel.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { teTunnelEntry 21=20
  }<BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; tePathRowStatus&nbsp;=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  RowStatus<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
MAX-ACCESS&nbsp;&nbsp;=20
  read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The =
status of=20
  this conceptual row.</FONT></DIV>
  <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  When the value of this object is 'active',=20
  =
then<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  the value of tePathName cannot be changed.&nbsp;=20
  =
All<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  other writable may be changed; however,=20
  =
these<BR>&lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  changes may affect traffic going over the=20
  =
TE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  other writable objects may be changed; however,=20
  =
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  these changes may affect traffic going over the=20
  =
TE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  tunnel, or require the path to be computed=20
  =
and/or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
re-signalled.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { tePathEntry 3=20
  }<BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; tePathBandwidth&nbsp;=20
  OBJECT-TYPE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SYNTAX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unsigned32<BR># You could =
use the=20
  MPLS TC MplsBitRate<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  UNITS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Kilobits per=20
  second"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAX-ACCESS&nbsp;&nbsp; =

  read-create<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  current<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESCRIPTION "The =
configured=20
  bandwidth for this=20
  =
Tunnel,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  in units of thousands of bits per second=20
  =
(Kbps).<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  "<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DEFVAL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  { 0 }<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ::=3D { tePathEntry 7=20
  }<BR></FONT></DIV>
  <DIV><BR><FONT face=3DArial size=3D2>----- Original Message ----- =
<BR>From: "Jim=20
  Boyle" &lt;jboyle@pdnets.com&gt;<BR>To: =
&lt;te-wg@ops.ietf.org&gt;<BR>Sent:=20
  Monday, August 18, 2003 8:46 PM<BR>Subject: WG Last Call:=20
  draft-ietf-tewg-mib-05.txt <BR><BR><BR>&gt; <BR>&gt; This message =
begins a WG=20
  last call for the TE-MIB, <BR>&gt; <BR>&gt; =
draft-ietf-tewg-mib-05.txt<BR>&gt;=20
  <BR>&gt; The last call will end 9/1/2003.<BR>&gt; <BR>&gt; =
Thanks,<BR>&gt;=20
  <BR>&gt; Jim<BR>&gt; <BR></FONT></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0002_01C36B1F.535EDD30--




From owner-te-wg@ops.ietf.org  Tue Aug 26 09:28:09 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03321
	for <tewg-archive@lists.ietf.org>; Tue, 26 Aug 2003 09:28:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19rdje-000FQu-6a
	for te-wg-data@psg.com; Tue, 26 Aug 2003 13:19:46 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.20)
	id 19rdjV-000FP3-2S
	for te-wg@ops.ietf.org; Tue, 26 Aug 2003 13:19:37 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 Aug 2003 15:18:47 +0200
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7QDHAHM004782
	for <te-wg@ops.ietf.org>; Tue, 26 Aug 2003 15:17:17 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 26 Aug 2003 15:19:28 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C36BD4.ACEEE222"
Subject: Relationship between "Shared Mesh Restoration" and DSTE Bandwidth Constraints Models
Date: Tue, 26 Aug 2003 14:19:27 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5330@xbe-lon-313.cisco.com>
Thread-Topic: Relationship between "Shared Mesh Restoration" and DSTE Bandwidth Constraints Models
Thread-Index: AcNr1KxuLfZotu5DSTWhKJo5I+Iq9g==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 26 Aug 2003 13:19:28.0283 (UTC) FILETIME=[AD651EB0:01C36BD4]
X-Spam-Status: No, hits=-2.4 required=5.0
	tests=BAYES_20,HTML_30_40
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C36BD4.ACEEE222
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
=20
We agreed in Vienna that the relationship between the Shared Mesh
Restoration mechanisms being developed in CCAMP and the DS-TE Bandwidth
Constraints Models needed to be investigated so we can decide "if there
is or is not an issue and if it needs to be addressed or not".
=20
In a nutshell (see [A] below for more details), our conclusions are
that:
    - Shared Mesh Restoration can work simultaneously with DS-TE.=20
    - Shared Mesh Restoration should operate independently within each
DS-TE Class-Type (and not across Class-Types).
    - Shared Mesh Restoration can work with RDM, MAM and MAR
=20
Thus, our proposal for moving ahead on this is:
    - make a wording change to the definition of "Reserved (CTc)" which
is used in the formulas for defining RDM, MAM and MAR so that the
formulas are compatible with how Shared-Mesh Restoration performs
bandwidth reservation/CAC (see [B] below for exact word change)
    - add a note in RDM, MAM and MAR specs that these BC Model
definitions are compatible with Shared Mesh Restoration with the
assumption that Shared Mesh Restoration operates independently within
each Class-Type.
=20
I would like to thank Yakov, Anna and JP for working with me on this
topic.
=20
Please let us know promptly if you have comments/issues with this.
=20
Thanks
=20
Francois
=20
=20
[A]
=3D=3D=3D
Shared Mesh Restoration is defined in
draft-ietf-ccamp-gmpls-recovery-functional-00.txt (see section 3.3).
=20
One key concept is that backup LSPs can share bandwidth as long as they
protect from failure of different resources (since signaling is used at
failure time to activate a particular pre-established backup LSP).
Because they can share bandwidth, it is clear that the total amount of
bandwidth actually *reserved* by the backup LSPs can be smaller than the
sum of the bandwidth *signaled* by each individual backup LSP.
=20
Another concept discussed in the context of Shared Mesh Restoration is
"Excess Traffic LSP" (altough I think this is not yet documented in the
current draft but will be added in upcoming one).  Excess Traffic LSPs
may be established (at a lower preemption priority) and use the
resources allocated (but not currently used) by backup LSPs (at higher
preemption priority). The idea being that these Excess Traffic LSPs will
get preempted as soon as resources are actually needed by some backup
LSPs. Since Excess Traffic LSPs "borrow" bandwidth from backup LSPs when
those don't need it, it is clear that the bandwidth actually "reserved*
collectively by backup LSPs and Excess Traffic LSPs is smaller than the
sum of the bandwidth *signaled* separately by backup LSPs and by Excess
Traffic LSPs.
=20
So a first conclusion is that the definition of "Reserved (CTc)" needs
to be ajusted to take into account the fact that the amount of bandwidth
actually reserved collectively by LSPs is not just a sum of bandwidth
reserved individually by all LSPs but rather that multiple LSPs may
share bandwidth resources and that what matters is the amount of
bandwidth *actually reserved" across the set of LSPs.
=20
=20
So now, how can Shared Mesh Restoration operate in conjunction with
DS-TE?
=20
We recommend that Shared Mesh Restoration operates only within each
Class-Type. This means that bandwidth sharing across Primary LSPs/Backup
LSPs and Excess Traffic LSPs only occurs within each given CT. In other
words, back up LSPs protecting Primary LSP of CTx are expected to also
belong to CTx. Similarly Excess Traffic LSPs sharing bandwidth with
Backup LSPs of CTx are expected to also belong to CTx.
=20
In this model, we can see that :
    - Shared Mesh Restoration model will define how much bandwidth is
actually collectively reserved by Primary LSPs + Backup LSPs + Excess
Traffic LSPs within a given Class-Type.
    - DS-TE Bandwidth Constraints Model defines the set of bandwidth
constraints applicable to the bandwidth collectively reserved by a given
CT.
    - the two models (ie Shared Mesh Restoration and BC Models) are
effectively orthogonal; ie the definitions of the Shared Mesh
Restoration concepts affect how one computes the amount of bandwidth
actually reserved by a given CT, but this does not affect/modify
which/how the bandwidth constraints apply to each CT. Thus, Shared Mesh
Restoration can operate simultaneously with DS-TE with RDM, MAM or MAR
BC models and these BC Models can be defined independently of eth
detailed concepts/rules of Shared Mesh Restoration.
=20
Note that, instead, one could conceive an extremely generic model for
how Shared Mesh Restoration operates with DS-TE whereby Shared Mesh
Restoration spans arbitrarily across Class-Types, for example where
Primary LSPs (or Excess Traffic LSPs) of one CT could share bandwidth
with backup LSPs of another CT. However, this does not seem to offer
significant real practical benefits while it introduces a significant
level of complexity. For a start, in such a model Sahred Mesh
Restoration and BC Models are no longer orthogonal and the definitions
of Shared Mesh Restoration concepts may affect how the bandwidth
constraints affect each CT. We concluded that the complexities of such a
generic model were not justified and not worth pursuing at this stage.
=20
=20
[B]
=3D=3D
Current definition is:
"Reserved (CTc)" is defined as the sum of the bandwidth  reserved by all
established LSPs which belong to CTc.=20
New Definition will be:
"Reserved (CTc)" is defined as the total amount of the bandwidth
reserved by all established LSPs which belong to CTc.=20
=20

------_=_NextPart_001_01C36BD4.ACEEE222
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY style=3D"COLOR: #000000; FONT-FAMILY: ">
<DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
size=3D2>Hello,</FONT></SPAN></DIV>
<DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D754245115-25082003><FONT face=3DArial size=3D2>We =
agreed in Vienna=20
that the relationship between the Shared Mesh Restoration mechanisms =
being=20
developed in CCAMP and the DS-TE Bandwidth Constraints Models needed to =
be=20
investigated so we can decide "if there is or is not an issue&nbsp;and =
if it=20
needs to be addressed or not".</FONT></SPAN></DIV>
<DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>In a =
nutshell (see=20
[A] below for more details), our conclusions&nbsp;are =
that:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
Shared Mesh Restoration&nbsp;can&nbsp;work simultaneously =
with&nbsp;DS-TE.=20
</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
Shared Mesh Restoration should operate independently within each DS-TE=20
Class-Type (and not across Class-Types).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;&nbsp;- Shared Mesh =
Restoration can=20
work with RDM, MAM and MAR</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>Thus, =
our proposal=20
for moving ahead on this is:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
make a wording change to the definition of "Reserved (CTc)" which is =
used in the=20
formulas for defining RDM, MAM and MAR so that the formulas are =
compatible with=20
how Shared-Mesh Restoration performs bandwidth reservation/CAC (see [B] =
below=20
for exact word change)</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
add a note&nbsp;in RDM, MAM and MAR specs that these BC Model =
definitions are=20
compatible with Shared Mesh&nbsp;Restoration with the assumption that =
Shared=20
Mesh Restoration operates independently within each=20
Class-Type.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>I =
would like to=20
thank Yakov, Anna and JP for working with me on this =
topic.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>Please =
let us know=20
promptly if you have comments/issues with this.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>Thanks</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>Francois</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>[A]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>=3D=3D=3D</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>Shared =
Mesh=20
Restoration is defined in =
draft-ietf-ccamp-gmpls-recovery-functional-00.txt (see=20
section 3.3).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>One =
key concept is=20
that backup LSPs can share bandwidth as long as they protect from =
failure of=20
different resources (since signaling is used at failure time to activate =
a=20
particular pre-established backup LSP). Because they can share =
bandwidth, it is=20
clear that the total amount of bandwidth actually *reserved* by the =
backup LSPs=20
can be smaller than the sum of the bandwidth *signaled* by each =
individual=20
backup LSP.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>Another concept=20
discussed in the context of&nbsp;Shared Mesh Restoration is "Excess =
Traffic LSP"=20
(altough I think this is not yet documented in the current draft but =
will be=20
added in upcoming one).<FONT size=3D2>&nbsp; Excess Traffic LSPs may be=20
established (at a lower preemption priority) and use the resources =
allocated=20
(but not currently used) by backup LSPs (at higher preemption priority). =
The=20
idea being that&nbsp;these Excess Traffic LSPs will get preempted as =
soon as=20
resources are actually needed&nbsp;by some backup LSPs. Since Excess =
Traffic=20
LSPs "borrow" bandwidth from backup LSPs when those don't need it, it is =
clear=20
that the bandwidth actually "reserved* collectively by backup LSPs and =
Excess=20
Traffic LSPs is smaller than the sum of the bandwidth *signaled* =
separately by=20
backup LSPs and by Excess Traffic LSPs.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>So a =
first=20
conclusion is that&nbsp;the definition of "Reserved (CTc)" needs to be =
ajusted=20
to take into account the fact that the amount of bandwidth actually =
reserved=20
collectively by LSPs is not just a sum of bandwidth reserved =
individually by all=20
LSPs but rather that&nbsp;multiple LSPs may share bandwidth resources =
and that=20
what matters is the amount of bandwidth *actually reserved" across the =
set of=20
LSPs.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>So =
now, how=20
can&nbsp;</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>Shared Mesh Restoration operate&nbsp;in =
conjunction=20
with&nbsp;DS-TE?</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003></SPAN></FONT><FONT=20
face=3DArial size=3D2><SPAN =
class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial=20
size=3D2><SPAN class=3D754245115-25082003></SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN class=3D754245115-25082003></SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN class=3D754245115-25082003></SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>We =
recommend that=20
Shared Mesh Restoration operates only within each Class-Type. This means =
that=20
bandwidth sharing across Primary LSPs/Backup LSPs and Excess Traffic =
LSPs only=20
occurs within each given CT. In other words, back up =
LSPs&nbsp;protecting=20
Primary LSP of CTx are expected to also belong to CTx. Similarly Excess =
Traffic=20
LSPs sharing bandwidth with Backup LSPs of CTx are expected to also =
belong to=20
CTx.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>In =
this model, we=20
can see that :</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
Shared Mesh Restoration model will define how much bandwidth is actually =

collectively reserved by Primary LSPs + Backup LSPs + Excess Traffic=20
LSPs&nbsp;within a given Class-Type.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
DS-TE Bandwidth Constraints Model defines the set of bandwidth =
constraints=20
applicable to the bandwidth collectively reserved by a given=20
CT.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp; -=20
the two models (ie Shared Mesh Restoration and BC Models) are =
effectively=20
orthogonal; ie the definitions of the Shared Mesh Restoration concepts =
affect=20
how one computes the amount of bandwidth actually reserved by a given =
CT, but=20
this does not affect/modify which/how the bandwidth constraints apply to =
each=20
CT. Thus, Shared Mesh Restoration can operate simultaneously with DS-TE =
with=20
RDM, MAM or MAR BC models and these BC Models can be defined =
independently of=20
eth detailed concepts/rules of Shared Mesh =
Restoration.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>Note =
that,=20
instead,&nbsp;one could conceive an extremely generic model for how =
Shared Mesh=20
Restoration operates with DS-TE whereby Shared Mesh Restoration spans=20
arbitrarily&nbsp;across Class-Types,&nbsp;for example where Primary LSPs =
(or=20
Excess Traffic LSPs) of one CT could share bandwidth with backup LSPs of =
another=20
CT. However, this does not seem to offer significant real practical =
benefits=20
while it introduces a significant level of complexity. For a start, in =
such a=20
model Sahred Mesh Restoration and BC Models are no longer orthogonal and =
the=20
definitions of Shared Mesh Restoration concepts&nbsp;may affect how the=20
bandwidth constraints&nbsp;affect each CT. We concluded that the =
complexities of=20
such&nbsp;a generic model were not justified and not worth pursuing at =
this=20
stage.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>[B]</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D754245115-25082003>=3D=3D</SPAN></FONT></DIV>
<DIV><SPAN class=3D754245115-25082003>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D754245115-25082003>Current=20
definition is:</SPAN></FONT></FONT></DIV>
<DIV><SPAN class=3D754245115-25082003></SPAN><FONT face=3DArial =
size=3D2>"Reserved=20
(CTc)" is defined as the sum of the bandwidth&nbsp;<SPAN=20
class=3D754245115-25082003>&nbsp;</SPAN>reserved by&nbsp;al<SPAN=20
class=3D754245115-25082003>l</SPAN> established LSPs which belong to =
CTc.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>New =
Definition will=20
be:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003><SPAN=20
class=3D754245115-25082003></SPAN>"Reserved (CTc)" is defined as the =
total amount=20
of the bandwidth reserved by&nbsp;<FONT face=3DArial size=3D2>all =
established LSPs=20
which belong to CTc. </FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial =
size=3D2></FONT>&nbsp;</DIV></SPAN></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C36BD4.ACEEE222--



From owner-te-wg@ops.ietf.org  Wed Aug 27 04:28:48 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05924
	for <tewg-archive@lists.ietf.org>; Wed, 27 Aug 2003 04:28:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.22)
	id 19rvVP-0003PG-GU
	for te-wg-data@psg.com; Wed, 27 Aug 2003 08:18:15 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.22)
	id 19rvUs-0002nV-Qx
	for te-wg@ops.ietf.org; Wed, 27 Aug 2003 08:17:42 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 27 Aug 2003 10:16:52 +0200
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7R8FMBG018306
	for <te-wg@ops.ietf.org>; Wed, 27 Aug 2003 10:15:23 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 27 Aug 2003 10:17:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C36C73.AE6C6DAA"
Subject: FW: Relationship between "Shared Mesh Restoration" and DSTE Bandwidth Constraints Models
Date: Wed, 27 Aug 2003 09:17:39 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D9E43A67@xbe-lon-313.cisco.com>
Thread-Topic: Relationship between "Shared Mesh Restoration" and DSTE Bandwidth Constraints Models
Thread-Index: AcNr1KxuLfZotu5DSTWhKJo5I+Iq9gAntsPw
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
Cc: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 27 Aug 2003 08:17:40.0572 (UTC) FILETIME=[AEC571C0:01C36C73]
X-Spam-Status: No, hits=-1.9 required=5.0
	tests=BAYES_20,HTML_30_40,HTML_FONT_COLOR_BLUE
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C36C73.AE6C6DAA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Just a resend (seems like it didn't go through the first time).
Francois

	-----Original Message-----
	From: Francois Le Faucheur (flefauch)=20
	Sent: 26 August 2003 15:19
	To: te-wg@ops.ietf.org
	Subject: Relationship between "Shared Mesh Restoration" and DSTE
Bandwidth Constraints Models
=09
=09
	Hello,
	=20
	We agreed in Vienna that the relationship between the Shared
Mesh Restoration mechanisms being developed in CCAMP and the DS-TE
Bandwidth Constraints Models needed to be investigated so we can decide
"if there is or is not an issue and if it needs to be addressed or not".
	=20
	In a nutshell (see [A] below for more details), our conclusions
are that:
	    - Shared Mesh Restoration can work simultaneously with
DS-TE.=20
	    - Shared Mesh Restoration should operate independently
within each DS-TE Class-Type (and not across Class-Types).
	    - Shared Mesh Restoration can work with RDM, MAM and MAR
	=20
	Thus, our proposal for moving ahead on this is:
	    - make a wording change to the definition of "Reserved
(CTc)" which is used in the formulas for defining RDM, MAM and MAR so
that the formulas are compatible with how Shared-Mesh Restoration
performs bandwidth reservation/CAC (see [B] below for exact word change)
	    - add a note in RDM, MAM and MAR specs that these BC Model
definitions are compatible with Shared Mesh Restoration with the
assumption that Shared Mesh Restoration operates independently within
each Class-Type.
	=20
	I would like to thank Yakov, Anna and JP for working with me on
this topic.
	=20
	Please let us know promptly if you have comments/issues with
this.
	=20
	Thanks
	=20
	Francois
	=20
	=20
	[A]
	=3D=3D=3D
	Shared Mesh Restoration is defined in
draft-ietf-ccamp-gmpls-recovery-functional-00.txt (see section 3.3).
	=20
	One key concept is that backup LSPs can share bandwidth as long
as they protect from failure of different resources (since signaling is
used at failure time to activate a particular pre-established backup
LSP). Because they can share bandwidth, it is clear that the total
amount of bandwidth actually *reserved* by the backup LSPs can be
smaller than the sum of the bandwidth *signaled* by each individual
backup LSP.
	=20
	Another concept discussed in the context of Shared Mesh
Restoration is "Excess Traffic LSP" (altough I think this is not yet
documented in the current draft but will be added in upcoming one).
Excess Traffic LSPs may be established (at a lower preemption priority)
and use the resources allocated (but not currently used) by backup LSPs
(at higher preemption priority). The idea being that these Excess
Traffic LSPs will get preempted as soon as resources are actually needed
by some backup LSPs. Since Excess Traffic LSPs "borrow" bandwidth from
backup LSPs when those don't need it, it is clear that the bandwidth
actually "reserved* collectively by backup LSPs and Excess Traffic LSPs
is smaller than the sum of the bandwidth *signaled* separately by backup
LSPs and by Excess Traffic LSPs.
	=20
	So a first conclusion is that the definition of "Reserved (CTc)"
needs to be ajusted to take into account the fact that the amount of
bandwidth actually reserved collectively by LSPs is not just a sum of
bandwidth reserved individually by all LSPs but rather that multiple
LSPs may share bandwidth resources and that what matters is the amount
of bandwidth *actually reserved" across the set of LSPs.
	=20
	=20
	So now, how can Shared Mesh Restoration operate in conjunction
with DS-TE?
	=20
	We recommend that Shared Mesh Restoration operates only within
each Class-Type. This means that bandwidth sharing across Primary
LSPs/Backup LSPs and Excess Traffic LSPs only occurs within each given
CT. In other words, back up LSPs protecting Primary LSP of CTx are
expected to also belong to CTx. Similarly Excess Traffic LSPs sharing
bandwidth with Backup LSPs of CTx are expected to also belong to CTx.
	=20
	In this model, we can see that :
	    - Shared Mesh Restoration model will define how much
bandwidth is actually collectively reserved by Primary LSPs + Backup
LSPs + Excess Traffic LSPs within a given Class-Type.
	    - DS-TE Bandwidth Constraints Model defines the set of
bandwidth constraints applicable to the bandwidth collectively reserved
by a given CT.
	    - the two models (ie Shared Mesh Restoration and BC Models)
are effectively orthogonal; ie the definitions of the Shared Mesh
Restoration concepts affect how one computes the amount of bandwidth
actually reserved by a given CT, but this does not affect/modify
which/how the bandwidth constraints apply to each CT. Thus, Shared Mesh
Restoration can operate simultaneously with DS-TE with RDM, MAM or MAR
BC models and these BC Models can be defined independently of eth
detailed concepts/rules of Shared Mesh Restoration.
	=20
	Note that, instead, one could conceive an extremely generic
model for how Shared Mesh Restoration operates with DS-TE whereby Shared
Mesh Restoration spans arbitrarily across Class-Types, for example where
Primary LSPs (or Excess Traffic LSPs) of one CT could share bandwidth
with backup LSPs of another CT. However, this does not seem to offer
significant real practical benefits while it introduces a significant
level of complexity. For a start, in such a model Sahred Mesh
Restoration and BC Models are no longer orthogonal and the definitions
of Shared Mesh Restoration concepts may affect how the bandwidth
constraints affect each CT. We concluded that the complexities of such a
generic model were not justified and not worth pursuing at this stage.
	=20
	=20
	[B]
	=3D=3D
=09
	Current definition is:
	"Reserved (CTc)" is defined as the sum of the bandwidth
reserved by all established LSPs which belong to CTc.=20
	New Definition will be:
	"Reserved (CTc)" is defined as the total amount of the bandwidth
reserved by all established LSPs which belong to CTc.=20
	=20


------_=_NextPart_001_01C36C73.AE6C6DAA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY style=3D"COLOR: #000000; FONT-FAMILY: ">
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D678341608-27082003>Just a=20
resend (seems like it didn't go through the first =
time).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D678341608-27082003>Francois</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Francois Le=20
  Faucheur (flefauch) <BR><B>Sent:</B> 26 August 2003 =
15:19<BR><B>To:</B>=20
  te-wg@ops.ietf.org<BR><B>Subject:</B> Relationship between "Shared =
Mesh=20
  Restoration" and DSTE Bandwidth Constraints =
Models<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
  size=3D2>Hello,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D754245115-25082003><FONT face=3DArial size=3D2>We =
agreed in=20
  Vienna that the relationship between the Shared Mesh Restoration =
mechanisms=20
  being developed in CCAMP and the DS-TE Bandwidth Constraints Models =
needed to=20
  be investigated so we can decide "if there is or is not an =
issue&nbsp;and if=20
  it needs to be addressed or not".</FONT></SPAN></DIV>
  <DIV><SPAN class=3D754245115-25082003><FONT face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>In a =
nutshell (see=20
  [A] below for more details), our conclusions&nbsp;are=20
that:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - Shared Mesh Restoration&nbsp;can&nbsp;work simultaneously =
with&nbsp;DS-TE.=20
  </SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - Shared Mesh Restoration should operate independently within each =
DS-TE=20
  Class-Type (and not across Class-Types).</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;&nbsp;- Shared Mesh =
Restoration can=20
  work with RDM, MAM and MAR</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>Thus, our proposal=20
  for moving ahead on this is:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - make a wording change to the definition of "Reserved (CTc)" which is =
used in=20
  the formulas for defining RDM, MAM and MAR so that the formulas are =
compatible=20
  with how Shared-Mesh Restoration performs bandwidth reservation/CAC =
(see [B]=20
  below for exact word change)</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - add a note&nbsp;in RDM, MAM and MAR specs that these BC Model =
definitions=20
  are compatible with Shared Mesh&nbsp;Restoration with the assumption =
that=20
  Shared Mesh Restoration operates independently within each=20
  Class-Type.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>I =
would like to=20
  thank Yakov, Anna and JP for working with me on this=20
topic.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>Please let us know=20
  promptly if you have comments/issues with this.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>Thanks</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>Francois</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>[A]</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>=3D=3D=3D</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>Shared Mesh=20
  Restoration is defined in =
draft-ietf-ccamp-gmpls-recovery-functional-00.txt=20
  (see section 3.3).</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>One =
key concept is=20
  that backup LSPs can share bandwidth as long as they protect from =
failure of=20
  different resources (since signaling is used at failure time to =
activate a=20
  particular pre-established backup LSP). Because they can share =
bandwidth, it=20
  is clear that the total amount of bandwidth actually *reserved* by the =
backup=20
  LSPs can be smaller than the sum of the bandwidth *signaled* by each=20
  individual backup LSP.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>Another concept=20
  discussed in the context of&nbsp;Shared Mesh Restoration is "Excess =
Traffic=20
  LSP" (altough I think this is not yet documented in the current draft =
but will=20
  be added in upcoming one).<FONT size=3D2>&nbsp; Excess Traffic LSPs =
may be=20
  established (at a lower preemption priority) and use the resources =
allocated=20
  (but not currently used) by backup LSPs (at higher preemption =
priority). The=20
  idea being that&nbsp;these Excess Traffic LSPs will get preempted as =
soon as=20
  resources are actually needed&nbsp;by some backup LSPs. Since Excess =
Traffic=20
  LSPs "borrow" bandwidth from backup LSPs when those don't need it, it =
is clear=20
  that the bandwidth actually "reserved* collectively by backup LSPs and =
Excess=20
  Traffic LSPs is smaller than the sum of the bandwidth *signaled* =
separately by=20
  backup LSPs and by Excess Traffic LSPs.</FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>So a =
first=20
  conclusion is that&nbsp;the definition of "Reserved (CTc)" needs to be =
ajusted=20
  to take into account the fact that the amount of bandwidth actually =
reserved=20
  collectively by LSPs is not just a sum of bandwidth reserved =
individually by=20
  all LSPs but rather that&nbsp;multiple LSPs may share bandwidth =
resources and=20
  that what matters is the amount of bandwidth *actually reserved" =
across the=20
  set of LSPs.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>So =
now, how=20
  can&nbsp;</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>Shared Mesh Restoration operate&nbsp;in =
conjunction=20
  with&nbsp;DS-TE?</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>We =
recommend that=20
  Shared Mesh Restoration operates only within each Class-Type. This =
means that=20
  bandwidth sharing across Primary LSPs/Backup LSPs and Excess Traffic =
LSPs only=20
  occurs within each given CT. In other words, back up =
LSPs&nbsp;protecting=20
  Primary LSP of CTx are expected to also belong to CTx. Similarly =
Excess=20
  Traffic LSPs sharing bandwidth with Backup LSPs of CTx are expected to =
also=20
  belong to CTx.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>In =
this model, we=20
  can see that :</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - Shared Mesh Restoration model will define how much bandwidth is =
actually=20
  collectively reserved by Primary LSPs + Backup LSPs + Excess Traffic=20
  LSPs&nbsp;within a given Class-Type.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - DS-TE Bandwidth Constraints Model defines the set of bandwidth =
constraints=20
  applicable to the bandwidth collectively reserved by a given=20
  CT.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003>&nbsp;&nbsp;&nbsp;=20
  - the two models (ie Shared Mesh Restoration and BC Models) are =
effectively=20
  orthogonal; ie the definitions of the Shared Mesh Restoration concepts =
affect=20
  how one computes the amount of bandwidth actually reserved by a given =
CT, but=20
  this does not affect/modify which/how the bandwidth constraints apply =
to each=20
  CT. Thus, Shared Mesh Restoration can operate simultaneously with =
DS-TE with=20
  RDM, MAM or MAR BC models and these BC Models can be defined =
independently of=20
  eth detailed concepts/rules of Shared Mesh =
Restoration.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>Note =
that,=20
  instead,&nbsp;one could conceive an extremely generic model for how =
Shared=20
  Mesh Restoration operates with DS-TE whereby Shared Mesh Restoration =
spans=20
  arbitrarily&nbsp;across Class-Types,&nbsp;for example where Primary =
LSPs (or=20
  Excess Traffic LSPs) of one CT could share bandwidth with backup LSPs =
of=20
  another CT. However, this does not seem to offer significant real =
practical=20
  benefits while it introduces a significant level of complexity. For a =
start,=20
  in such a model Sahred Mesh Restoration and BC Models are no longer =
orthogonal=20
  and the definitions of Shared Mesh Restoration concepts&nbsp;may =
affect how=20
  the bandwidth constraints&nbsp;affect each CT. We concluded that the=20
  complexities of such&nbsp;a generic model were not justified and not =
worth=20
  pursuing at this stage.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>[B]</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN=20
  class=3D754245115-25082003>=3D=3D</SPAN></FONT></DIV>
  <DIV><SPAN class=3D754245115-25082003>
  <DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D754245115-25082003>Current=20
  definition is:</SPAN></FONT></FONT></DIV>
  <DIV><SPAN class=3D754245115-25082003></SPAN><FONT face=3DArial =
size=3D2>"Reserved=20
  (CTc)" is defined as the sum of the bandwidth&nbsp;<SPAN=20
  class=3D754245115-25082003>&nbsp;</SPAN>reserved by&nbsp;al<SPAN=20
  class=3D754245115-25082003>l</SPAN> established LSPs which belong to =
CTc.=20
  </FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN class=3D754245115-25082003>New =
Definition=20
  will be:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><SPAN =
class=3D754245115-25082003><SPAN=20
  class=3D754245115-25082003></SPAN>"Reserved (CTc)" is defined as the =
total=20
  amount of the bandwidth reserved by&nbsp;<FONT face=3DArial =
size=3D2>all=20
  established LSPs which belong to CTc. </FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial=20
size=3D2></FONT>&nbsp;</DIV></SPAN></DIV></BLOCKQUOTE></BODY></HTML>
=00
------_=_NextPart_001_01C36C73.AE6C6DAA--



From owner-te-wg@ops.ietf.org  Wed Aug 27 09:03:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23749
	for <tewg-archive@lists.ietf.org>; Wed, 27 Aug 2003 09:03:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.22)
	id 19rzou-00012e-Lr
	for te-wg-data@psg.com; Wed, 27 Aug 2003 12:54:40 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.22)
	id 19rzoP-000107-9h
	for te-wg@ops.ietf.org; Wed, 27 Aug 2003 12:54:09 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 27 Aug 2003 14:53:18 +0200
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h7RCpl2n020108;
	Wed, 27 Aug 2003 14:51:49 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 27 Aug 2003 14:53:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: How to progress DSTE, particularly p -> TE-Class[i] = {CT, p}
Date: Wed, 27 Aug 2003 13:53:58 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5337@xbe-lon-313.cisco.com>
Thread-Topic: How to progress DSTE, particularly p -> TE-Class[i] = {CT, p}
Thread-Index: AcNmEgxYvYD3dQPkSNCp4mSMDgVlNgGhEipA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 27 Aug 2003 12:53:59.0194 (UTC) FILETIME=[486667A0:01C36C9A]
X-Spam-Status: No, hits=-3.0 required=5.0
	tests=BAYES_20,QUOTED_EMAIL_TEXT
	version=2.55
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Jim and all,

I favor approach 2). Specifically, this separate document would make the
necessary generalisation to cover Link Bundles and FA-LSPs.
One of the benefits I can see in that approach is that we can be more
explicit about exactly how DS-TE works in the context of Link Bundles
and in the context of FA-LSP. It would make it very clear exactly where
DS-TE has an impact on each of Link-Bundling and FA-LSP and how it will
work.
Also, it would allow us to address details which are specific to the
DS-TE-over-Bundle or DSTE-over-FA-LSP and would not be captured by
generalisation statements a la "p is mapped to TE-class[i]". For
example, the lsp-hierarchy draft defines how the Traffic Engineering
parameters of a FA-LSP are derived including the Unreserved Bandwdith
and the Max Reservable bandwidth. Where DS-TE runs over the FA-LSP, it
may be that the natural behaviour would no longer be to set all intial
Unreserved Bw values to the FA-LSP bandwidth, but rather to set to zero
all those that relate to TE-classes whose CT is different to the FA-LSP
CT. Similarly, there is a question as to how you select the BC values
over an FA-LSP (for example assuming RDM, perhaps it should be that, if
FA-LSP belongs to CTn, then BCm=3D<FA-LSP Bandwidth> if m<=3Dn, and =
BCm=3D0 if
m>n ). These rules are open to discussion of course and they may not be
the right ones, I don't know yet, but there are just examples of things
which are specific to DSTE operations over FA-LSP and that we may want
to think about and specify.
Another benefit of course, is that we can finalise DS-TE proto without
any further delays.

If we were to go with approach 1), we would also need some words to
capture the other dimension of the generalisation, which is that
references to "Max Reservable Banwdith" should be mapped to "<Max
Reservable Bw, BCs>"

I agree 3) is not very viable.

Cheers

Francois

>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com]=20
>> Sent: 19 August 2003 07:03
>> To: te-wg@ops.ietf.org
>> Subject: How to progress DSTE, particularly p -> TE-Class[i]=20
>> =3D {CT, p}
>>=20
>>=20
>>=20
>> One issue that draft-sivabalan-diff-te-bundling-02.txt=20
>> highlights is that=20
>> there may be text in existing RFCs and I-Ds for MPLS/TE=20
>> which address how=20
>> to support priority preemption between LSPs. =20
>>=20
>> draft-ietf-tewg-diff-te-proto-04.txt redefines the=20
>> reservable bandwidth=20
>> available at priority "p" to be the reservable bandwidth=20
>> available for=20
>> TE-Class "i" where that is defined as:
>>=20
>>      TE-Class[i]  <-->  < CTc , preemption p > =20
>>=20
>> Where this mapping is defined locally.
>>=20
>> This creates a problem, as improvements to the base of MPLS, for
>> instance bundled links refer to how to address the=20
>> particulars of that
>> improvement with regards to priority, would also likely beof use e
>> might want to in a diff-serv TE environment as well.
>>=20
>> It is obvious that one should assume that where one reads=20
>> about "p" they=20
>> should be thinking TE-Class[i], however it would be best for=20
>> this to be=20
>> explicitly stated somewhere.
>>=20
>> Before the DSTE proto draft and the BC models progress to WG=20
>> last call,=20
>> I'd like to see this resolved.
>>=20
>> There are 3 approaches that I've heard suggested.
>>=20
>> 1) Address this in the diff-te-proto draft. State that for=20
>> the IGP and
>> RSVP RFCs, as well as technologies that improve upon them
>> (e.g. FA-LSP, link bundling, etc..), in order to be diff-serv TE
>> compliant, you need to map all references of "p" to TE-Class[i]
>>=20
>> 2) Address this in a parallel document to diff-te-proto, and let=20
>> diff-te-proto progress to IESG before this is resolved. =20
>> This parallel=20
>> document will somehow generalize "p" in base documents, and=20
>> diff-te-proto=20
>> will fit on-top of that (somehow)
>>=20
>> 3) Generalize "p" in the base documents, RFC3209, the=20
>> igp-traffic drafts,=20
>> all of the other MPLS/TE and GMPLS drafts as well.  For the=20
>> record, I am=20
>> not personally in favor of this approach.
>>=20
>> Please advise how you propose we move forward with this,
>>=20
>> thanks,
>>=20
>> Jim
>>=20
>>=20
>>=20



