Re: [mpls] draft-ietf-mpls-tp-use-cases-and-design-02
"Adrian Farrel" <adrian@olddog.co.uk> Wed, 08 August 2012 08:13 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30ABA11E80AD for <mpls@ietfa.amsl.com>; Wed, 8 Aug 2012 01:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.882
X-Spam-Level:
X-Spam-Status: No, score=-1.882 tagged_above=-999 required=5 tests=[AWL=-0.704, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9ghD60KCIY5 for <mpls@ietfa.amsl.com>; Wed, 8 Aug 2012 01:13:46 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id DCFDD21F861E for <mpls@ietf.org>; Wed, 8 Aug 2012 01:13:42 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q788DXXo007265; Wed, 8 Aug 2012 09:13:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id q788DTe0007212 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 8 Aug 2012 09:13:30 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: "'Luyuan Fang (lufang)'" <lufang@cisco.com>, 'Shahram Davari' <davari@broadcom.com>, mpls@ietf.org
References: <4A6CE49E6084B141B15C0713B8993F2806E252@SJEXCHMB12.corp.ad.broadcom.com> <0DB8F45437AB844CBB5102F807A0AD930F4C9E61@xmb-rcd-x03.cisco.com>
In-Reply-To: <0DB8F45437AB844CBB5102F807A0AD930F4C9E61@xmb-rcd-x03.cisco.com>
Date: Wed, 08 Aug 2012 09:13:29 +0100
Message-ID: <023301cd753d$b1f3eb60$15dbc220$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_0234_01CD7546.13BF3130"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIXHBJEF8FkHEwJftuC9PLCnW2MvQH5310olqx0JKA=
Content-Language: en-gb
Subject: Re: [mpls] draft-ietf-mpls-tp-use-cases-and-design-02
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mpls>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2012 08:13:49 -0000
I will include this point in my AD review and you can fix it in the respin that will be needed. A From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Luyuan Fang (lufang) Sent: 08 August 2012 02:57 To: Shahram Davari; mpls@ietf.org Subject: Re: [mpls] draft-ietf-mpls-tp-use-cases-and-design-02 Shahram, It is a valid point, thanks. We can replace "PHP as optional" with "PHP must be disabled by default". I assume we can make the change through RFC editing process, Loa can help to confirm if OK. Thanks, Luyuan From: mpls-bounces@ietf.org [mailto:mpls-bounces@ietf.org] On Behalf Of Shahram Davari Sent: Tuesday, August 07, 2012 4:45 PM To: mpls@ietf.org Subject: [mpls] draft-ietf-mpls-tp-use-cases-and-design-02 Hi, I am not sure it is late or not, but I found a discrepancy between This draft and RFC5960. This draft says PHP is optional for MPLS-TP, while RFC5960 says PHP MUST not be used. Is there any way to correct this before IESG publication? Thank you, Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: cid:image009.jpg@01CD505E.7B800DB0 Shahram Davari | Technical Director, Network Switching Group Broadcom Corporation | (O) 408-922-7436 | (M) 408-660-5695 <http://www.linkedin.com/company/broadcom> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image005 <http://twitter.com/#!/broadcom> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image002 <https://www.facebook.com/Broadcom> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image003 <https://plus.google.com/109188783526874806673/posts#109188783526874806673/posts > Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image004 <https://www.youtube.com/user/BroadcomCorporation> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image006 <http://blog.broadcom.com/> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image008 <http://broadcom.com/> Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: image007
- [mpls] draft-ietf-mpls-tp-use-cases-and-design-02 Shahram Davari
- Re: [mpls] draft-ietf-mpls-tp-use-cases-and-desig… Gregory Mirsky
- Re: [mpls] draft-ietf-mpls-tp-use-cases-and-desig… Luyuan Fang (lufang)
- Re: [mpls] draft-ietf-mpls-tp-use-cases-and-desig… Adrian Farrel
- Re: [mpls] draft-ietf-mpls-tp-use-cases-and-desig… Luyuan Fang (lufang)