Internet-Drafts | 2 Jan 2011 09:30
Picon
Favicon

I-D Action:draft-ietf-mpls-tp-oam-analysis-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           : OAM functions in MPLS based transport network
	Author(s)       : N. Sprecher, et al.
	Filename        : draft-ietf-mpls-tp-oam-analysis-03.txt
	Pages           : 14
	Date            : 2011-01-02

This document describes the outcome of the discussions on the
necessary OAM functionality for the first release of MPLS based
transport networks.  The discussion is based on the set of
requirements for Operations, Administration, and Maintenance (OAM)
for MPLS based transport networks as defined in [MPLS-TP OAM Reqs].
An important aspect was to evaluate whether existing OAM tools from
the current MPLS protocol suite can be used to fulfill these
requirements.  Eventually, the purpose of the document is to map the
set of functions to a set of tools based on the existing OAM tool-
set.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-oam-analysis-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
(Continue reading)

The IESG | 3 Jan 2011 16:05
Picon
Favicon

Protocol Action: 'Label Edge Router Forwarding of IPv4 Option Packets' to Proposed Standard (draft-ietf-mpls-ip-options-07.txt)

The IESG has approved the following document:
- 'Label Edge Router Forwarding of IPv4 Option Packets'
  (draft-ietf-mpls-ip-options-07.txt) as a Proposed Standard

This document is the product of the Multiprotocol Label Switching Working
Group.

The IESG contact persons are Adrian Farrel and Stewart Bryant.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-mpls-ip-options/

Technical Summary

Requirements for Label Edge Router Forwarding of IPv4 Option Packets specifies 
how Label Edge Routers (LER) should behave when determining whether to MPLS 
encapsulate an IP packet with header options.  Lack of a formal standard has resulted 
in different LER forwarding behaviors for IP packets with header options despite being 
associated with a prefix-based Forwarding Equivalence Class (FEC). IP option packets
 that belong to a prefix-based FEC but fail to be MPLS encapsulated simply due to their 
header options present a security risk against the MPLS infrastructure. Further, LERs 
that are unable to MPLS encapsulate IP packets with header options cannot operate in 
certain MPLS environments.  While this newly defined LER behavior is mandatory to 
implement, it is optional to invoke.

Working Group Summary

Nothing worth noting, except that there was some discussion of whether this should go
 forward as an informational draft.  The WG consensus was to have it on the Standards 
track. Further details of this dicussion can be seen in the proto write-up.
(Continue reading)

Picon

PW / VCCV User Implementation Survey - Please Participate!

 

Just a friendly reminder to complete (or ask your customers to complete) the PW/VCCV User Implementation Survey. 

 

We have 6 responses so far.

 

The deadline is February 25, 2011.

 

Thanks,

Nick

 

From: pwe3-bounces <at> ietf.org [mailto:pwe3-bounces <at> ietf.org] On Behalf Of Delregno, Christopher N (Nick DelRegno)
Sent: Thursday, November 04, 2010 3:55 PM
To: pwe3; mpls <at> ietf.org; l2vpn <at> ietf.org
Cc: Malis, Andrew G. (Andy)
Subject: [PWE3] PW / VCCV Service Provider Implementation Survey

 

All:

 

Per the direction of the PWE3 working group, beginning in IETF77 and reinforced in IETF78, the PWE3 working group is conducting a Service Provider implementation survey related to:

 

-          Pseudowire Encapsulations

-          Control Word Support

-          Control Word Use

-          VCCV Control Channel Support

-          VCCV Control Channel Use

 

http://www.surveymonkey.com/s/pwe3

 

This is a short survey directed toward Service Providers who currently operate networks using any of the defined PWE3 encapsulations.  The results of this survey will be used to determine the direction of the Control Word support in current and future encapsulations as well as solutions to VCCV interoperability challenges.

 

We sincerely urge all service providers to participate.  We ask that all equipment providers encourage participation by their Service Provider customers.  The more feedback we receive, the better view of the existing network we can have on which to base going-forward direction.

 

