Hi Andrew, All,

the IPR disclosed are related to the content of both documents:
draft-filsfils-spring-segment-routing-04.txt
draft-filsfils-rtgwg-segment-routing-01.txt

Should we re-issue an IPR disclosure ?

s.


On Oct 18, 2014, at 9:18 PM, Andrew G. Malis wrote:

> Alvaro,
> 
> Not to be a pain about this, but I just did a comparison between 
> draft-filsfils-rtgwg-segment-routing-01.txt and 
> draft-filsfils-spring-segment-routing-04.txt, and the changes are quite 
> impressive, a great majority of the text in the older draft is either missing 
> or changed in the newer draft. You can see for yourself by clicking on 
> http://tinyurl.com/q2ykstg . I would appreciate it if the patent holder could 
> update their declaration to the current draft, or publicly state whether or 
> not the declaration still applies to draft-filsfils-spring-segment-routing-04 
> .
> 
> Thanks,
> Andy
> 
> On Fri, Oct 17, 2014 at 10:23 PM, Alvaro Retana (aretana) <aret...@cisco.com> 
> wrote:
> On 10/7/14, 11:26 AM, "Stefano Previdi (sprevidi)" <sprev...@cisco.com>
> wrote:
> 
> >IPR is in the process of being disclosed.
> 
> The IPR was filed on Oct/7, but it was done against
> draft-filsfils-rtgwg-segment-routing, which is the precursor of this
> draft.  The filing is ok, it just took me a while to find it.
> 
> For the WG reference:  http://datatracker.ietf.org/ipr/2457/
> 
> 
> Authors:  We still havenĀ¹t received an explicit answer form Clarence,
> Ahmed, Stephane, Igor, Wim and Ed.  [Note that some of you may have
> replied for draft-filsfils-spring-segment-routing-mpls..]  It would be
> very nice if we can close on this requirement by Oct/23 so (if adopted) we
> have time to publish the WG-titled document before the deadline.
> 
> Thanks!
> 
> Alvaro.
> 
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
> 

_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring

Reply via email to