Return-Path: X-Original-To: ospf@ietfa.amsl.com Delivered-To: ospf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E0212D7D5; Wed, 15 Jun 2016 16:09:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.699 X-Spam-Level: X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 knw31HeIUkjT; Wed, 15 Jun 2016 16:09:13 -0700 (PDT) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3F9812D828; Wed, 15 Jun 2016 16:09:13 -0700 (PDT) Received: by mail-qk0-x236.google.com with SMTP id s186so38472203qkc.1; Wed, 15 Jun 2016 16:09:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=IrY+jzwzt6oU+2F7iRpv0kjoJ2WkDor6XfoRJVRtSZA=; b=EGTKe0Wpg7XLFXbetACbD9ANnDLNypenW7xYVb/V+k0VeT24f7Kl3fGS95iaw7LA9I y9NFkxR70/YOpwZEQkbg9O07aDYrT3328SlN5BCP5cvc/o5m/tWzurLuW38ENyrv4OFr SK0JOgGjlrNBF1AsHxX3qXWiDoCMG/YQGSM21gSVNn7c2Cuivb3y4XZ30jDvmnmojxVX BqYRivjkg1s/17JEJ4O6SoNq+fa0HEPKDSV/cJBV72/EX3lqdS8xVxkGQCO+BzlfavZF pjbGEetygBh1aJd2/gw6nIEWViRR6YIm7S/PJ1Z7DRlzK8en1cusGTXe3EH3XBX2n2UA VOjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=IrY+jzwzt6oU+2F7iRpv0kjoJ2WkDor6XfoRJVRtSZA=; b=lQGaooq7rw4Mz9H87xc03oA6uWe50hZa/U7NY3spd6iFiIsfMiGwuumCWdlQuycc+U y3XFtXvBjuLdSCYcKq9V14gWFNgu5o2DiL0VYbqAN2GhtUHnnKdF2+/Oj5UmsgDEa0jc 5j8fIaZZKcHVf2J/gGhKIA0WsshQ5U3LNuOa/M0IrAY8uVaaUB30GUzLg+YB+CBwCHRD qSojVk+nNzpwCO9jm1vwtcjEMKG09H18tWoEp8pYxN/TRQQiBeomgOAzGpkGnD3udTWw C87lVxW9iLTmDzQ1+TjNtuvtQY2gOZlatHkPHZ7J5MDJ2MC3s0WGHT+ASwLxOVOxSrN8 3JJg== X-Gm-Message-State: ALyK8tJoLOY4jJd6s7MJhkDP3BuquX5O2sVhZ5XThEyWEj+6Hld/mGxWrl5em3YgZ/DrKch8MwxwxQCXQFYcvw== X-Received: by 10.233.237.14 with SMTP id c14mr1396677qkg.88.1466032152790; Wed, 15 Jun 2016 16:09:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.57.81 with HTTP; Wed, 15 Jun 2016 16:09:11 -0700 (PDT) In-Reply-To: <20160615224723.26169.55291.idtracker@ietfa.amsl.com> References: <20160615224723.26169.55291.idtracker@ietfa.amsl.com> From: Alia Atlas Date: Wed, 15 Jun 2016 19:09:11 -0400 Message-ID: To: OSPF List , draft-ietf-ospf-segment-routing-extensions@ietf.org Content-Type: multipart/alternative; boundary=94eb2c0c0a06b24b3c05355935c8 Archived-At: Subject: Re: [OSPF] IPR Disclosure Cisco Systems, Inc.'s Statement about IPR related to draft-ietf-ospf-segment-routing-extensions X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jun 2016 23:09:15 -0000 --94eb2c0c0a06b24b3c05355935c8 Content-Type: text/plain; charset=UTF-8 Stefano, Clarence, and Peter, Could you please clarify if this IPR disclosure is simply updating the previously disclosed IPR or represents additional IPR? I do see that there is at least some overlap. Thanks, Alia On Wed, Jun 15, 2016 at 6:47 PM, IETF Secretariat wrote: > Dear Peter Psenak, Stefano Previdi, Clarence Filsfils, Wim Henderickx, > Jeff Tantsura, Hannes Gredler, Rob Shakir: > > > An IPR disclosure that pertains to your Internet-Draft entitled "OSPF > Extensions for Segment Routing" > (draft-ietf-ospf-segment-routing-extensions) was submitted to the IETF > Secretariat on and has been posted on the "IETF Page of Intellectual > Property > Rights Disclosures" (https://datatracker.ietf.org/ipr/2808/). The title > of the > IPR disclosure is "Cisco Systems, Inc.'s Statement about IPR related to > draft-ietf-ospf-segment-routing-extensions" > > > Thank you > > IETF Secretariat > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf > --94eb2c0c0a06b24b3c05355935c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Stefano, Clarence, and Peter,

Could you= please clarify if this IPR disclosure is simply updating the previously
disclosed IPR or represents additional IPR?

I do see that there is at least some overlap.

Th= anks,
Alia

On Wed, Jun 15, 2016 at 6:47 PM, IETF Secretariat <ietf-i= pr@ietf.org> wrote:
Dear Pe= ter Psenak, Stefano Previdi, Clarence Filsfils, Wim Henderickx, Jeff Tantsu= ra, Hannes Gredler, Rob Shakir:


An IPR disclosure that pertains to your Internet-Draft entitled "OSPF<= br> Extensions for Segment Routing"
(draft-ietf-ospf-segment-routing-extensions) was submitted to the IETF
Secretariat on=C2=A0 and has been posted on the "IETF Page of Intellec= tual Property
Rights Disclosures" (https://datatracker.ietf.org/ipr/280= 8/). The title of the
IPR disclosure is "Cisco Systems, Inc.'s Statement about IPR relat= ed to
draft-ietf-ospf-segment-routing-extensions"


Thank you

IETF Secretariat

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

--94eb2c0c0a06b24b3c05355935c8--