IETF Logo Mail Archive

Re: [CCAMP] Regarding IPR on draft-ali-ccamp-additional-signal-type-g709v3-05

"Zafar Ali (zali)" <zali@cisco.com> Thu, 23 October 2014 16:32 UTC

Return-Path: <zali@cisco.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6BA1A924C for <ccamp@ietfa.amsl.com>; Thu, 23 Oct 2014 09:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FtvZHCfjO14n for <ccamp@ietfa.amsl.com>; Thu, 23 Oct 2014 09:32:46 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0A781ACD8B for <ccamp@ietf.org>; Thu, 23 Oct 2014 09:32:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2167; q=dns/txt; s=iport; t=1414081942; x=1415291542; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=qxFG3mp9YDvkP1nlC5oo4XCQNvRYJV9bmnpJYCHsJ/Q=; b=g2enrEtZYynULatVL0NwsNi+vOaiMNDhkYyFcX93KwHWI7SrDTkAiWvD FhVFGiyI8O4dizG+V+VA+Q7bkAR39AvEOu0ZmAqeUvTK0d0C2or0wrrcq PWoc/S6bo8BE3kW+0yEiKgopPxIN/sKIL3+2JiTFMQupUR6pzPlu682nH 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwUABItSVStJV2c/2dsb2JhbABcgw5UXLoWkmiHTQKBEhYBfYQCAQEBBHQFDAYBCA4DAwECYR0IAgQBDQWIQQ3IawEBAQEBAQEBAQEBAQEBAQEBAQEZjkqBLBEBUAcGhEUFkgWERocSgTE8gw2NMoQBg3hsAYEOOYEDAQEB
X-IronPort-AV: E=Sophos;i="5.04,776,1406592000"; d="scan'208";a="365823233"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 23 Oct 2014 16:32:22 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s9NGWLYa019051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Oct 2014 16:32:22 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.159]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 11:32:21 -0500
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Lou Berger <lberger@labn.net>, "Antonello Bonfanti (abonfant)" <abonfant@cisco.com>, Fatai Zhang <zhangfatai@huawei.com>
Thread-Topic: Regarding IPR on draft-ali-ccamp-additional-signal-type-g709v3-05
Thread-Index: AQHP7t5oLOYg5w1PmkOmGBFb6//TKZw98f+A
Date: Thu, 23 Oct 2014 16:32:20 +0000
Message-ID: <D06EA6B1.D43F9%zali@cisco.com>
In-Reply-To: <54492CAC.1090605@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [10.86.255.208]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <556CBC0AA7841D4A92765730B7917519@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ccamp/98Zh-7BOQUVvI4jzI8V183tS2mk
Cc: CCAMP <ccamp@ietf.org>
Subject: Re: [CCAMP] Regarding IPR on draft-ali-ccamp-additional-signal-type-g709v3-05
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 16:32:52 -0000

Hi- 

No, I'm not aware of any IPR that applies to this draft.


Thanks

Regards Š Zafar



-----Original Message-----
From: "lberger@labn.net" <lberger@labn.net>
Date: Thursday, October 23, 2014 12:28 PM
To: zali <zali@cisco.com>, "Antonello Bonfanti (abonfant)"
<abonfant@cisco.com>, Fatai Zhang <zhangfatai@huawei.com>
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Regarding IPR on draft-ali-ccamp-additional-signal-type-g709v3-05

>Authors, Contributors, (CCAMP)
>
>As part of the preparation for polling for WG document adoption:
>
>Are you aware of any IPR that applies to draft identified above?
>
>  Please state either:
>
>  "No, I'm not aware of any IPR that applies to this draft"
>  or
>  "Yes, I'm aware of IPR that applies to this draft"
>
>If so, has this IPR been disclosed in compliance with IETF IPR rules
>(see RFCs 3979, 4879, 3669 and 5378 for more details)?
>
>If yes to the above, please state either:
>
>  "Yes, the IPR has been disclosed in compliance with IETF IPR rules"
>  or
>  "No, the IPR has not been disclosed"
>
>If you answer no, please provide any additional details you think
>  appropriate.
>
>If you are listed as a document author or contributor please answer the
>above by responding to this email regardless of whether or not you are
>aware of any relevant IPR.  This document will not advance to the next
>stage until a response has been received from each author and listed
>contributor.  NOTE: THIS APPLIES TO ALL OF YOU LISTED IN THIS MESSAGE'S
>TO LINES.
>
>If you are on the CCAMP WG email list but are not listed as an author or
>contributor, we remind you of your obligations under the IETF IPR rules
>which encourages you to notify the IETF if you are aware of IPR of
>others on an IETF contribution, or to refrain from participating in any
> contribution or discussion related to your undisclosed IPR.  For more
>information, please see the RFCs listed above and
>http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>
>Thank you,
>CCAMP WG Chairs
>
>PS Please include all listed in the headers of this message in your
>response.

v2.23.0 | Report a Bug | By Email