Re: [pim] Call for adoption of sr-mpls-multicast-framework

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Wed, 15 August 2018 13:24 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58461129C6B for <pim@ietfa.amsl.com>; Wed, 15 Aug 2018 06:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 QAEghcW3FyrA for <pim@ietfa.amsl.com>; Wed, 15 Aug 2018 06:24:15 -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 4F1A4130E5A for <pim@ietf.org>; Wed, 15 Aug 2018 06:24:14 -0700 (PDT)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w7FDJ548015359; Wed, 15 Aug 2018 06:24:08 -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=v15llSk1VS2NN10Ox0podUxVwbWNXlemL6OqZhJ8tak=; b=Zxk2Ug9bl0NqcxUHL9dPMxFmi8rWaGJmKmjjxTsAc9c1YKJAslUKJoOKvI/gN82OBZou 9jNrkv+cFkUGSrYs2/vMwnGzA4H93IFMbPlHKuoKPfBobS44vTazclXFfTIIadc9i7wo U7fmbYugM3QDnvFJymQOe5XgWmmDv+sSlEuXv3od/KmThcrgYrx9+EMJ0tpKg/2gpq/U aMgQZIWwApx1W1AUqFvrLsbLti70+W/99GQXz5zFBAdwMYF6rJf/3ygGH2r2tEoVss6i 5D2v0c1rea/fsRVA2e+2K+zOL6Q7fwFbqJ3M2mTU0AMGiNmvGFDdp6nCZExQ4Rmb5n3h Fw==
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp0085.outbound.protection.outlook.com [216.32.180.85]) by mx0a-00273201.pphosted.com with ESMTP id 2kvmq2g0xj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 15 Aug 2018 06:24:08 -0700
Received: from BN3PR05MB2642.namprd05.prod.outlook.com (10.166.72.18) by BN3PR05MB2770.namprd05.prod.outlook.com (10.167.2.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1059.9; Wed, 15 Aug 2018 13:24:05 +0000
Received: from BN3PR05MB2642.namprd05.prod.outlook.com ([fe80::c0b9:8206:2890:5ea5]) by BN3PR05MB2642.namprd05.prod.outlook.com ([fe80::c0b9:8206:2890:5ea5%7]) with mapi id 15.20.1059.010; Wed, 15 Aug 2018 13:24:05 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: IJsbrand Wijnands <ice=40cisco.com@dmarc.ietf.org>, Michael McBride <Michael.McBride@huawei.com>
CC: "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [pim] Call for adoption of sr-mpls-multicast-framework
Thread-Index: AdQtssFIzPvft4cGQsCivyxneIMT5QCgXD0AARmjZFA=
Date: Wed, 15 Aug 2018 13:24:05 +0000
Message-ID: <BN3PR05MB26428DF5EFBB423B6D5A906AD43F0@BN3PR05MB2642.namprd05.prod.outlook.com>
References: <8CCB28152EA2E14A96BBEDC15823481A1CC89175@sjceml521-mbx.china.huawei.com> <3D4288A8-AD9D-45DB-81B0-2ED70125BE40@cisco.com>
In-Reply-To: <3D4288A8-AD9D-45DB-81B0-2ED70125BE40@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.0.400.15
dlp-reaction: no-action
x-originating-ip: [66.129.241.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR05MB2770; 6:a21ixqTj5bs/HEyQ9W1fMeyWJHAsN7HCKtsgXKKOpR7qHtbOFHf7TMHFAInHI8uyceXNSf5siMO9GcXr4cpa2RgGjTeDLJXrgEk8ffUmEsQLhShxD8APULf/ydjJCAby1qq6R4HBf7oqJO6my9PL2VzqlDjqNz2uqc2KyH3XWE8q4KUTDGda+FOkcBcuWT8CrxCyY257p9gWW+YtWtSghJrSLF/huJ5WC4HSh3bD6On1ui9JdIX0/c+IRHQ0lbH5ncHZO7bkaaVcT6Mg1kCrZyN5STnLxUrA9rOZJ+PBOrQm2yLIV9cWLRYvmREezDQJyx5VUio7hFyH1h/Wew/pKRYB8EvHotrULcKUvFS7w5exHaYudZ3Al62YJ00wk3EmjmQoQMAM+0xto3+Q++QskS7ZXS4qmPlZD9+v07MqMSTRcTxV+KyuiFIW6hH0Qpv1u8kTQBzbVVv/HPPTCnQITg==; 5:SM1Ea/2+0zX27Ces2G8W43woI39hShjy50+3W9IeKPjMqgYWbktA+eV0U/DWnYIgciHHSBC9Y/VMI7sJZY+Uju9H8X8tpLkNk1IC34zkKNNV8ngXIxTIIn4/A3wWZP7HD4e3XxR3o1JABzWTLIBN6zG2EowDZebBjNpIb1VokxA=; 7:AXBf8yfd4rOfU5cnhpw7/Go/fIBDuU7fVCGQF7jByXDUMn0xEmw2UncepgVW48ls3m5j47qqDq77AV2zUTBhzn5E6l3ziej6BUNtGu9qi7N6toNenW9rmmaRiJdtU/LNfkGLSPU72yVBrbafnI/a+tKA1izCG44G9JNYj5GYvzM1EUpuAWSXYDRB34O3FhHQZFaE2zc8J53ddVjr7EGz/exi8GOvj+59d0YC98fa4j7qJXmSWkwIyAx+Nhc3OpO8
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2bbc33df-302f-4e04-92c3-08d602b25fdd
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(4618075)(2017052603328)(7153060)(49563074)(7193020); SRVR:BN3PR05MB2770;
x-ms-traffictypediagnostic: BN3PR05MB2770:
x-microsoft-antispam-prvs: <BN3PR05MB2770F3C09BC0F505D00A4BBAD43F0@BN3PR05MB2770.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(50582790962513);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:BN3PR05MB2770; BCL:0; PCL:0; RULEID:; SRVR:BN3PR05MB2770;
x-forefront-prvs: 07658B8EA3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39860400002)(376002)(136003)(396003)(346002)(199004)(189003)(13464003)(478600001)(74316002)(45954006)(105586002)(966005)(14454004)(11346002)(476003)(486006)(446003)(102836004)(2906002)(106356001)(81156014)(575784001)(81166006)(305945005)(8676002)(86362001)(25786009)(19627235002)(97736004)(8936002)(110136005)(53546011)(99286004)(33656002)(68736007)(186003)(4326008)(7696005)(5250100002)(53936002)(6246003)(7736002)(3846002)(6116002)(6436002)(316002)(5024004)(66066001)(99936001)(6306002)(6506007)(9686003)(5660300001)(2900100001)(55016002)(26005)(256004)(76176011)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR05MB2770; H:BN3PR05MB2642.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-microsoft-antispam-message-info: JCHEbqo3dsn6WmCx8/vsbxw/d9bmI/mJHNcfa/8dBlUJdEnXIc2Vu3AFjm74rGPKARMY6JeniPzvZXx83y2WaqExomhIOxtSGKI8LtXL2DCkDgVIFFiOlQSjKe7O8R1UzXiq2DTKzma89QG4T5HWcxQyyIMiAATJvsAveZa8eo0W0WglUPZSiANztSKAMuS+euN/+yDeSCyfB62MaMsZPPYXS9F1GWQ6zZVAmugHC+zPlGAv4a1g1hhhEDWOHEscXV3LehY+jC8RBLxwv0jhPpkz58vCbgEmQTD6/dS36Xdv1QCCN9DyYYcyv/IHyolZda0qjRB27lHCw9lSHi6faF4iyp9Cn6AoHcSTEAs4edk=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_002_BN3PR05MB26428DF5EFBB423B6D5A906AD43F0BN3PR05MB2642namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 2bbc33df-302f-4e04-92c3-08d602b25fdd
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Aug 2018 13:24:05.2722 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR05MB2770
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-08-15_04:, , 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=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1808150144
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/zzUJX_FWLkBEiR-ALZV9R1eOGnQ>
Subject: Re: [pim] Call for adoption of sr-mpls-multicast-framework
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2018 13:24:18 -0000

I also share the concerns that have been said by others, and I object to the adoption of this document.

As I spoke at the mic in our Montreal session, this is similar to MOSPF and still maintains per-tree state in the core on roots, leaves and branch points (the only saving compared to MOSPF is that there is no state on other nodes on the tree, i.e. nodes that simply forward but not replicate an incoming packet). Compared to PIM or existing P2MP technologies, there is way more control plane state throughout the network in that it floods membership information everywhere.

A few of us prepared an informational draft "Multicast in SR Networks" (draft-zzhang-pim-sr-multicast - see attached email) that exams all options that are available or have been proposed (including this draft-allan-pim-sr-mpls-multicast-framework). I think we should have a good review and discussion on various options before we adopt this.

Thanks.
Jeffrey

> -----Original Message-----
> From: pim <pim-bounces@ietf.org> On Behalf Of IJsbrand Wijnands
> Sent: Thursday, August 9, 2018 6:56 PM
> To: Michael McBride <Michael.McBride@huawei.com>
> Cc: pim@ietf.org
> Subject: Re: [pim] Call for adoption of sr-mpls-multicast-framework
> 
> Hi,
> 
> I'm apposed to the adoption of this draft.
> 
> I share the concerns that Eric and Toerless have expressed.
> 
> I also think a more high level discussion is needed to determine whether we
> need an other state-full protocol to build multicast trees. This draft proposes to
> create multicast state by using the IGP. Are the benefits of that so significant,
> compared to existing protocols, to justify building it? There will still be state,
> which will lead to convergence issues and complexity in operating it. Claiming
> that this idea follows the SR architecture because state is carried in the IGP is
> not a convincing argument.
> 
> Thx,
> 
> Ice.
> 
> 
> > On 6 Aug 2018, at 20:24, Michael McBride <Michael.McBride@huawei.com>
> wrote:
> >
> > Hello good people,
> >
> > Today begins a two week call for adoption of draft-allan-pim-sr-mpls-
> multicast-framework-00 which was presented in Montreal. There was a good
> discussion in the meeting and now it’s time to gauge interest in adoption on
> the list. Please respond and let us know what you think about adopting this
> draft.
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_id_draft-2Dallan-2Dpim-2Dsr-2Dmpls-2Dmulticast-
> 2Dframework-2D00.txt&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-
> ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&
> m=NoOAWfggpxm4roCZiMhp3okMVUF5wxSwu-
> DLHT1XUwo&s=fxb5b29a_7aafJd-3qsPbz_77rcBxXMuRkRp_cIKBRY&e=
> >
> > thanks,
> > mike
> > _______________________________________________
> > pim mailing list
> > pim@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_pim&d=DwIGaQ&c=HAkYuh63rsuhr6Scbf
> h0UjBXeMK-
> ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&
> m=NoOAWfggpxm4roCZiMhp3okMVUF5wxSwu-DLHT1XUwo&s=J1gx6t-cG_-
> aUSzxW8MxQwyuS1yglnQhBohO_1oLEzs&e=
> 
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_pim&d=DwIGaQ&c=HAkYuh63rsuhr6Scbf
> h0UjBXeMK-
> ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&
> m=NoOAWfggpxm4roCZiMhp3okMVUF5wxSwu-DLHT1XUwo&s=J1gx6t-cG_-
> aUSzxW8MxQwyuS1yglnQhBohO_1oLEzs&e=
--- Begin Message ---
A new version of I-D, draft-zzhang-pim-sr-multicast-00.txt
has been successfully submitted by Zhaohui Zhang and posted to the
IETF repository.

Name:		draft-zzhang-pim-sr-multicast
Revision:	00
Title:		Multicast in SR Networks
Document date:	2018-08-15
Group:		Individual Submission
Pages:		8
URL:            https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_internet-2Ddrafts_draft-2Dzzhang-2Dpim-2Dsr-2Dmulticast-2D00.txt&d=DwICaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=8jo9o94w8A8EYyBO9Ymv8tt4GtjWUllvPlZajxHPV58&s=T5XwI5JV07xnGVikpEnTJhY9bMg-cSLXO53qCVfXYBM&e=
Status:         https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dzzhang-2Dpim-2Dsr-2Dmulticast_&d=DwICaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=8jo9o94w8A8EYyBO9Ymv8tt4GtjWUllvPlZajxHPV58&s=cJB2FH8PMFDWjrAF7fxXA3B4OtUuREJ7X16D_M_Z3Oc&e=
Htmlized:       https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dzzhang-2Dpim-2Dsr-2Dmulticast-2D00&d=DwICaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=8jo9o94w8A8EYyBO9Ymv8tt4GtjWUllvPlZajxHPV58&s=C7UZ8PCvUHMHizFwlAlO34CByVOW4hr3UjTGiZNTX1s&e=
Htmlized:       https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dzzhang-2Dpim-2Dsr-2Dmulticast&d=DwICaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=8jo9o94w8A8EYyBO9Ymv8tt4GtjWUllvPlZajxHPV58&s=C4YFPXbkIhy36l501IvtEsDde971fUJksPcb4cDOwko&e=


Abstract:
   With Segment Routing (SR) architecture [rfc8402], a unicast flow can
   be routed through an SR network following an explicit path specified
   in the packet, w/o the need for per-flow state in the network.  As a
   result, the otherwise needed protocols to signal the per-flow unicast
   state can also be removed from the network.  This document discusses
   options for multicast in an SR network.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--- End Message ---