IETF Logo Mail Archive

Re: [Idr] IPR Call for draft-li-idr-flowspec-srv6

Huaimo Chen <huaimo.chen@futurewei.com> Tue, 03 March 2020 17:34 UTC

Return-Path: <huaimo.chen@futurewei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D27DD3A2404 for <idr@ietfa.amsl.com>; Tue, 3 Mar 2020 09:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 cs8-7RmmnWD1 for <idr@ietfa.amsl.com>; Tue, 3 Mar 2020 09:34:06 -0800 (PST)
Received: from NAM11-CO1-obe.outbound.protection.outlook.com (mail-co1nam11on2115.outbound.protection.outlook.com [40.107.220.115]) (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 9EEB53A2403 for <idr@ietf.org>; Tue, 3 Mar 2020 09:34:05 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IIXw7cuSyO8aL9y7QFYAvi1aKOzxEsqUNMDZ5/489tN00DWzs2boh2TUcU8MtIhpJrxOfAPNVDmmJw5/dcVanWmtNln5m90/rAobLQj6Mx8Lg0zLi9tQFVTRQdRTm5oUk9DSRtzWeBV2LT/An/98NS/pyJy0fx/wEWqSTfd4E08wXXe8WFaIT2NRMG6AskXz4BO3BbYSo4V/oY6/vfDhj1NZUhUXG5FGiE9TZz7jXrUB6zX9lofQHwnrJRUAXjQTxsIwHILYLrYRp2z6bc5SUcGxZq9F9Zu/BwwiJwoGl42Fn5BmI4vn2DlmsWOuv4IyR2aiGdysKm6CBOmFBf1GCw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=dkidFITkf/+UV/VXt4w+pUOK5FSNk4oR9JxGajqLsCE=; b=RErd0C8dXf1dUOsiyWnWc5CyhqU9DgLGKM+sUPwki2/CKe6/Swyn45wwfXgerdjVvJdbIL4oK52EfAlgx7R1/wloZOtXQ0g3Yks55ssoaJoF9CDfZvrRRaU/pCJl3/m/gE/HvKvQkEFffzu8RGU2ub39/NjS4Php9uSKCBRI08POa3sKeQAmdmbsPZhU1/oeindJhUll8zOxVhZJ/O8wV1KxeJuduXE+731M2w9GR+VTHmJOBEpHPJJqU/4cObMIjqcYBhPzjoCxvuksqc944fy06x4x2+gUPEntYQ27HC+B2NlmKvPZZH5Uid/UxfxMA6muEdtpYgME8G1KC8cUTQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;bh=dkidFITkf/+UV/VXt4w+pUOK5FSNk4oR9JxGajqLsCE=; b=OjcJi0AQ3wFI2a1eUzABn9URB4WqpuXX72c3CY2gRG5WkESP6gl6s5YS9BLROglHvgDj2D/idmODtsycZ3HF+gq/fUIqB2R3X6DoCUvIhudqpkL4T+QODuwUcBzOD7MQY1987T0nu8hJI+FGWrR4p0u8YhPi77VWbhA0PreP6yM=
Received: from BY5PR13MB3651.namprd13.prod.outlook.com (2603:10b6:a03:22e::19) by BY5PR13MB2950.namprd13.prod.outlook.com (2603:10b6:a03:185::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2793.5; Tue, 3 Mar 2020 17:34:03 +0000
Received: from BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::789b:f4a:c3e3:e921]) by BY5PR13MB3651.namprd13.prod.outlook.com ([fe80::789b:f4a:c3e3:e921%7]) with mapi id 15.20.2793.011; Tue, 3 Mar 2020 17:34:03 +0000
From: Huaimo Chen <huaimo.chen@futurewei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IPR Call for draft-li-idr-flowspec-srv6
Thread-Index: AdXrF6YefQ/aBuJURImPFwA7se+WjAAbOtuQAX9K3s0=
Date: Tue, 03 Mar 2020 17:34:02 +0000
Message-ID: <BY5PR13MB3651DC77E2C97EB6BFC4A260F2E40@BY5PR13MB3651.namprd13.prod.outlook.com>
References: <000701d5eb18$71a02200$54e06600$@ndzh.com>, <5A5B4DE12C0DAC44AF501CD9A2B01A8D936450D6@DGGEMM532-MBX.china.huawei.com>
In-Reply-To: <5A5B4DE12C0DAC44AF501CD9A2B01A8D936450D6@DGGEMM532-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=huaimo.chen@futurewei.com;
x-originating-ip: [2601:199:4300:8e5a:1892:e8dc:1d57:128c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8e2ff367-ab09-4c1f-6575-08d7bf9910eb
x-ms-traffictypediagnostic: BY5PR13MB2950:
x-microsoft-antispam-prvs: <BY5PR13MB2950B609217F9AFFBB4E8920F2E40@BY5PR13MB2950.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 03319F6FEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(346002)(376002)(396003)(39850400004)(366004)(189003)(199004)(316002)(478600001)(110136005)(6506007)(66476007)(64756008)(66446008)(66556008)(81156014)(2906002)(66946007)(8936002)(81166006)(86362001)(53546011)(186003)(8676002)(55016002)(7696005)(52536014)(44832011)(19627405001)(33656002)(9686003)(5660300002)(71200400001)(76116006); DIR:OUT; SFP:1102; SCL:1; SRVR:BY5PR13MB2950; H:BY5PR13MB3651.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: wGJEHNr3ezMacs+e6AaqwVLL/hr9qEPaJG6tuGRJVoCZTTNZi6LNmiCOQP9old3MGSHUiwZZw/0tPvTxCzGk2ZBkmHdk6qWW6I2+afwCOh7Y9HGbYbWPBD45GIlP7eXlKL8BIYaQ+Mya3iXrEykB0v0dc1/+mf2ianSGvxoF7FKUcKWwRCyhA/lLwrpcCmekFdgywSuYke5LAI0RWtSyM009IvS+VQZdF4GUXe/UBM0dEBGu26Z1aAYMB8/8WC583pH5LW8GVIT20vq5twh3bCz3QKDIHTtxRUNZogQirFF9LasvrJ+Ew7+G+fytrofi2ZcBBYW81oC+Sl0ZbpT1XGy4M/Mj8+awF5DMc7K4uuy/yFvwz+dYcWzGN10TJR/IHtHKExg+p6ty2J5AmhT0tGp55mNLLY9OhIhRfzJtmPprZHDyw8QVUC99Ru7pvsaE
x-ms-exchange-antispam-messagedata: DJ40NdrqFZ2q0GupkroeoK+ccNsoc+ooRjYmTVT3dOeJi7GRrpWC3GSZqpkjsLE1CCQHhQgt8/rO5X11OUfykwEyeja/nnp22t7+3E3FExbZXR+M6JfI7xJdIWbch5IyqgaRJYlFIOGvPK/e4wqn01OEhXZ4vkBB+q5DFVSHssFShj/wUY3UrxNzvJHitb8ur80hKTnMTC+SF5oFhg2QCQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BY5PR13MB3651DC77E2C97EB6BFC4A260F2E40BY5PR13MB3651namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8e2ff367-ab09-4c1f-6575-08d7bf9910eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2020 17:34:02.9285 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1reUhORYqR6Q5sagTOLtEkIH0mM4oYlW9LpnkvtDgCR3pFpDE0GD0hoi68k5y6Vsbwy7VkRm09JTDJDXEcKmtA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR13MB2950
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IqWDgQyw2a897DwgiPmCIfWf2oU>
Subject: Re: [Idr] IPR Call for draft-li-idr-flowspec-srv6
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2020 17:34:09 -0000

I am not aware of any IPR related to the draft.

Best Regards,
Huaimo



From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, February 24, 2020 9:44 PM
To: idr@ietf.org
Subject: [Idr] IPR Call for draft-li-idr-flowspec-srv6



Greetings:



This begins a IPR call for /raft-li-idr-flowspec-srv6-02.txt.  The adoption call will begin after all authors have responded to this email with an IPR statement.  For the authors who have responded before, you will need to respond to this email message as well.



A bit thanks to the authors who have waited patiently for the IDR chairs.



For the WG general discussion on IDR flow specification,  this call is to inquiry if this draft’s approach is useful.   As has been discussed on the list, the IETF 107 IDR working group meeting will need to decide if all additions to flow specification should go into  a version 2 specification.



In order to have a fruitful discussion regarding the amount of additions for flow specification, we will be calling for the WG to discuss any potential Flow specification drafts.



Cheers, Sue

v2.23.0 | Report a Bug | By Email