{3} Active Tickets by Milestone (18 matches)
This report shows how to color results by priority, while grouping results by milestone.
Last modification time, description and reporter are included as hidden fields for useful RSS export.
Release (18 matches)
Ticket | Summary | Component | Version | Type | Owner | Status | Created |
---|---|---|---|---|---|---|---|
#210 | What should we call this effort? | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#211 | We should talk more about why this is a hard problem. | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#212 | Section 2.2 should be more detailed. | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#213 | In use case 2.1, direct endpoint-to-endpoint connectivity may not be possible | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#214 | Should gateways figure things out completely or just punt endpoints to a closer gateway? | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#215 | Should traffic flow through the gateway while a shortcut is being established? | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#216 | Multiple interfaces or mobile endpoint | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#217 | Temporary credentials | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#218 | Exhaustive configuration | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#219 | Star topology as an admin choice | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#220 | Sec. 3.2: dangling paragraph | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#221 | IPsec architecture and proprietary approaches | p2p-vpn-problem | defect | draft-ietf-ipsecme-p2p-vpn-problem@… | new | 20/03/12 | |
#223 | Add a whitelist for known IP addresses | ddos-protection | defect | draft-ietf-ipsecme-ddos-protection@… | new | 26/11/14 | |
#224 | Cryptographic Agility | ddos-protection | defect | draft-ietf-ipsecme-ddos-protection@… | new | 26/11/14 | |
#227 | Make difficulty level part of the puzzle | ddos-protection | defect | draft-ietf-ipsecme-ddos-protection@… | new | 26/11/14 | |
#228 | Probabilistic support of legacy clients | ddos-protection | defect | draft-ietf-ipsecme-ddos-protection@… | new | 26/11/14 | |
#230 | Use puzzles for DoS protection within an IKE SA | ddos-protection | enhancement | draft-ietf-ipsecme-ddos-protection@… | new | 10/04/15 | |
#229 | Need to decide the nature of the puzzle | ddos-protection | task | draft-ietf-ipsecme-ddos-protection@… | new | 10/04/15 |
Note:
See TracReports for help on using and creating reports.