[lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt
Padma Pillay-Esnault <padma.ietf@gmail.com> Fri, 23 January 2026 07:23 UTC
Return-Path: <padma.ietf@gmail.com>
X-Original-To: lisp@mail2.ietf.org
Delivered-To: lisp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id ABEDAABD88F0 for <lisp@mail2.ietf.org>; Thu, 22 Jan 2026 23:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0eGLkgUnQCO for <lisp@mail2.ietf.org>; Thu, 22 Jan 2026 23:23:46 -0800 (PST)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B9D51ABD88D9 for <lisp@ietf.org>; Thu, 22 Jan 2026 23:23:45 -0800 (PST)
Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-65063a95558so2766660a12.0 for <lisp@ietf.org>; Thu, 22 Jan 2026 23:23:45 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1769153025; cv=none; d=google.com; s=arc-20240605; b=OI6qnyUNQ+PrDD2TOspdY6VCTmCvZw9xhB3LGRMx/qS61hUYcj7Lwk6mx0Fh0D+nk4 yxAmCXsnwzLPd49JMPzFNr7LEZaVq1TFeI9RD0MuZffgSjSLS2WKgazn48X/b2CAHEyf iH567ZAL+zgS9QecfjBjhfip98PdPsY3W9SJsLFUGO3jUxNtQU9+T/XO07Qz7aw99OTW LBZNp8CPZMv4rFgs88gsaMvO1/ZYXv9aBXkgkdcLh/bmL8RbvNcOzNCAwgXlj6hiFu32 z2uWb7QLeEuu5nc0dC7emt9TAi6D1G4QlMF6odqffQBbVo7xI1rrZts8OQ5FZZ3wV02D DYww==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=ijAcbB28087HmW1EQddPwyS/Mu5yBJNqtpmqbv2QQ0s=; fh=y3tHIiNCXV4MfFYN0eND928+8x4JlFDe8cw43onHzsI=; b=DoSAcOLetpnSYvSY9VwtFVLB5nuzAfwo5Jo1kYE2w3IqNSqFfGycX3I4DJ8Wi/3EFA sM5V/65ReDJipgh49xHDGnUdTo020awAniTW5raVi9vujSI3810vqCsuZBGoygwpLqpR 69RoqrsiuFi5kvcXUWlXXfIagbSuShIQZtVrrITkfSrHDqek7o/JXUvN8ZnZ7OcDEw0J LHTWJ4Va0p6FkiIcsQrPzz6Zql/hmRGihZpKLYnDpABIMrP7+wI7chWAcD/NhvONASjD LepWsXUZ450BdaIkaY33weOjpXarSOM481VyafYEfskvswTUnSueQbHlbeYCEiLywUkL 8QDA==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1769153025; x=1769757825; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ijAcbB28087HmW1EQddPwyS/Mu5yBJNqtpmqbv2QQ0s=; b=eOZKYiUnqcr2kvtffTs0BXI6mh2K8mJT7STXMySiBluIyk4FK8jpJ5KkiFi1uLCo7F 9mtEPuxz+EtWm1rPhOlLF81v0Enf8JijFPi939YpOwuX60iRnr40N77yXmsTFy+rWhYx xDeDBJC1/rjNMIMrR8gEQymJ6XzGs0DZwFtlA6mlFJivKfAWTxtg7R7hfoRFQ4eHDB7U hZF9/mz+x7KU+rnew77iryif0nzQV0cNlitdlr1MXzuTBf1n6QzWayCb1KpDiPedPLph OdDEnSsnanQph7Ni9JK14g8tAO+7J3pQtUCfPFJiwWrQUxQG8zGV061qyP/NnwcuFRRf noTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1769153025; x=1769757825; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ijAcbB28087HmW1EQddPwyS/Mu5yBJNqtpmqbv2QQ0s=; b=snMc/Cdibl4lqzTNQ2pBVfpq+fS8C5PyukJ2L25B9JpgRhruw0vwtVa8d4MzjVXi+3 gACcERDNMZE45/Txk3WWHobJzEezX3Qx8UKVhE8ZJq2njKAvxmoZ+x4iZDeCQPxjrN31 AdDdQZK7pwmaY+erFI96OYg1dY5tYi6afNbs4UOCKvdyb5/eDa350YbQtHpPSa+9TuMg a6U3iOeQAXRPu7elhXLLTiShuNwBxIAa2hbS86dmzFFEOvCrOJ+aKg6eAaxnk4+26BA0 4uwLdIDR1Lk23I6pbsZB91sgxXibpHjx2xPpjt7eFdpi9BvqMcFojpOa45sgdTUpu+ia fBxg==
X-Forwarded-Encrypted: i=1; AJvYcCX5muEdla9e/04wm/KoqA4UhGe22wpxzsfA3HgwQ5lFxD4AYRPIbqMPzuJFcnGSjP7BFJz1@ietf.org
X-Gm-Message-State: AOJu0Yz/twAsJRHyd0Ct/BM2HSr/HAWzOq2nPn7josHUlz2zWOX5NK1j tyCt9f9UsMDKhjj3mxpugrprQA01xqJCYkZI2ZYG2ptNV5y9yvCSJQY7YHMOThkJAgE7I4iVW9X 6VeMwP953iBT1wWY30ByGqebZu1JJsGA=
X-Gm-Gg: AZuq6aKzPl29Cl8tf1AdZk1ZJBc+1yV+B2+RFdRHmP0Jp8AcBD2G7iR09IVHFv+erTJ 43tCTO3mb9NjGBZ56+7cRh4Gtpm14TDL1e5+L/AkyIBoVmOFcA9zgdAJCqs1ePtSw1PPDVdoLg1 7BkZ6zuKt7AntIGGTipS4ESl4AXhhMTBzEKG7F3dSZ2X8ISACdZ5/Ei1L8dWioPopxa6yB/OP3/ oTbKWnPajMlCgiOuIcMuNclpx5y61HkrQw/4brgyrJHcDUr58QiJ9UxOetJ+Z+TXjVq7a0=
X-Received: by 2002:a05:6402:3581:b0:658:1a41:13c with SMTP id 4fb4d7f45d1cf-6584874e1d1mr1046801a12.1.1769153024198; Thu, 22 Jan 2026 23:23:44 -0800 (PST)
MIME-Version: 1.0
References: <176800633753.260671.6895206452673113136@dt-datatracker-5656579b89-r5kdq> <CAG-CQxqrOtvviJ+ayck6UKJte9RFE79HSUf5WNd5xN0nCK1yQw@mail.gmail.com> <CAH6gdPxYjYUgjRAR5F+TVzLMc4bu2bCy9kjysn-wxreS6Twmtg@mail.gmail.com>
In-Reply-To: <CAH6gdPxYjYUgjRAR5F+TVzLMc4bu2bCy9kjysn-wxreS6Twmtg@mail.gmail.com>
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Thu, 22 Jan 2026 23:23:32 -0800
X-Gm-Features: AZwV_QjDSQeWXRnf7X2U-NIcdyEU0MeoEr0gPrKzAlG8Hlz-4V_ciADVL-mCikc
Message-ID: <CAG-CQxr=MsAKFAo5ETuxTe9WZRG3Jf2CJB1X9-7sdqN0q3y5_Q@mail.gmail.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008f8ede0649090958"
Message-ID-Hash: AVK2SF5TSAS2OMUA5AD5E5K7WW5ZZPKF
X-Message-ID-Hash: AVK2SF5TSAS2OMUA5AD5E5K7WW5ZZPKF
X-MailFrom: padma.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-lisp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Dhruv Dhody <dd@dhruvdhody.com>, BOUCADAIR Mohamed IMT/OLN <mohamed.boucadair@orange.com>, lisp-chairs@ietf.org, LISP mailing list list <lisp@ietf.org>, draft-ietf-lisp-te@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/4eyDkusz9LGrE8YDxgQO9SXuANY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Owner: <mailto:lisp-owner@ietf.org>
List-Post: <mailto:lisp@ietf.org>
List-Subscribe: <mailto:lisp-join@ietf.org>
List-Unsubscribe: <mailto:lisp-leave@ietf.org>
Hi Ketan, Thank you for flagging this. In the current *-24* draft, the clarification and references to existing LISP behavior (including multicast) are present earlier in the document, in *Section 7*. During the edits between -22 and -24 (notably the addition of new sections), the section numbering shifted, so what was previously “Multicast section 10" is no longer numbered the same way. That text explicitly relies on existing LISP specifications (including RFC 6831) and clarifies that this document does not redefine LISP multicast behavior is in section 7. So substantively, the point you raised is addressed, just not under the section number you originally cited. If you think it would improve clarity, we can certainly add an explicit cross-reference to RFC 6831 in a more visible way in section 8 as well. Thanks again for the careful review. Best regards, Padma On Thu, Jan 22, 2026 at 5:40 AM Ketan Talaulikar <ketant.ietf@gmail.com> wrote: > Hi Padma, > > Appreciate your help in working on this document and posting the updates. > > My ballot was non-blocking comments. I will let the other ADs drive their > DISCUSSions. > > There was just one comment that I did not find covered (or I possibly > missed the response): > > "Regarding Section 10 Multicast, I believe some references to LISP > multicast documents are necessary. Perhaps RFC6831 can be referenced again > here. I am not sure if any other is needed." > > Thanks, > Ketan > > > On Sat, Jan 10, 2026 at 7:12 AM Padma Pillay-Esnault <padma.ietf@gmail.com> > wrote: > >> >> Hello Everyone >> >> Thank you again for your review and comments. >> The version -24 addresses all comments on the LC. >> >> Thanks >> Padma on behalf of all authors >> >> For your convenience i have the tracking table for these changes below >> >> *ID* >> >> *Reviewer* >> >> *Type* >> >> *Comment / Issue* >> >> *Where Addressed* >> >> *First Fixed In* >> >> MED-1 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Doc readiness / LC follow-ups >> >> Manageability & Ops >> >> *-24* >> >> MED-2 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Experimental status justification >> >> Introduction >> >> *-22* >> >> MED-3 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Deployment incentives missing >> >> Deployment Incentives >> >> *-24* >> >> MED-4 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Underlay control overstated >> >> Deployment Incentives >> >> *-24* >> >> MED-5 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Must not replace underlay protection >> >> Deployment Incentives >> >> *-24* >> >> MED-6 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Failure example viability >> >> Deployment Incentives >> >> *-24* >> >> MED-7 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Service chaining rationale >> >> Deployment Incentives / Service Chaining >> >> *-24* >> >> MED-8 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Existing service chaining not addressed >> >> Service Chaining >> >> *-24* >> >> MED-9 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Policy reasons insufficient >> >> Deployment Incentives >> >> *-24* >> >> MED-10 >> >> Mohamed Boucadair >> >> DISCUSS >> >> Interception risk acknowledgment >> >> Deployment Incentives / Security >> >> *-24* >> >> DHRUV-1 >> >> Dhruv Dhody >> >> OPSDIR >> >> No manageability section >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-2 >> >> Dhruv Dhody >> >> OPSDIR >> >> How ELPs are set >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-3 >> >> Dhruv Dhody >> >> OPSDIR >> >> How ELPs are monitored >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-4 >> >> Dhruv Dhody >> >> OPSDIR >> >> Packet drops (MUSTs) >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-5 >> >> Dhruv Dhody >> >> OPSDIR >> >> Logging expectations >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-6 >> >> Dhruv Dhody >> >> OPSDIR >> >> Failure signaling >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-7 >> >> Dhruv Dhody >> >> OPSDIR >> >> Troubleshooting guidance >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-8 >> >> Dhruv Dhody >> >> OPSDIR >> >> Verify ELP compliance >> >> Manageability / ELP Probing >> >> *-23* >> >> DHRUV-9 >> >> Dhruv Dhody >> >> OPSDIR >> >> YANG requirements >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-10 >> >> Dhruv Dhody >> >> OPSDIR >> >> Multiple mapping systems >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-11 >> >> Dhruv Dhody >> >> OPSDIR >> >> Bad ELP impact >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-12 >> >> Dhruv Dhody >> >> OPSDIR >> >> ELP validation responsibility >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-13 >> >> Dhruv Dhody >> >> OPSDIR >> >> Experimental vs Standards >> >> Introduction >> >> *-22* >> >> DHRUV-14 >> >> Dhruv Dhody >> >> OPSDIR >> >> “No protocol change” claim >> >> Abstract / Intro >> >> *-22* >> >> DHRUV-15 >> >> Dhruv Dhody >> >> OPSDIR >> >> “New RLOC encoding” wording >> >> Abstract >> >> *-22* >> >> DHRUV-16 >> >> Dhruv Dhody >> >> OPSDIR >> >> Terminology clarity >> >> Definitions >> >> *-22* >> >> DHRUV-17 >> >> Dhruv Dhody >> >> OPSDIR >> >> RTR scalability >> >> Manageability & Ops >> >> *-23* >> >> DHRUV-18 >> >> Dhruv Dhody >> >> OPSDIR >> >> Overall ops readiness >> >> Sections 1, 6, 10, 11 >> >> *-23* >> >> GORRY-1 >> >> Gorry Fairhurst >> >> DISCUSS >> >> ELP probing underspecified >> >> ELP Probing >> >> *-22* >> >> GORRY-2 >> >> Gorry Fairhurst >> >> DISCUSS >> >> ELP path validation >> >> ELP Probing >> >> *-22* >> >> GORRY-3 >> >> Gorry Fairhurst >> >> DISCUSS >> >> Monitoring expectations >> >> ELP Probing >> >> *-22* >> >> KETAN-1 >> >> Ketan Talaulikar >> >> COMMENT >> >> Probing integral >> >> ELP Probing >> >> *-22* >> >> KETAN-2 >> >> Ketan Talaulikar >> >> COMMENT >> >> Probing reference status >> >> ELP Probing >> >> *-22* >> >> KETAN-3 >> >> Ketan Talaulikar >> >> COMMENT >> >> Service chaining ambiguity >> >> Service Chaining / Deployment Incentives >> >> *-24* >> >> KETAN-4 >> >> Ketan Talaulikar >> >> COMMENT >> >> Which traffic to services >> >> Service Chaining >> >> *-24* >> >> KETAN-5 >> >> Ketan Talaulikar >> >> COMMENT >> >> Experimental track concern >> >> Introduction >> >> *-22* >> >> KETAN-6 >> >> Ketan Talaulikar >> >> COMMENT >> >> LCAF maturity >> >> Introduction >> >> *-22* >> >> KETAN-7 >> >> Ketan Talaulikar >> >> COMMENT >> >> Multicast refs missing >> >> Multicast Considerations >> >> *-22* >> >> KETAN-8 >> >> Ketan Talaulikar >> >> COMMENT >> >> Multicast behavior >> >> Multicast Considerations >> >> *-22* >> >> GENART-1 >> >> Peter Yee >> >> GEN-ART >> >> Abstract implies new encoding >> >> Abstract >> >> *-22* >> >> GENART-2 >> >> Peter Yee >> >> GEN-ART >> >> Intro ordering >> >> Introduction >> >> *-22* >> >> GENART-3 >> >> Peter Yee >> >> GEN-ART >> >> Acronyms expanded >> >> Intro / Definitions >> >> *-22* >> >> GENART-4 >> >> Peter Yee >> >> GEN-ART >> >> Path stretch defined >> >> Introduction >> >> *-22* >> >> GENART-5 >> >> Peter Yee >> >> GEN-ART >> >> ELP definition consistency >> >> Definitions / Sec 5 >> >> *-22* >> >> GENART-6 >> >> Peter Yee >> >> GEN-ART >> >> SHOULD/MAY usage >> >> Definitions >> >> *-22* >> >> GENART-7 >> >> Peter Yee >> >> GEN-ART >> >> ELP retrieval failure >> >> Section 5 >> >> *-22* >> >> GENART-8 >> >> Peter Yee >> >> GEN-ART >> >> CoS terminology >> >> Section 4.3 >> >> *-22* >> >> GENART-9 >> >> Peter Yee >> >> GEN-ART >> >> Loop wording >> >> Section 4.4 >> >> *-22* >> >> GENART-10 >> >> Peter Yee >> >> GEN-ART >> >> Expired reference >> >> References >> >> *-22* >> >> ERIC-1 >> >> Eric Vyncke >> >> COMMENT >> >> Security over-claim >> >> Security Considerations >> >> *-23* >> >> ERIC-2 >> >> Eric Vyncke >> >> COMMENT >> >> Interception risk clarity >> >> Security Considerations >> >> *-23* >> >> ADRIAN-1 >> >> Adrian Farrel >> >> COMMENT >> >> TE definition alignment >> >> Introduction >> >> *-22* >> >> ADRIAN-2 >> >> Adrian Farrel >> >> COMMENT >> >> RFC 9522 reference >> >> Introduction >> >> *-22* >> >> CHEN-1 >> >> Meiling Chen >> >> COMMENT >> >> Missing architecture figure >> >> Architecture / Figures >> >> *-22* >> >> CHEN-2 >> >> Meiling Chen >> >> COMMENT >> >> Protocol scope unclear >> >> Introduction / Architecture >> >> *-22* >> >> CHEN-3 >> >> Meiling Chen >> >> COMMENT >> >> Security risks analysis >> >> Security Considerations >> >> *-24* >> >> IANA-1 >> >> IANA (David Dong) >> >> IANA >> >> Registry actions >> >> IANA Considerations >> >> *-22* >> >> IANA-2 >> >> IANA (David Dong) >> >> IANA >> >> Retain IANA section >> >> IANA Considerations >> >> *-22* >> >> ---------- Forwarded message --------- >> From: <internet-drafts@ietf.org> >> Date: Fri, Jan 9, 2026 at 4:52 PM >> Subject: [lisp] I-D Action: draft-ietf-lisp-te-24.txt >> To: <i-d-announce@ietf.org> >> Cc: <lisp@ietf.org> >> >> >> Internet-Draft draft-ietf-lisp-te-24.txt is now available. It is a work >> item >> of the Locator/ID Separation Protocol (LISP) WG of the IETF. >> >> Title: LISP Traffic Engineering >> Authors: Dino Farinacci >> Michael Kowal >> Parantap Lahiri >> Padma Pillay-Esnault >> Name: draft-ietf-lisp-te-24.txt >> Pages: 25 >> Dates: 2026-01-09 >> >> Abstract: >> >> This document describes how Locator/Identifier Separation Protocol >> (LISP) re-encapsulating tunnels can be used for Traffic Engineering >> purposes. The mechanisms described in this document require no LISP >> protocol changes and specify how existing Routing Locator encodings >> are used to construct Explicit Locator Paths for traffic engineering >> purposes. The Traffic Engineering features provided by these LISP >> mechanisms can span intra-domain, inter-domain, or a combination of >> both. >> >> The IETF datatracker status page for this Internet-Draft is: >> https://datatracker.ietf.org/doc/draft-ietf-lisp-te/ >> >> There is also an HTML version available at: >> https://www.ietf.org/archive/id/draft-ietf-lisp-te-24.html >> >> A diff from the previous version is available at: >> https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-te-24 >> >> Internet-Drafts are also available by rsync at: >> rsync.ietf.org::internet-drafts >> >> >> _______________________________________________ >> lisp mailing list -- lisp@ietf.org >> To unsubscribe send an email to lisp-leave@ietf.org >> >
- [lisp] I-D Action: draft-ietf-lisp-te-24.txt internet-drafts
- [lisp] Fwd: I-D Action: draft-ietf-lisp-te-24.txt Padma Pillay-Esnault
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Padma Pillay-Esnault
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Ketan Talaulikar
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Padma Pillay-Esnault
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Dino Farinacci
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Ketan Talaulikar
- [lisp] Re: I-D Action: draft-ietf-lisp-te-24.txt Padma Pillay-Esnault