IETF Logo Mail Archive

Re: [PWE3] FW: New Version Notification for draft-jiang-pwe3-mc-pon-01.txt

"JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)" <shrinivas_ashok.joshi@alcatel-lucent.com> Mon, 03 March 2014 09:26 UTC

Return-Path: <shrinivas_ashok.joshi@alcatel-lucent.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDFF01A0C81 for <pwe3@ietfa.amsl.com>; Mon, 3 Mar 2014 01:26:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWgINBCRZQAX for <pwe3@ietfa.amsl.com>; Mon, 3 Mar 2014 01:26:50 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2031A0BFC for <pwe3@ietf.org>; Mon, 3 Mar 2014 01:26:50 -0800 (PST)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s239QRJg011938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 3 Mar 2014 03:26:28 -0600 (CST)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id s239QRuc029068 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Mar 2014 04:26:27 -0500
Received: from SG70YWXCHHUB04.zap.alcatel-lucent.com (135.253.2.38) by US70UWXCHHUB01.zam.alcatel-lucent.com (135.5.2.48) with Microsoft SMTP Server (TLS) id 14.2.247.3; Mon, 3 Mar 2014 04:26:27 -0500
Received: from SG70YWXCHMBA06.zap.alcatel-lucent.com ([169.254.6.7]) by SG70YWXCHHUB04.zap.alcatel-lucent.com ([135.253.2.38]) with mapi id 14.02.0247.003; Mon, 3 Mar 2014 17:26:11 +0800
From: "JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)" <shrinivas_ashok.joshi@alcatel-lucent.com>
To: "jiangyuanlong@huawei.com" <jiangyuanlong@huawei.com>
Thread-Topic: RE: [PWE3] FW: New Version Notification for draft-jiang-pwe3-mc-pon-01.txt
Thread-Index: Ac82wpzVAB4Km32WSte37k85z3obbQ==
Date: Mon, 3 Mar 2014 09:26:10 +0000
Message-ID: <B7069DBE4D36564C9417940314B929511088A5@SG70YWXCHMBA06.zap.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.253.19.17]
Content-Type: multipart/alternative; boundary="_000_B7069DBE4D36564C9417940314B929511088A5SG70YWXCHMBA06zap_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/y7jkf5PFc_2D6fJpCPcDMHY5HpA
Cc: "pwe3@ietf.org" <pwe3@ietf.org>
Subject: Re: [PWE3] FW: New Version Notification for draft-jiang-pwe3-mc-pon-01.txt
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3/>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 09:26:56 -0000

Hi Yuanlong

I read through the draft. There is benefit in having a protocol to support this use case of synchronizing protection and context information between two chassis providing protection.

However I see the same use case applicable to other first mile access technologies like point to point ethernet & DSL (G.Fast) where operators want to protect services offered to business users or backhaul (wifi or mobile).


The draft as proposed is specific to PON, I would like to see the protocol extended in more generic manner to support point to point ethernet and DSL technologies as well, and would be willing to work with you for the same.

Regards
--
Shree


-----Original Message-----

From: internet-drafts at ietf.org [mailto:internet-drafts at ietf.org]

Sent: Saturday, January 18, 2014 11:45 AM

To: Luoyong (Dennis); Edwin Mallette; Edwin Mallette; Jiangyuanlong; Jiangyuanlong; Luoyong (Dennis)

Subject: New Version Notification for draft-jiang-pwe3-mc-pon-01.txt





A new version of I-D, draft-jiang-pwe3-mc-pon-01.txt

has been successfully submitted by Yuanlong Jiang and posted to the

IETF repository.



Name:          draft-jiang-pwe3-mc-pon

Revision:      01

Title:         Multi-chassis PON Protection in MPLS

Document date: 2014-01-18

Group:         Individual Submission

Pages:         14

URL:            http://www.ietf.org/internet-drafts/draft-jiang-pwe3-mc-pon-01.txt

Status:         https://datatracker.ietf.org/doc/draft-jiang-pwe3-mc-pon/

Htmlized:       http://tools.ietf.org/html/draft-jiang-pwe3-mc-pon-01

Diff:           http://www.ietf.org/rfcdiff?url2=draft-jiang-pwe3-mc-pon-01



Abstract:

   MPLS is being deployed deeper into operator networks, often to or

   past the access network node. Separately network access nodes such as

   PON OLTs have evolved to support first-mile access protection, where

   one or more physical OLTs provide first-mile diversity to the

   customer edge. Multi-homing support is needed on the MPLS-enabled PON

   OLT to provide resiliency for provided services.  This document

   describes the multi-chassis PON protection architecture in MPLS and

   also proposes the ICCP extension to support it.









Please note that it may take a couple of minutes from the time of submission

until the htmlized version and diff are available at tools.ietf.org.



The IETF Secretariat

v2.8.7 | Report a Bug | By Email