Re: [L3sm] IPR confirmation on draft-wu-l3sm-rfc8049bis

<stephane.litkowski@orange.com> Wed, 06 September 2017 11:56 UTC

Return-Path: <stephane.litkowski@orange.com>
X-Original-To: l3sm@ietfa.amsl.com
Delivered-To: l3sm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024F513214D for <l3sm@ietfa.amsl.com>; Wed, 6 Sep 2017 04:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 8D5j3_QxRMDs for <l3sm@ietfa.amsl.com>; Wed, 6 Sep 2017 04:56:14 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F8D1126DD9 for <l3sm@ietf.org>; Wed, 6 Sep 2017 04:56:14 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id C5A19120B30; Wed, 6 Sep 2017 13:56:12 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id A9E0E180072; Wed, 6 Sep 2017 13:56:12 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%18]) with mapi id 14.03.0361.001; Wed, 6 Sep 2017 13:56:12 +0200
From: stephane.litkowski@orange.com
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
CC: 'l3sm' <l3sm@ietf.org>
Thread-Topic: IPR confirmation on draft-wu-l3sm-rfc8049bis
Thread-Index: AdMnBFTQmQGcjf4iSUuDiQpTCCn73QAAr/kA
Date: Wed, 06 Sep 2017 11:56:11 +0000
Message-ID: <8817_1504698972_59AFE25C_8817_81_1_9E32478DFA9976438E7A22F69B08FF921EA4830D@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <07cc01d32704$5e57c840$1b0758c0$@olddog.co.uk>
In-Reply-To: <07cc01d32704$5e57c840$1b0758c0$@olddog.co.uk>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/YZXNWXCLD9Bw_Qx3PZqGOpfdNUM>
Subject: Re: [L3sm] IPR confirmation on draft-wu-l3sm-rfc8049bis
X-BeenThere: l3sm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: L3VPN Service YANG Model discussion group <l3sm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3sm>, <mailto:l3sm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l3sm/>
List-Post: <mailto:l3sm@ietf.org>
List-Help: <mailto:l3sm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3sm>, <mailto:l3sm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2017 11:56:17 -0000

No, I am not aware of any IPR that covers this document.

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk] 
Sent: Wednesday, September 06, 2017 13:36
To: draft-wu-l3sm-rfc8049bis@ietf.org
Cc: 'l3sm'
Subject: IPR confirmation on draft-wu-l3sm-rfc8049bis

Hi,

Could the authors please confirm that all relevant IPR for this document has been disclosed. Suitable responses could be picked from the list below.

Note that other contributors on this mailing list should be aware that they are also subject to IETF IPR rules and should disclose any relevant IPR of which they are aware.

1. No, I am not aware of any IPR that covers this document.
2. Yes, I am aware of IPR that covers this document and it has already been disclosed.
3. Yes, I am aware of IPR that covers this document, but it has not yet been disclosed. I am working to ensure that a disclosure is made very soon.

Thanks,
Adrian


> -----Original Message-----
> From: L3sm [mailto:l3sm-bounces@ietf.org] On Behalf Of Qin Wu
> Sent: 06 September 2017 11:25
> To: l3sm; David Ball
> Cc: Benoit Claise (bclaise); adrian
> Subject: Re: [L3sm] New Version Notification for 
> draft-wu-l3sm-rfc8049bis-03.txt
> 
> We have incorporated additional comments from David in v-(03).
> https://www.ietf.org/rfcdiff?url2=draft-wu-l3sm-rfc8049bis-03
> Thank David, thanks for L3SM design team help complete this.
> 
> -Qin
> -----邮件原件-----
> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 发送时间: 2017年9月6日 18:18
> 收件人: Qin Wu; Luis Tomotaki; Kenichi Ogaki; Stephane Litkowski
> 主题: New Version Notification for draft-wu-l3sm-rfc8049bis-03.txt
> 
> 
> A new version of I-D, draft-wu-l3sm-rfc8049bis-03.txt has been 
> successfully submitted by Qin Wu and posted to the IETF repository.
> 
> Name:		draft-wu-l3sm-rfc8049bis
> Revision:	03
> Title:		YANG Data Model for L3VPN Service Delivery
> Document date:	2017-09-06
> Group:		Individual Submission
> Pages:		181
> URL:            https://www.ietf.org/internet-drafts/draft-wu-l3sm-rfc8049bis-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-wu-l3sm-rfc8049bis/
> Htmlized:       https://tools.ietf.org/html/draft-wu-l3sm-rfc8049bis-03
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-wu-l3sm-rfc8049bis-03
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-wu-l3sm-rfc8049bis-03
> 
> Abstract:
>    This document defines a YANG data model that can be used for
>    communication between customers and network operators and to deliver
>    a Layer 3 provider-provisioned VPN service.  This document is limited
>    to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364.  This
>    model is intended to be instantiated at the management system to
>    deliver the overall service.  It is not a configuration model to be
>    used directly on network elements.  This model provides an abstracted
>    view of the Layer 3 IP VPN service configuration components.  It will
>    be up to the management system to take this model as input and use
>    specific configuration models to configure the different network
>    elements to deliver the service.  How the configuration of network
>    elements is done is out of scope for this document.
> 
>    If approved, this document obsoletes RFC 8049.  The changes are a
>    series of small fixes to the YANG module, and some clarifications to
>    the text.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of 
> submission until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> _______________________________________________
> L3sm mailing list
> L3sm@ietf.org
> https://www.ietf.org/mailman/listinfo/l3sm


_________________________________________________________________________________________________________________________

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.