Re: [mpls] IPR poll on draft-andersson-mpls-spl-terminology

"Adrian Farrel" <> Tue, 30 April 2019 10:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A9308120296; Tue, 30 Apr 2019 03:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 90YmkUKPrLwt; Tue, 30 Apr 2019 03:11:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B33B12028A; Tue, 30 Apr 2019 03:11:08 -0700 (PDT)
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id x3UAB58W015505; Tue, 30 Apr 2019 11:11:05 +0100
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 8207822042; Tue, 30 Apr 2019 11:11:05 +0100 (BST)
Received: from (unknown []) by (Postfix) with ESMTPS id 761272204C; Tue, 30 Apr 2019 11:11:05 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id x3UAB4Lp027018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 30 Apr 2019 11:11:04 +0100
Reply-To: <>
From: "Adrian Farrel" <>
To: <>, <>
Cc: <>, <>
References: <LEJPR01MB0377E6C42A8591652A038006983A0@LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEJPR01MB0377E6C42A8591652A038006983A0@LEJPR01MB0377.DEUPRD01.PROD.OUTLOOK.DE>
Date: Tue, 30 Apr 2019 11:11:02 +0100
Organization: Old Dog Consulting
Message-ID: <029701d4ff3d$04ab2540$0e016fc0$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0298_01D4FF45.666F8D40"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI0GyTttIk2XH6Lg35SnnfbtNGbIKWWQn9g
Content-Language: en-gb
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--24.847-10.0-31-10
X-imss-scan-details: No--24.847-10.0-31-10
X-TMASE-Result: 10--24.847400-10.000000
X-TMASE-MatchedRID: gzVbiXtWD9vxIbpQ8BhdbGzBijri5+RVbv16+gil4jdoYDoakaUh1MWg mIw8xvFebrgUJ4CnqHiqEjHR8FX3BS3F56OiNwp/b8JTZf0kEzvqe8CwJZFGUZTVN3FiLkyog0T HjI2jZEVUNb4KGOm2sCw8LAwMBGLbnPecQ/hKOMCprpImTnz4to7vhl9PIBCwCVuEXtlNqcvuc/ n71nc6DRuHs1ba36aMzhZguZB9diZzjLovRKWwwu9VsdrlGzy3Q6/DFZugyt27/NQTVI1I+cbK+ pu0ZYwRBHVm0xh58VY8LuP+bOkMWt3jF2fVcPdzDB+ErBr0bANar2Wff4KSIaUXswX/xrIS1BoO 0FXL0sjuDNx+Tk7mC2JdCNPFSfXrp3Cwl7p83YsSDAzxRL+lMZkShYcLpGH9BL+V9lD389FL/hr /YMmS/27Wbor+4y0FrlH1qheKYcDBp2db7m7iUQ6w00GeWBFafS0Ip2eEHnyvXSmSdlcYmsnjLT A/UDoAHwAqApZ40aHQqQhSw0x2VOJGF26G8SWypfzLa08EuFD1SgS9RingR8pZgmM1KlIW5o7av otHrRM7kJjgLtPKdqID+lQLXr0x
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <>
Subject: Re: [mpls] IPR poll on draft-andersson-mpls-spl-terminology
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 30 Apr 2019 10:11:12 -0000

Hi Nic,


I am not aware of any IPR applicable to this document.





From: <> 
Sent: 30 April 2019 08:55
Subject: IPR poll on draft-andersson-mpls-spl-terminology


Working Group, authors,


We have started to prepare draft-andersson-mpls-spl-terminology for working
group adoption, prior to the WGAP we need to do an IPR poll.


This mail starts this IPR poll.


Are you aware of any IPR that applies to


If so, has this IPR been disclosed in compliance with IETF IPR rules (see
RFCs 3979, 4879, 3669 and 5378 for more details).


There no IPR disclosures against draft-andersson-mpls-spl-terminology.


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 MPLS 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 MPLS 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.