From owner-p4-projects@FreeBSD.ORG Fri Jul 10 01:34:42 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 7E9D51065672; Fri, 10 Jul 2009 01:34:42 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EFA7106566C for ; Fri, 10 Jul 2009 01:34:42 +0000 (UTC) (envelope-from zjriggl@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 2DA998FC08 for ; Fri, 10 Jul 2009 01:34:42 +0000 (UTC) (envelope-from zjriggl@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n6A1YgoV033851 for ; Fri, 10 Jul 2009 01:34:42 GMT (envelope-from zjriggl@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n6A1Yg86033849 for perforce@freebsd.org; Fri, 10 Jul 2009 01:34:42 GMT (envelope-from zjriggl@FreeBSD.org) Date: Fri, 10 Jul 2009 01:34:42 GMT Message-Id: <200907100134.n6A1Yg86033849@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to zjriggl@FreeBSD.org using -f From: Zachariah Riggle To: Perforce Change Reviews Cc: Subject: PERFORCE change 165890 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jul 2009 01:34:43 -0000 http://perforce.freebsd.org/chv.cgi?CH=165890 Change 165890 by zjriggl@zjriggl_tcpregression on 2009/07/10 01:33:53 Updated Milestones Affected files ... .. //depot/projects/soc2009/zjriggl_tcpregression/Milestones#5 edit Differences ... ==== //depot/projects/soc2009/zjriggl_tcpregression/Milestones#5 (text+ko) ==== @@ -1,5 +1,29 @@ -Tentative Milestones -¥ Framework successfully tests and validates a standard TCP setup and tear-down. -¥ Framework successfully tests and validates standard TCP cases. -¥ Framework successfully tests and validates the ARP protocol, per RFC 826. -¥ Additional features and milestones TBD per project's progress.+Early May + +Become familiar with PCS +Download and set up +Run tests to ensure proper setup +Modify canned example case to do something new +Late May / June + +Get familiar with the TCP RFC. Very familiar. Uncomfortably familiar. +Start planning the test suite framework (this does not include any tests) +Start implementing framework +July + +Continue implementing framework +Implement first few tests (TCP setup/tear-down) using calls to TCP implementation to test it +Re-implement first few tests by hooking into the correct sections and manually executing the tested code segments. +Milestones + +Framework successfully tests and validates a standard TCP setup and tear-down. +Framework successfully tests and validates standard TCP cases. +LISTEN -> SYN-RECVD -> ESTABLISHED +SYN-SENT -> SYN-RECVD -> ESTABLISHED +FIN-WAIT-1 -> FIN-WAIT-2 vs. FIN-WAIT-1 -> CLOSING +Potential Milestones + +Time permitting: + +Framework successfully tests and validates the ARP protocol, per RFC 826. +Additional features and milestones TBD per project's progress.