Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis

Loa Andersson <loa@pi.nu> Sun, 20 December 2015 05:45 UTC

To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
References: <5674E8D9.3020000@pi.nu> <47814701-766D-4441-81FD-40E2128CBEE6@cisco.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <56764056.7090204@pi.nu>
Date: Sun, 20 Dec 2015 13:44:54 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <47814701-766D-4441-81FD-40E2128CBEE6@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/_9c-zMAJhTtS-IdX3OPg3SGG6M8>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, "draft-smack-mpls-rfc4379bis@ietf.org" <draft-smack-mpls-rfc4379bis@ietf.org>
Subject: Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis
Precedence: list

Carlos, working group,

Good question - the track flags the RFC 4379 IPRs (as related documents)
when you search for IPRs draft-smack-mpls-rfc4379bis, but nothing for
documents that update 4379. I don't there is another (fail-proof) way of
getting relevant IPRs flagged than that the IPR owners re-disclose them
against the 4379bis. I think that they should do this,

On the other hand I will follow up on this.

/Loa

On 2015-12-20 11:04, Carlos Pignataro (cpignata) wrote:
> Loa,
>
> I am not aware of any IPR on top of the RFCs this document is bis-ing/merging.
>
> Question for you: should the data tracker flag the IPR disclosed to 4379 as to this doc?
>
> Thumb typed by Carlos Pignataro.
> Excuze typofraphicak errows
>
>> On Dec 19, 2015, at 12:19, Loa Andersson <loa@pi.nu> wrote:
>>
>> Working Group,
>>
>> The authors of draft-smack-mpls-rfc4379bis has told us that
>> the document is ready for working adoption.
>>
>> We will do an IPR poll in parallel to the wgap.
>>
>> This mail starts the IPR poll.
>>
>> Are you aware of any IPR that applies to draft-smack-mpls-rfc4379bis?
>>
>> If so, has this IPR been disclosed in compliance with IETF IPR rules
>> (see RFCs 3979, 4879, 3669 and 5378 for more details).
>>
>> There are no IPR disclosures filed directly against this document.
>> However, there are  tow IPR disclosures against RFC 4379.
>>
>> 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.
>>
>>
>> /Loa
>> mpls wg co-chair
>> --
>>
>>
>> Loa Andersson                        email: loa@mail01.huawei.com
>> Senior MPLS Expert                          loa@pi.nu
>> Huawei Technologies (consultant)     phone: +46 739 81 21 64

[mpls] IPR poll on draft-smack-mpls-rfc4379bis Loa Andersson
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Sam Aldrin
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Carlos Pignataro (cpignata)
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Loa Andersson
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Nagendra Kumar Nainar (naikumar)
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Mach Chen
Re: [mpls] IPR poll on draft-smack-mpls-rfc4379bis Kireeti Kompella