Prabakaran T Sampath | 1 Feb 2004 16:23

FW: MPLS individual draft submission - MPLS WG - RSVP Hello State machine

Dear MPLS-WG,

We are sending the draft which is posted to IETF, seems to me it was
not published.  we are sending this to MPLS-WG whomever finds it helpful
please make use of it, if someone find comments please let us know.

Thanks in advance,

Best regards,
Prabakaran T.S.
Arumugam R.
Future Software Limited,
480-481, Anna Salai,
Chennai - 600035, India.
Off Phone: +91-44-24330550

 -----Original Message-----
From: 	Prabakaran T Sampath [mailto:prabakarts <at> future.futsoft.com]
Sent:	Wednesday, 22 October 2003 10:51 PM
To:	'internet-drafts <at> ietf.org'; 'swallow <at> cisco.com'; 'loa <at> pi.se';
'fenner <at> research.att.com'; 'zinin <at> psg.com'
Cc:
Subject:	MPLS individual draft submission - MPLS WG

Dear IETF Secretariat, MPLS chairs,

We submit an Internet-Draft:

	Title		: RSVP Hello State machine
	Author(s)	: Arumugam R, Prabakaran T.S
(Continue reading)

Martin Dubuc | 1 Feb 2004 19:55
Favicon

Re: DT's review of draft-ietf-mpls-telink-mib-05.txt

Dave,

I have updated the TE link MIB according to your comments and comments from
Bert sent on Janaury 29, 2004 on MPLS mailing list. I have submitted the new
version, draft-ietf-mpls-telink-mib-06.txt, to IETF Web site.

Here is a summary of changes:

To address your concerns:
- I have added an Applicability of ifRcvAddressTable section.

To address Bert's comments:
- I have changed all TE-LINK-MIB references to TE-LINK-STD-MIB.
- I have changed the TeLinkBandwidth textual convention to be an OCTET
STRING (SIZE(4)). I have removed the DISPLAY-HINT clause. I have replaced
reference to 32 bit with 4 octet IEEE floating.
- I have added justification for use of 0 and 1 for
TeLinkSdhSonetIndication.
- I have updated the author list for the [LMP] and [GMPLS-ARCH] references.

Some more comments on your message:
- I have not added any text regarding special conditions of the media
concerning the inclusion of framing characters regarding ifXXXOctets
counters because there aren't any specific to TE link interfaces. As
specified in last paragraph of Section 8.1, the values of the ifXXXOctets
fields are the aggregation of the values of ifXXXOctets of all interfaces
that are contained by a TE link.

- ifRcvAddressTable is not applicable to TE link MIB because TE link
interfaces are logical interfaces. They are not associated with any
(Continue reading)

Panita Pongpaibool | 2 Feb 2004 18:27
Picon

MPLS-LSR-MIB

Hi

I'm new to this list. I hope my questions is appropriate.

I'm looking at draft-ietf-mpls-lsr-mib-14.txt. I wonder if any vendors
support the the in-segment/out-segment performance table (i.e.,
mplsInSegmentPerfTable and mplsOutSegmentPerfTable).

On Cisco website, it says that these tables are supported in their IOS
software. But when I go to manuals for specific router models (7300, 7600,
10000 series), I found that they don't have the hardware support.

So I wonder if these MIBs are supported by other vendors. If so, do
carriers really use/monitor them? Or they just turn these MIBs off?

Thank you for your help.
Panita

kurien_joseph | 2 Feb 2004 18:43
Favicon

RE: MPLS-LSR-MIB

I know for sure, Cisco supports it from IOS 12.x.(not sure about the specifics)
I have 3600 routers that support these tables.(I would assume 7200 and above with the right IOS will have
these tables)

-Kurien.

-----Original Message-----
From: owner-mpls <at> UU.NET [mailto:owner-mpls <at> UU.NET]On Behalf Of Panita
Pongpaibool
Sent: Monday, February 02, 2004 9:28 AM
To: mpls <at> UU.NET
Subject: MPLS-LSR-MIB 

Hi

I'm new to this list. I hope my questions is appropriate.

I'm looking at draft-ietf-mpls-lsr-mib-14.txt. I wonder if any vendors
support the the in-segment/out-segment performance table (i.e.,
mplsInSegmentPerfTable and mplsOutSegmentPerfTable).

On Cisco website, it says that these tables are supported in their IOS
software. But when I go to manuals for specific router models (7300, 7600,
10000 series), I found that they don't have the hardware support.

So I wonder if these MIBs are supported by other vendors. If so, do
carriers really use/monitor them? Or they just turn these MIBs off?

Thank you for your help.
Panita
(Continue reading)

W. Mark Townsley | 2 Feb 2004 21:26
Picon
Favicon

MPLS over L2TPv3 encap for RFC 2547 VPNs


Based on comments received from the previous IETF meeting, I have split the MPLS 
over L2TPv3 draft into two documents.

draft-townsley-l2tpv3-mpls-01.txt targets mpls, and presents only the MPLS over 
L2TPv3 encapsulation.

draft-townsley-l3vpn-l2tpv3-00.txt targets l3vpn, and discusses the use of MPLS 
over L2TPv3 within the context of RFC2547-Style VPNs.

Yakov also had three specific points raised during both meetings that I promised 
to bring to the list. These follow:

> 1. Why extending BGP for multipoint-to-point L2TP signaling
> is preferred to the existing L2TP signaling (or extending L2TP
> to provide multipoint-to-point signaling) ?

Any sort of point to multipoint manual configuration or signaling may in fact be 
used. However, BGP does seem prudent for what is effectively an extension to 
RFC2547.

> 2. The applicability scope is by no means limited to 2547 - it is
> applicable to any multipoint-to-point application.

