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

"Mankamana Mishra (mankamis)" <mankamis@cisco.com> Thu, 14 February 2019 23:43 UTC

Return-Path: <mankamis@cisco.com>
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 05AAD1289FA; Thu, 14 Feb 2019 15:43:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 w_O3jHDjzKhU; Thu, 14 Feb 2019 15:43:38 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4813124C04; Thu, 14 Feb 2019 15:43:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2538; q=dns/txt; s=iport; t=1550187817; x=1551397417; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=5e5sq7aUJAT+oxH1ObMsuH3TJD0mOANnerUNa3fvaKQ=; b=mUMb7ztTTy7j74jIAXwqGPoFVv9XMUnKxXdx/UfDFH5MzcuWLaein3/1 cUkFz0yp9QcmkCmeWlM2xwALcgU3k7brIyeZ+S2zrKB4Qss00PZKM7yxR 0CF/EGw66EYu9Kd8qCdzE6F7+EBW6BdpiYw/nmdhuJt4aajPI3s6ErXhp E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BdAABs/GVc/5pdJa1kGgEBAQEBAgEBAQEHAgEBAQGBZYIDgWonCoN8lAqCDZoOCwEBhGwCF4NMIjgSAQMBAQIBAQJtKIVKAQEBBB0GEUUMBAIBCA4DAwECAwImAgICMBUICAIEAQ0FG4MFgXOrLIEvhUSEcYELizkXgUA/gTgfgkyICjGCJgKjLgkCklIZgW6FVIsxiWsJRpFxAhEUgSc2IYFWcBVlAYJBkF1BMY9HgR8BAQ
X-IronPort-AV: E=Sophos;i="5.58,370,1544486400"; d="scan'208";a="516971666"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Feb 2019 23:43:36 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x1ENha1l021314 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Feb 2019 23:43:36 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 14 Feb 2019 17:43:35 -0600
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1395.000; Thu, 14 Feb 2019 17:43:35 -0600
From: "Mankamana Mishra (mankamis)" <mankamis@cisco.com>
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>
Thread-Topic: [Lsr] WG Adoption Call for draft-li-lsr-dynamic-flooding-02 + IPR poll.
Thread-Index: AQHUwfcyZQNJFRTMu0ukLKJH0mg+fKXf2L2A
Date: Thu, 14 Feb 2019 23:43:35 +0000
Message-ID: <FF022A07-E28C-4EA4-8A73-36FE9F706F34@cisco.com>
References: <sa6lg2md2ok.fsf@chopps.org>
In-Reply-To: <sa6lg2md2ok.fsf@chopps.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.204.190]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0CF0E9BFD8A58445A060795DE8145214@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/plVX1gvnlOfKpVUxNHitsVdkot4>
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 23:43:40 -0000

Support. 

Thanks 
Mankamana 
 

-----Original Message-----
From: Lsr <lsr-bounces@ietf.org> on behalf of Christian Hopps <chopps@chopps.org>
Date: Monday, February 11, 2019 at 2:47 AM
To: "lsr@ietf.org" <lsr@ietf.org>
Cc: "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>, "chopps@chopps.org" <chopps@chopps.org>
Subject: [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.