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

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 06 September 2017 11:36 UTC

Return-Path: <adrian@olddog.co.uk>
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 DF71C132351; Wed, 6 Sep 2017 04:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 7NkwIrWAKpJI; Wed, 6 Sep 2017 04:36:31 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C649F13214D; Wed, 6 Sep 2017 04:36:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v86BaSAo008091; Wed, 6 Sep 2017 12:36:28 +0100
Received: from 950129200 (196.252.114.87.dyn.plus.net [87.114.252.196]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id v86BaPBK008040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Sep 2017 12:36:26 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-wu-l3sm-rfc8049bis@ietf.org>
Cc: "'l3sm'" <l3sm@ietf.org>
Date: Wed, 6 Sep 2017 12:36:22 +0100
Message-ID: <07cc01d32704$5e57c840$1b0758c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdMnBFTQmQGcjf4iSUuDiQpTCCn73Q==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23306.006
X-TM-AS-Result: No--26.195-10.0-31-10
X-imss-scan-details: No--26.195-10.0-31-10
X-TMASE-MatchedRID: taQWJ55fAd1jDV//SvkH3u5xcghYf69zbv16+gil4jcifM7JMNHW6/Sf gC6y7D/AKA4CVogmhU5fPHaAuFrGWhwsxVjZ4G6wr51gSC67hpU2O5Eh+45TR83J+h/wWLV9wua niM9QXy3njmT3vqmhOQB/td/4dwbXyNkakgF4d95CvapcIkxJXwrwwyqgLT32D6jy6ZBWV4hDXY 5H2MxX4GdTW3wtD2WPE0Mk5oFWWfKOXseOXKE0ixhTGJQ1M8K9EAvNbbgHz74n+p552csI1Va9s dg2p9nAkJugaIxP1s8uUoQ0FUfck6XTmm9dN5FHxZQoGMRGhhPopsYER8BMJu/FI0vC1VAH/E9/ MrlHaDqtEwybAQDtY991P9j+GNhXG2VEF4WD2MySRFDtqiM5SxNtTUpgahCnV9eB8vnmKe+cpCB irilG2d2aC4Uz4N5wA1OAB6ov7/c109PlO/IjKC0x8J2DopENdZPoD9V2prSbKItl61J/ybLn+0 Vm71Lc9/6tBPDUrmoLbigRnpKlKU0Pn8oFtLCc/N9/P5Y462I=
Archived-At: <https://mailarchive.ietf.org/arch/msg/l3sm/SzOZFO4_hnKhW3CsCpaQagGm_p0>
Subject: [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:36:33 -0000

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