JP Vasseur | 1 Dec 16:34 2006
Picon

Re: WG Last Call on draft-ietf-mpls-number-0-bw-te-lsps-02.txt

Hi Loa,

The new revision accounting for all comments during LC received by  
Daniel King, Adrian, Acee, Loa ... has been posted: http:// 
www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te-lsps-03.txt

Thanks.

JP.

On Sep 1, 2006, at 4:08 AM, Loa Andersson wrote:

> Working Group,
>
> this initiates a two week working group last call on
> draft-ietf-mpls-number-0-bw-te-lsps-02.txt
>
> The wg last call ends on September 17.
>
> Please send comments to the working group mailing list and/or
> the working group chairs.
>
> /Loa and George
>
> -- 
> Loa Andersson
>
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
(Continue reading)

Internet-Drafts | 1 Dec 16:50 2006
Picon

I-D ACTION:draft-ietf-mpls-number-0-bw-te-lsps-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		: A Link-Type sub-TLV to convey the number of
                          Traffic Engineering Label Switch Paths 
                          signalled signalled with zero reserved bandwidth across a link
	Author(s)	: J. Vasseur, et al.
	Filename	: draft-ietf-mpls-number-0-bw-te-lsps-03.txt
	Pages		: 9
	Date		: 2006-12-1
	
Several Link-type sub-TLVs have been defined for OSPF and ISIS in the    context of Multiprotocol Label
Switching (MPLS) Traffic Engineering
   (TE) in order to advertise some link characteristics such as the
   available bandwidth, traffic engineering metric, administrative group
   and so on.  By making statistical assumption on the aggregated
   traffic carried onto a set of TE Label Switched Paths (LSPs)
   signalled with zero bandwdith (referred to as unconstrained TE LSP in
   this document), and with the knowledge of the number of unconstrained
   TE LSPs signalled across a link, algorithms can be designed to load
   balance (existing or newly configured) unconstrained TE LSP across a
   set of equal cost paths.  This requires the knowledge of the number
   of unconstrained TE LSPs signalled across a link.  This document
   specifies a new Link-type Traffic Engineering sub-TLV used to
   advertise the number of unconstrained TE LSP(s) signalled across a
   link.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te-lsps-03.txt
(Continue reading)

shilpa goel | 4 Dec 06:23 2006
Picon

: label space configuration

Hi..

  Can you please give me an insight as to how label space (per interface or per platform) is configured in a LSR i.e. what all considerations need to be taken into account:

for 2 cases-
    -LSR consisting of only ethernet ports
    -LSR consisting of both ATM and ethernet interfaces

thanks and regards,
Shilpa

Mohammed Shahnawaz | 5 Dec 14:28 2006

: Tagging of BGP extended community

 

Hi,

 

Can someone explain how routers support tagging of multiple BGP extended communities for VPN4 routes using a single interface between PE and CE.  Please provide some documents as well, if possible.

 

 

Thanks & Regards,

 

Shahnawaz

 

 

 

Internet-Drafts | 8 Dec 21:50 2006
Picon

I-D ACTION:draft-ietf-mpls-number-0-bw-te-lsps-04.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		: A Link-Type sub-TLV to convey the number of 
                          Traffic Engineering Label Switch Paths 
                          signalled signalled with zero reserved bandwidth across a link
	Author(s)	: J. Vasseur, et al.
	Filename	: draft-ietf-mpls-number-0-bw-te-lsps-04.txt
	Pages		: 9
	Date		: 2006-12-8
	
Several Link-type sub-TLVs have been defined for OSPF and ISIS in the
   context of Multiprotocol Label Switching (MPLS) Traffic Engineering
   (TE) in order to advertise some link characteristics such as the
   available bandwidth, traffic engineering metric, administrative group
   and so on.  By making statistical assumption on the aggregated
   traffic carried onto a set of TE Label Switched Paths (LSPs)
   signalled with zero bandwdith (referred to as unconstrained TE LSP in
   this document), and with the knowledge of the number of unconstrained
   TE LSPs signalled across a link, algorithms can be designed to load
   balance (existing or newly configured) unconstrained TE LSP across a
   set of equal cost paths.  This requires the knowledge of the number
   of unconstrained TE LSPs signalled across a link.  This document
   specifies a new Link-type Traffic Engineering sub-TLV used to
   advertise the number of unconstrained TE LSP(s) signalled across a
   link.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te-lsps-04.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-number-0-bw-te-lsps-04.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 <at> ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mpls-number-0-bw-te-lsps-04.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.
Attachment: message/external-body, 148 bytes
_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
Santanu.Ganguly | 11 Dec 13:31 2006

RE: label space configuration

Hi Shilpa,
 
Perhaps RFC 3036 could be a guideline ? In section 2.2.2, it says the follwoing:
 
2.2.2. LDP Identifiers
 
   An LDP identifier is a six octet quantity used to identify an LSR
   label space.  The first four octets identify the LSR and must be a
   globally unique value, such as a 32-bit router Id assigned to the
   LSR.  The last two octets identify a specific label space within the
   LSR.  The last two octets of LDP Identifiers for platform-wide label
   spaces are always both zero.  This document uses the following print
   representation for LDP Identifiers:
 
             <LSR Id> : <label space id>
 
   e.g., lsr171:0, lsr19:2.
 
   Note that an LSR that manages and advertises multiple label spaces
   uses a different LDP Identifier for each such label space.
 
   A situation where an LSR would need to advertise more than one label
   space to a peer and hence use more than one LDP Identifier occurs
   when the LSR has two links to the peer and both are ATM (and use per
   interface labels).  Another situation would be where the LSR had two
   links to the peer, one of which is ethernet (and uses per platform
   labels) and the other of which is ATM.
 
Cheers
 
santanu
 