Yes, though the scope does not extend beyond reachability information to a given 
PE. The MPLS labels for the VPN routes themselves continue to be distributed by 
the existing mechanisms of RFC2547.

> 3. The security claims have to be reviewed by the Security ADs.

(Continue reading)

Internet-Drafts | 2 Feb 2004 22:04
Picon
Favicon

I-D ACTION:draft-farrel-mpls-preemption-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: Multiprotocol Label Switching Pre-emption
	Author(s)	: A. Farrel
	Filename	: draft-farrel-mpls-preemption-00.txt
	Pages		: 9
	Date		: 2004-2-2
	
Multiprotocol Label Switching (MPLS) signaling is documented in
'RSVP-TE: Extensions to RSVP for LSP Tunnels', RFC 3209, using
mechanisms inherited from 'Resource ReserVation Protocol --
Version 1 Functional Specification', RFC 2205.

MPLS includes the concept of pre-emption where, for administrative
reasons such as contention for system resources, a new Label Switched
Path (LSP) may displace an existing LSP.

This document clarifies the procedures for MPLS pre-emption in the
light of implementation experience. The procedures in this document
update those described in RFC 2205 and RFC 3209, but apply only to
RSVP-TE used in the MPLS context.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-farrel-mpls-preemption-00.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,
(Continue reading)

Internet-Drafts | 2 Feb 2004 22:06
Picon
Favicon

I-D ACTION:draft-ietf-mpls-bgp-mpls-restart-03.txt

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

	Title		: Graceful Restart Mechanism for BGP with MPLS
	Author(s)	: Y. Rekhter, R. Aggarwal
	Filename	: draft-ietf-mpls-bgp-mpls-restart-03.txt
	Pages		: 11
	Date		: 2004-2-2
	
A mechanism for BGP that would help minimize the negative effects on
   routing caused by BGP restart is described in 'Graceful Restart
   Mechanism for BGP' (see [1]). This document extends this mechanism to
   also minimize the negative effects on MPLS forwarding caused by the
   Label Switching Router's (LSR's) control plane restart, and
   specifically by the restart of its BGP component when BGP is used to
   carry MPLS labels and the LSR is capable of preserving the MPLS
   forwarding state across the restart.

   The mechanism described in this document is agnostic with respect to
   the types of the addresses carried in the BGP Network Layer
   Reachability Information (NLRI) field. As such it works in
   conjunction with any of the address famililies that could be carried
   in BGP (e.g., IPv4, IPv6, etc...)

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-bgp-mpls-restart-03.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.

(Continue reading)

Internet-Drafts | 2 Feb 2004 22:06
Picon
Favicon

I-D ACTION:draft-ietf-mpls-nodeid-subobject-02.txt

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

	Title		: Definition of an RRO node-id subobject
	Author(s)	: J. Vasseur
	Filename	: draft-ietf-mpls-nodeid-subobject-02.txt
	Pages		: 9
	Date		: 2004-2-2
	
In the context of MPLS TE Fast Reroute, the Merge Point (MP) address is 
required at the Point of Local Repair (PLR) in order to select a backup 
tunnel intersecting a fast reroutable Traffic Engineering LSP on a 
downstream LSR.  However, existing protocol mechanisms are not 
sufficient to find an MP address in multi-areas or multi-domain routing 
networks. Hence, the current MPLS Fast Reroute mechanism cannot be used 
to protect inter-area or inter-AS TE LSPs from a failure of an ABR 
(Area Border Router) or ASBR (Autonomous System Border Router) 
respectively. This document specifies the use of existing RRO IPv4 and 
IPv6 subobjects (with a new flag defined) to define the node-id 
subobject in order to solve this issue. Note that the MPLS Fast reroute 
mechanism mentioned in this document refers to the 'Facility backup' 
MPLS TE Fast Reroute method.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-02.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
(Continue reading)

Internet-Drafts | 2 Feb 2004 22:07
Picon
Favicon

I-D ACTION:draft-ietf-mpls-telink-mib-06.txt

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

	Title		: Traffic Engineering Link Management Information Base
	Author(s)	: M. Dubuc, S. Dharanikota, T. Nadeau, J. Lang
	Filename	: draft-ietf-mpls-telink-mib-06.txt
	Pages		: 54
	Date		: 2004-2-2
	
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 modeling TE links as
described in the Link Bundling in MPLS Traffic Engineering document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-telink-mib-06.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-mpls-telink-mib-06.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.
(Continue reading)

Adrian Farrel | 3 Feb 2004 00:46
Picon

Re: I-D ACTION:draft-farrel-mpls-preemption-00.txt

All,

I have submitted a draft to attempt to start the process of resolving the pre-emption
debate.

It would be well for people to indicate their support, disapproval, or (equally valuable
to the assessment of the value of the draft) their apathy.
Comments on the mailing list are more valuable than private emails.

Thanks,
Adrian
----- Original Message ----- 
From: <Internet-Drafts <at> ietf.org>
To: <IETF-Announce:>
Cc: <mpls <at> uu.net>
Sent: Monday, February 02, 2004 9:04 PM
Subject: I-D ACTION:draft-farrel-mpls-preemption-00.txt

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
> Title : Multiprotocol Label Switching Pre-emption
> Author(s) : A. Farrel
> Filename : draft-farrel-mpls-preemption-00.txt
> Pages : 9
> Date : 2004-2-2
>
> Multiprotocol Label Switching (MPLS) signaling is documented in
> 'RSVP-TE: Extensions to RSVP for LSP Tunnels', RFC 3209, using
> mechanisms inherited from 'Resource ReserVation Protocol --
(Continue reading)


Gmane