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

"JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)" <shrinivas_ashok.joshi@alcatel-lucent.com> Thu, 24 July 2014 04:09 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 169A01ABB90 for <pwe3@ietfa.amsl.com>; Wed, 23 Jul 2014 21:09:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Vq61OpuoOfw2 for <pwe3@ietfa.amsl.com>; Wed, 23 Jul 2014 21:08:58 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8AE1ABB31 for <pwe3@ietf.org>; Wed, 23 Jul 2014 21:08:57 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s6O48mH6000090 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 23 Jul 2014 23:08:49 -0500 (CDT)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id s6O48ld1016009 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 24 Jul 2014 00:08:47 -0400
Received: from SG70XWXCHHUB02.zap.alcatel-lucent.com (135.253.2.47) by US70UWXCHHUB02.zam.alcatel-lucent.com (135.5.2.49) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 24 Jul 2014 00:08:47 -0400
Received: from SG70YWXCHMBA06.zap.alcatel-lucent.com ([169.254.6.126]) by SG70XWXCHHUB02.zap.alcatel-lucent.com ([135.253.2.47]) with mapi id 14.02.0247.003; Thu, 24 Jul 2014 12:08:39 +0800
From: "JOSHI, SHRINIVAS ASHOK (SHRINIVAS ASHOK)" <shrinivas_ashok.joshi@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>, Jiangyuanlong <jiangyuanlong@huawei.com>
Thread-Topic: Re: New Version Notification for draft-jiang-pwe3-mc-pon-02.txt
Thread-Index: Ac+m9PJodoQ98eygQUujszevc3JAUg==
Date: Thu, 24 Jul 2014 04:08:39 +0000
Message-ID: <B7069DBE4D36564C9417940314B929511D01DE@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/R6Wo-wn5LTK1vLixEwPVI5FaGDU
Subject: Re: [PWE3] New Version Notification for draft-jiang-pwe3-mc-pon-02.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: Thu, 24 Jul 2014 04:09:00 -0000

Hi Yuanlong,

Thanks for including DSL and P2P in use cases in Introduction. However the TLV's and procedures are still PON specific.
I would suggest to make the TLV and procedures generic so they are applicable to DSL and P2P Ethernet as well.

Also in access network i.e. PON and P2P ethernet there is significant amount of dynamic information e.g. DHCP leases, PPP sessions etc which are maintained by OLT for each subscriber, the draft should cover the procedure for synchronization of this dynamic information between the two OLT's.

One additional point current draft does not cover the procedure for PON configuration TLV when & how it would be used.

Also it would be good to have some discussion/feedback on mailing list on the expanded draft to see if it covers all scenario's.

Thanks
--
Shrinivas Joshi

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

Hi colleagues,
 
We had updated the draft to a new revision. The main updates include:
1.	Add more application scenarios, such as MSO and DSL;
2.	Add support to a deployment scenario of partly protection raised by some service providers;
3.	Add Chenbin and Yimin to our co-authors;
4.  Substantial editorial changes. 

Please feedback you opinions on this version. Thanks!

Regards,
Yuanlong

-----Original Message-----
From: internet-drafts at ietf.org [mailto:internet-drafts at ietf.org] 
Sent: Wednesday, April 02, 2014 11:19 AM
To: Yimin Shen; Luoyong (Dennis); Chengbin Shen; Chengbin Shen; Edwin Mallette; Yimin Shen; Edwin Mallette; Jiangyuanlong; Jiangyuanlong; Luoyong (Dennis)
Subject: New Version Notification for draft-jiang-pwe3-mc-pon-02.txt


A new version of I-D, draft-jiang-pwe3-mc-pon-02.txt
has been successfully submitted by Yuanlong Jiang and posted to the
IETF repository.

Name:		draft-jiang-pwe3-mc-pon
Revision:	02
Title:		Multi-chassis PON Protection in MPLS
Document date:	2014-04-02
Group:		Individual Submission
Pages:		15
URL:            http://www.ietf.org/internet-drafts/draft-jiang-pwe3-mc-pon-02.txt
Status:         https://datatracker.ietf.org/doc/draft-jiang-pwe3-mc-pon/
Htmlized:       http://tools.ietf.org/html/draft-jiang-pwe3-mc-pon-02
Diff:           http://www.ietf.org/rfcdiff?url2=draft-jiang-pwe3-mc-pon-02

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