If you have any questions, regarding the survey, especially of a technical nature, please contact me.  If you have non-technical questions, feel free to reach out to the PWE3 WG chairs and myself.

 

The results of the survey will be aggregated and shared at a high level.  No low-level details of network implementations will be shared.  All participant’s responses will remain private, if not anonymous.

 

All responses will require a valid email address to help ensure the survey’s validity.

 

Thanks,

Nick

 

Christopher N. “Nick” DelRegno, PMTS

CNT, Ethernet Network Architecture & Design

400 International Pkwy

Richardson, TX  75081

Tel:  972-729-3411

Email:  Nick.DelRegno <at> verizon.com

 

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

Re: I-D Action:draft-ietf-mpls-tp-oam-analysis-03.txt

Hi all,

We have updated this draft to prevent it from expiring.  This version
addresses some of the comments received during the WG LC.  We will
republish when we have completed addressing all of the comments.

Best Regards,
The Editors

>> -----Original Message-----
>> From: mpls-bounces <at> ietf.org [mailto:mpls-bounces <at> ietf.org] On Behalf
>> Of ext Internet-Drafts <at> ietf.org
>> Sent: Sunday, January 02, 2011 10:30 AM
>> To: i-d-announce <at> ietf.org
>> Cc: mpls <at> ietf.org
>> Subject: [mpls] I-D Action:draft-ietf-mpls-tp-oam-analysis-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           : OAM functions in MPLS based transport network
>> 	Author(s)       : N. Sprecher, et al.
>> 	Filename        : draft-ietf-mpls-tp-oam-analysis-03.txt
>> 	Pages           : 14
>> 	Date            : 2011-01-02
>> 
>> This document describes the outcome of the discussions on the
>> necessary OAM functionality for the first release of MPLS based
>> transport networks.  The discussion is based on the set of
>> requirements for Operations, Administration, and Maintenance (OAM)
>> for MPLS based transport networks as defined in [MPLS-TP OAM Reqs].
>> An important aspect was to evaluate whether existing OAM tools from
>> the current MPLS protocol suite can be used to fulfill these
>> requirements.  Eventually, the purpose of the document is to map the
>> set of functions to a set of tools based on the existing OAM tool-
>> set.
>> 
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-oam-analysis-
>> 03.txt
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls

New version of draft-weingarten-mpls-tp-ring-protection-04

Hello all,

We have submitted a new version of the ring protection draft, mainly to prevent the draft from expiring.  However, there is one significant change from the previous version in the section on p2mp steering protection where the description now references the concept of context-labels in order to explain the working of the working and protection SPME.  Any comments regarding this section especially would be appreciated, as the editors are still discussing how to improve the description.

Best regards,

Yaacov Weingarten

Nokia Siemens Networks

Industry Environment, PTE

ph#:  +972-9-775 1827

mob#: +972-54-220 0977

_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
lizhong.jin | 5 Jan 2011 07:24
Picon

Request comments for HSMP LSP


Hi all,
During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS session.
HSMP LSP has several use cases described in the draft, e.g, time synchronization in MPLS network, IPTV scenario, or P2MP PW. It would be appreciated if you could give more scenarios for HSMP LSP. Please review the draft, and any comments are welcome.

The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-01
 
Thank you.
Authors of draft-hsmp.
-------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Ed | 5 Jan 2011 08:05
Picon

Re: Request comments for HSMP LSP

Hi Lizhong,

 

I think one possible application for HSMP LSPs is to reduce the overall broadcast/multicast utilization on a VPLS. In current VPLS implementations with a full mesh of P2P LSPs between PEs, broadcast, multicast and unknown traffic are not efficiently propagated on the physical links between PEs and Ps.

 

In the VPLS implementation scenario with HSMP LSPs, each PE signals a HSMP LSP with itself as a root to all other PEs in the VPLS. Thereafter, all broadcast/multicast/unknown traffic from this PE will use this HSMP LSP. Unicast traffic from a particular PE (e.g. PE1) to another PE (e.g. PE2) will be sent from leaf to root using the HSMP LSP where PE2 is the root.

 

This simplifies the VPLS implementation by:

