Re: [mpls] MPLS-RT review of draft-zzhang-mpls-rmr-multicast

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Tue, 09 April 2019 13:04 UTC

Return-Path: <zzhang@juniper.net>
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 048711207ED; Tue, 9 Apr 2019 06:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level:
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.363, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 iW81BvfJmanp; Tue, 9 Apr 2019 06:04:55 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5563D1207EE; Tue, 9 Apr 2019 06:04:54 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x39D4eDf011747; Tue, 9 Apr 2019 06:04:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=PPS1017; bh=vzKPyWjH6gbnAviynGvbhCs+nCAUkhCB7ZKwE/0kuVc=; b=g3CN5kG2+RLmVFUlYpzA6a9Yuek9v/IF02w5jxNWpF5V+Pv9Nzfzd33FAtJB2Hr4wc2C ekuJVXqnecKwV6y8MY06YreCDR0RDooRZxTqYE6zrSDgpOEMwJ8J4AI52ud2Nb0a4/1D BY6Wn5dZ0KqFyInpFJE9o3KLaM2RkojKUd4MzKXJ6DNzuBjcCZsJW8CFTW1XDth/oH5I rRc1VCVcCY0OwzE4bSj7waAai3UyYVCjtjMzV5bBOBxuqF/3JrmHmfnhxLXI4LNYFQxH 2ipWDwmtqrZx7EpLSZwqtm1orUaj7SHpQ9EdYyomsZLYRMzMTNtW9rESL5/NxzcbJFis vw==
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp2056.outbound.protection.outlook.com [104.47.40.56]) by mx0b-00273201.pphosted.com with ESMTP id 2rrrd18cad-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 09 Apr 2019 06:04:51 -0700
Received: from CO2PR05MB2455.namprd05.prod.outlook.com (10.166.95.137) by CO2PR05MB2760.namprd05.prod.outlook.com (10.174.192.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.9; Tue, 9 Apr 2019 13:04:48 +0000
Received: from CO2PR05MB2455.namprd05.prod.outlook.com ([fe80::81e2:bbe8:6851:16b2]) by CO2PR05MB2455.namprd05.prod.outlook.com ([fe80::81e2:bbe8:6851:16b2%6]) with mapi id 15.20.1792.007; Tue, 9 Apr 2019 13:04:48 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
CC: "draft-zzhang-mpls-rmr-multicast@ietf.org" <draft-zzhang-mpls-rmr-multicast@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: MPLS-RT review of draft-zzhang-mpls-rmr-multicast
Thread-Index: AQHU5UdoXX/k5SRry0WfLJCBg3kMV6YyGKsAgAAHF+CAAKMngIABGOvA
Content-Class:
Date: Tue, 9 Apr 2019 13:04:48 +0000
Message-ID: <CO2PR05MB24554DED1C246AA9227C1015D42D0@CO2PR05MB2455.namprd05.prod.outlook.com>
References: <0df832d7-8389-e9dd-95aa-46d8c8d06da5@pi.nu> <be4eb733-b0a2-68d6-0442-94c5129da516@gmail.com> <CO2PR05MB2455B56BCF23C0059D4EB90DD42C0@CO2PR05MB2455.namprd05.prod.outlook.com> <beaab152-6a9f-9e0a-8cc8-6c6c6cee5584@gmail.com>
In-Reply-To: <beaab152-6a9f-9e0a-8cc8-6c6c6cee5584@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.100.23
dlp-reaction: no-action
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Owner=zzhang@juniper.net; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2019-04-09T13:04:41.9092707Z; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Internal; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Application=Microsoft Azure Information Protection; MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Extended_MSFT_Method=Automatic; Sensitivity=Juniper Internal
x-originating-ip: [116.197.188.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ee1214de-ea3d-43da-ef6e-08d6bcebf20b
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:CO2PR05MB2760;
x-ms-traffictypediagnostic: CO2PR05MB2760:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <CO2PR05MB2760BD4B873CF7C50304B566D42D0@CO2PR05MB2760.namprd05.prod.outlook.com>
x-forefront-prvs: 000227DA0C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(396003)(346002)(376002)(136003)(189003)(199004)(31014005)(37854004)(446003)(5660300002)(102836004)(8676002)(97736004)(6506007)(4326008)(2501003)(68736007)(256004)(26005)(6436002)(99286004)(53546011)(25786009)(33656002)(7736002)(74316002)(11346002)(93886005)(476003)(186003)(52536014)(81156014)(81166006)(7696005)(478600001)(14444005)(76176011)(14454004)(8936002)(486006)(55016002)(66574012)(316002)(106356001)(229853002)(6246003)(86362001)(9686003)(6306002)(236005)(53946003)(71190400001)(790700001)(110136005)(54896002)(3846002)(6116002)(2906002)(71200400001)(53936002)(54906003)(66066001)(105586002)(579004)(559001)(569006); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR05MB2760; H:CO2PR05MB2455.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: AJxUut1JBZ/m9k4ApSDEIJMfOCyyC4oON3tRJItG0WqV0ON0xqqpFnTf5QctvqRYtDKK5bkwqFikzy2IXKfKEeMMcM19JQrlg450FWVyRYMsmGdEVLSlQgRuaqyab/x12jZovtC/tzVtGlqlotuQvWJbsHyJtyTGxjb9d/a2Aloh4vw+yUVEsZRGP3Jlb4mjcqqPiAK1C0GHoBqPTDrFAt5O2qHTun7z/nNWnjG4rKRnVMkDEeqjZMHW/xRrVDUTMY758lZSU2OSiYsu/mCffKRj9EL4xLG37EnkRdRlD5kSg97ctVe2PCEJNTLwSGrAcpq93Bvg8533NSq58nuvPKo17A1bDr7CAxn0n+DmEiXjAHZ92NTpUTHHgys339bfq/bZWYU3yIeUhG1iOvGbqtroo2hru4+7t8rPkdiL+oQ=
Content-Type: multipart/alternative; boundary="_000_CO2PR05MB24554DED1C246AA9227C1015D42D0CO2PR05MB2455namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: ee1214de-ea3d-43da-ef6e-08d6bcebf20b
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Apr 2019 13:04:48.2367 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR05MB2760
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-09_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904090083
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/MiYmWbORIN1ukvIY8V8VRQ4Pc6Q>
Subject: Re: [mpls] MPLS-RT review of draft-zzhang-mpls-rmr-multicast
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 09 Apr 2019 13:04:58 -0000

Huub,

Please see zzh2> below.



Juniper Internal
From: Huub van Helvoort <huubatwork@gmail.com>;
Sent: Monday, April 8, 2019 4:08 PM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>;; mpls@ietf.org
Cc: draft-zzhang-mpls-rmr-multicast@ietf.org; mpls-chairs@ietf.org
Subject: Re: MPLS-RT review of draft-zzhang-mpls-rmr-multicast

Hello Jeffrey,

Please see my response in-line [hvh].

Hi Huub,

Thank you for your review and comments. Please see zzh> below.



Non-Juniper
From: Huub van Helvoort <huubatwork@gmail.com><mailto:huubatwork@gmail.com>
Sent: Monday, April 8, 2019 5:58 AM
To: mpls@ietf.org<mailto:mpls@ietf.org>
Cc: draft-zzhang-mpls-rmr-multicast@ietf.org<mailto:draft-zzhang-mpls-rmr-multicast@ietf.org>; mpls-chairs@ietf.org<mailto:mpls-chairs@ietf.org>
Subject: MPLS-RT review of draft-zzhang-mpls-rmr-multicast

All,

I've been selected as an MPLS-RT reviewer for draft-zzhang-mpls-rmr-multicast,
which is currently a candidate for MPLS WG adoption.

In the abstract is stated:

   With Resilient MPLS Rings (RMR), although all existing multicast

   procedures and solutions can work as is, there are optimizations that

   could be done for RSVP-TE P2MP tunnel signaling and Fast-ReRouting

   for both mLDP and RSVP-TE P2MP tunnels.
I have carefully read the draft but I could not find any justification
for the optimisation that could be done.

Zzh> By "justification", do you mean "need"? I thought the following text provides that:

   For a conventionally signaled RSVP-TE P2MP tunnel, an ingress LSR
   discovers leaves and signals one sub-LSP for each leaf.  Even though
   the forwarding state is merged at each hop (i.e, one incoming label
   mapping to multiple outgoing entries), the control plane maintains
   individual sub-LSP state.  This leads to lots of redundant state on
   routers close to the ingress.
[hvh] "lots of state" - can you be more specific? is the redundancy 10% or 90% ?

Zzh2> Depending on how many leaves you have. With traditional RSVP-TE P2MP, there is one sub-LSP to each leaf. If you have 20 leaves, the saving is 95% (I mean you only need to maintain 5% of state compared to traditional way). If you have 10 leaves, the saving is 90%. I don't think the draft needs to quantify it.


Zzh> Or do you mean "why" the optimization COULD be done? The key is that this is a ring, and:

   ... As the PATH message passes along the ring, the leaves
   send RESV messages, but only one RESV message reaches the tunnel
   ingress.
[hvh] can you explain why only one RESV message reaches the tunnel ingress?

Zzh2> Because only one PATH message is sent, and the RESV state gets merged accordingly along the way.


 Zzh> If you mean "how" it is done, I thought the following describes it:

   ... With RMR, this can be optimized such
   that only a single LSP is signaled, with all the leaves listed in the
   PATH message.  As the PATH message passes along the ring, the leaves
   send RESV messages, but only one RESV message reaches the tunnel
   ingress.

   The ingress LSR may also send PATH messages in both directions, so
   that the tunnel is set up in such a way that minimum delay is
   incurred for traffic to reach all leaves.  Alternatively, the ingress
   may send PATH message only in one direction for best bandwidth
   utilization.  For example, a leaf D is three hops away from the
   ingress A in clockwise direction (A,B,C,D) and four hops away in the
   other direction (A,E,F,G,D), but G is also a leaf so it may be better
   to just send the PATH message in the anticlockwise direction.

   Each router establishes forwarding state accordingly.  Transit
   routers switches traffic towards downstream.  A transit router could
   also be a leaf router and in that case it does "drop and continue" -
   sends traffic off the ring and switches traffic downstream.


2.1.  Tunnel Protection and FRR

   Each node on a ring signals two counter-rotating MP2P RSVP-TE LSPs to
   itself.  As these LSPs are self-signaled after the discovery of the
   ring, they can be used to protect P2MP LSPs on ring.  So neither mLDP
   nor RSVP-TE has to setup a separate P2P bypass LSPs for link and node
   protection.
[hvh]  This is clear.


I also did not find any indication how this optimisation has to be
deployed. Do all the nodes in the ring, or in the network have to
support this optimisation before it becomes effective.

Zzh> The context is RMR - Resilient MPLS Ring. All routers on the ring need to support RMR and the multicast optimization for this to be effective. I can make that clear.
[hvh] OK. Thanks.


 I think these issues have to be documented before this draft can
be adopted as WG draft.

Zzh> Besides explicitly stating that all routers on the ring need to support the RSVP-TE P2MP optimization for it to be effective, please advise further how the first issue can be better documented.
[hvh] when you use the word "optimize" I expect an indication of
the effect of the optimization on performance, or used resources.

Zzh2> I see. The optimization is on (simpler) procedures and (less) resources. I don't think we need to quantify it.
Zzh2> I will update the draft to point out that all routers on the ring needs to support the optimization - please let me know if that is enough.
Zzh2> Thanks!
Zzh2> Jeffrey


Cheers, Huub.




--

================================================================

Always remember that you are unique...just like everyone else...