Santanu Ganguly
Swisscom Fixnet Wholesale
Binz Ring 17
Zurich
Switzerland

From: shilpa goel [mailto:shilpa07 <at> gmail.com]
Sent: Monday, December 04, 2006 6:24 AM
To: mpls <at> uu.net; mpls-ops <at> mplsrc.com; mpls <at> lists.ietf.org
Subject: [mpls] label space configuration

Hi..

  Can you please give me an insight as to how label space (per interface or per platform) is configured in a LSR i.e. what all considerations need to be taken into account:

for 2 cases-
    -LSR consisting of only ethernet ports
    -LSR consisting of both ATM and ethernet interfaces

thanks and regards,
Shilpa
_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
shilpa goel | 12 Dec 05:03 2006
Picon

Re: : label space configuration

Hi,

 Thanks for the clarification. I still have 2 doubts in this.

Firstly, what is meant by the line  'as the router knows about all of them'?  (2nd para)

Also, this is clear that for ATM, interface label space should be used but why should platform wide labelling be used in an Ethernet configuration i.e. why can't we use interface label space for ethernet also thereby seeking the same advantage as we are getting for ATM?

thanks,
Shilpa

On 12/4/06, Roger Williams (rogwilli) <rogwilli <at> cisco.com> wrote:
Shilpa, platform-wide labeling is used in an Ethernet configuration, whereas port or interface lablespace is used for ATM.
 
Basically what that means is that for Ethernet a given router advertises its whole self with one label upstream. All ports would be covered under that single label advertisement, as the router knows about all of them. And it is done as soon as the underlying IGP routing protocol knows there are routes to be labeled, not waiting for the demands of traffic to build label paths.
 
With ATM the doling out of labels is much more conservative, and done only when requested by traffic demand. The reason for this is the limited number of VCs that an ATM switch can support (I think 4096). The labels point to a VC underneath it all. Since there is no routing done at the Layer 2 of an ATM switch, each label is used as a per-interface advertisement, which effectively is a per-VC advertisement.
 
I hope that helps.
 
Roger.

From: shilpa goel [mailto:shilpa07 <at> gmail.com]
Sent: Monday, December 04, 2006 12:24 AM
To: mpls <at> uu.net; mpls-ops <at> mplsrc.com; mpls <at> lists.ietf.org
Subject: [MPLS-OPS]: label space configuration

Hi..

  Can you please give me an insight as to how label space (per interface or per platform) is configured in a LSR i.e. what all considerations need to be taken into account:

for 2 cases-
    -LSR consisting of only ethernet ports
    -LSR consisting of both ATM and ethernet interfaces

thanks and regards,
Shilpa

Loa Andersson | 12 Dec 14:07 2006
Picon

draft-ietf-mpls-number-0-bw-te-lsps-04 last wg last call

Working Group,

we have a small draft "draft-ietf-mpls-number-0-bw-te-lsps-04"
that is about ready to be sent to the IESG.

The draft has been updated after working group last call (though
we are aware of a couple of small editorial nits, e.g. repeated
words in the title).

This mails start a one week working last call to verify that
all comments been addressed and that there are no outstanding
issues, i.e. if you are happy with the draft you don't need
to respond.

Loa and George.

--

-- 
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson <at> acreo.se
                                           loa <at> pi.se

_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

Raveendra Torvi | 12 Dec 15:46 2006
Picon

Re: draft-ietf-mpls-number-0-bw-te-lsps-04 last wg last call

Hi,
 Is it assumed that  LSR counts both p2mp and p2p TE-LSPs?
Should we count them separetely? 
IMO, counting them seperately might help as traffic characteristics are different for unicast and multicast.
Thanks,
Ravi.
 
On 12/12/06, Loa Andersson <loa <at> pi.se> wrote:
Working Group,

we have a small draft "draft-ietf-mpls-number-0-bw-te-lsps-04"
that is about ready to be sent to the IESG.

The draft has been updated after working group last call (though
we are aware of a couple of small editorial nits, e.g. repeated
words in the title).

This mails start a one week working last call to verify that
all comments been addressed and that there are no outstanding
issues, i.e. if you are happy with the draft you don't need
to respond.

Loa and George.

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson <at> acreo.se
                                          loa <at> pi.se

_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls
JP Vasseur | 12 Dec 20:34 2006
Picon

Re: draft-ietf-mpls-number-0-bw-te-lsps-04 last wg last call

Hi Ravi,

On Dec 12, 2006, at 9:46 AM, Raveendra Torvi wrote:

Hi,
 Is it assumed that  LSR counts both p2mp and p2p TE-LSPs?
Should we count them separetely? 
IMO, counting them seperately might help as traffic characteristics are different for unicast and multicast.


The TLVs report the number of TE LSPs (P2P and P2MP), no plan to have two separate TLVs.

Thanks.

JP.

Thanks,
Ravi.
 
On 12/12/06, Loa Andersson <loa <at> pi.se> wrote:
Working Group,

we have a small draft "draft-ietf-mpls-number-0-bw-te-lsps-04"
that is about ready to be sent to the IESG.

The draft has been updated after working group last call (though
we are aware of a couple of small editorial nits, e.g. repeated
words in the title).

This mails start a one week working last call to verify that
all comments been addressed and that there are no outstanding
issues, i.e. if you are happy with the draft you don't need
to respond.

Loa and George.

--
Loa Andersson

Principal Networking Architect
Acreo AB                           phone:  +46 8 632 77 14
Isafjordsgatan 22                  mobile: +46 739 81 21 64
Kista, Sweden                      email:  loa.andersson <at> acreo.se
                                          loa <at> pi.se

_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

_______________________________________________
mpls mailing list

_______________________________________________
mpls mailing list
mpls <at> lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

Gmane