-          Reducing traffic utilization from broadcast, multicast and unknown traffic

-          Reducing the total number of LSPs maintained by each PE (i.e. instead of requiring a full mesh of LSPs, now only require one HSMP LSP per PE).

 

This is similar to the idea expressed in  draft-key-l2vpn-etree-frwk-03.txt (in a more general sense).

 

What do you think? Would HSMP LSP be suitable for this?


Regards,

Edward

 

 

 
On Wed, Jan 5, 2011 at 5:24 PM, <lizhong.jin <at> zte.com.cn> wrote:

Hi all,
During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS session.
HSMP LSP has several use cases described in the draft, e.g, time synchronization in MPLS network, IPTV scenario, or P2MP PW. It would be appreciated if you could give more scenarios for HSMP LSP. Please review the draft, and any comments are welcome.

The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-mldp-hsmp-01
 
Thank you.
Authors of draft-hsmp.
-------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls


_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
lizhong.jin | 5 Jan 2011 08:50
Picon

Re: Request comments for HSMP LSP


Hi Edward,
Thank you for the comments. I add l2vpn maillist in cc list. I agree with the application you proposed, and in order to improve the scalability of VPLS, P2MP PW multiplexed to HSMP LSP could be used for VPLS. Actually this is a good application case for P2MP PW with reverse path (section 4.4, draft-ietf-pwe3-p2mp-pw-00). We can add some description about this use case.

Regards
Lizhong
 

Ed <maillist.ed <at> gmail.com> wrote on 2011-01-05 15:05:30:

> Hi Lizhong,
>  
> I think one possible application for HSMP LSPs is to reduce the
> overall broadcast/multicast utilization on a VPLS. In current VPLS
> implementations with a full mesh of P2P LSPs between PEs, broadcast,
> multicast and unknown traffic are not efficiently propagated on the
> physical links between PEs and Ps.
>  
> In the VPLS implementation scenario with HSMP LSPs, each PE signals
> a HSMP LSP with itself as a root to all other PEs in the VPLS.
> Thereafter, all broadcast/multicast/unknown traffic from this PE
> will use this HSMP LSP. Unicast traffic from a particular PE (e.g.
> PE1) to another PE (e.g. PE2) will be sent from leaf to root using
> the HSMP LSP where PE2 is the root.
>  
> This simplifies the VPLS implementation by:
> -          Reducing traffic utilization from broadcast, multicast
> and unknown traffic
> -          Reducing the total number of LSPs maintained by each PE
> (i.e. instead of requiring a full mesh of LSPs, now only require one
> HSMP LSP per PE).
>  
> This is similar to the idea expressed in  draft-key-l2vpn-etree-
> frwk-03.txt (in a more general sense).
>  
> What do you think? Would HSMP LSP be suitable for this?
>
> Regards,
> Edward
>  
>  
>  
> On Wed, Jan 5, 2011 at 5:24 PM, <lizhong.jin <at> zte.com.cn> wrote:
>
> Hi all,
> During IETF 79 Beijing, we made a presentation for HSMP LSP at MPLS session.
> HSMP LSP has several use cases described in the draft, e.g, time
> synchronization in MPLS network, IPTV scenario, or P2MP PW. It would
> be appreciated if you could give more scenarios for HSMP LSP. Please
> review the draft, and any comments are welcome.
>
> The draft link is: http://tools.ietf.org/html/draft-jin-jounay-mpls-
> mldp-hsmp-01
>  
> Thank you.
> Authors of draft-hsmp.
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail is solely 
property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
> This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
>
> _______________________________________________
> mpls mailing list
> mpls <at> ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

-------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Internet-Drafts | 5 Jan 2011 13:00
Picon
Favicon

I-D Action:draft-ietf-mpls-tp-mib-management-overview-01.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           : Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-based Management Overview
	Author(s)       : A. Farrel, et al.
	Filename        : draft-ietf-mpls-tp-mib-management-overview-01.txt
	Pages           : 22
	Date            : 2011-01-05

