[mpls] MPLS-RT comments on draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp-08

"Eric Osborne (eosborne)" <eosborne@cisco.com> Wed, 25 July 2012 15:47 UTC

Return-Path: <eosborne@cisco.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 7AC2D21F866E for <mpls@ietfa.amsl.com>; Wed, 25 Jul 2012 08:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 g9RwWSFwdB09 for <mpls@ietfa.amsl.com>; Wed, 25 Jul 2012 08:47:41 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id AB99821F8666 for <mpls@ietf.org>; Wed, 25 Jul 2012 08:47:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=eosborne@cisco.com; l=1745; q=dns/txt; s=iport; t=1343231261; x=1344440861; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=/miOOERPtV48QCJ9hnH2xkoi6dQ/afHcip6cSHfIk7U=; b=JH6HSCsDwnpnP7q1xyiEazlVWW0sRuDMURh3K0hhwE+npiIPXs47STmT Nm2vcUgKOmzV3Wae3Ypdz7Mg19Aand3MfM8tjkn9R3xiwoXGZoeLbVQWx Rb0/zCcQ5WJmKBiFjsTWDhCA2MBDTP/pwfcXPiR4stBym9yGHfQTpRuDX c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAB4UEFCtJV2d/2dsb2JhbABFuWOBB4IiAQQSASc/EgEqFEImAQQBDQ0ah2ubIaBNkWFgA6NwgWaCXw
X-IronPort-AV: E=Sophos;i="4.77,653,1336348800"; d="scan'208";a="105249091"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 25 Jul 2012 15:47:41 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q6PFlfQb010187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Jul 2012 15:47:41 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.118]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0298.004; Wed, 25 Jul 2012 10:47:40 -0500
From: "Eric Osborne (eosborne)" <eosborne@cisco.com>
To: "draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp@tools.ietf.org" <draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp@tools.ietf.org>, "mpls-chairs@tools.ietf.org" <mpls-chairs@tools.ietf.org>, "martin.vigoureux@alcatel-lucent.com" <martin.vigoureux@alcatel-lucent.com>, "tnadeau@juniper.net" <tnadeau@juniper.net>, "Gregory Mirsky (gregory.mirsky@ericsson.com)" <gregory.mirsky@ericsson.com>
Thread-Topic: MPLS-RT comments on draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp-08
Thread-Index: Ac1qfG7TgDIuSC+YR7STXOHL/wRWoA==
Date: Wed, 25 Jul 2012 15:48:16 +0000
Message-ID: <20ECF67871905846A80F77F8F4A2757203537A@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.98.23.84]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19062.004
x-tm-as-result: No--29.923100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: [mpls] MPLS-RT comments on draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp-08
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: Wed, 25 Jul 2012 15:47:42 -0000

These are my review team comments on draft-ali-mpls-inter-domain-p2mp-rsvp-te-lsp-08.  

* Is the document coherent?
 
It needs work.  The formatting is off (try to print the pdf version of the txt doc and you'll see what I mean).  It needs a serious editorial cleanup - for example, section 4.1/4.2 refer to a flag as both Recording and Recording Request, and another as Re-merge Presence and Re-merge Present.  It also has a structure that makes it hard to follow, and a large number of SHOULDs where I think there ought to be MUSTs.


* Is it useful (ie, is it likely to be actually useful in operational networks), and is the document technically sound?  

I believe that this document solves the problem it purports to solve.  It does so largely by adding three bits and an error code to extend existing p2mp single-area procedures across domain boundaries.  I think at its heart it is technically sound, although its current state makes it hard to follow.


* Is the document ready to be considered for WG adoption?

There are three parts to this question: technical suitability, document quality, and desirability.

The document seems technically suitable; the procedures it defines are a good start to solving the problem, and that's what a document needs to be before WG status.

As I said above, the quality is not quite there.

As far as desirabilty...I have reviewed v08 of the document.  v00 was posted in July of 2008, so the doc is quite old.  Although I buy into the general idea that things which work in a single domain should work across domains, I'd like to see whether this document has interest from others, primarily operators.  



eric