Return-Path: 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 6E7C83A0A3A for ; Fri, 6 Mar 2020 12:37:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.497 X-Spam-Level: X-Spam-Status: No, score=-1.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org 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 nMsOGU7GwHLZ for ; Fri, 6 Mar 2020 12:37:56 -0800 (PST) Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D773A0A37 for ; Fri, 6 Mar 2020 12:37:55 -0800 (PST) Received: by mail-ot1-x32f.google.com with SMTP id v19so3752381ote.8 for ; Fri, 06 Mar 2020 12:37:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3MDnYenhfD8m2yAq1SEAvxdzGRyi5WoBkQWU580KMMI=; b=fYcRWz++tZTXkNNd8Hhsq5TTMjPrxp/hUlYI1bO3cDZeqU83VeP+HyasR9w/zn8kNn GKaM3Nls230nfgz/4D2vzN74aX5ehzKmGLaDPPWkUxqeOi98Qi4WSjAFvm1Cj74JLTel 3Q3Uaw0FAAUzkxmujsqrJxD2bs/u8QQv2OM0Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3MDnYenhfD8m2yAq1SEAvxdzGRyi5WoBkQWU580KMMI=; b=EzYGXm8D9grCZ3cetHj9ps5e2t4omcmt+npK6zx5lGIMOC3M+/8XRIyyb6y/Ku/kQa UvXwO1LYXFMtyhiplxvFMU9RoHpIylwKUV53Gg7JyfeI9W81k2oBMH+3dA+14qyl21HT AkUGlofYSlMeRFSfPy3UtTEB1zFpf5kODeQZYd/wVznY/Sf0bgACU7f9Jb/YSz2SBQbh yo8UhMdt7Uj2i4HOQd0Wu54LVL0cuEWzr1xO+4Ei6+HMCe4mYAF5nzj15vxDJj/QLMmR a8RIW7/WwRI1nS+l/p1vT/ZxxpwOruRMTQBFANU6ywttw26dtGpcF21hAdYyuOSuuT8d U2Bg== X-Gm-Message-State: ANhLgQ0SUi04SrY4GfF+4hrR9jRvp3PFLRurXW2jNcgk3VYCJFFk7IiQ zZ7VzwXMuZp6029KU4b0y6fFQG2UOnqWKs4pJzY= X-Google-Smtp-Source: =?utf-8?q?ADFU+vvNCIe6ghbXMjKP8gsGBifKeqZLeMKG0ehT7/HU?= =?utf-8?q?mYg4ioHhkl6Dv/y6BlzdkALfvJd4QXmLikqpvFZ92/2O1vY=3D?= X-Received: by 2002:a9d:10d:: with SMTP id 13mr4203870otu.334.1583527075058; Fri, 06 Mar 2020 12:37:55 -0800 (PST) MIME-Version: 1.0 References: <000701d5eb18$71a02200$54e06600$@ndzh.com> In-Reply-To: <000701d5eb18$71a02200$54e06600$@ndzh.com> From: LEI LIU Date: Fri, 6 Mar 2020 12:38:25 -0800 Message-ID: To: Susan Hares Cc: idr wg Content-Type: multipart/alternative; boundary="000000000000cd18b605a035a0da" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Mar 2020 20:37:58 -0000 --000000000000cd18b605a035a0da Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi All, I am not aware of any IPR related to the draft. Best regards, Lei On Mon, Feb 24, 2020 at 5:44 AM Susan Hares wrote: > 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 wi= ll > 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=E2=80=99s approach is useful. As has been discuss= ed 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 > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > --000000000000cd18b605a035a0da Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,=C2=A0

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

Best regards,=C2=A0
Lei=C2=A0=

= On Mon, Feb 24, 2020 at 5:44 AM Susan Hares <shares@ndzh.com> wrote:

Gree= tings:

=C2=A0

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

=C2=A0

A bit thanks to the authors who have waited patiently for the ID= R chairs.=C2=A0

=C2=A0

For the WG general discussion on IDR flow spec= ification,=C2=A0 this call is to inquiry if this draft=E2=80=99s approach i= s useful. =C2=A0=C2=A0As has been discussed on the list, the IETF 107 IDR w= orking group meeting will need to decide if all additions to flow specifica= tion should go into =C2=A0a version 2 specification.=C2=A0=C2=A0 =

=C2=A0

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 poten= tial Flow specification drafts.

=C2=A0

Cheers, Sue

=
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr



--000000000000cd18b605a035a0da--