A range of Management Information Base (MIB) modules has been
developed to help model and manage the various aspects of
Multiprotocol Label Switching (MPLS) networks.  These MIB modules are
defined in separate documents that focus on the specific areas of
responsibility of the modules that they describe.

The MPLS Transport Profile (MPLS-TP) is a profile of MPLS
functionality specific to the construction of packet-switched
transport networks.

This document describes the MIB-based management architecture for 
MPLS-TP, indicates the interrelationships between different 
existing MIB modules that can be leveraged for MPLS-TP network
management and identifies areas where additional MIB modules would be
required.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network as
defined by the ITU-T.

This Informational Internet-Draft is aimed at achieving IETF
Consensus before publication as an RFC and will be subject to an IETF
Last Call.

[RFC Editor, please remove this note before publication as an RFC and
insert the correct Streams Boilerplate to indicate that the published
RFC has IETF Consensus.]

King & Venkatesan,  et al.

 [page 1]

draft-ietf-mpls-tp-mib-management-overview-01.txt

January 2011

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-mib-management-overview-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
_______________________________________________
mpls mailing list
mpls <at> ietf.org
https://www.ietf.org/mailman/listinfo/mpls
Daniel King | 5 Jan 2011 13:19
Picon

New version of draft-ietf-mpls-tp-mib-management-overview (01)

Hi All, 

Happy New Year!

Please note that the authors of draft-ietf-mpls-tp-mib-management-overview
have issued a new version of said document. Updates include:

- Cleaned up Abstract. 
- Included GMPLS TC references where relevant. 
- Updated Pseudowire Module section.
- Added significant text (tables) to the Fault Management and Performance
Management section.
- Updated MPLS-TP Gap Analysis section. 
- Added a new co-author. 
- Addressed various grammar and nits. 
  	
We have also identified the need for an MPLS-TP abstract model document.
This new draft will provide an abstract model and use a formal language to
define the terminology, the information that must be retrieved and stored.
It will also list the new MPLS-TP MIB modules, identified as part of the gap
analysis in  draft-ietf-mpls-tp-mib-management-overview. 

Br, Dan. 

-----Original Message-----
From: i-d-announce-bounces <at> ietf.org [mailto:i-d-announce-bounces <at> ietf.org]
On Behalf Of Internet-Drafts <at> ietf.org
Sent: 05 January 2011 12:00
To: i-d-announce <at> ietf.org
Cc: mpls <at> ietf.org
Subject: I-D Action:draft-ietf-mpls-tp-mib-management-overview-01.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           : Multiprotocol Label Switching Transport Profile
(MPLS-TP) MIB-based Management Overview
	Author(s)       : A. Farrel, et al.
	Filename        : draft-ietf-mpls-tp-mib-management-overview-01.txt
	Pages           : 22
	Date            : 2011-01-05

A range of Management Information Base (MIB) modules has been developed to
help model and manage the various aspects of Multiprotocol Label Switching
(MPLS) networks.  These MIB modules are defined in separate documents that
focus on the specific areas of responsibility of the modules that they
describe.

The MPLS Transport Profile (MPLS-TP) is a profile of MPLS functionality
specific to the construction of packet-switched transport networks.

This document describes the MIB-based management architecture for MPLS-TP,
indicates the interrelationships between different existing MIB modules that
can be leveraged for MPLS-TP network management and identifies areas where
additional MIB modules would be required.

This document is a product of a joint Internet Engineering Task Force
(IETF) / International Telecommunication Union Telecommunication
Standardization Sector (ITU-T) effort to include an MPLS Transport Profile
within the IETF MPLS and PWE3 architectures to support the capabilities and
functionalities of a packet transport network as defined by the ITU-T.

This Informational Internet-Draft is aimed at achieving IETF Consensus
before publication as an RFC and will be subject to an IETF Last Call.

[RFC Editor, please remove this note before publication as an RFC and insert
the correct Streams Boilerplate to indicate that the published RFC has IETF
Consensus.]

King & Venkatesan,  et al.

 [page 1]

draft-ietf-mpls-tp-mib-management-overview-01.txt

January 2011

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-mib-management-overvi
ew-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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


Gmane