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

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Tue, 07 May 2019 18:51 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 56860120235; Tue, 7 May 2019 11:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 nQ0MWSo-p50Z; Tue, 7 May 2019 11:51:11 -0700 (PDT)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 CA4B7120228; Tue, 7 May 2019 11:51:10 -0700 (PDT)
Received: from pps.filterd (m0108156.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x47IofsU031961; Tue, 7 May 2019 11:51:09 -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=GbtqoSXkwmtS7+2goAc7/gUL5KTFduUUb33jw3w5HrY=; b=1V+3dCdPN6FcWI5m2BxdV7r4SrFvMkgNWrwqaU4FEicjb6SWhgTxpFK2Wpg8bfhnufaX apH3ipQhAAjMi8X80HZHCLxvbrEM8LVKlnVZGpkY4mHql1D5NKasw0X8hfCMwgrJrNyS J7nrTBbz7bUtmKw3ryy189InQwwwe3fdeb9MGrvj/LsM2aJfg6qjvFtecRlov7yEzU5o c3mBgND1WhbGW2G+EX9h5IwS6iFwQaQbuhtAw5od0RQ4ogdaPN/BZyVTwcJ8Cnzx6s7r QNSPCq0Tr8BrJzPWoa8k/dblIScFSxaTHHDe7Bf3ZRvLles8ZTMD4xUXisZpx2jzhK1n ZQ==
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp2056.outbound.protection.outlook.com [104.47.34.56]) by mx0a-00273201.pphosted.com with ESMTP id 2sbfn5801u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 07 May 2019 11:51:08 -0700
Received: from DM5PR05MB3548.namprd05.prod.outlook.com (10.174.242.153) by DM5PR05MB2940.namprd05.prod.outlook.com (10.168.178.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1878.11; Tue, 7 May 2019 18:51:06 +0000
Received: from DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::71a0:993e:dee4:3ebc]) by DM5PR05MB3548.namprd05.prod.outlook.com ([fe80::71a0:993e:dee4:3ebc%6]) with mapi id 15.20.1878.019; Tue, 7 May 2019 18:51:06 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>, Tarek Saad <tsaad.net@gmail.com>
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+CAAKMngIABGOvAgAMCjACAKWI9oA==
Content-Class:
Date: Tue, 7 May 2019 18:51:06 +0000
Message-ID: <DM5PR05MB3548CE8FF009A6936E4C5535D4310@DM5PR05MB3548.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> <CO2PR05MB24554DED1C246AA9227C1015D42D0@CO2PR05MB2455.namprd05.prod.outlook.com> <d24bb64f-18f5-73e2-f891-46d1a86dfe49@gmail.com>
In-Reply-To: <d24bb64f-18f5-73e2-f891-46d1a86dfe49@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-05-07T18:51:01.4955230Z; 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: [24.218.241.3]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d3267e80-196e-4d95-8fb5-08d6d31cf644
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:DM5PR05MB2940;
x-ms-traffictypediagnostic: DM5PR05MB2940:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <DM5PR05MB2940ED42E7807A12C303A221D4310@DM5PR05MB2940.namprd05.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0030839EEE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(39860400002)(346002)(366004)(396003)(199004)(37854004)(31014005)(189003)(76176011)(81166006)(53546011)(6436002)(54896002)(236005)(55016002)(53946003)(81156014)(52536014)(8936002)(6306002)(102836004)(6506007)(66476007)(66556008)(64756008)(66446008)(33656002)(73956011)(66946007)(25786009)(68736007)(316002)(4326008)(229853002)(76116006)(53936002)(86362001)(6246003)(110136005)(54906003)(66574012)(2501003)(478600001)(7696005)(6116002)(3846002)(446003)(11346002)(476003)(486006)(790700001)(606006)(66066001)(71200400001)(71190400001)(5660300002)(9686003)(74316002)(2906002)(256004)(14454004)(7736002)(99286004)(966005)(186003)(14444005)(8676002)(26005)(569006); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB2940; H:DM5PR05MB3548.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: yTDgNamJl98RUErWVl4AFThPWaKKL9/hbYJi1rXzSxbYhg32Dc1B54Bf1lr0ckTD5oYpauHzNNmtAyhhIfC6q9BlRgwyo+4/GyDOePj5t2iaArdy9Yz/Dp2DZXq3Id89FqOSjzuLlvjbtxU4M0o7YXojFPeX0Jj6Oy+I2TVWGNPZH8POXGL0PiJtGmEbi2BZPBZbQl2roCsSVjG9DlgI4lzHKwrGqZ8j9sLECZU/ivEHA4BHjSgQzE70H0zgBCQjJj3Vivgy/N9/g4ch/ujausZb5W74fuIQU1DzS3Z0qF0wRQria/PUNeNzJMsF0rL6nLqA66xhMBIaX0rbfxfcNiN2nFdu1lP0/CkZj3yj80YkAG9b+SdxmpYRaGtZq3OPV3cMa88aElPDH6uvPkc08IM7zzcQILyXVPWAXneZDGQ=
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB3548CE8FF009A6936E4C5535D4310DM5PR05MB3548namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: d3267e80-196e-4d95-8fb5-08d6d31cf644
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 May 2019 18:51:06.2008 (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: DM5PR05MB2940
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-07_10:, , 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-1905070120
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/YOOVB8gSuIdW9WRAxEroj7QrfRM>
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, 07 May 2019 18:51:15 -0000

Hi Huub, Tarek,

Based on your comments, I removed the text about RSVP-TE P2MP tunnel optimization and simply refer to the other document. Hope this will address your concerns.

https://datatracker.ietf.org/doc/draft-zzhang-mpls-rmr-multicast/

Thanks!
Jeffrey



Juniper Internal
From: Huub van Helvoort <huubatwork@gmail.com>
Sent: Thursday, April 11, 2019 6:51 AM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>et>; 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 [hvh-2] below.

Huub,

Please see zzh2> below.



Juniper Internal
From: Huub van Helvoort <huubatwork@gmail.com><mailto:huubatwork@gmail.com>
Sent: Monday, April 8, 2019 4:08 PM
To: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net><mailto:zzhang@juniper.net>; 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: 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.
[hvh-2] the draft should mention it because it may be a reason to apply the
optimization or not.

[hvh-2] if a leave is deleted, added, or changed all leaves will be notified and will
have to process the notification.


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.
[hvh-2] the merging requires processing resources.


 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.

[hvh-2] I would like to know why I should deploy this "optimisation",
and maybe others would like to know too.
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

Best regards, Huub.



--

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

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