lisp Discussion Archive - Thread Index
[Prev Page] [Next Page] [Date Index]
[IETF Mailing List Directory]
[lisp List Information]
- Re: [lisp] EID allocation / ALT base, (continued)
- [lisp] Deployment: Map Resolvers,
Joel M. Halpern
- [lisp] Deployment Document - P-ITR,
Joel M. Halpern
- Re: [lisp] Deployment Document - P-ITR,
Loránd Jakab
- <Possible follow-ups>
- Re: [lisp] Deployment Document - P-ITR,
Noel Chiappa
- Re: [lisp] Deployment Document - P-ITR,
Dino Farinacci
- Re: [lisp] Deployment Document - P-ITR,
Joel M. Halpern
- Re: [lisp] Deployment Document - P-ITR,
Dino Farinacci
- Re: [lisp] Deployment Document - P-ITR,
Joel M. Halpern
- Re: [lisp] Deployment Document - P-ITR,
Dino Farinacci
- Re: [lisp] Deployment Document - P-ITR,
Joel M. Halpern
- Re: [lisp] Deployment Document - P-ITR,
Dino Farinacci
- [lisp] EID allocation / ALT base,
Joel M. Halpern
- Re: [lisp] EID allocation / ALT base,
Dino Farinacci
- Re: [lisp] EID allocation / ALT base,
Joel M. Halpern
- Re: [lisp] EID allocation / ALT base,
Dino Farinacci
- [lisp] I-D Action:draft-ietf-lisp-multicast-04.txt,
Internet-Drafts
- [lisp] I-D Action:draft-ietf-lisp-lig-01.txt,
Internet-Drafts
- [lisp] I-D Action:draft-ietf-lisp-09.txt,
Internet-Drafts
- [lisp] Is LISP specifying a mechanizm to encapsulate an outer IP header over IP frame?,
Linda Dunbar
- [lisp] Proposed minor updates to draft-ietf-lisp-09.txt,
Dino Farinacci
- [lisp] I-D Action:draft-ietf-lisp-map-versioning-00.txt,
Internet-Drafts
- [lisp] Fwd: New Version Notification for draft-jakab-lisp-deployment-00,
LorÃnd Jakab
- [lisp] IETF 79 request for agenda items,
Terry Manderson
- [lisp] Fwd: NomCom 2010-2011: Call for More Nominations,
Joel M. Halpern
- [lisp] lig updated....,
David Meyer
- [lisp] I-D Action:draft-ietf-lisp-interworking-01.txt,
Internet-Drafts
- [lisp] draft-schudel-lisp-mib-00.txt,
Dino Farinacci
- [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Terry Manderson
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Dino Farinacci
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Job W. J. Snijders
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Damien Saucez
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Yakov Rekhter
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Victor Moreno (vimoreno)
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Robert Raszuk
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Amit Jain
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Loránd Jakab
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
brad dreisbach
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
brad dreisbach
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Terry Manderson
- <Possible follow-ups>
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
David Meyer
- Re: [lisp] draft-farinacci-lisp-lcaf-00 as a work group item,
Niels Raijer
- [lisp] draft-iannone-lisp-mapping-versioning as a work group item,
Terry Manderson
- [lisp] I-D Action:draft-ietf-lisp-08.txt,
Internet-Drafts
- [lisp] Draft minutes from IETF78 Maastricht,
Terry Manderson
- [lisp] Updates for draft-ietf-lisp-08.txt,
Dino Farinacci
- [lisp] Issue Title (number): SMR handling (42),
Darrel Lewis
- [lisp] Issue Title (number): RLOC Reachability (43),
Darrel Lewis
- [lisp] Issue Title (number): Map Reply Consistency (47, 48, 49, 50),
Darrel Lewis
- [lisp] Proposed changes to draft-ietf-lisp-08.txt,
Dino Farinacci
- [lisp] Issue Title (number): Data Probe Decap (40),
Darrel Lewis
- [lisp] Issue Title (number): LISP for inbound TE (113),
Darrel Lewis
- [lisp] Issue Title (number): Re-encapsulating Tunnels underspecefied (112),
Darrel Lewis
- [lisp] Issue Title (number): Anycasting RLOCs (111),
Darrel Lewis
- [lisp] Issue Title (number): Returning all 3 prefixes (105),
Darrel Lewis
- [lisp] Issue Title (number): MTU and ICMP Filtering(101),
Darrel Lewis
- [lisp] Issue Title (number): ETR support of Map-Requests Flood(104),
Darrel Lewis
- [lisp] Issue Title (number): Originating ITR address (102),
Darrel Lewis
- [lisp] Issue Title (number): MTU handling Stateless(100),
Darrel Lewis
- [lisp] Issue Title (number): LISP Data Packet Nonce(98),
Darrel Lewis
- [lisp] Issue Title (number): Control Plane Performance (94),
Darrel Lewis
- [lisp] Issue Title (number): Limiting number of headers(90),
Darrel Lewis
- [lisp] Issue Title (number): Naming of the Inner Header (89),
Darrel Lewis
- [lisp] Issue Title (number): PIvsPA (87),
Darrel Lewis
- [lisp] Issue Title (number): Lock in to EID Provider (84),
Darrel Lewis
- [lisp] Issue Title (number): Editorial comment about LISP (82),
Darrel Lewis
- [lisp] Issue Title (number): Site location of xTRs (81),
Darrel Lewis
- [lisp] Issue Title (number): Editorial Comments to Section 8 (34),
Darrel Lewis
- [lisp] Issue Title (number): Header Prepending (38),
Darrel Lewis
- [lisp] Issue Title (number): Map-Cache Validation (36),
Darrel Lewis
- [lisp] Issue Title (number): EID to RLOC selection (73),
Darrel Lewis
- [lisp] Issue Title (number): EID to RLOC selection (71),
Darrel Lewis
- [lisp] Issue Title (number): Cache Lookup Performance (39),
Darrel Lewis
- [lisp] Issue Title (number): ITR ignoring weights (70),
Darrel Lewis
- [lisp] Issue Title (number): Map-Reply Security (69),
Darrel Lewis
- [lisp] Issue Title (number): Source of Negative Map Reply (68),
Darrel Lewis
- [lisp] Issue Title (number): LSB handling details (66),
Darrel Lewis
- [lisp] Issue Title (number): Host BAsed Implementation (64),
Darrel Lewis
- [lisp] Issue Title (number): LISP-TE and ETR(63),
Darrel Lewis
- [lisp] Issue Title (number): LISP and uRPF and Anonomous Tunneling(58),
Darrel Lewis
- [lisp] Issue Title (number): How to determine EIDs not forwardable on the routable(57),
Darrel Lewis
- [lisp] Issue Title (number): ETR Failure Restoration (55),
Darrel Lewis
- [lisp] Issue Title (number): ITR Failure Restoration (54),
Darrel Lewis
- [lisp] Issue Title (number): EID Reachability (53),
Darrel Lewis
- [lisp] Issue Title (number): LISP vs Multihoming w NAT (45),
Darrel Lewis
- [lisp] Issue Title (number): LISP Cache Handling (46),
Darrel Lewis
- [lisp] Issue Title (number): LISP vs PI addressing (44),
Darrel Lewis
- [lisp] Issue Title (number): Map Reply Sent when EID is unreachable (41),
Darrel Lewis
- [lisp] IETF78 draft agenda,
Terry Manderson
- [lisp] draft-klein-lisp-mn-nat-traversal-00 and TTR Mobility,
Robin Whittle
- [lisp] Fwd: I-D Action:draft-saucez-lisp-security-01.txt,
Damien Saucez
- [lisp] Updated EEMDP proposal for managing holes in maps,
Sriram, Kotikalapudi
- [lisp] [Fwd: New Version Notification for draft-klein-lisp-mn-nat-traversal-00],
Michael Menth
- [lisp] [Fwd: Please volunteer for the 2010-2011 Nomcom],
Joel M. Halpern
- [lisp] planning for IETF78,
Terry Manderson
- [lisp] [Fwd: IETF 78 - Meeting and Sponsorship Information],
Joel M. Halpern
- [lisp] LISP WG meeting on IETF 78,
Humberto Galiza
- [lisp] More work needed I think.,
Terry Manderson
- [lisp] #113: inbound traffic engineering support with LISP,
lisp issue tracker
- [lisp] #112: use of re-encapsulation is underspecified,
lisp issue tracker
- [lisp] #111: Semantics of LSB,
lisp issue tracker
- [lisp] #110: "Mapping Protocol Data" in Map-Reply Message Format (comment 22 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #109: "Locator" in Map-reply message format (comment 22 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #108: "R" bit in Map-Reply message format (comment 22 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #107: "Weight" in Map-Reply Message Format (comment 22 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #106: Unassigned values in Map-Reply messages (comment 22 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #105: EID-to-RLOC UDP Map-Reply message (comment 23 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #104: Impact of slashdotting ETR (comment 21 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #103: Mapping Protocol Data (comment 20 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #102: Originating ITR RLOC address (comment 20 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #101: Filtering ICMP messages (comment 19 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #100: "Stateless" and "Stateful" MTU handling (comment 18 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #99: Confusion in Section 5.4.1 (comment 18 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #98: LISP nonce (comment 17 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #97: MTU concerns (comment 16 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #96: Confidence in informal Survey (comment 16 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #95: On eliminating vs. deferring mapping lookup (comment 15 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #94: Implications on using Control plane for data forwarding (comment 15 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #93: VPN (comment 14 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #92: Restriction on number of encapsulations (comment 13 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #91: Data probe (comment 12 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #90: Restricting re-encapsulation (comment 12 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #89: On redefining the name of the encapsulated packet header (comment 12 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #88: "Proxy device" description (comment 12 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
lisp issue tracker
- <Possible follow-ups>
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Joel M. Halpern
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Joel M. Halpern
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Joel M. Halpern
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #87: On reusing globally routed address block as EID-prefix (comment 11 reported by Y. Rekhter),
Yakov Rekhter
- [lisp] #86: On the design goals and requirements (comment 10 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #85: Mobility without address changing (comment 9 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Eliot Lear
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Ross Callon
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Robert Raszuk
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Eliot Lear
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Ross Callon
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Darrel Lewis
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Eliot Lear
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
Joel M. Halpern
- <Possible follow-ups>
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #84: Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #83: Wording in Abstract (comment 8 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #82: Wording in Abstract (comment 8 reported by Y. Rekhter),
lisp issue tracker
- [lisp] #81: Implication of deploying of xTRs as first/last hop.,
lisp issue tracker
- [lisp] #80: Router Performances,
lisp issue tracker
- [lisp] Fwd: New Version Notification for draft-ietf-lisp-ms-05,
Vince Fuller
- [lisp] Fwd: New Version Notification for draft-ietf-lisp-alt-04,
Vince Fuller
- [lisp] I-D Action:draft-ietf-lisp-ms-05.txt,
Internet-Drafts
- [lisp] I-D Action:draft-ietf-lisp-alt-04.txt,
Internet-Drafts
- [lisp] issue tracker,
Joel M. Halpern
- [lisp] #79: Editorial Issues (from J. Arkko's mail),
lisp issue tracker
- [lisp] #78: Missing things (from J. Arkko's mail),
lisp issue tracker
- [lisp] #77: On the use of key-chaining for re-keying,
lisp issue tracker
- [lisp] #76: Implication of using anycast addresses for Map-servers,
lisp issue tracker
- [lisp] #75: Security of Map-Register message.,
lisp issue tracker
- [lisp] I-D Action:draft-ietf-lisp-07.txt,
Internet-Drafts
- Re: [lisp] LISP Site definition,
Noel Chiappa
- [lisp] draft-ietf-lisp-07.txt ready to post,
Darrel Lewis
- [lisp] #74: Deployment Scenarios (from R. Bonica review for the RTG directorate),
lisp issue tracker
- [lisp] #73: Tunnel liveness (from R. Bonica review for the RTG directorate),
lisp issue tracker
- Re: [lisp] #32: Editorial Issues Section 6 ofdraft-ietf-lisp-06.txt raised by Dimitri Papadimitriou in his review,
Noel Chiappa
- Re: [lisp] Discussion of comment 3 (Map-Replies) [was: Re: comments on draft-ietf-lisp-06.txt (part 1)],
Noel Chiappa
- [lisp] #72: RTT estimation for the forwarding path (from D. Papadimitriou's review),
lisp issue tracker
- [lisp] #71: Missing description mechanism to make EID-to-RLOC (from D. Papadimitriou's review),
lisp issue tracker
- [lisp] #70: Client not respecting RLOC weights (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #69: Inadequate solution for ETR overclaims (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #68: What is the source address for a negative reply, which has a zero length locator -set ? (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #67: What would it mean if N were clear and E were set? (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #66: Strict RLOC ordering causing problems on mapping changes (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #65: Missing step to restore 24h TTL in clock-sweep mechanism (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #64: Host based LISP implementations (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Eliot Lear
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Yakov Rekhter
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Eliot Lear
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Yakov Rekhter
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Eliot Lear
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Robert Raszuk
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Yakov Rekhter
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Robert Raszuk
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Yakov Rekhter
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Dino Farinacci
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Yakov Rekhter
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Dino Farinacci
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Olivier Bonaventure
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Robert Raszuk
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Dino Farinacci
- <Possible follow-ups>
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
Noel Chiappa
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #63: On the use of anycast addresses for RLOCs (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #62: Control of the egress tunnel endpoints by the provider ISP (from Y. Rekhter Review),
lisp issue tracker
- [lisp] #61: How to identify "traceroute packet" (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #60: Editorial Issues Section 9 of draft-ietf-lisp-06.txt (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #59: Editorial Issues Section 10 of draft-ietf-lisp-06.txt (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #58: LISP breaking RPF and used as anonymization service (from Y. Rekhter's review),
lisp issue tracker
- Re: [lisp] #15: chairs to review normative and informative references,
lisp issue tracker
- [lisp] #57: How to determine EIDs not forwardable on the routable topology (from Y. Rekhter's review),
lisp issue tracker
- [lisp] #56: ETR unreachability (review by Y. Rekhter),
lisp issue tracker
- [lisp] #55: ETR failure and its implications on connectivity restoration time (review by Y. Rekhter),
lisp issue tracker
- [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Michael Menth
- <Possible follow-ups>
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
lisp issue tracker
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Joel M. Halpern
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Joel M. Halpern
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Yakov Rekhter
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Dino Farinacci
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
John Scudder
- Re: [lisp] #54: ITR failures and implications on connectivity restoration time (review by Y. Rekhter),
Dino Farinacci
- [lisp] #53: Reachability between ETR and EID (review by Y. Rekhter),
lisp issue tracker
- [lisp] #52: Changing the EID-to-RLOC Mapping (review by Y. Rekhter),
lisp issue tracker
- [lisp] #51: Returning same locator-set for a given EID (review by Y. Rekhter),
lisp issue tracker
- [lisp] #50: MAP-Replies content that MUST be invariant (review by Y. Rekhter),
lisp issue tracker
- [lisp] #49: "MAP-Replies" content that is allowed to change (review by Y. Rekhter),
lisp issue tracker
- [lisp] #48: MAP-Replies returning different contents for a given EID,
lisp issue tracker
- [lisp] #47: Ambiguity on "MAP-replies" requirements,
lisp issue tracker
- [lisp] #46: Cache Thrashing,
lisp issue tracker
- [lisp] #45: LISP vs. Existing (from Y. Rekhter),
lisp issue tracker
- [lisp] #44: LISP vs existing,
lisp issue tracker
- [lisp] #43: Issues related to RLOC rechability (definition and mechanism) raised by D. Papadimitriou in his review,
lisp issue tracker
Mail converted by MHonArc
