Re: [Lsr] OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

"Ketan Talaulikar (ketant)" <> Mon, 18 June 2018 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A5D65130DE3 for <>; Mon, 18 Jun 2018 08:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hkobZ5S5Z9EM for <>; Mon, 18 Jun 2018 08:31:49 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D9AE712872C for <>; Mon, 18 Jun 2018 08:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=9898; q=dns/txt; s=iport; t=1529335908; x=1530545508; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=MZyg8JwJ4/YS3m/ryhuJ7XzwTQNQor4Ty/mpTWuQyts=; b=INl9amloj8YwQ0IPmz6acPqVqRH7E3IsJBqprvLNQAj025RWBU70qU3v L4SjTFkJKlCYbkZihljXPrAlBh8l0wlSjvCZMrYlHto5z1ydFuFFTOnjo GKC6646s4g/Y15VqO592obHO76HBBjs7P3eUhxUBXksmuW1UwM4+gRRyT 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.51,239,1526342400"; d="scan'208,217";a="130801163"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jun 2018 15:31:48 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w5IFVmiB018405 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 18 Jun 2018 15:31:48 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 18 Jun 2018 10:31:47 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Mon, 18 Jun 2018 10:31:47 -0500
From: "Ketan Talaulikar (ketant)" <>
To: "Acee Lindem (acee)" <>, "" <>, "draft-ietf-ospf-lls-interface-id@ietf.orig" <draft-ietf-ospf-lls-interface-id@ietf.orig>
Thread-Topic: OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02
Thread-Index: AQHUBxh05ZDWeCznxUCL6RlXKqUk2aRmJJQA
Date: Mon, 18 Jun 2018 15:31:47 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_53d81d5587454ee381b163f049dad1b4XCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Lsr] OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 18 Jun 2018 15:31:52 -0000

Hello Acee/All,

I am not aware of any IPR that applies to this draft.


From: Lsr <> On Behalf Of Acee Lindem (acee)
Sent: 18 June 2018 20:55
To:; draft-ietf-ospf-lls-interface-id@ietf.orig
Subject: [Lsr] OSPF LLS Extensions for Local Interface ID Advertisement - draft-ietf-ospf-lls-interface-id-02

Authors,  LSR WG,

This mail is to start the Working Group Last Call IPR poll on the subject document.

Are you aware of any IPR that applies to draft-ietf-ospf-lls-interface-id?

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 currently no IPR disclosures against draft-ietf-ospf-lls-interface-id.

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