Re: [mpls] IPR poll on draft-ietf-mpls-ri-rsvp-frr

"Tarek Saad (tsaad)" <tsaad@cisco.com> Mon, 13 November 2017 14:48 UTC

Return-Path: <tsaad@cisco.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FAB1289B5; Mon, 13 Nov 2017 06:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 9-L_1-7Uj6_F; Mon, 13 Nov 2017 06:48:01 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A11B124D37; Mon, 13 Nov 2017 06:48:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12080; q=dns/txt; s=iport; t=1510584481; x=1511794081; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=nekd6ms4XBkS1SAsOaAtxO9C+C44HRuJ66bmDHzuv8U=; b=M9YCpIJJozCPMGItOiF9VSoi3jrsp+rXMQKy+gOx/ORJJJqdUHlu+o/X nVojfR9UhO/ydYoRZFMFgs2SGfzJeeN3kAPoXwSFAyqxCys+19gywh5ci Ex2Y+ut0k3HOhUOMxwcCJfmvKZBiCef7M+S9K0f+a7oR/hs2vouDgoUcu k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CgAQBsrwla/5ldJa1bGQEBAQEBAQEBAQEBAQcBAQEBAYJEcWRuJweDd5lJgVcmkQiFWIEiA1wKH4UcAhqEQUMUAQEBAQEBAQEBayiFHgEBAQEDI0sGFQIBCBEDAQIrAgICMB0IAQEEARKJPkwDFRCrUIInJopfAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWDNIIHgVWBaSkLgnaCa4F5ARIBNgmCdTGCMgWZFIkWAodpjRmCFYYIiyWMaIkPAhEZAYE4ATYhTzRvehVJLQGCNoRfdwGGLoEkgREBAQE
X-IronPort-AV: E=Sophos;i="5.44,389,1505779200"; d="scan'208,217";a="320001497"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Nov 2017 14:47:59 +0000
Received: from XCH-RTP-005.cisco.com (xch-rtp-005.cisco.com [64.101.220.145]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vADElxPf028254 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 13 Nov 2017 14:47:59 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-005.cisco.com (64.101.220.145) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 13 Nov 2017 09:47:52 -0500
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1320.000; Mon, 13 Nov 2017 09:47:52 -0500
From: "Tarek Saad (tsaad)" <tsaad@cisco.com>
To: "N.Leymann@telekom.de" <N.Leymann@telekom.de>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-ri-rsvp-frr@ietf.org" <draft-ietf-mpls-ri-rsvp-frr@ietf.org>
Thread-Topic: IPR poll on draft-ietf-mpls-ri-rsvp-frr
Thread-Index: AdNUg1Cpe5dA+Y+xRUqVbHS1g/VoIAINOgYA
Date: Mon, 13 Nov 2017 14:47:52 +0000
Message-ID: <1BDB8DC5-701A-4989-9818-AD5D0830AA8D@cisco.com>
References: <3a590768494f45208f2c568b80913b91@HE105662.emea1.cds.t-internal.com>
In-Reply-To: <3a590768494f45208f2c568b80913b91@HE105662.emea1.cds.t-internal.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.247.160]
Content-Type: multipart/alternative; boundary="_000_1BDB8DC5701A49899818AD5D0830AA8Dciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/Z_C6dumk6LNQW5utOG_o1MgkppA>
Subject: Re: [mpls] IPR poll on draft-ietf-mpls-ri-rsvp-frr
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 14:48:04 -0000

Hi all,

I am not aware of any additional IPR other than what was disclosed and that applies to this draft.

Regards,
Tarek

From: "N.Leymann@telekom.de" <N.Leymann@telekom.de>
Date: Saturday, November 4, 2017 at 5:01 AM
To: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "draft-ietf-mpls-ri-rsvp-frr@ietf.org" <draft-ietf-mpls-ri-rsvp-frr@ietf.org>
Subject: IPR poll on draft-ietf-mpls-ri-rsvp-frr
Resent-From: <alias-bounces@ietf.org>
Resent-To: <csekar@juniper.net>, <inaminei@google.com>, <dante.j.pacella@verizon.com>, Tarek Saad <tsaad@cisco.com>
Resent-Date: Saturday, November 4, 2017 at 5:01 AM

Working Group,

We are currently preparing draft-ietf-mpls-ri-rsvp-frr for working group last call. We will do an IPR poll prior to the wglc.

This is to start the IPR Poll.

Are you aware of any IPR that applies to draft-ietf-mpls-ri-rsvp-frr?

If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

Please note that there is already one IPR disclosed for the individual document:

https://datatracker.ietf.org/ipr/2580/

If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the MPLS wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor.

If you are on the MPLS WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

Best regards

Nic