Timeline


and

May 24, 2010:

9:10 AM Ticket #113 (inbound traffic engineering support with LISP) created by yakov@…
From Section 2: 4. Traffic engineering capabilities that can be …
9:06 AM Ticket #112 (use of re-encapsulation is underspecified) created by yakov@…
The draft does not provide sufficient details on the use of …
9:04 AM Ticket #111 (Semantics of LSB) created by yakov@…
What is the semantics and use of LSB when RLOCs are anycast addresses ?

May 11, 2010:

4:07 AM IetfSpecificFeatures edited by trac
(diff)

Apr 27, 2010:

10:51 PM Ticket #110 ("Mapping Protocol Data" in Map-Reply Message Format (comment 22 ...) created by wmhaddad@…
Section 6.1.4: Mapping Protocol Data: See [CONS] or [ALT] …
10:50 PM Ticket #109 ("Locator" in Map-reply message format (comment 22 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.4: Locator: an IPv4 or IPv6 address (as encoded by …
10:48 PM Ticket #108 ("R" bit in Map-Reply message format (comment 22 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.4: R: when this bit is set, the locator is known to …
10:47 PM Ticket #107 ("Weight" in Map-Reply Message Format (comment 22 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.4: Weight: when priorities are the same for …
10:44 PM Ticket #106 (Unassigned values in Map-Reply messages (comment 22 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.4 ACT: This 3-bit field describes negative Map-Reply …
10:37 PM Ticket #105 (EID-to-RLOC UDP Map-Reply message (comment 23 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.5 EID-to-RLOC UDP Map-Reply message A Map-Request for …
10:35 PM Ticket #104 (Impact of slashdotting ETR (comment 21 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.3 General questions on this section include what is the …
10:33 PM Ticket #103 (Mapping Protocol Data (comment 20 reported by Y. Rekhter)) created by wmhaddad@…
Mapping Protocol Data: See [CONS] or [ALT] for details. => There are …
10:32 PM Ticket #102 (Originating ITR RLOC address (comment 20 reported by Y. Rekhter)) created by wmhaddad@…
Section 6.1.2 Originating ITR RLOC Address: Used to give the …
10:29 PM Ticket #101 (Filtering ICMP messages (comment 19 reported by Y. Rekhter)) created by wmhaddad@…
Section 5.4.2 How would this work if the ITR is behind the firewall, …
10:28 PM Ticket #100 ("Stateless" and "Stateful" MTU handling (comment 18 reported by Y. Rekhter)) created by wmhaddad@…
Regarding the "stateless" and "stateful" MTU handling solutions, there …
10:26 PM Ticket #99 (Confusion in Section 5.4.1 (comment 18 reported by Y. Rekhter)) created by wmhaddad@…
Section 5.4.1 As written, this section seems broken. Perhaps the …
10:23 PM Ticket #98 (LISP nonce (comment 17 reported by Y. Rekhter)) created by wmhaddad@…
Section 5.3 LISP Nonce: is a 24-bit value that is randomly …
10:21 PM Ticket #97 (MTU concerns (comment 16 reported by Y. Rekhter)) created by wmhaddad@…
Section 5: To address MTU concerns, mainly raised on the RRG …
10:20 PM Ticket #96 (Confidence in informal Survey (comment 16 reported by Y. Rekhter)) created by wmhaddad@…
Section 5: Based on informal surveys of large ISP traffic …
10:18 PM Ticket #95 (On eliminating vs. deferring mapping lookup (comment 15 reported by Y. ...) created by wmhaddad@…
Section 4.1: In order to eliminate the need for a mapping lookup …
10:16 PM Ticket #94 (Implications on using Control plane for data forwarding (comment 15 ...) created by wmhaddad@…
Section 4.1 In LISP 1.5, the packet is routed on a different …
10:14 PM Ticket #93 (VPN (comment 14 reported by Y. Rekhter)) created by wmhaddad@…
Section 4 Another example, perhaps for a VPN service out-sourced …
10:12 PM Ticket #92 (Restriction on number of encapsulations (comment 13 reported by Y. Rekhter)) created by wmhaddad@…
Section 4: An additional LISP header may be prepended to packets …
10:10 PM Ticket #91 (Data probe (comment 12 reported by Y. Rekhter)) created by wmhaddad@…
Data Probe: a LISP-encapsulated data packet where the inner …
9:59 PM Ticket #90 (Restricting re-encapsulation (comment 12 reported by Y. Rekhter)) created by wmhaddad@…
Section 3: Reencapsulating Tunnels: when a packet has no more …
9:57 PM Ticket #89 (On redefining the name of the encapsulated packet header (comment 12 ...) created by wmhaddad@…
Section 3: Endpoint ID (EID): a 32-bit (for IPv4) or 128-bit …
9:55 PM Ticket #88 ("Proxy device" description (comment 12 reported by Y. Rekhter)) created by wmhaddad@…
Section 3 Note that this destination RLOC may be an …
9:53 PM Ticket #87 (On reusing globally routed address block as EID-prefix (comment 11 ...) created by wmhaddad@…
Section 3 A globally routed address block (whether PI or PA) is …
9:50 PM Ticket #86 (On the design goals and requirements (comment 10 reported by Y. Rekhter)) created by wmhaddad@…
Section 2 Some of the design goals of this proposal include: 1. …
9:47 PM Ticket #85 (Mobility without address changing (comment 9 reported by Y. Rekhter)) created by wmhaddad@…
Introduction: 5. Mobility without address changing. Existing …
9:45 PM Ticket #84 (Renumbering burden when clients change providers (comment 9 reported ...) created by wmhaddad@…
In the Introduction: 3. Easing of renumbering burden when clients …
9:41 PM Ticket #83 (Wording in Abstract (comment 8 reported by Y. Rekhter)) created by wmhaddad@…
The proposed protocol can be implemented in a relatively small number …
9:41 PM Ticket #82 (Wording in Abstract (comment 8 and 44 reported by Y. Rekhter)) created by wmhaddad@…
The first sentence says LISP is "simple". Yet such components of LISP …

Apr 26, 2010:

12:24 PM Ticket #81 (Implication of deploying of xTRs as first/last hop.) created by luigi@…
From Y. Rekhter's review Comment 37: Section 8.1 If ITR/ETR …
9:32 AM Ticket #80 (Router Performances) created by luigi@…
From Y. Rekhter's review This is comment 35 Section 7 …
1:34 AM Ticket #79 (Editorial Issues (from J. Arkko's mail)) created by luigi@…
Issue raised by J. Arkko in: …
1:30 AM Ticket #78 (Missing things (from J. Arkko's mail)) created by luigi@…
Issue raised by J. Arkko in: …
1:24 AM Ticket #77 (On the use of key-chaining for re-keying) created by luigi@…
Issue raise by J. Arkko in: …
1:21 AM Ticket #76 (Implication of using anycast addresses for Map-servers) created by luigi@…
Issue raise by J. Arkko in: …
1:16 AM Ticket #75 (Security of Map-Register message.) created by luigi@…
Issue raise by J. Arkko in: …
Note: See TracTimeline for information about the timeline view.