Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.

John E Drake <jdrake@juniper.net> Thu, 14 February 2019 16:00 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108BA131096; Thu, 14 Feb 2019 08:00:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 Hs7zyjsAkLzf; Thu, 14 Feb 2019 08:00:37 -0800 (PST)
Received: from mx0b-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 CF6EA13104A; Thu, 14 Feb 2019 08:00:37 -0800 (PST)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1EFxtp8001106; Thu, 14 Feb 2019 08:00:35 -0800
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 : content-transfer-encoding : mime-version; s=PPS1017; bh=6EkWk+QUPSM7Q94PTmaw1T83aKDIMtK4FZIb9oaaVJI=; b=uDesaVEfLq99+NvcoUKhZdXTmbIPIdahAwsEfTc1Mt2zarc4Dd+iQd78BmYNh0AAapgW h9GSMPH1H2X93gM0CF9fWsHsHKOsIunROu9Hr0Xz8bNtRpUPlPl6hIf523aL13LkDZXC ntNEp32309AtJ9SRKfeuzqABlzlgSaSMzV771XDo7Let7xn5Y33ASznwNDNuUysmSzrb nDYak/xGcKs8g4nc61TxZIuNljYCG0PlQq6S0QlMQTQtNsC1auXAJt7aa7XO+KAA7KjH EvLF0vaqvuD7Sm2AX2QteaxFvimbpelGVihVwhFlK6WSILnZGefqXiFUmsRnGCrxt89k ow==
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp2051.outbound.protection.outlook.com [104.47.34.51]) by mx0a-00273201.pphosted.com with ESMTP id 2qmw7g97p7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Feb 2019 08:00:32 -0800
Received: from BYAPR05MB5029.namprd05.prod.outlook.com (20.177.230.211) by BYAPR05MB6677.namprd05.prod.outlook.com (20.178.235.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1643.9; Thu, 14 Feb 2019 16:00:24 +0000
Received: from BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7]) by BYAPR05MB5029.namprd05.prod.outlook.com ([fe80::b58f:10f1:a40b:abf7%4]) with mapi id 15.20.1622.016; Thu, 14 Feb 2019 16:00:24 +0000
From: John E Drake <jdrake@juniper.net>
To: Christian Hopps <chopps@chopps.org>, "lsr@ietf.org" <lsr@ietf.org>
CC: "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>, Aijun Wang <wangaijun@tsinghua.org.cn>
Thread-Topic: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
Thread-Index: AQHUxH3lvye7OP/ShEO8YRe07MhUsqXfc7VQ
Date: Thu, 14 Feb 2019 16:00:24 +0000
Message-ID: <BYAPR05MB5029A0885EDEC33D25560E17C7670@BYAPR05MB5029.namprd05.prod.outlook.com>
References: <sa6lg2md2ok.fsf@chopps.org> <008d01d4c40e$3e66d5a0$bb3480e0$@org.cn> <sa636oqtld8.fsf@chopps.org>
In-Reply-To: <sa636oqtld8.fsf@chopps.org>
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
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fcbad21d-034a-4160-a3f6-08d6929587ab
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600110)(711020)(4605077)(4618075)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB6677;
x-ms-traffictypediagnostic: BYAPR05MB6677:
x-microsoft-exchange-diagnostics: 1;BYAPR05MB6677;23:pPuatGoelEwU0105NyrHVFTdGrMVOpFMKcrmkVEFFtPokhYmcfuYi7eGwFaPzp8BtW8OduRCg7BeoP0lVCzb8WS0zU08YQY2xB32uMWtKwBTERyWaCvKMpVTUnGj5W4WLybGp4eTEgvNybnsg2pRAHJbcxMu4EGuVha3FS2sgLbVa2Fdit6TsGi1zkJDvZLvj7o+NnBD8uiXlqtQl3/ioQ+m7luJpUlGtSqcYZFh+KjDMZKr/JqPvTPF2zoUMn/DzTgU0p+eh+GDQSHuf95xlEMHw4QrNOFa7eS0QZckXyP6VQAus3TO4icYFotAOwf5eTgr+L1RE1P6GtwXtjC6Hnlt94pII3YDi0aj9qDu6pKLQnT6UAGQUZqgCgpf8cogGYHLvO2B8d1aNq8bo+AS5e+lyylsiUlfm5JeTE8aoaYVfUmZ4a/Q8N1lpC6CZLqUoEBuQfeI13a7RcrNgA8NGf3Np5peLBvDndNPHsdWhQUYZTg8RzBiJE8ikwFolJxHC9fBQMe1GxS2+VTD7g5H2qyka5VAjLqFRnJq2VesY3FB9t80hlJG4/WFfCBfG6tl6m7KOpAMr3hHK0l0/njoXuXtdHue3LRxnVBHeNQnoTYlYOBun3Va9lhXm61Cu3wXrZC0D812+psj6E5HQ9wTBf9Mk9xGox2t67moksRZCy6YO9gOgiTn7SLMUjioeCojjB//03AcABFjsHcxMAv93aVfMgDLxYz5iZ38b/15ifDVSaJ5WP1MiJ4RSQM+GmdSP6+Y/wg4rHhPdmhIIxtho3isK7/9iNoKJum/DruBAuor15Pz+Qe1eDg/HVHENQulooVvpiWAG9UhnHN0fe4uf9JYNNvCkgSVER9KYnvneARHWbXy7T7EwLxrRoXIMhcHU4v1Ks9SBL5yfA1yoJFh/PKxQahID/RvooEJm/y9uIVrO7bdPVIseLXOzX83lVpWkrzDaO9E7YcIrpcj4kp4KTAEsVwSjnJkspR3VvXhZfXWKOdSQ1/9zpQNur9S3hdRb323qQfaYm5iYWOwVo6jEObMBIAoHrBoSj0AoHpVG26irCMck7G/9PNblHw2bLlyI7ar8IJ9lxdGo28oryj+hwHBZ+h9XR4ng/3SOfFVb8nEVDdcoBCbyMWnit9JeaJi3WAHApuAFvt9L+dxEFpzUZSTFtxXYP+piVWtPjINYNuzC2qOjj7382aVJwUm10UGbKqhAxKi59TXxzjpW9IK/p2be9UCvnMKR/tsgiNIVvU=
x-microsoft-antispam-prvs: <BYAPR05MB66771897E98FCC8C16FC13CAC7670@BYAPR05MB6677.namprd05.prod.outlook.com>
x-forefront-prvs: 09480768F8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(39860400002)(346002)(376002)(136003)(199004)(189003)(13464003)(105586002)(224303003)(106356001)(486006)(316002)(14454004)(110136005)(3846002)(6116002)(26005)(25786009)(66066001)(8936002)(6246003)(74316002)(256004)(99286004)(33656002)(81166006)(81156014)(2906002)(561944003)(54906003)(97736004)(7736002)(53546011)(9686003)(305945005)(71200400001)(2501003)(71190400001)(86362001)(6506007)(102836004)(53936002)(229853002)(476003)(478600001)(68736007)(7696005)(6436002)(186003)(446003)(4326008)(11346002)(55016002)(76176011); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB6677; H:BYAPR05MB5029.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: HOsWnIOCupSczmnv8BojbiryiMICleN1B8BfNeQJx9s/PwztUePie/LS6gJFx9Mf8y3PLAUiHueKX5xxO9YhCSbzm++z2t0tWsmeEF0CNEsu6QWnwVs18MqO5A1eHe3FP/IURprQlmYG0AlZgO5JoCdvM8ydDBp9QONphICBTlXsDoRaH6HxK87Z9tWRsnL9hFsRSeKiufODTyATkjsdDwsAi+7TEwQfkhulrJ4OpFc3MxNg7NcjRrtUYA9iLOtrUNxa+DapQwYf14/qMi8sYvZDpGrvjYD3kQv9fvbUVzujsjkutI8TCb5DD/F6JQRTeKsh04oJ841irP94O42zyT/4hLVxxJyyg1RbHdBWQG+Kc11EtkfMqh8OCcwtMBtKIKDykjV62cbfrz7XIpAgu95dLSSDkupxAA2DHS4bIAc=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: fcbad21d-034a-4160-a3f6-08d6929587ab
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2019 16:00:24.1837 (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: BYAPR05MB6677
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-02-14_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 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-1810050000 definitions=main-1902140110
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/k8L3mUqzIC3yWPZP5kIktZ-lTRU>
Subject: Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2019 16:00:40 -0000

Chris,

Well put.

Yours Irrespectively,

John

> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of Christian Hopps
> Sent: Thursday, February 14, 2019 10:56 AM
> To: lsr@ietf.org
> Cc: lsr-chairs@ietf.org; lsr-ads@ietf.org; 'Christian Hopps'
> <chopps@chopps.org>; Aijun Wang <wangaijun@tsinghua.org.cn>
> Subject: Re: [Lsr] 答复: WG Adoption Call for draft-li-lsr-dynamic-flooding-02 +
> IPR poll.
> 
> 
> Hi folks,
> 
> It's not useful for people to be adding a bunch of extra qualifications and
> caveats to the adoption poll.
> 
> This is not a dual adoption poll. We are not calling for adoption of an unwritten,
> unfinished algorithm document. That makes no sense; we adopt reviewed
> acceptable work, not the promise of it. We're also not going to hold up
> standardizing the signaling work waiting on unfinished algorithm work, that's
> literally the opposite of the goal here which is to un-tie these two things so we
> can make progress on both in parallel.
> 
> Thanks,
> Chris.
> 
> Aijun Wang <wangaijun@tsinghua.org.cn> writes:
> 
> > Hi, Christian:
> >
> > Supports for the adoption of two drafts at the same time, in which
> > one(draft-li-lsr-dynamic-flooding-02) focuses on the centralized mode
> > and the other(draft-cc-lsr-flooding-reduction-01) focuses on the
> > distributed mode.
> >
> > The centralized mode for is one straightforward way to realize the
> > flooding reduction, and I admire Tony Li give his solution first. But
> > from the consideration of solution robustness, the distributed mode
> > may be more promising.
> > My consideration for distributed mode is that it should not cover only
> > the algorithm, more contents need to be standardized in future. Huaimo
> > has one good start point for distributed mode, and he also gives
> > abundant thoughts for the centralized mode that the current version of
> > draft-li-lsr-dynamic-flooding-02 has not covered yet.
> >
> > Proposal for the name of two drafts may be
> > draft-ietf-lsr-flooding-reduction-centralized-mode and
> > draft-ietf-lsr-flooding-reduction-distributed-mode.
> >
> >
> > Best Regards.
> >
> > Aijun Wang
> > Network R&D and Operation Support Department China Telecom Corporation
> > Limited Beijing Research Institute,Beijing, China.
> >
> > -----邮件原件-----
> > 发件人: Christian Hopps [mailto:chopps@chopps.org]
> > 发送时间: 2019年2月11日 18:45
> > 收件人: lsr@ietf.org
> > 抄送: lsr-chairs@ietf.org; lsr-ads@ietf.org; chopps@chopps.org
> > 主题: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR
> > poll.
> >
> >
> > Hi Folks,
> >
> > We are starting a 2 week adoption call on draft-li-lsr-dynamic-flooding-02.
> >
> > The aim of this document is to describe the problem space and
> > standardize a way to signal dynamic flooding information. It does not
> > standardize any specific algorithm for flooding topology creation.
> >
> > Authors please respond indicating if you are aware of any IPR related
> > to this work.
> >
> > We also have another draft (draft-cc-lsr-flooding-reduction-01) that
> > started as a distributed flooding topology algorithm and morphed into
> > that plus competing ideas on signaling of flooding topology
> > information. The intent after adoption of
> > draft-li-lsr-dynamic-flooding-02 is two-fold. One, the WG can discuss
> > adding any signaling ideas from this work to the adopted signaling
> > draft (with proper attribution given as appropriate), and two, for the
> > authors of draft-cc-lsr-flooding-reduction-01 to publish a new
> > document without the signaling portion and instead focus on their
> > flooding topology algorithm. This new focused document can be considered in
> parallel along with the other algorithm work that has been proposed.
> >
> > Flooding topology creation is seen as a hard problem for which we
> > don't expect a one-size-fits-all solution. Taking the steps outlined
> > above will help us move forward on the solutions.
> >
> > Thanks,
> > Chris & Acee.
> > LSR WG Chairs.