Custom Query (81 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Ticket Summary Owner Type Priority Component Severity
#1 Proposal for new Path MTU behavior technical major draft-ietf-lisp -
#2 lisp-ms needs mandatory key management and security mechanism technical major ms -
#4 LISP errors technical major draft-ietf-lisp -
#6 LISP ITRs using value of 0 for UDP Checksum in IPv6 LISP outer header technical major draft-ietf-lisp -
#7 LISP ETRs ignoring checksum value in LISP UDP outer header on decapsulation technical major draft-ietf-lisp -
#8 Limits on "Gleaned" Map Entries Not Clear hartmans-ietf@… technical major draft-ietf-lisp -
#9 Sending UDP Zero Checksums Violates RFC 2460 technical major draft-ietf-lisp -
#10 Sending UDP Zero Checksums not Universally Implemented technical major draft-ietf-lisp -
#11 Not Checking Inbound Non-Zero UDP Checksums Violates RFC 1122 and RFC 2460 technical major draft-ietf-lisp -
#12 Not Checking Inbound Non-Zero Checksums not Universally Implemented. technical major draft-ietf-lisp -
#13 Use of Zero UDP Checksums (in IPv4 and IPv6) Requires Analysis technical major draft-ietf-lisp -
#14 LAG/ECMP Requirements Not Well-Explained technical major draft-ietf-lisp -
#16 Map versioning discussion technical major draft-ietf-lisp -
#17 Data plane request for control-plane reply technical major draft-ietf-lisp -
#18 record count >1 for map request dino@… technical major draft-ietf-lisp -
#19 mobility bit in map reply technical major draft-ietf-lisp -
#20 SMR bit only in control plane technical major draft-ietf-lisp -
#22 An ETR MUST consume UDP port 4342 packets not addressed to it technical major alt -
#24 Encapsulated control packets on the LISP data port 4341 technical major draft-ietf-lisp -
#28 An ITR may claim a larger prefix than is delegated to it technical major draft-ietf-lisp -
#39 On the performance of cache lookup (from D. Papadimitriou's review) technical major draft-ietf-lisp -
#40 On the handling of decapsulated packets (from D. Papadimitriou's review) technical major draft-ietf-lisp -
#44 LISP vs existing (reported by Yakov Rekhter) technical major draft-ietf-lisp -
#45 LISP vs. Existing (from Y. Rekhter) technical major draft-ietf-lisp -
#47 Ambiguity on "MAP-replies" requirements (review by Y. Rekhter) technical major draft-ietf-lisp -
#48 MAP-Replies returning different contents for a given EID (review by Y, Rekhter) technical major draft-ietf-lisp -
#49 "MAP-Replies" content that is allowed to change (review by Y. Rekhter) technical major draft-ietf-lisp -
#50 MAP-Replies content that MUST be invariant (review by Y. Rekhter) technical major draft-ietf-lisp -
#51 Returning same locator-set for a given EID (review by Y. Rekhter) technical major draft-ietf-lisp -
#56 ETR unreachability (review by Y. Rekhter) technical major draft-ietf-lisp -
#57 How to determine EIDs not forwardable on the routable topology (from Y. Rekhter's review) technical major draft-ietf-lisp -
#58 LISP breaking RPF and used as anonymization service (from Y. Rekhter's review) technical major draft-ietf-lisp -
#63 On the use of anycast addresses for RLOCs (from Y. Rekhter's review) technical major draft-ietf-lisp -
#66 Strict RLOC ordering causing problems on mapping changes technical major draft-ietf-lisp -
#68 What is the source address for a negative reply, which has a zero length locator -set ? (from Y. Rekhter's review) technical major draft-ietf-lisp -
#69 Inadequate solution for ETR overclaims (from Y. Rekhter's review) technical major draft-ietf-lisp -
#70 Client not respecting RLOC weights (from Y. Rekhter's review) technical major draft-ietf-lisp -
#76 Implication of using anycast addresses for Map-servers technical major ms -
#80 Router Performances technical major draft-ietf-lisp -
#82 Wording in Abstract (comment 8 and 44 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#83 Wording in Abstract (comment 8 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#84 Renumbering burden when clients change providers (comment 9 reported by Y. Rekhter) technical major draft-ietf-lisp -
#85 Mobility without address changing (comment 9 reported by Y. Rekhter) technical major draft-ietf-lisp -
#86 On the design goals and requirements (comment 10 reported by Y. Rekhter) technical major draft-ietf-lisp -
#88 "Proxy device" description (comment 12 reported by Y. Rekhter) technical major draft-ietf-lisp -
#89 On redefining the name of the encapsulated packet header (comment 12 reported by Y. Rekhter) technical major draft-ietf-lisp -
#90 Restricting re-encapsulation (comment 12 reported by Y. Rekhter) technical major draft-ietf-lisp -
#91 Data probe (comment 12 reported by Y. Rekhter) technical major draft-ietf-lisp -
#93 VPN (comment 14 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#94 Implications on using Control plane for data forwarding (comment 15 reported by Y. Rekhter) technical major draft-ietf-lisp -
#96 Confidence in informal Survey (comment 16 reported by Y. Rekhter) technical major draft-ietf-lisp -
#97 MTU concerns (comment 16 reported by Y. Rekhter) technical major draft-ietf-lisp -
#98 LISP nonce (comment 17 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#99 Confusion in Section 5.4.1 (comment 18 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#100 "Stateless" and "Stateful" MTU handling (comment 18 reported by Y. Rekhter) technical major draft-ietf-lisp -
#102 Originating ITR RLOC address (comment 20 reported by Y. Rekhter) technical major draft-ietf-lisp -
#103 Mapping Protocol Data (comment 20 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#104 Impact of slashdotting ETR (comment 21 reported by Y. Rekhter) technical major draft-ietf-lisp -
#105 EID-to-RLOC UDP Map-Reply message (comment 23 reported by Y. Rekhter) technical major draft-ietf-lisp -
#106 Unassigned values in Map-Reply messages (comment 22 reported by Y. Rekhter) technical major draft-ietf-lisp -
#107 "Weight" in Map-Reply Message Format (comment 22 reported by Y. Rekhter) technical major draft-ietf-lisp -
#109 "Locator" in Map-reply message format (comment 22 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#110 "Mapping Protocol Data" in Map-Reply Message Format (comment 22 reported by Y. Rekhter) editorial major draft-ietf-lisp -
#111 Semantics of LSB technical major draft-ietf-lisp -
#113 inbound traffic engineering support with LISP technical major draft-ietf-lisp -
#114 EID-to-RLOC mapping - transients technical major alt -
#115 claims in Section 7 technical major draft-ietf-lisp -
#5 protocol version in lisp header technical minor draft-ietf-lisp -
#21 Section 5.1 behavior technical minor alt -
#23 inner source RLOC undefined in some cases technical minor ms -
#38 On the limitation of LISP recursive encapsulation (from D. Papadimitriou's review) technical minor draft-ietf-lisp -
#41 Map-Reply sent for not reachable EID (from D. Papadimitriou's review) technical minor draft-ietf-lisp -
#43 Issues related to RLOC rechability (definition and mechanism) technical minor draft-ietf-lisp -
#71 Missing description mechanism to make EID-to-RLOC (from D. Papadimitriou's review) technical minor draft-ietf-lisp -
#77 On the use of key-chaining for re-keying technical minor ms -
#78 Missing things (from J. Arkko's mail) technical minor ms -
#95 On eliminating vs. deferring mapping lookup (comment 15 reported by Y. Rekhter) editorial minor draft-ietf-lisp -
#108 "R" bit in Map-Reply message format (comment 22 reported by Y. Rekhter) editorial minor draft-ietf-lisp -
#33 Editorial Issues Section 7 of draft-ietf-lisp-06.txt editorial trivial draft-ietf-lisp -
#34 Editorial Issues Section 8 of draft-ietf-lisp-06.txt editorial trivial draft-ietf-lisp -
#112 use of re-encapsulation is underspecified editorial trivial draft-ietf-lisp -
Note: See TracQuery for help on using queries.