Re: [spring] draft-ginsberg-spring-conflict-resolution - IPR Call

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Wed, 13 April 2016 14:14 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B7512D09F; Wed, 13 Apr 2016 07:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level:
X-Spam-Status: No, score=-15.517 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 vRTU4zZwZSCy; Wed, 13 Apr 2016 07:14:40 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63A2212D0BF; Wed, 13 Apr 2016 07:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2509; q=dns/txt; s=iport; t=1460556880; x=1461766480; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=izuqqySaabn1kKlrSYiT0RymzkUf+VaVvpXcVG0kXaE=; b=ATbgFR/kFYn6r95LxpLP/2uioLdvN2WaJtMX1UuAcKVz8RHct4yMllx6 QUD3sPbEIQRlgl93cEw2RlauHTl0Nf64JymtbSWZAxGVCO3aP0bum1hAv snkF9JmiIIVAiow/jsbLpIn8hf524aRt7z1fJHQ/hJXkpG29fz9IIbqNK g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ACAgACVA5X/5ldJa1egzeBUAa6RgENgXSGDgKBPzgUAQEBAQEBAWUnhEEBAQEEOjQGEQQCAQgRBAEBHwkHMhQJCAEBBAESCIggwygBAQEBAQEBAQEBAQEBAQEBAQEBAQEVhiGES4QPEAIBhXMFmAgBjgWBboROiFuPJgEeAQFCg2dsiHx+AQEB
X-IronPort-AV: E=Sophos;i="5.24,479,1454976000"; d="scan'208";a="96867642"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2016 14:14:39 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u3DEEd2R001147 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 13 Apr 2016 14:14:39 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 13 Apr 2016 09:14:38 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.009; Wed, 13 Apr 2016 09:14:38 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "spring@ietf.org" <spring@ietf.org>, "draft-ginsberg-spring-conflict-resolution@ietf.org" <draft-ginsberg-spring-conflict-resolution@ietf.org>
Thread-Topic: draft-ginsberg-spring-conflict-resolution - IPR Call
Thread-Index: AdGVWfO+jYDfBBCkSeuvYrRPTUg40gANL4UQ
Date: Wed, 13 Apr 2016 14:14:38 +0000
Message-ID: <30f115b6a5a6417d8b4a9bbc30d7a015@XCH-ALN-001.cisco.com>
References: <17961_1460534212_570DFBC4_17961_1664_1_53C29892C857584299CBF5D05346208A0F86CD00@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <17961_1460534212_570DFBC4_17961_1664_1_53C29892C857584299CBF5D05346208A0F86CD00@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.79.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/spring/_KTsoO58wj8WHbcf0ZQvaYFUchA>
Subject: Re: [spring] draft-ginsberg-spring-conflict-resolution - IPR Call
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 14:14:43 -0000

Support (as co-author).

I am not aware of any relevant IPR.

   Les


> -----Original Message-----
> From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com]
> Sent: Wednesday, April 13, 2016 12:57 AM
> To: spring@ietf.org; draft-ginsberg-spring-conflict-resolution@ietf.org
> Subject: draft-ginsberg-spring-conflict-resolution - IPR Call
> 
> Working Group,
> 
> The authors of draft-ginsberg-spring-conflict-resolution believe that the
> document is ready to be considered for working adoption.
> 
> This mail starts the IPR poll.
> 
> Are you aware of any IPR that applies to draft-ginsberg-spring-conflict-
> resolution?
> 
> If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
> 3979, 4879, 3669 and 5378 for more details)?
> 
> 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 SPRING 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 SPRING 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.
> 
> Thanks,
> -- Bruno, John
> 
> 
> __________________________________________________________
> __________________________________________________________
> _____
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites
> ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez
> le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration, Orange decline toute
> responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged
> information that may be protected by law; they should not be distributed,
> used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.