[mpls] MPLS-RT review of draft-rhd-mpls-tp-psc-sd

Sam Aldrin <aldrin.ietf@gmail.com> Fri, 23 August 2013 22:26 UTC

Return-Path: <aldrin.ietf@gmail.com>
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 E4EE111E8139 for <mpls@ietfa.amsl.com>; Fri, 23 Aug 2013 15:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level:
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6]
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 LIbVl0ndXIuJ for <mpls@ietfa.amsl.com>; Fri, 23 Aug 2013 15:26:01 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 566FD11E80EF for <mpls@ietf.org>; Fri, 23 Aug 2013 15:26:01 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so1179685pbc.36 for <mpls@ietf.org>; Fri, 23 Aug 2013 15:25:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=Dnlfa4Ay8GnjB1MBmPcpUom3KMCOcndk60qP6+QPldY=; b=TwH2FY4tJSuSOhrYBSC3VtWysdkxUYm2bhuSAwU3/BZ66olwPf1KQzpYi6uxCp1eNh zMvYeZizTsI1RydZ0XCKrOk6Ac99ZG3PN8rBbwbOS1aTRm0LBF55FP2IvO/dX10Ur183 xq06CTVzRzYo1SfsOb0JCVMlk1JUeQPl+taCKzPMPSgrBwgu6TtIa98qYaVyzIgkbjjV gimPBnL0B678M5mq8I5cr5VVVFH6gAgvz7YJTEHQ4K1QSB6g8TAByzZJLuNjNs/Tso4s WzmOh8WJegok8vVIPPXJvqnQbQJmugK7W382lR2rHby4HmUiCbzBVefNLmfVe52B3Qs2 fJ9g==
X-Received: by 10.66.161.99 with SMTP id xr3mr1097874pab.172.1377296759076; Fri, 23 Aug 2013 15:25:59 -0700 (PDT)
Received: from [192.168.1.8] (c-98-248-237-85.hsd1.ca.comcast.net. [98.248.237.85]) by mx.google.com with ESMTPSA id pu5sm3343210pac.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 15:25:57 -0700 (PDT)
From: Sam Aldrin <aldrin.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F8D6301B-63B9-4A4A-9236-4A8C2458EB8E"
Date: Fri, 23 Aug 2013 15:25:55 -0700
Message-Id: <79E5D3D3-6AB4-4CE7-97A9-6D324C053490@gmail.com>
To: Jeong-dong Ryoo <ryoo@etri.re.kr>, "Huub van Helvoort (huub.van.helvoort@huawei.com)" <huub.van.helvoort@huawei.com>, Alessandro D Alessandro <alessandro.dalessandro@telecomitalia.it>, mpls@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Cc: Ross Callon <rcallon@juniper.net>, "<mpls@ietf.org>" <mpls@ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>
Subject: [mpls] MPLS-RT review of draft-rhd-mpls-tp-psc-sd
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Fri, 23 Aug 2013 22:26:02 -0000

Hi,

I have done a review of draft-rhd-mpls-tp-psc-sd as part of MPLS RT process. Please find my comments inline. 

-sam

General comments:
-------------------------
- Have similar comment like other drafts. This draft contains the diff off what is not present in the existing RFC. Is the intention to create a separate RFC in addition to existing RFC6378, by correcting the priority scheme?

Nitpicks/Editorial:
-----------
- Clarity question, Is  it mandated to use PSC only as communication medium or there could be other means, like OAM?

- Sec 1.2, Could you please add clarity to the sentence
The priority level of Clear SF defined in [RFC6378] can cause traffic
   disruption when a node that has experienced local signal fails on
   both working and protection paths is recovering from these failures.

- In Sec 4.2 - When you say SHALL, is it interpreted as MUST or SHOULD?

Assessment comments:
-----------------------------
- Is the document coherent?
> Yes, it is coherent and consistent

- Is the document useful?
> Yes. Correcting the priority as identified in RFC6378 is needed

- Is the document technically sound?
- Yes

- Is is ready for WG adoption
- Not in its correct form. This document is mostly identifying changes to RFC. My preference is to combine all the changes to RFC6378 and re-issue a new RFCbis.  Otherwise, this will be very confusing to refer two or more documents every time to make sense of what is the correct behavior for PSC in linear protection. 
- If that is (creating new RFC bis) something not possible(hope there is a real strong reason for this), then the document should be edited to be more stand alone document. i.e. remove add/replace to more assertive sections for readers to understand without having to go back to RFC, every time.