Re: [mpls] IPR poll on draft-ietf-mpls-ldp-yang

"Kamran Raza (skraza)" <skraza@cisco.com> Tue, 03 July 2018 14:20 UTC

Return-Path: <skraza@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 9EC08130E04; Tue, 3 Jul 2018 07:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 eN_6stXmQWrq; Tue, 3 Jul 2018 07:19:59 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B986130DE6; Tue, 3 Jul 2018 07:19:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9906; q=dns/txt; s=iport; t=1530627599; x=1531837199; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1mRLujLsGDpfaThwQunAdnG5JQAIgeSZyTJFvPcbH88=; b=crwhQGwVjQvl1k/Z2oSvr0f0ltPm3uJTUhR9XyiV0uMSBVvdNRdyf9VA EB1rk9Qxzj27coqOZUt3XVDUz2Sc7NZ3mK5+sn6alWQPFqKjEOa/YQVII /Wj1ISf5+Qutu/mxv+795Tc5YCdvhFDumoV7H0wY/BQI85/8oaajnUOBj A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DhAQDdhDtb/5pdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTdmJ/KAqDb5REgWUikBqFIoFmC4RsAheCASE4FAECAQECAQECbSiFNgEBAQQjSwYFEAIBCBEDAQIrAgICMB0IAQEEAQ0FgyABgRtkqFSCHIhPgTqIbYIVgTYMglyERwERAgE1CYJhMYIkAohNkH4JAo8dgUCEDIgLkWICERMBgSQ0IWFxcBU7KgGCPgmQSW+PLIEaAQE
X-IronPort-AV: E=Sophos;i="5.51,303,1526342400"; d="scan'208,217";a="137520627"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jul 2018 14:19:58 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w63EJwgY028132 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Jul 2018 14:19:58 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 3 Jul 2018 09:19:57 -0500
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1320.000; Tue, 3 Jul 2018 09:19:57 -0500
From: "Kamran Raza (skraza)" <skraza@cisco.com>
To: "N.Leymann@telekom.de" <N.Leymann@telekom.de>, "mpls@ietf.org" <mpls@ietf.org>
CC: "draft-ietf-mpls-ldp-yang@ietf.org" <draft-ietf-mpls-ldp-yang@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>
Thread-Topic: IPR poll on draft-ietf-mpls-ldp-yang
Thread-Index: AdQO59HoibL27d3iSPuyPBUZVyJ7RQD+XqIA
Date: Tue, 03 Jul 2018 14:19:57 +0000
Message-ID: <4D2E9C01-FAE8-4822-82D9-9CF927508234@cisco.com>
References: <LEJPR01MB0713322556F69FA258441813984F0@LEJPR01MB0713.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEJPR01MB0713322556F69FA258441813984F0@LEJPR01MB0713.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.248.165]
Content-Type: multipart/alternative; boundary="_000_4D2E9C01FAE8482282D99CF927508234ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/LpC61600obeG5s2aIaB0uPq4Gvk>
Subject: Re: [mpls] IPR poll on draft-ietf-mpls-ldp-yang
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.26
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: Tue, 03 Jul 2018 14:20:02 -0000

Hi Nic/WG,

I am not aware of any IPR related to this YANG modeling document.

From: "N.Leymann@telekom.de" <N.Leymann@telekom.de>
Date: Thursday, June 28, 2018 at 10:21 AM
To: "mpls@ietf.org" <mpls@ietf.org>
Cc: "draft-ietf-mpls-ldp-yang@ietf.org" <draft-ietf-mpls-ldp-yang@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Subject: IPR poll on draft-ietf-mpls-ldp-yang
Resent-From: <alias-bounces@ietf.org>
Resent-To: <skraza@cisco.com>, <rajiva@cisco.com>, <xufeng_liu@jabil.com>, <sesale@juniper.net>, <jescia.chenxia@huawei.com>, <hshah@ciena.com>
Resent-Date: Thursday, June 28, 2018 at 10:21 AM

Working Group,

We are currently preparing draft draft-ietf-mpls-ldp-yang for working group last call.

Part of this preparation is to do an IPR poll.

This mail is to start the IPR poll.

Are you aware of any IPR that applies to draft-ietf-mpls-ldp-yang?

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

There are no IPR disclosures against draft-ietf-mpls-ldp-yang.

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.

regards

Nic