IETF Logo Mail Archive

Re: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy

"Francois Clad (fclad)" <fclad@cisco.com> Tue, 22 May 2018 07:06 UTC

Return-Path: <fclad@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 3DE5612EAB8; Tue, 22 May 2018 00:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 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, 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 A9wr4vf__put; Tue, 22 May 2018 00:06:32 -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 080FD12E6D7; Tue, 22 May 2018 00:06:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15154; q=dns/txt; s=iport; t=1526972792; x=1528182392; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KFYfDE6Nat+/+sw56G+XE8oWzgWanHzQeCMPz5lJD1A=; b=aPy/F03pGL/uYgCOAjMSWPknS20+OQmlEnYSMTHk17K71rJIpvfJlU2r Jc6cdqBCll5OR2NkA1WpHoe9KU9Jpri9imKUUl50u4ihLQCwoVlPRcy+B IkBq9b5nlwT+9UOvT7UgYokEJlo992rM+ePpJ86DnIyxevgLiY4sg17cP s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAAAvwQNb/5ldJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJNdmJ9KAqDa4gEjHSBeYEPjj+EdxSBZAslhEcCGoIEITQYAQIBAQEBAQECbBwMhSgBAQEEHQZWEAIBCBEEAQEoAwICAjAUCQgCBAENBYMiAoEbZA+oTYIciEWCCgWINYFUP4EzgmmDEQICAReBEwESATYfgkowgiQChyORKwkChWiIbYE3g22HWYlfhnICERMBgSQBHDhhcXAVOyoBghiLEIU+bw6OMoEfgRgBAQ
X-IronPort-AV: E=Sophos;i="5.49,429,1520899200"; d="scan'208,217";a="117526830"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 May 2018 07:06:30 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w4M76Um6022552 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 May 2018 07:06:30 GMT
Received: from xch-rcd-014.cisco.com (173.37.102.24) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 22 May 2018 02:06:30 -0500
Received: from xch-rcd-014.cisco.com ([173.37.102.24]) by XCH-RCD-014.cisco.com ([173.37.102.24]) with mapi id 15.00.1320.000; Tue, 22 May 2018 02:06:30 -0500
From: "Francois Clad (fclad)" <fclad@cisco.com>
To: Rob Shakir <robjs@google.com>, SPRING WG List <spring@ietf.org>
CC: Bruno Decraene <bruno.decraene@orange.com>, "draft-filsfils-spring-segment-routing-policy@ietf.org" <draft-filsfils-spring-segment-routing-policy@ietf.org>
Thread-Topic: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy
Thread-Index: AQHT7SmDWdPG6wUHtESJZOLSks0bsaQy25+AgAjUqwA=
Date: Tue, 22 May 2018 07:06:30 +0000
Message-ID: <73DC995E-31E1-4FD4-8BDA-24EE109508D2@cisco.com>
References: <CAHd-QWsAYVWcAE9TRbkzSfY_60wC+O0YZZQB7ZnRHr=mPkuBpw@mail.gmail.com> <11090_1526487312_5AFC5910_11090_188_1_53C29892C857584299CBF5D05346208A47A4899A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <11090_1526487312_5AFC5910_11090_188_1_53C29892C857584299CBF5D05346208A47A4899A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.168.40]
Content-Type: multipart/alternative; boundary="_000_73DC995E31E14FD48BDA24EE109508D2ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/9wFb_nrJGKJmXuX8iiZRhk9VRkM>
Subject: Re: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <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: Tue, 22 May 2018 07:06:35 -0000

I’m not aware of any IPR other than already disclosed at https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-filsfils-spring-segment-routing-policy

Francois

On 16 May 2018, at 18:15, bruno.decraene@orange.com<mailto:bruno.decraene@orange.com> wrote:

[+ authors]

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

--Bruno

From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Rob Shakir
Sent: Wednesday, May 16, 2018 5:20 PM
To: SPRING WG List
Subject: [spring] IPR Poll for draft-filsfils-spring-segment-routing-policy

Hi SPRING WG,

In parallel to the call for adoption for draft-filsfils-spring-segment-routing-policy, we would like to poll for IPR.

If you are aware of IPR that applies to draft-filsfils-spring-segment-routing-policy please respond to this email. If you are aware of IPR, please indicate whether it has been disclosed in accordance with IETF IPR rules (RFCs 3979, 4879, 3669 and 5378 provide more details).

If you are an author or contributor please respond to this email regardless of whether or not you're aware of any IPR. If you are not an author or contributor, please explicitly respond only if you are aware of IPR that has not yet been disclosed.

This document will not advance into the working group until IPR confirmations have been received from all authors and contributors.

Thanks,
Bruno & Rob.

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email