IETF Discussion (date)
August 31, 2005
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Keith Moore, 20:36
- Re: Single DNS root, JFC (Jefsey) Morfin, 20:22
- IETF last call on draft-hansen-2717bis-2718bis-uri-guidelines-05: The practical case of SMS and MMS URI schemes, Markus . Isomaki, 15:50
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Dave Singer, 15:08
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Christian Huitema, 14:25
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 14:14
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Tony Finch, 11:24
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Ian Jackson, 11:17
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Ned Freed, 11:09
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Ian Jackson, 11:08
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 11:05
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Ian Jackson, 10:53
- Re: Additional appeal against publication of draft-lyon-senderid-* in regards to its recommended use of Resent- header fields in the way that is inconsistant with RFC2822, Tony Finch, 10:39
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Eric A. Hall, 10:34
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Ned Freed, 09:55
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Ned Freed, 09:49
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Eric A. Hall, 08:52
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Christian de Larrinaga, 08:45
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Paul Hoffman, 08:30
- Alternative roots (was: Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard), Paul Hoffman, 08:28
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Christian Huitema, 07:30
- Single DNS root (Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard), Harald Tveit Alvestrand, 07:01
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 06:26
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 06:20
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 05:56
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Brian E Carpenter, 05:54
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Jeroen Massar, 04:57
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Steven M. Bellovin, 04:41
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Harald Tveit Alvestrand, 04:26
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Brian E Carpenter, 04:17
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Marc Manthey, 04:12
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Bill Manning, 03:59
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Pekka Savola, 03:27
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, william(at)elan.net, 03:12
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Frank Ellermann, 02:51
- Re: Is it necessary to go through Standards Track to Get to Historic?, Brian E Carpenter, 02:32
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 02:29
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Stephane Bortzmeyer, 01:22
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Frank Ellermann, 01:05
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Henrik Levkowetz, 00:58
August 30, 2005
- Re: STD, Doug Ewell, 22:50
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Frank Ellermann, 22:27
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' toProposed Standard, Spencer Dawkins, 20:59
- Re: Is it necessary to go through Standards Track to Get to Historic?, Frank Ellermann, 20:49
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Jeffrey Hutzelman, 20:42
- Re: Is it necessary to go through Standards Track to Get to Historic?, Bruce Lilly, 19:29
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Bruce Lilly, 19:16
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Bruce Lilly, 19:06
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Iljitsch van Beijnum, 17:05
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Russ Allbery, 16:45
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Russ Allbery, 16:37
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR) ' to Proposed Standard, Ned Freed, 16:35
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Iljitsch van Beijnum, 14:49
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 14:21
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 11:18
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 10:50
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Christian Huitema, 10:33
- RE: Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin, Hallam-Baker, Phillip, 10:32
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 09:44
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 09:32
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 08:51
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 08:37
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Brian E Carpenter, 08:07
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 07:14
- Enough was enough, JFC (Jefsey) Morfin, 06:38
- Re: Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin (Harald Tveit Alvestrand), Marc Manthey, 03:43
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Ian Jackson, 03:36
- Re: Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin (Harald Tveit Alvestrand), Peter Constable, 02:51
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Brian E Carpenter, 02:34
- Re: [Ltru] Re: STD, Brian E Carpenter, 02:25
- [spf-discuss] Re: Additional appeal against publication of draft-lyon-senderid-* in regards to its recommended use of Resent- header fields in the way that is inconsistant with RFC2822, Brian E Carpenter, 02:12
August 29, 2005
- Re: Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin, Harald Tveit Alvestrand, 23:31
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Harald Tveit Alvestrand, 23:26
- Re: Autoresponder lameness, Markus Stumpf, 20:04
- HELO SES (was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02), Frank Ellermann, 15:30
- Re: Reply-To, Frank Ellermann, 14:34
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict, Frank Ellermann, 14:01
- Re: [spf-discuss] Re: Additional appeal against publication of draft-lyon-senderid-* in regards to its recommended use of Resent- header fields in the way that is inconsistant with RFC2822, william(at)elan.net, 13:56
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Frank Ellermann, 12:00
- Re: Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin, John Leslie, 11:44
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, SM, 11:41
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, SM, 11:40
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Russ Allbery, 11:29
- Re: Additional appeal against publication of draft-lyon-senderid-* in regards to its recommended use of Resent- header fields in the way that is inconsistant with RFC2822, Frank Ellermann, 11:11
- Re: [Ltru] Re: Last Call: 'Tags for Identifying Languages' to BCP, Mark Davis, 10:38
- Re: [Ltru], Frank Ellermann, 09:41
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 09:28
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Ned Freed, 09:26
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 08:50
- RE: Is it necessary to go through Standards Track to Get to Histo ric?, Gray, Eric, 08:47
- [spf-discuss] Additional appeal against publication of draft-lyon-senderid-* in regards to its recommended use of Resent- header fields in the way that is inconsistant with RFC2822, william(at)elan.net, 08:29
- RE: Last Call: 'Tags for Identifying Languages' to BCP [Re: Ietf Digest, Vol 16, Issue 95], Peter Constable, 08:27
- Re: [Ltru] Re: STD (was: Last Call: 'Tags for Identifying Languages' to BCP), Stephane Bortzmeyer, 08:18
- Re: [Ltru] Re: STD (was: Last Call: 'Tags for Identifying Languages' to BCP), Doug Ewell, 08:03
- Re: Last Call: 'Tags for Identifying Languages' to BCP [Re: Ietf Digest, Vol 16, Issue 95], Brian E Carpenter, 07:53
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Doug Ewell, 07:41
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Doug Ewell, 07:38
- Enough is enough: Intent to file an RFC 3683 against Jefsey Morfin, Harald Tveit Alvestrand, 07:37
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Peter Constable, 06:50
- RE: Ietf Digest, Vol 16, Issue 95, Peter Constable, 06:46
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Brian E Carpenter, 06:05
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Brian E Carpenter, 05:54
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Peter Constable, 05:13
- Re: IESG powers, Brian E Carpenter, 05:03
- Re: NAT/Proxy combinations, Brian E Carpenter, 05:01
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Brian E Carpenter, 04:58
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, bmanning, 04:53
- Re: [Ltru] Re: STD (was: Last Call: 'Tags for Identifying Languages' to BCP), r&d afrac, 04:52
- e: Appeal: Publication of draft-lyon-senderid-core-01 in conflict, Go Mehwua, 04:50
- Re: [Ltru] RE: STD (was: Last Call: 'Tags for Identifying Languages'toBCP), r&d afrac, 04:46
- Re: [Ltru] Re: Last Call: language root file size (long), r&d afrac, 04:44
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Stephane Bortzmeyer, 02:52
- RE: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 01:25
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 01:24
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Pekka Savola, 00:53
- RE: NAT/Proxy combinations, Nicholas Staff, 00:31
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Scott W Brim, 00:29
- Re: [Ltru] RE: STD (was: Last Call: 'Tags for Identifying Languages'toBCP), JFC (Jefsey) Morfin, 00:21
August 28, 2005
- Re: NAT/Proxy combinations, Peter Dambier, 23:22
- Re: STD (was: Last Call: 'Tags for Identifying Languages' to BCP), Doug Ewell, 22:47
- Re: [Ltru] Re: Last Call: language root file size (long), Doug Ewell, 22:18
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 22:10
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 21:56
- Re: [Ltru] Re: Last Call: language root file size (long), Doug Ewell, 21:15
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Frank Ellermann, 20:46
- Re: Dynamic salting in encryption algorithms for peer to peer communication, Steven M. Bellovin, 20:24
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Peter Constable, 20:04
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, Harald Tveit Alvestrand, 19:50
- RE: Last Call: 'Tags for Identifying Languages' to BCP, Peter Constable, 19:44
- RE: STD (was: Last Call: 'Tags for Identifying Languages'toBCP), Peter Constable, 19:26
- Re: [Ltru] Re: Last Call: language root file size, JFC (Jefsey) Morfin, 19:00
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 18:56
- Re: Dynamic salting in encryption algorithms for peer to peer communication, Benyamin Nasution, 18:08
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Peter Constable, 17:51
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 17:43
- STD (was: Last Call: 'Tags for Identifying Languages'toBCP), JFC (Jefsey) Morfin, 17:42
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 17:41
- Re: Is it necessary to go through Standards Track to Get to Historic?, C. M. Heard, 17:34
- Re: Last Call: language root file size, Doug Ewell, 17:10
- Re: Reply-To, Bruce Lilly, 16:03
- Re: Reply-To, Bruce Lilly, 15:15
- Re: Is it necessary to go through Standards Track to Get to Historic?, Bruce Lilly, 14:55
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Frank Ellermann, 13:36
- Re: Reply-To (Was Re: [Re: regarding IETF lists using mailman: nodupes considered harmful]), Iljitsch van Beijnum, 12:47
- Re: Reply-To, Frank Ellermann, 12:33
- Re: Autoresponder lameness, Frank Ellermann, 12:23
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 11:58
- Autoresponder lameness, Bruce Lilly, 11:50
- Is it necessary to go through Standards Track to Get to Historic? (WAS: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02), C. M. Heard, 11:50
- Reply-To (Was Re: [Re: regarding IETF lists using mailman: nodupes considered harmful]), Bruce Lilly, 10:57
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Bruce Lilly, 08:28
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Bruce Lilly, 07:45
- Re: Last Call: 'Tags for Identifying Languages' to BCP, Bruce Lilly, 07:15
- Re: I-D ACTION:draft-sanz-rfc1032-historic-00.txt, SM, 07:07
- Re: Dynamic salting in encryption algorithms for peer to peer communication, David Hopwood, 07:07
- Re: Last Call: language root file size, JFC (Jefsey) Morfin, 06:58
- Dynamic salting in encryption algorithms for peer to peer communication, Atul Sabharwal, 02:30
- Re: NAT/Proxy combinations, Brian E Carpenter, 01:19
- Re: NAT/Proxy combinations, Iljitsch van Beijnum, 00:27
August 27, 2005
- NAT/Proxy combinations, Atul Sabharwal, 23:53
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, william(at)elan.net, 22:09
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 21:29
- Re: Last Call: language root file system, JFC (Jefsey) Morfin, 20:38
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Douglas Otis, 18:03
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Nicholas Staff, 15:28
- Re: Last Call: language root file system, David Hopwood, 15:26
- [spf-discuss] RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Nicholas Staff, 15:24
- Re: Last Call: language root file system, JFC (Jefsey) Morfin, 12:12
- [spf-discuss] RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, william(at)elan.net, 12:01
- RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02 MARID<ietf-mxcomp(_at_)imc(_dot_)org>, Thomas Gal, 11:24
- Re: Last Call: language root file system, David Hopwood, 09:12
- Re: IESG powers, JFC (Jefsey) Morfin, 04:37
- Last Call: language root file system, JFC (Jefsey) Morfin, 04:34
August 26, 2005
- Re: IESG powers, william(at)elan.net, 23:50
- Re: IESG powers, Frank Ellermann, 23:47
- Re: regarding IETF lists using mailman: nodupes considered harmful, Frank Ellermann, 23:22
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflict with referenced draft-schlitt-spf-classic-02, Scott Kitterman, 23:13
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflict with referenced draft-schlitt-spf-classic-02, Scott Kitterman, 23:06
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 22:30
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02 MARID <ietf-mxcomp(_at_)imc(_dot_)org>, Frank Ellermann, 21:14
- Re: [Re: regarding IETF lists using mailman: nodupes considered harmful], Joel M. Halpern, 20:51
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, John Glube, 20:41
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 20:34
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 20:06
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 19:23
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Douglas Otis, 18:03
- RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' toProposed Standard, Hallam-Baker, Phillip, 17:47
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Pete Resnick, 17:42
- Re: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, JFC (Jefsey) Morfin, 16:59
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 16:30
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Steven M. Bellovin, 16:22
- [spf-discuss] RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, william(at)elan.net, 16:21
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 15:48
- RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 15:46
- RE: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 15:39
- [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 15:11
- Re: [Re: regarding IETF lists using mailman: nodupes considered harmful], Peter Dambier, 14:47
- Re: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Sam Hartman, 14:40
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 14:23
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, Alan DeKok, 14:04
- Re: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Frank Ellermann, 14:03
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Frank Ellermann, 13:24
- Re: DKIM, Mark Baugher, 13:17
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Marc Manthey, 13:17
- Re: IESG powers, JFC (Jefsey) Morfin, 13:16
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 13:10
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 12:59
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 12:44
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Rob Austein, 12:37
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, wayne, 12:33
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 12:33
- RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 12:30
- RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 12:20
- RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 12:15
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 12:02
- RE: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Jeff Macdonald, 11:48
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Dotzero, 11:42
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, wayne, 11:37
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 11:32
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Bill Manning, 11:30
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Sam Hartman, 11:13
- RE: Appeal: Publication of draft-lyon-senderid-core-01 in conflictwith referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 10:54
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Russ Allbery, 10:39
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Douglas Otis, 10:27
- RE: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Hallam-Baker, Phillip, 10:26
- DKIM, Keith Moore, 10:26
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Mark Baugher, 10:19
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Keith Moore, 09:43
- Re: DKIM, Keith Moore, 09:37
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Iljitsch van Beijnum, 09:30
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Mark Baugher, 09:22
- (no subject), Hallam-Baker, Phillip, 09:09
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, wayne, 08:57
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Ian Jackson, 08:55
- Re: [Re: regarding IETF lists using mailman: nodupes considered harmful], Iljitsch van Beijnum, 08:50
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Tony Finch, 08:47
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Keith Moore, 08:41
- Re: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Brian E Carpenter, 08:27
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Keith Moore, 08:26
- Re: [spf-discuss] Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 08:25
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Marshall Eubanks, 08:11
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Andrew Newton, 07:46
- Re: regarding IETF lists using mailman: nodupes considered harmful, Bill Fenner, 07:42
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, wayne, 07:26
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02 MARID <ietf-mxcomp(_at_)imc(_dot_)org>, Andrew Newton, 06:58
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Bill Manning, 06:58
- Re: regarding IETF lists using mailman: nodupes considered harmful, Bill Fenner, 06:32
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02 MARID <ietf-mxcomp(_at_)imc(_dot_)org>, Stephane Bortzmeyer, 06:16
- Re: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, JFC (Jefsey) Morfin, 06:04
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Andrew Newton, 05:50
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Brian E Carpenter, 04:29
- Re: multi-RFC BCPs [Re: Fwd: I-D ACTION:draft-carpenter-bcp101-update-00.txt], Brian E Carpenter, 04:19
- Re: IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Brian E Carpenter, 04:12
- Re: regarding IETF lists using mailman: nodupes considered harmful, Jeroen Massar, 03:38
- Re: regarding IETF lists using mailman: nodupes considered harmful, Ken Raeburn, 03:13
- Re: regarding IETF lists using mailman: nodupes considered harmful, Jari Arkko, 02:46
- Re: [Re: regarding IETF lists using mailman: nodupes considered harmful], Jeroen Massar, 02:18
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Russ Allbery, 02:15
- [Re: regarding IETF lists using mailman: nodupes considered harmful], Peter Dambier, 01:36
- Re: regarding IETF lists using mailman: nodupes considered harmful, Ken Raeburn, 01:23
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stephane Bortzmeyer, 01:22
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Marc Manthey, 01:01
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stephane Bortzmeyer, 00:29
- Re: regarding IETF lists using mailman: nodupes considered harmful, Jeroen Massar, 00:21
August 25, 2005
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 21:24
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 21:17
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 18:56
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 18:55
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 18:55
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 18:06
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 17:43
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 17:07
- IESG powers - was: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, JFC (Jefsey) Morfin, 17:05
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 16:58
- Re: Last Call: 'Tags for Identifying Languages' to BCP, David Hopwood, 15:43
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 15:36
- regarding IETF lists using mailman: nodupes considered harmful, Keith Moore, 15:22
- RE: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 14:46
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Keith Moore, 14:29
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Douglas Otis, 13:27
- multi-RFC BCPs [Re: Fwd: I-D ACTION:draft-carpenter-bcp101-update-00.txt], Peter Koch, 13:27
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 13:18
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Theodore Ts'o, 13:00
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 12:32
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Stephane Bortzmeyer, 12:26
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Dave Crocker, 12:13
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Spencer Dawkins, 12:12
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Bill Sommerfeld, 12:10
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Ned Freed, 11:38
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Marc Manthey, 11:18
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Bill Sommerfeld, 11:11
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Harald Tveit Alvestrand, 10:59
- Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Harald Tveit Alvestrand, 10:33
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 10:26
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Margaret Wasserman, 07:15
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Harald Tveit Alvestrand, 06:51
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Bill Sommerfeld, 06:48
- RE: Last Call: 'Tags for Identifying Languages' to BCP, Bill Fenner, 06:26
- RE: Last Call: 'Tags for Identifying Languages' to BCP, Scott Hollenbeck, 05:47
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Peter Dambier, 03:45
August 24, 2005
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Pekka Savola, 22:51
- Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard, Stuart Cheshire, 22:43
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 20:48
- RE: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 20:47
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Sam Hartman, 20:30
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Bill Sommerfeld, 16:33
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, John C Klensin, 16:15
- Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02, Julian Mehnle, 15:50
- Re: Revised Last Call: 'SSH Transport Layer Encryption Modes' to Proposed, Sam Hartman, 14:27
- Re: New attempt to kill "whois", Frank Ellermann, 12:29
- Re: New attempt to kill "whois", Frank Ellermann, 11:59
- RE: Last Call: 'Tags for Identifying Languages' to BCP, Scott Hollenbeck, 09:27
- Re: New attempt to kill "whois", Harald Tveit Alvestrand, 09:14
- Re: Last Call: 'Tags for Identifying Languages' to BCP, David Hopwood, 08:43
- RE: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 08:17
- RE: Last Call: 'Tags for Identifying Languages' to BCP, Scott Hollenbeck, 04:26
- Re: Last Call: 'Tags for Identifying Languages' to BCP, JFC (Jefsey) Morfin, 02:37
- Re: New attempt to kill "whois", Stephane Bortzmeyer, 01:30
August 22, 2005
- New attempt to kill "whois", Frank Ellermann, 17:23
- Re: is the WG-Charter concept changed?, JFC (Jefsey) Morfin, 10:00
- RE: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Hallam-Baker, Phillip, 09:46
- RE: Why have we gotten away from running code?, Eric Burger, 08:15
- Re: IETF 63 On-line Survey, Tony Finch, 08:12
- Re: Stopping loss of transparency..., bmanning, 05:49
- Re: is the WG-Charter concept changed?, Spencer Dawkins, 05:22
- Re: is the WG-Charter concept changed?, Margaret Wasserman, 04:59
- Re: is the WG-Charter concept changed?, Brian E Carpenter, 03:08
August 20, 2005
- Re: RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, Harald Tveit Alvestrand, 15:11
- RFC 2487 [5]: Suggest dropping of "TLS Required"- forbid and extensions of current standards, thomas schorpp, 09:59
- Re: is the WG-Charter concept changed?, JFC (Jefsey) Morfin, 09:49
- Re: is the WG-Charter concept changed?, Henrik Levkowetz, 01:43
- Re: is the WG-Charter concept changed?, JFC (Jefsey) Morfin, 01:10
August 19, 2005
- Re: Why have we gotten away from running code?, Lisa Dusseault, 17:32
- Re: Stopping loss of transparency..., David Hopwood, 14:00
- Last Call comments on draft-ietf-xcon-bfcp-05.txt, Jeffrey Hutzelman, 13:34
- Re: Stopping loss of transparency..., Roland Bless, 09:02
- Re: what is a threat analysis?, Brian E Carpenter, 07:47
- Re: IETF 63 On-line Survey, Brian E Carpenter, 07:20
- Re: is the WG-Charter concept changed?, Brian E Carpenter, 07:14
- VIáGRRA-Super, Zeph Willoughby, 07:10
- Re: BCPs and STDs, Brian E Carpenter, 07:09
- RE: Stopping loss of transparency..., Hallam-Baker, Phillip, 07:04
- Re: Stopping loss of transparency..., Bill Manning, 06:53
- Re: Stopping loss of transparency..., Artur Hecker, 04:31
August 18, 2005
- Re: IETF 63 On-line Survey, Stephen Casner, 22:20
- Re: IETF 63 On-line Survey, Harald Tveit Alvestrand, 21:39
- Re: Stopping loss of transparency..., David Hopwood, 21:21
- Re: BCPs and STDs, Jeffrey Hutzelman, 18:00
- Re: IETF 63 On-line Survey, Jeffrey Hutzelman, 17:45
- RE: Stopping loss of transparency..., Jeffrey Hutzelman, 17:32
- RE: Stopping loss of transparency..., Nicholas Staff, 17:12
- Re: BCPs and STDs, grenville armitage, 16:08
- Re: IETF 63 On-line Survey, Joel Jaeggli, 15:21
- Re: IETF 63 On-line Survey, Prakash Jayaraman, 15:08
- Re: BCPs and STDs, Bob Braden, 15:01
- RE: BCPs and STDs, Bob Braden, 14:48
- Re: BCPs and STDs, Bob Braden, 14:48
- Re: BCPs and STDs, Iljitsch van Beijnum, 14:47
- Re: IETF 63 On-line Survey, Michael Richardson, 14:46
- RE: BCPs and STDs, Nelson, David, 14:24
- Re: BCPs and STDs, Bob Braden, 14:16
- Re: BCPs and STDs, Bob Braden, 14:09
- Re: Stopping loss of transparency..., David Hopwood, 12:05
- Re: BCPs and STDs, Edward Lewis, 10:19
- RE: IETF 63 On-line Survey, James M. Polk, 09:44
- Re: IETF 63 On-line Survey, Joel Jaeggli, 09:20
- Re: IETF 63 On-line Survey, JORDI PALET MARTINEZ, 09:16
- Re: BCPs and STDs, Bob Braden, 09:13
- Re: IETF 63 On-line Survey, Tony Hansen, 09:13
- Re: IETF 63 On-line Survey, Spencer Dawkins, 09:04
- RE: IETF 63 On-line Survey, Nelson, David, 08:56
- Re: IETF 63 On-line Survey, James M. Polk, 08:50
- RE: Stopping loss of transparency..., Nicholas Staff, 08:48
- Re: IETF 63 On-line Survey, Stephen Casner, 08:19
- Re: IETF 63 On-line Survey, Lars Eggert, 08:17
- Re: IETF 63 On-line Survey, Joel Jaeggli, 07:38
- Re: Fwd: I-D ACTION:draft-carpenter-bcp101-update-00.txt, Brian E Carpenter, 06:15
- Re: BCPs and STDs, Edward Lewis, 04:49
- Re: BCPs and STDs, Edward Lewis, 04:48
- Dependency on hosts (Re: IETF 63 On-line Survey), Harald Tveit Alvestrand, 04:46
- Re: Stopping loss of transparency..., Prakash Jayaraman, 04:32
- Re: Fwd: I-D ACTION:draft-carpenter-bcp101-update-00.txt, Harald Tveit Alvestrand, 04:24
- Re: BCPs and STDs, Harald Tveit Alvestrand, 04:24
- Re: IETF 63 On-line Survey, Brian E Carpenter, 03:53
- Re: IETF 63 On-line Survey, Jeffrey Altman, 03:24
- Re: Stopping loss of transparency..., Iljitsch van Beijnum, 03:11
- Re: BCPs and STDs, Iljitsch van Beijnum, 02:59
- is the WG-Charter concept changed?, JFC (Jefsey) Morfin, 02:05
- Fwd: I-D ACTION:draft-carpenter-bcp101-update-00.txt, Brian E Carpenter, 01:16
- Re: IETF 63 On-line Survey, Brian E Carpenter, 01:07
- Re: BCPs and STDs, Brian E Carpenter, 00:56
- Re: IETF 63 On-line Survey, Lars Eggert, 00:23
August 17, 2005
- Re: BCPs and STDs, Frank Ellermann, 22:26
- RE: Stopping loss of transparency..., Nicholas Staff, 21:10
- Re: IETF 63 On-line Survey, Michael Richardson, 19:50
- Re: what is a threat analysis?, Dave Crocker, 14:47
- Re: what is a threat analysis?, Michael Thomas, 11:40
- Re: what is a threat analysis?, Dave Crocker, 11:31
- Re: Stopping loss of transparency..., Prakash Jayaraman, 11:04
- Re: what is a threat analysis?, Russ Housley, 10:48
- Re: Stopping loss of transparency..., John C Klensin, 09:42
- Re: Stopping loss of transparency..., Roland Bless, 09:13
- Re: Stopping loss of transparency..., Steven M. Bellovin, 09:08
- Re: BCPs and STDs, Edward Lewis, 08:26
- Re: BCPs and STDs, Frank Ellermann, 08:16
- Re: BCPs and STDs, Joe Abley, 08:09
- Re: IETF 63 On-line Survey, Rob Evans, 07:56
- Re: IETF 63 On-line Survey, Stig Venaas, 07:50
- BCPs and STDs, Edward Lewis, 07:48
- Re: IETF 63 On-line Survey, john . loughney, 07:36
- Re: Stopping loss of transparency..., Marc Manthey, 07:17
- Re: Stopping loss of transparency..., Iljitsch van Beijnum, 07:12
- Re: Stopping loss of transparency..., Marc Manthey, 06:34
- Re: IETF 63 On-line Survey, Jari Arkko, 06:26
- Re: Stopping loss of transparency..., Iljitsch van Beijnum, 06:20
- Re: Stopping loss of transparency..., Frank Ellermann, 06:19
- Re: IETF 63 On-line Survey, Spencer Dawkins, 06:13
- Re: Stopping loss of transparency..., Brian E Carpenter, 06:03
- Re: Stopping loss of transparency..., Peter Dambier, 05:27
- Stopping loss of transparency..., Roland Bless, 04:13
August 16, 2005
- Re: what is a threat analysis?, Ned Freed, 11:02
- Re: what is a threat analysis?, Dave Crocker, 09:54
- RE: what is a threat analysis?, Fleischman, Eric, 08:46
- Re: what is a threat analysis?, Ned Freed, 08:26
- Re: what is a threat analysis?, Marc Manthey, 07:37
- RE: what is a threat analysis?, Christian Huitema, 06:54
- Re: what is a threat analysis?, Michael Thomas, 06:23
- Re: what is a threat analysis?, Brian E Carpenter, 05:25
- Re: what is a threat analysis?, Dave Crocker, 00:20
August 15, 2005
- RE: what is a threat analysis?, Nicholas Staff, 21:52
- RE: what is a threat analysis?, JFC (Jefsey) Morfin, 17:56
- RE: what is a threat analysis?, Fleischman, Eric, 10:33
- Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), shogunx, 10:14
- Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), Iljitsch van Beijnum, 09:48
- Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), Margaret Wasserman, 09:05
- Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), Iljitsch van Beijnum, 06:55
- Re: IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), Margaret Wasserman, 05:57
- Re: Why have we gotten away from running code?, Harald Tveit Alvestrand, 01:45
- IPv6 DNS resolvers issue (Re: Why have we gotten away from running code?), Harald Tveit Alvestrand, 00:55
August 12, 2005
- RE: Last Call: 'Internet Code Point Assignments' to Proposed Stan dard, Gray, Eric, 11:25
- RE: Last Call: 'Internet Code Point Assignments' to Proposed Stan dard, Gray, Eric, 10:20
- Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard, Alexey Melnikov, 08:29
- [Fwd: Turing Lecture by Cerf/Kahn (watch webcast or attend)], Brian E Carpenter, 07:52
- Re: what is a threat analysis?, Dave Crocker, 07:34
- Re: what is a threat analysis?, Dave Crocker, 07:30
- Re: what is a threat analysis?, Michael Thomas, 07:24
- RE: what is a threat analysis?, Hallam-Baker, Phillip, 07:03
- Re: what is a threat analysis?, Stephen Kent, 06:29
- Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard, Pekka Savola, 05:54
- Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard, Brian E Carpenter, 05:43
- Re: what is a threat analysis?, Jeffrey Hutzelman, 02:46
- Re: what is a threat analysis?, JFC (Jefsey) Morfin, 02:07
- Re: what is a threat analysis?, Harald Tveit Alvestrand, 01:16
August 11, 2005
- Re: Why have we gotten away from running code?, Masataka Ohta, 18:16
- Re: Why have we gotten away from running code?, Ned Freed, 15:52
- Re: what is a threat analysis?, Ned Freed, 15:12
- Re: what is a threat analysis?, Bill Sommerfeld, 15:11
- Re: what is a threat analysis?, Ned Freed, 15:08
- Re: Why have we gotten away from running code?, Alexandru Petrescu, 14:58
- Re: Why have we gotten away from running code?, Bill Manning, 14:14
- Re: Why have we gotten away from running code?, Bill Manning, 14:06
- Re: what is a threat analysis?, Michael Thomas, 13:43
- Re: what is a threat analysis?, Stephen Kent, 12:51
- Conflicts with "0-" header?, JFC (Jefsey) Morfin, 11:34
- Re: what is a threat analysis?, Ned Freed, 11:24
- Re: what is a threat analysis?, Dave Crocker, 10:58
- Re: what is a threat analysis?, Michael Thomas, 10:28
- Re: Why have we gotten away from running code?, Alexandru Petrescu, 07:10
- Re: what is a threat analysis?, David Hopwood, 06:49
- Re: what is a threat analysis?, Philip Guenther, 03:56
- Re: Why have we gotten away from running code?, C Wegrzyn, 03:31
- Re: Why have we gotten away from running code?, Iljitsch van Beijnum, 03:24
- Re: Why have we gotten away from running code?, Brian E Carpenter, 02:22
- Re: what is a threat analysis?, Jari Arkko, 02:13
- Re: what is a threat analysis?, Brian E Carpenter, 02:11
- Re: Why have we gotten away from running code?, Jeroen Massar, 01:34
August 10, 2005
- Re: what is a threat analysis?, Steven M. Bellovin, 18:19
- Re: what is a threat analysis?, David Hopwood, 16:58
- Re: what is a threat analysis?, Stephen Kent, 15:26
- Re: what is a threat analysis?, Dave Crocker, 14:56
- Re: what is a threat analysis?, Bruce Lilly, 14:30
- Re: Cautionary tale: Paris pickpockets, Dave Singer, 13:55
- what is a threat analysis?, Michael Thomas, 13:39
- Re: Cautionary tale: Paris pickpockets, Hadmut Danisch, 13:19
- Re: Last Call: 'Internet Code Point Assignments' to Proposed Standard, Pekka Savola, 13:04
- Re: Cautionary tale: Paris pickpockets, Dave Crocker, 12:56
- Re: Why have we gotten away from running code?, Henning Schulzrinne, 12:25
- Re: Why have we gotten away from running code?, Dave Singer, 12:19
- Re: Why have we gotten away from running code?, C Wegrzyn, 12:13
- Re: Why have we gotten away from running code?, Jari Arkko, 11:54
- Re: Why have we gotten away from running code?, C Wegrzyn, 11:25
- Re: Myths of the IESG: Reading documents is the problem, Spencer Dawkins, 10:46
- Re: Why have we gotten away from running code?, Lakshminath Dondeti, 10:24
- Re: Why have we gotten away from running code?, Marc Manthey, 09:57
- Re: Why have we gotten away from running code?, Dave Singer, 09:56
- Re: Why have we gotten away from running code?, Simon Josefsson, 09:38
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 09:37
- Re: Myths of the IESG: Reading documents is the problem, Theodore Ts'o, 09:07
- Re: Why have we gotten away from running code?, wayne, 08:28
- Re: Myths of the IESG: Reading documents is the problem, John C Klensin, 07:56
- Re: Why have we gotten away from running code?, C Wegrzyn, 07:49
- Re: Why have we gotten away from running code?, Jari Arkko, 07:49
- Re: Why have we gotten away from running code?, Marc Manthey, 07:27
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 07:22
- Re: Why have we gotten away from running code?, Iljitsch van Beijnum, 06:53
- Re: Myths of the IESG: Reading documents is the problem, Sam Hartman, 06:49
- Re: Why have we gotten away from running code?, Brian E Carpenter, 06:47
- Re: Myths of the IESG: Reading documents is the problem, Brian E Carpenter, 06:40
- Re: Why have we gotten away from running code?, Harald Tveit Alvestrand, 03:34
- Autoreply: Re: Why have we gotten away from running code?, hverma, 02:52
- Re: Why have we gotten away from running code?, Bruce Lilly, 02:49
- Re: Why have we gotten away from running code?, Love Hörnquist Åstrand, 02:19
- Re: Why have we gotten away from running code?, Iljitsch van Beijnum, 01:41
- Re: Myths of the IESG: Reading documents is the problem, Harald Tveit Alvestrand, 01:06
- Re: Why have we gotten away from running code?, wayne, 00:48
August 09, 2005
- RE: Two laptops lost right inside IETF WG meeting room, +ACI-DENG, HUI -HCHBJ+ACI-, 20:38
- Re: Myths of the IESG: Reading documents is the problem, Steven M. Bellovin, 18:20
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 17:54
- Re: Myths of the IESG: Reading documents is the problem, John C Klensin, 17:25
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 16:38
- Re: Keeping this IETF's schedule in the future...?, Dave Crocker, 16:07
- Re: Myths of the IESG: Reading documents is the problem, Sam Hartman, 15:08
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 14:00
- Re: Myths of the IESG: Reading documents is the problem, Sam Hartman, 13:56
- Re: Myths of the IESG: Reading documents is the problem, Sam Hartman, 13:55
- Re: Myths of the IESG: Reading documents is the problem, Spencer Dawkins, 13:53
- Re: Myths of the IESG: Reading documents is the problem, Theodore Ts'o, 13:49
- Re: Myths of the IESG: Reading documents is the problem, Spencer Dawkins, 13:42
- Re: Myths of the IESG: Reading documents is the problem, John C Klensin, 13:33
- Re: Myths of the IESG: Reading documents is the problem, Theodore Ts'o, 13:29
- Re: IETF Chair, General Area, process and complexity, John C Klensin, 12:21
- Re: Myths of the IESG: Reading documents is the problem, Dave Crocker, 12:04
- Re: Two laptops lost right inside IETF WG meeting room, Dave Crocker, 11:29
- Re: Two laptops lost right inside IETF WG meeting room, Scott W Brim, 07:54
- RE: Two laptops lost right inside IETF WG meeting room, +ACI-DENG, HUI -HCHBJ+ACI-, 07:35
- Re: Two laptops lost right inside IETF WG meeting room, Jim Sermersheim, 07:24
- Re: Review panel's role, Brian E Carpenter, 06:43
- Two laptops lost right inside IETF WG meeting room, +ACI-DENG, HUI -HCHBJ+ACI-, 06:42
- Re: project management (from Town Hall meeting), Brian E Carpenter, 06:33
- Re: "The IETF has difficulty solving complex problems", JFC (Jefsey) Morfin, 06:29
- rejection of a document by the review panel [Re: The plenary and the nomcom-term and review panel proposals], Brian E Carpenter, 06:26
- Re: Why have we gotten away from running code?, Brian E Carpenter, 06:16
- Re: On standards review panel and division of work, Brian E Carpenter, 05:30
- Re: "The IETF has difficulty solving complex problems", Brian E Carpenter, 05:21
- shuttle landet, Marc Manthey, 05:14
- Re: IETF Chair, General Area, process and complexity, Brian E Carpenter, 05:03
- Re: Myths of the IESG: Reading documents is the problem, Brian E Carpenter, 05:00
- Re: "IETF servers aren't for testing", Brian E Carpenter, 04:47
- Re: Keeping this IETF's schedule in the future...?, Brian E Carpenter, 04:37
- Re: Keeping this IETF's schedule in the future...?, Brian E Carpenter, 04:25
August 07, 2005
- Re: Why have we gotten away from running code?, JFC (Jefsey) Morfin, 15:33
- Re: Why have we gotten away from running code?, Scott W Brim, 15:12
- Re: Why have we gotten away from running code?, Melinda Shore, 14:59
- Re: Why have we gotten away from running code?, Scott W Brim, 14:41
- Re: Why have we gotten away from running code?, Mark Baugher, 12:08
- Re: Why have we gotten away from running code?, Melinda Shore, 10:43
- Re: Why have we gotten away from running code?, Bill Fenner, 06:28
- Re: Why have we gotten away from running code?, grenville armitage, 06:02
- Re: Why have we gotten away from running code?, Jeroen Massar, 06:01
- Re: Why have we gotten away from running code?, Spencer Dawkins, 05:53
- Re: Why have we gotten away from running code?, Melinda Shore, 05:47
- Re: Why have we gotten away from running code?, John Leslie, 05:13
- Re: Why have we gotten away from running code?, Henning Schulzrinne, 04:35
- Re: Why have we gotten away from running code?, Scott W Brim, 04:23
- One and a half points (was: Re: "IETF servers aren't for testing"), Spencer Dawkins, 02:52
- Re: "IETF servers aren't for testing", Harald Tveit Alvestrand, 01:36
August 06, 2005
- Re: Dog Food (was "IETF servers aren't for testing"), shogunx, 18:56
- Re: "IETF servers aren't for testing", shogunx, 18:50
- Re: Why have we gotten away from running code?, JFC (Jefsey) Morfin, 18:13
- Dog Food (was "IETF servers aren't for testing"), JFC (Jefsey) Morfin, 18:13
- Re: "IETF servers aren't for testing", JORDI PALET MARTINEZ, 17:07
- Re: "IETF servers aren't for testing", JORDI PALET MARTINEZ, 17:06
- Re: Why have we gotten away from running code?, Spencer Dawkins, 16:22
- Why have we gotten away from running code?, Brian Rosen, 16:08
- Re: "IETF servers aren't for testing", shogunx, 15:38
- Re: "IETF servers aren't for testing", Harald Tveit Alvestrand, 15:13
- Re: "IETF servers aren't for testing", shogunx, 14:58
- Re: "IETF servers aren't for testing", JORDI PALET MARTINEZ, 14:14
- Re: "IETF servers aren't for testing", shogunx, 12:39
- Re: "IETF servers aren't for testing", JORDI PALET MARTINEZ, 11:53
- Re: "IETF servers aren't for testing", Harald Tveit Alvestrand, 11:43
- Re: "IETF servers aren't for testing", shogunx, 10:59
- Re: "IETF servers aren't for testing", Harald Tveit Alvestrand, 10:26
- Re: About Internet Draft Again :), Steven M. Bellovin, 09:20
- Re: I'm not the microphone police, but ..., Joel M. Halpern, 07:42
- Re: About Internet Draft Again :), zhen, 06:53
- Re: I'm not the microphone police, but ..., Steven M. Bellovin, 05:51
- Re: About Internet Draft Again :), Steven M. Bellovin, 05:48
- About Internet Draft Again :), zhen, 05:43
- Re: I'm not the microphone police, but ..., Iljitsch van Beijnum, 04:02
- Re: I'm not the microphone police, but ..., John C Klensin, 03:51
- Re: I'm not the microphone police, but ..., Keith Moore, 03:01
August 05, 2005
- Re: IETF63 network shutdown at noon today, Pekka Savola, 21:00
- Re: "IETF servers aren't for testing", Ole Jacobsen, 16:11
- Re: IETF63 network shutdown at noon today, JORDI PALET MARTINEZ, 14:54
- Re: "IETF servers aren't for testing", JORDI PALET MARTINEZ, 14:52
- Re: "IETF servers aren't for testing", shogunx, 13:07
- Re: IETF63 network shutdown at noon today, David Hopwood, 12:54
- Re: "IETF servers aren't for testing", Kevin Loch, 11:29
- Re: IETF63 network shutdown at noon today, JORDI PALET MARTINEZ, 09:44
- Re: "IETF servers aren't for testing", Richard Irving, 08:16
- Re: "IETF servers aren't for testing", Eric A. Hall, 07:59
- Re: IETF63 network shutdown at noon today, Tony Hansen, 04:08
- Re: "IETF servers aren't for testing", Jari Arkko, 02:26
- Re: "IETF servers aren't for testing", Bill Sommerfeld, 02:19
- IETF63 network shutdown at noon today, MERCIER Francois RD-CSRD-ISS, 01:55
- Re: "IETF servers aren't for testing", Jeroen Massar, 01:21
- Re: "IETF servers aren't for testing", Joel Jaeggli, 00:54
- Re: "IETF servers aren't for testing", shogunx, 00:52
- "IETF servers aren't for testing", Iljitsch van Beijnum, 00:45
August 04, 2005
- IETF Meeting Wiki (Was: Re: Completely out of scope: Restaurant reccomendation), Henrik Levkowetz, 23:03
- RE: "straightforward, reasonable, and fair", Hallam-Baker, Phillip, 13:56
- RE: "The IETF has difficulty solving complex problems", Hallam-Baker, Phillip, 11:51
- IETF Chair, General Area, process and complexity, avri doria, 10:52
- work on diagnostics, RL 'Bob' Morgan, 09:56
- Re: Review panel's role, Steven M. Bellovin, 09:40
- Re: "The IETF has difficulty solving complex problems", JFC (Jefsey) Morfin, 08:26
- Re: Review panel's role, Spencer Dawkins, 08:09
- Re: Review panel's role, Harald Tveit Alvestrand, 07:41
- Re: Review panel's role, Pekka Savola, 07:26
- Re: Review panel's role, Spencer Dawkins, 07:13
- Re: Review panel's role, John C Klensin, 06:41
- Re: project management (from Town Hall meeting), Henrik Levkowetz, 06:35
- Re: Review panel's role, Pekka Savola, 06:33
- Re: Review panel's role, Spencer Dawkins, 06:18
- RE: project management (from Town Hall meeting), Lars-Erik Jonsson (LU/EAB), 06:11
- Re: Review panel's role, Henning Schulzrinne, 06:08
- Re: project management (from Town Hall meeting), Henning Schulzrinne, 05:59
- Re: Review panel's role, Spencer Dawkins, 05:39
- Re: On standards review panel and division of work, Joel M. Halpern, 05:26
- Review panel's role, Pekka Savola, 04:06
- unsubscribe, Suresh Kumar, 03:53
- Re: project management (from Town Hall meeting), Henrik Levkowetz, 03:31
- Re: project management (from Town Hall meeting), Henning Schulzrinne, 03:17
- Re: project management (from Town Hall meeting), Pekka Savola, 03:10
- Re: On standards review panel and division of work, John C Klensin, 03:09
- Re: project management (from Town Hall meeting), Henk Uijterwaal, 02:40
- Re: On standards review panel and division of work, Spencer Dawkins, 02:34
- The plenary and the nomcom-term and review panel proposals, John C Klensin, 02:32
- Re: project management (from Town Hall meeting), Aki Niemi, 02:12
- Re: project management (from Town Hall meeting), Henning Schulzrinne, 02:08
- Re: Effecting major infrastructure change RE: I'm not the microphone police, but ..., Iljitsch van Beijnum, 01:51
- Re: project management (from Town Hall meeting), Henk Uijterwaal, 01:49
- Re: Keeping this IETF's schedule in the future...?, Iljitsch van Beijnum, 01:44
- Re: project management (from Town Hall meeting), Henning Schulzrinne, 01:05
- Tech topics and plans for tonight's plenary, Leslie Daigle, 00:56
- two Air France bus tickets to CDG available, Steven M. Bellovin, 00:21
August 03, 2005
- Process change review and approval by fresh eyes, Pekka Savola, 23:53
- On standards review panel and division of work, Pekka Savola, 23:36
- "The IETF has difficulty solving complex problems", Scott W Brim, 22:05
- RE: Keeping this IETF's schedule in the future...?, JFC (Jefsey) Morfin, 16:47
- project management (from Town Hall meeting), Yaakov Stein, 11:30
- Re: I'm not the microphone police, but ..., Tom Petch, 11:18
- RE: Keeping this IETF's schedule in the future...?, Hallam-Baker, Phillip, 11:17
- RE: Keeping this IETF's schedule in the future...?, Thomas Gal, 10:57
- Re: Keeping this IETF's schedule in the future...?, John C Klensin, 09:39
- Re: IETF63 Network and IPv6, Jeroen Massar, 09:30
- Re: Keeping this IETF's schedule in the future...?, Samuel Weiler, 08:36
- Re: I'm not the microphone police, but ..., JFC (Jefsey) Morfin, 07:56
- Fwd: Keeping this IETF's schedule in the future...?, fenwayfrank, 07:33
- Effecting major infrastructure change RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 07:10
- IETF63 Network and IPv6, Brian Haberman, 07:09
- Re: Keeping this IETF's schedule in the future...?, Michael StJohns, 07:05
- RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 06:52
- Re: Keeping this IETF's schedule in the future...?, Scott W Brim, 06:45
- Re: Keeping this IETF's schedule in the future...?, Steven M. Bellovin, 06:44
- Re: Keeping this IETF's schedule in the future...?, John C Klensin, 06:40
- Re: Keeping this IETF's schedule in the future...?, John C Klensin, 06:36
- Re: Keeping this IETF's schedule in the future...?, Francis Dupont, 06:29
- Re: Keeping this IETF's schedule in the future...?, Marshall Eubanks, 06:23
- Re: Keeping this IETF's schedule in the future...?, Jeffrey Altman, 06:22
- Re: Keeping this IETF's schedule in the future...?, Michael StJohns, 06:20
- Re: Keeping this IETF's schedule in the future...?, Andrew G. Malis, 06:16
- Re: Keeping this IETF's schedule in the future...?, Steven M. Bellovin, 06:15
- Re: Keeping this IETF's schedule in the future...?, Pekka Savola, 06:10
- Re: Keeping this IETF's schedule in the future...?, Randy Presuhn, 06:09
- Re: Keeping this IETF's schedule in the future...?, Lars Eggert, 06:08
- Re: Keeping this IETF's schedule in the future...?, Steven M. Bellovin, 06:04
- Re: I'm not the microphone police, but ..., Brian E Carpenter, 06:00
- Re: Keeping this IETF's schedule in the future...?, Steven M. Bellovin, 05:59
- RE: Keeping this IETF's schedule in the future...?, Romascanu, Dan \(Dan\), 05:57
- RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 05:56
- Re: Keeping this IETF's schedule in the future...?, Lars Eggert, 05:46
- Re: Keeping this IETF's schedule in the future...?, Andrew G. Malis, 05:40
- Re: Keeping this IETF's schedule in the future...?, Joerg Ott, 05:40
- Personal & company email addresses (Re: Re: I'm not the microphone police, but ...), Harald Tveit Alvestrand, 05:30
- Re: Keeping this IETF's schedule in the future...?, Henk Uijterwaal, 05:18
- Re: I'm not the microphone police, but ..., Spencer Dawkins, 05:17
- Re: Keeping this IETF's schedule in the future...?, Randy Presuhn, 05:13
- Re: Keeping this IETF's schedule in the future...?, Scott W Brim, 05:02
- Re: I'm not the microphone police, but ..., JFC (Jefsey) Morfin, 04:57
- Re: I'm not the microphone police, but ..., Brian E Carpenter, 04:43
- Re: Keeping this IETF's schedule in the future...?, Brian E Carpenter, 04:39
- Re: Keeping this IETF's schedule in the future...?, Spencer Dawkins, 04:37
- Re: Keeping this IETF's schedule in the future...?, Bill Fenner, 04:36
- Re: Re: I'm not the microphone police, but ..., Spencer Dawkins, 04:30
- Re: Keeping this IETF's schedule in the future...?, JORDI PALET MARTINEZ, 04:27
- Re: Keeping this IETF's schedule in the future...?, Carsten Bormann, 04:09
- Re: Keeping this IETF's schedule in the future...?, Lakshminath Dondeti, 04:05
- Re: Keeping this IETF's schedule in the future...?, Stig Venaas, 03:59
- Re: Keeping this IETF's schedule in the future...?, Jari Arkko, 03:52
- Re: Keeping this IETF's schedule in the future...?, RL 'Bob' Morgan, 03:51
- Re: Keeping this IETF's schedule in the future...?, Tim Chown, 03:45
- Keeping this IETF's schedule in the future...?, Joerg Ott, 03:38
- Re: Re: I'm not the microphone police, but ..., John Loughney, 02:53
- Re: Completely out of scope: Restaurant reccomendation, Dave Crocker, 02:38
- Re: I'm not the microphone police, but ..., Spencer Dawkins, 00:11
August 02, 2005
- RE: I'm not the microphone police, but ..., John C Klensin, 22:50
- missing mouse, Aaron Falk, 22:47
- RE: I'm not the microphone police, but ..., JFC (Jefsey) Morfin, 18:46
- RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 17:55
- Re: Internet Draft Process Procedure, Brian E Carpenter, 14:43
- A Complaint to the IETF and IESG (was Re: Please change the Subject: when you change the subject [Re: Sarcarm and intimidation]), Dean Anderson, 12:17
- Re: Completely out of scope: Restaurant reccomendation, Henrik Levkowetz, 10:44
- Re: I'm not the microphone police, but ..., Aki Niemi, 10:25
- Very helpful Parisians (Was: Cautionary tale: Paris pickpockets), Steven M. Bellovin, 10:02
- RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 09:58
- RE: I'm not the microphone police, but ..., JFC (Jefsey) Morfin, 09:24
- Personal Security Reminder, IETF Secretariat, 08:35
- Internet Draft Process Procedure, zhen, 07:52
- RE: I'm not the microphone police, but ..., Hallam-Baker, Phillip, 07:23
- Reminder: IAOC Office hours, Lucy E. Lynch, 06:37
- Re: Completely out of scope: Restaurant reccomendation, Will McAfee, 06:23
- Re: I'm not the microphone police, but ..., JFC (Jefsey) Morfin, 05:00
- Re: Completely out of scope: Restaurant reccomendation, Clint Chaplin, 02:13
- Completely out of scope: Restaurant reccomendation, Olaf M. Kolkman, 01:28
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Harald Tveit Alvestrand, 00:36
August 01, 2005
- Last day: Call for volunteers: narrative minutes of IESG meetings, Brian E Carpenter, 23:26
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Theodore Ts'o, 14:35
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Harald Tveit Alvestrand, 13:49
- Re: Zero Configuration Printers in Terminal Room, Stuart Cheshire, 12:14
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), bill, 10:17
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Eric Rosen, 09:42
- BOF jabber rooms, Peter Saint-Andre, 09:37
- Re: Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Spencer Dawkins, 09:35
- ietf63 network status, Odonoghue, Karen F CIV B35-Branch, 09:09
- Let's make the benches longer.... (Re: draft-klensin-nomcom-term-00.txt), Harald Tveit Alvestrand, 09:05
- Re: I'm not the microphone police, but ..., bill, 08:52
- Re: draft-klensin-nomcom-term-00.txt, Pete Resnick, 08:26
- Re: I'm not the microphone police, but ..., Spencer Dawkins, 08:22
- Re: I'm not the microphone police, but ..., John Loughney, 08:06
- Re: Zero Configuration Printers in Terminal Room, Jim Martin, 07:49
- Re: draft-klensin-nomcom-term-00.txt, Eliot Lear, 07:47
- I'm not the microphone police, but ..., Spencer Dawkins, 07:45
- Zero Configuration Printers in Terminal Room, Stuart Cheshire, 07:23
- Urgent : IETF'63 Social event, Bernard MARTI, 06:54
- Re: Coach class, Sandy Wills, 06:16
- Re: draft-klensin-nomcom-term-00.txt, Pete Resnick, 06:05
- Re: IANA "Office Hours" at IETF-63 in Paris, Lars Eggert, 05:20
- Re: Coach class, Adrian Farrel, 03:31
- Re: Coach class, Tim Chown, 03:30
- RE: draft-klensin-nomcom-term-00.txt, Lars-Erik Jonsson (LU/EAB), 03:15
- Re: Coach class, Steven M. Bellovin, 03:14
- Re: draft-klensin-stds-review-panel-00.txt, Brian E Carpenter, 03:09
- Re: 63rd IETF Facilities Update, Brian E Carpenter, 02:50
- Re: draft-klensin-nomcom-term-00.txt, Scott W Brim, 02:50
- Re: 63rd IETF Facilities Update, James M. Polk, 02:50
- Re: Re: draft-klensin-nomcom-term-00.txt, John Loughney, 02:50
- IETF 63 Streaming officially begins (Status of audio streaming for IETF 63), Joel Jaeggli, 02:50
- Re: Quality/Quantity of NOMCOM candidates, Danny McPherson, 02:33
- Re: draft-klensin-nomcom-term-00.txt, Scott W Brim, 01:50
- Re: 63rd IETF Facilities Update, Adam Roach, 01:20
- Coach class, Carsten Bormann, 01:10
- Re: draft-klensin-stds-review-panel-00.txt, John C Klensin, 01:01
- jabber rooms, Brian E Carpenter, 01:00
- BOF jabber rooms, Sam Hartman, 00:01