saag Discussion Archive - Thread Index

[Prev Page] [Next Page] [Date Index] [IETF Mailing List Directory] [saag List Information]

• Re: [saag] Remove tunnel mode from ipsec-tunnels-02? (fwd), (continued)
  • Re: [saag] Remove tunnel mode from ipsec-tunnels-02? (fwd), Bora Akyol
    • Re: [saag] Remove tunnel mode from ipsec-tunnels-02? (fwd), Pekka Savola
• [saag] OpenPGP Minutes / Quick Summary, Derek Atkins
  • Message not available
    • Re: [saag] OpenPGP Minutes / Quick Summary, Sam Hartman
  • Re: [saag] OpenPGP Minutes / Quick Summary, Thomas Roessler
• [saag] DKIIM WG - quck summary for saag, stephen . farrell
• [saag] IETF66 Summary of Kitten WG Meeting, Jeffrey Altman
• [saag] fyi: report on security risks of applying CALEA to VoIP, Jeff . Hodges
• [saag] VOIPSEC, Hallam-Baker, Phillip
• [saag] [Sam Hartman] [Ietf-http-auth] BOF Request: WARP - Web Authentication Resistant to Phishing, Sam Hartman
• [saag] Last Call: 'GigaBeam High-Speed Radio Link Encryption' to Informational RFC (draft-housley-gigabeam-radio-link-encrypt), The IESG
• [saag] Review of OASIS SAML work encouraged, Sam Hartman
• Re: [saag] [AVT] Re: The use of AES-192 and AES-256 in Secure RTP, Fries, Steffen
• [saag] AES-256, Black_David
• [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
  • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Lakshminath Dondeti
    • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Lakshminath Dondeti
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Stephen Kent
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, The Purple Streak, Hilarie Orman
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Lakshminath Dondeti
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Paul Hoffman
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, The Purple Streak, Hilarie Orman
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, der Mouse
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Lakshminath Dondeti
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Stephen Kent
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Steven M. Bellovin
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Stephen Kent
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Jon Callas
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
  • <Possible follow-ups>
  • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Rick Porter
    • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
  • [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
    • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Paul Hoffman
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Jon Callas
    • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, Paul Hoffman
      • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
  • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, laurent . pilati
    • Re: [saag] The use of AES-192 and AES-256 in Secure RTP, David McGrew
• [saag] IPsec spec problems, Stephen Kent
• Re: [saag] IPsec spec problems, Barry Greene \(bgreene\)
  • <Possible follow-ups>
  • Re: [saag] IPsec spec problems, Barry Greene \(bgreene\)
    • Re: [saag] IPsec spec problems, Stephen Kent
    • Re: [saag] IPsec spec problems, Sam Hartman
    • Re: [saag] IPsec spec problems, Michael Richardson
  • Re: [saag] IPsec spec problems, Gray, Eric
    • Re: [saag] IPsec spec problems, Sam Hartman
  • Re: [saag] IPsec spec problems, Barry Greene \(bgreene\)
    • Re: [saag] IPsec spec problems, Stephen Kent
  • Re: [saag] IPsec spec problems, Barry Greene \(bgreene\)
  • Re: [saag] IPsec spec problems, Barry Greene \(bgreene\)
    • Re: [saag] IPsec spec problems, Stephen Kent
• [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Sam Hartman
  • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Michael Richardson
    • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Sam Hartman
    • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Bernard Aboba
  • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Mark Townsley
    • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, der Mouse
      • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Nicolas Williams
    • Re: [saag] IPsec configuration via BGP--softwires to support overlay network confidentiality/integrity, Sam Hartman
• [saag] Fwd: draft-bonica-tcp-auth, Russ Housley
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Stephen Kent
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Jari Arkko
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Tero Kivinen
      • [saag] IPsec spec problems, Pekka Savola
      • [saag] IPsec spec problems, Tero Kivinen
      • Re: [saag] IPsec spec problems, Pekka Savola
      • Re: [saag] IPsec spec problems, Tero Kivinen
      • Re: [saag] IPsec spec problems, Sam Hartman
      • Re: [saag] IPsec spec problems, Stephen Kent
      • Re: [saag] IPsec spec problems, Nicolas Williams
      • Re: [saag] IPsec spec problems, Sam Hartman
      • Re: [saag] IPsec spec problems, Nicolas Williams
      • Re: [saag] IPsec spec problems, Stephen Kent
      • Re: [saag] IPsec spec problems, Stephen Kent
      • Re: [saag] IPsec spec problems, Sam Hartman
      • Re: [saag] IPsec spec problems, Vishwas Manral
      • Re: [saag] IPsec spec problems, Stephen Kent
      • Re: [saag] IPsec spec problems, Wes Hardaker
      • Re: [saag] IPsec spec problems, Pasi.Eronen
      • Re: [saag] IPsec spec problems, Nicolas Williams
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Russ Housley
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Michael Richardson
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Pekka Savola
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Jari Arkko
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Stephen Kent
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Stephen Kent
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Tero Kivinen
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
    • Re: [saag] Fwd: draft-bonica-tcp-auth, David McGrew
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Pekka Savola
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
      • Re: [saag] Fwd: draft-bonica-tcp-auth, David McGrew
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Pekka Savola
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Pekka Savola
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Nicolas Williams
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Pekka Savola
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Tero Kivinen
      • Re: [saag] Fwd: draft-bonica-tcp-auth, David McGrew
  • <Possible follow-ups>
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Ron Bonica
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Barry Greene \(bgreene\)
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Gray, Eric
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Barry Greene \(bgreene\)
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Sam Hartman
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Stephen Kent
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Gray, Eric
    • Re: [saag] Fwd: draft-bonica-tcp-auth, der Mouse
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Nicolas Williams
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Gray, Eric
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Nicolas Williams
      • Re: [saag] Fwd: draft-bonica-tcp-auth, Jon Callas
  • Re: [saag] Fwd: draft-bonica-tcp-auth, Gray, Eric
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Nicolas Williams
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Eric Rescorla
    • Re: [saag] Fwd: draft-bonica-tcp-auth, Steven M. Bellovin
• [saag] Backbone attacks and protections (fwd), Pekka Savola
• [saag] Fwd: Public mailing list to discuss OATH specs, Russ Housley
• [saag] FYI: EAP WG last call on the EAP Key Management Framework Document, Bernard Aboba
• [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Jeffrey Altman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Bernard Aboba
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Jeffrey Altman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Jeffrey Altman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Peter Gutmann
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Michael Richardson
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, der Mouse
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Jeffrey Altman
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Brian E Carpenter
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Bernard Aboba
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Jari Arkko
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Leslie Daigle
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Bernard Aboba
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Eric Rescorla
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Tim Shepard
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Sam Hartman
  • <Possible follow-ups>
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Hallam-Baker, Phillip
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Bernard Aboba
      • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Nicolas Williams
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Hallam-Baker, Phillip
    • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Peter Gutmann
  • Re: [saag] Frameworks, multiple mechanisms and draft-iab-auth-mech-05.txt, Hallam-Baker, Phillip
• [saag] Draft SAAG Meeting Minutes, Russ Housley
• [saag] LTANS summary, IETF 65, Carl Wallace
• [saag] MOBIKE meeting summary, Paul Hoffman
  • Re: [saag] MOBIKE meeting summary, Stephen Kent
• [saag] ISMS IETF65 session summary, Juergen Quittek
  • [saag] WG reports, Michael Richardson
• [saag] TLS WG Summary, Eric Rescorla
  • [saag] MSEC report, Lakshminath Dondeti
• [saag] PKIX Working Group Summary, IETF 65, tim . polk
• [saag] DKIM Working Group Summary, IETF 65, DKIM Chair
  • Re: [saag] [ietf-dkim] DKIM Working Group Summary, IETF 65, Hector Santos
• [saag] SAAG Scribes, Russ Housley
• [saag] EMU Working group summary, Salowey, Joe
  • <Possible follow-ups>
  • [saag] EMU working group summary, Joseph Salowey (jsalowey)
  • [saag] EMU working group summary, Joseph Salowey (jsalowey)
  • [saag] EMU Working group summary, Joseph Salowey (jsalowey)
  • [saag] EMU Working Group Summary, Joseph Salowey (jsalowey)
• [saag] BTNS IETF65 session summary, Love Hörnquist Åstrand
• [saag] pki4ipsec WG summary IETF65 Dallas, Gregory M. Lebovitz
• [saag] NIST SP 800-56A is Finally Available, Russ Housley
• [saag] Two NIST Draft documents: FIPS 186-3 and NIST SP 800-89, Russ Housley
• [saag] SAAG Mailing List has moved (sort of), Jeffrey I. Schiller
  • Re: [saag] SAAG Mailing List has moved (sort of), Jeffrey I. Schiller
  • Re: [saag] SAAG Mailing List has moved (sort of), Marcus Leech
  • Re: [saag] SAAG Mailing List has moved (sort of), Steven M. Bellovin
    • Re: [saag] SAAG Mailing List has moved (sort of), Jeffrey I. Schiller
      • Re: [saag] SAAG Mailing List has moved (sort of), Steven M. Bellovin
      • Re: [saag] SAAG Mailing List has moved (sort of), Michael Richardson
      • Re: [saag] SAAG Mailing List has moved (sort of), Jeffrey I. Schiller
      • Re: [saag] SAAG Mailing List has moved (sort of), Michael Richardson
    • Re: [saag] SAAG Mailing List has moved (sort of), der Mouse
      • Re: [saag] SAAG Mailing List has moved (sort of), Derek Atkins
      • Re: [saag] SAAG Mailing List has moved (sort of), Gary E. Miller
      • Re: [saag] SAAG Mailing List has moved (sort of), der Mouse
      • Re: [saag] SAAG Mailing List has moved (sort of), Gary E. Miller
      • Re: [saag] SAAG Mailing List has moved (sort of), der Mouse
      • Re: [saag] SAAG Mailing List has moved (sort of), Gary E. Miller
  • <Possible follow-ups>
  • Re: [saag] SAAG Mailing List has moved (sort of), Jaques, James @ IEC
  • Re: [saag] SAAG Mailing List has moved (sort of), Hallam-Baker, Phillip
    • Re: [saag] SAAG Mailing List has moved (sort of), der Mouse
  • Re: [saag] SAAG Mailing List has moved (sort of), Hallam-Baker, Phillip
    • Re: [saag] SAAG Mailing List has moved (sort of), der Mouse
• [saag] Cryptographic Token Key Initialization Protocol Version 1.0, Russ Housley
• [saag] BCP 61, advancing to draft, Sam Hartman
  • Re: [saag] BCP 61, advancing to draft, Harald Tveit Alvestrand
    • Re: [saag] BCP 61, advancing to draft, Sam Hartman
      • Re: [saag] BCP 61, advancing to draft, Peter Gutmann
      • Re: [saag] BCP 61, advancing to draft, RJ Atkinson
      • Re: [saag] BCP 61, advancing to draft, Steven M. Bellovin
      • Re: [saag] BCP 61, advancing to draft, Peter Gutmann
      • Re: [saag] BCP 61, advancing to draft, RJ Atkinson
      • Re: [saag] BCP 61, advancing to draft, Sam Hartman
      • Re: [saag] BCP 61, advancing to draft, RJ Atkinson
      • Re: [saag] BCP 61, advancing to draft, Sam Hartman
      • Re: [saag] BCP 61, advancing to draft, RJ Atkinson
      • Re: [saag] BCP 61, advancing to draft, Paul Hoffman
      • Re: [saag] BCP 61, advancing to draft, Sam Hartman
      • Re: [newtrk] Re: [saag] BCP 61, advancing to draft, Joe Touch
      • [saag] definition of 'feature'; reasons to advance, Pekka Savola
      • [saag] RE: [newtrk] definition of 'feature'; reasons to advance, Larry Masinter
      • [saag] Re: [newtrk] definition of 'feature'; reasons to advance, Sam Hartman
      • [saag] Re: definition of 'feature'; reasons to advance, Sam Hartman
      • Re: [saag] BCP 61, advancing to draft, Jari Arkko
      • Re: [saag] BCP 61, advancing to draft, Michael Richardson
      • Re: [saag] BCP 61, advancing to draft, Jari Arkko
      • [saag] Re: BCP 61, advancing to draft, Simon Josefsson
      • [saag] Re: BCP 61, advancing to draft, Peter Gutmann
      • [saag] Re: BCP 61, advancing to draft, Simon Josefsson
      • [saag] Re: BCP 61, advancing to draft, Peter Gutmann
      • [saag] Re: BCP 61, advancing to draft, Simon Josefsson
      • Re: [saag] BCP 61, advancing to draft, Sam Hartman
      • Re: [saag] BCP 61, advancing to draft, Russ Housley
    • Re: [saag] BCP 61, advancing to draft, RJ Atkinson
    • Re: [saag] BCP 61, advancing to draft, Paul Hoffman
      • Re: [saag] BCP 61, advancing to draft, Michael Richardson
      • Re: [newtrk] Re: [saag] BCP 61, advancing to draft, Tony Hansen
    • Re: [saag] BCP 61, advancing to draft, Michael Richardson
  • Re: [saag] BCP 61, advancing to draft, Kurt D. Zeilenga
• [saag] Please review draft-bonica-tcp-auth-04, Russ Housley
• [saag] [Fwd: I-D ACTION:draft-kelly-saag-des-implications-00.txt], Scott G Kelly
• [saag] International Conference on Network Security 2006, Russ Housley
• [saag] Fwd: The Second Cryptographic Hash Workshop Call for Participation, Tim Polk
• [saag] Message on Behalf of RAND Europe, Russ Housley
• [saag] Help, songyi
  • Re: [saag] Help, Jari Arkko
• [saag] Fwd: Comments requested on NIST Draft RNG Publication, Russ Housley
• [saag] IETF Open PGP broken link, Gary Hanyzewski
  • Re: [saag] IETF Open PGP broken link, Derek Atkins
  • Re: [saag] IETF Open PGP broken link, Sam Hartman
    • Re: [saag] IETF Open PGP broken link, Gary Hanyzewski
      • Re: [saag] IETF Open PGP broken link, Sam Hartman
      • Re: [saag] IETF Open PGP broken link, Jeffrey I. Schiller
    • Re: [saag] IETF Open PGP broken link, Derek Atkins
• [saag] You are enrolled in the wrong email list for SAAG, Russ Housley
  • Re: [saag] You are enrolled in the wrong email list for SAAG, Russ Housley
• [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
  • Re: [saag] Structure of documents discussing protocols and hashes, Michael Richardson
    • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, Michael Richardson
  • Re: [saag] Structure of documents discussing protocols and hashes, David McGrew
    • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, David McGrew
      • Re: [saag] Structure of documents discussing protocols and hashes, David McGrew
      • Re: [saag] Structure of documents discussing protocols and hashes, RJ Atkinson
      • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, RJ Atkinson
    • Re: [saag] Structure of documents discussing protocols and hashes, Michael Richardson
      • Re: [saag] Structure of documents discussing protocols and hashes, David McGrew
      • Re: [saag] Structure of documents discussing protocols and hashes, Michael Richardson
      • Re: [saag] Structure of documents discussing protocols and hashes, Hugo Krawczyk
      • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, Steven M. Bellovin
      • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, Hugo Krawczyk
      • Re: [saag] Structure of documents discussing protocols and hashes, Sam Hartman
      • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
      • Re: [saag] Structure of documents discussing protocols and hashes, Michael Richardson
  • <Possible follow-ups>
  • Re: [saag] Structure of documents discussing protocols and hashes, Hugo Krawczyk
    • Re: [saag] Structure of documents discussing protocols and hashes, Hugo Krawczyk
  • Re: [saag] Structure of documents discussing protocols and hashes, Paul Hoffman
• [saag] RE: SHA1, Blumenthal, Uri
  • [saag] Re: [secdir]RE: SHA1, Jeffrey Hutzelman
  • Re: [saag] RE: SHA1, Michael Richardson
  • <Possible follow-ups>
  • RE: [saag] RE: SHA1, Blumenthal, Uri
• RE: [secdir]RE: [saag] Security Area Response to Hash Function "Breaks", Blumenthal, Uri
• [saag] Security Area Response to Hash Function "Breaks", Russ Housley
  • Re: [saag] Security Area Response to Hash Function "Breaks", der Mouse
    • Re: [saag] Security Area Response to Hash Function "Breaks", Steven M. Bellovin
    • Re: [saag] Security Area Response to Hash Function "Breaks", Russ Housley
  • <Possible follow-ups>
  • RE: [saag] Security Area Response to Hash Function "Breaks", Hallam-Baker, Phillip
    • Re: [saag] Security Area Response to Hash Function "Breaks", Michael Richardson
• [saag] Draft Minutes for IETf 64 SAAG meeting, Sam Hartman
• [saag] EMU BOF Summary, Salowey, Joe
• [saag] INCH WG report from IETF 64 (fwd), Roman Danyliw
• [saag] IETF64 SASL WG summary, Tom Yu
• [saag] IETF64 Kitten WG Summary, Jeffrey Altman
• [saag] draft-housley-aaa-key-mgmt-01.txt, Russ Housley
• [saag] Secure Interdomain Routing BOF, Alex Zinin
• [saag] Fwd: Impending publication: draft-iab-dos-03.txt, Paul Hoffman
• [saag] KDF: Randomness extraction vs. key expansion, canetti
  • Re: [saag] KDF: Randomness extraction vs. key expansion, Bill Sommerfeld
    • Re: [saag] KDF: Randomness extraction vs. key expansion, canetti
  • Re: [saag] KDF: Randomness extraction vs. key expansion, Nicolas Williams
  • [saag] Re: [Cfrg] KDF: Randomness extraction vs. key expansion, D. J. Bernstein
    • Re: [saag] Re: [Cfrg] KDF: Randomness extraction vs. key expansion, canetti
      • Re: [saag] Re: [Cfrg] KDF: Randomness extraction vs. key expansion, D. J. Bernstein
      • Re: [saag] Re: [Cfrg] KDF: Randomness extraction vs. key expansion, canetti
• [saag] Hash-Based Key Derivation, Russ Housley
  • Re: [saag] Hash-Based Key Derivation, Nicolas Williams
    • Re: [saag] Hash-Based Key Derivation, Russ Housley
      • Re: [saag] Hash-Based Key Derivation, Nicolas Williams
    • Re: [saag] Hash-Based Key Derivation, Tim Polk
  • Re: [saag] Hash-Based Key Derivation, Bill Sommerfeld
    • Re: [saag] Hash-Based Key Derivation, Tim Polk
      • Re: [saag] Hash-Based Key Derivation, Bill Sommerfeld
      • Re: [saag] Hash-Based Key Derivation, Tim Polk
      • Re: [saag] Hash-Based Key Derivation, Bill Sommerfeld
      • Re: [saag] Hash-Based Key Derivation, Steven M. Bellovin
  • Re: [saag] Hash-Based Key Derivation, Alexander Gantman
  • <Possible follow-ups>
  • Re: [saag] Hash-Based Key Derivation, Tim Polk
• [saag] Re: [smb at cs.columbia.edu: Skype security evaluation], Damien Miller
• [saag] FWD: Skype Security Evaluation, Robert Moskowitz
• [saag] status of SSL vs SHA-1/MD-5, etc.?, Alex Alten
  • Re: [saag] status of SSL vs SHA-1/MD-5, etc.?, Steven M. Bellovin
    • Re: [saag] status of SSL vs SHA-1/MD-5, etc.?, Ben Laurie
      • Re: [saag] status of SSL vs SHA-1/MD-5, etc.?, Steven M. Bellovin
  • [saag] Re: status of SSL vs SHA-1/MD-5, etc.?, Ian G
• [saag] Phishing attack targets one-time passwords, Russ Housley
  • <Possible follow-ups>
  • RE: [saag] Phishing attack targets one-time passwords, Guida, Richard [JJCUS]
• [saag] Fwd: New Public Review Issue: UTR #36, UTS #39 (Security), Paul Hoffman
• [saag] Distributed Security mailing-list set up, Pekka Savola
  • Re: [saag] Distributed Security mailing-list set up, Michael Richardson
    • Re: [saag] Distributed Security mailing-list set up, Pekka Savola
• [saag] I-D ACTION:draft-bellovin-useipsec-04.txt (Forwarded), Steven M. Bellovin
  • Re: [saag] I-D ACTION:draft-bellovin-useipsec-04.txt (Forwarded), Lakshminath Dondeti
• [saag] Informational RFC to be: draft-krovetz-umac-04.txt, Russ Housley
• [saag] Preliminary ALIEN BoF minutes available for corrections, Pekka Nikander
  • [saag] Crypto Rump Session to be webcast, james hughes
    • [saag] Re: Crypto Rump Session to be webcast, james hughes
• [saag] [The IESG] Last Call: 'Storing Certificates in the Domain Name System (DNS)' to Proposed Standard, Sam Hartman
  • Re: [saag] [The IESG] Last Call: 'Storing Certificates in the Domain Name System (DNS)' to Proposed Standard, Bernard Aboba
• [saag] IETF63 ISMS WG summary, Juergen Quittek
• [saag] Hash Bof notes, Paul Hoffman
• [saag] MASS/DKIM BOF Summary, Dave Crocker
• [saag] Summary of the MASS/DKIM BoF, Jim Fenton
• [saag] LTANS WG Session Summary - IETF 63 - August 1, 2005, 16:30-18:00, Tobias Gondrom
• [saag] IETF63 SASL WG summary, Tom Yu
  • <Possible follow-ups>
  • RE: [saag] IETF63 SASL WG summary, Christian Huitema
    • Re: [saag] IETF63 SASL WG summary, Steven M. Bellovin
      • Re: [saag] IETF63 SASL WG summary, Jeffrey Altman
      • Re: [saag] IETF63 SASL WG summary, Marcus Leech
      • Re: [saag] IETF63 SASL WG summary, Steven M. Bellovin
• [saag] INCH wg summary from IETF 63, Roman Danyliw
• [saag] krb-wg summary from IETF 63, Jeffrey Hutzelman
• [saag] BTNS WG meeting summary, Love Hörnquist Åstrand
• [saag] MOBIKE summary, Jari Arkko
• [saag] summary of sacred WG, Stephen Farrell
• [saag] Status of pki4ipsec, ietf63, Gregory M Lebovitz
• [saag] FW: [SECMECH] Summary of IETF63 secmech BOF, Salowey, Joe
• [saag] PKIX WG meeting summary, Stephen Kent
• [saag] [Fwd: [MSEC] MSEC at IETF-63 meeting summary and draft minutes.], Lakshminath Dondeti
• [saag] Status of OpenPGP at IETF-63, Derek Atkins
• [saag] Brief ALIEN BoF report, Pekka Nikander
• [saag] [Fwd: Summary of IETF63 Kitten meeting], Jeffrey Altman
• [saag] secmech BOF Tuesday 10:30, Salowey, Joe
• [saag] Asking to review multi-domain PKI interoperability I-D, Masaki SHIMAOKA
  • [saag] Re: Asking to review multi-domain PKI interoperability I-D, Masaki SHIMAOKA
    • Re: [saag] Re: Asking to review multi-domain PKI interoperability I-D, Jeff Williams
      • Re[2]: [saag] Re: Asking to review multi-domain PKI interoperability I-D, Masaki SHIMAOKA
      • Re: [saag] Re: Asking to review multi-domain PKI interoperability I-D, Jeff Williams
      • Re[2]: [saag] Re: Asking to review multi-domain PKI interoperability I-D, Masaki SHIMAOKA
• [saag] Re: I-D ACTION:draft-ietf-v6ops-ipsec-tunnels-00.txt (fwd), Pekka Savola
• [saag] 3rd International IEEE Security in Storage Workshop, james hughes
• [saag] SHAs source code ID, Eastlake III Donald-LDE008
  • [saag] Re: SHAs source code ID, Tony Hansen
• RE: [saag] RE: AAA Key Management, Sood, Kapil
• [saag] Fwd: Notification re UTR #36, Security Issues, Paul Hoffman
  • Re: [saag] Fwd: Notification re UTR #36, Security Issues, Ben Laurie
    • Re: [saag] Fwd: Notification re UTR #36, Security Issues, Jeff Williams
• [saag] [Fwd: New work for sacred working group?], Stephen Farrell
• [saag] SECMECH list announcement, Salowey, Joe
• [saag] AAA Key Management, Russ Housley
  • <Possible follow-ups>
  • [saag] AAA Key Management, Alper Yegin
    • [saag] Re: AAA Key Management, Russ Housley
      • [saag] RE: AAA Key Management, Alper Yegin
      • [saag] RE: AAA Key Management, Russ Housley
      • [saag] RE: AAA Key Management, Alper Yegin
      • [saag] RE: AAA Key Management, Russ Housley
      • [saag] RE: AAA Key Management, Alper Yegin
• [saag] Meaningful MD5 Collisions, Jeff Williams
• [saag] Discussion of IEEE 802.16e Security Issues, Bernard Aboba
• [saag] Response to 802.16 Liaison request to IETF, Bernard Aboba
  • Re: [saag] Response to 802.16 Liaison request to IETF, RJ Atkinson
• [saag] Hash BoF, Russ Housley
• [saag] [Sam Hartman] draft-harris-ssh-arcfour-fixes-02: informational or proposed?, Sam Hartman
  • Re: [saag] [Sam Hartman] draft-harris-ssh-arcfour-fixes-02: informational or proposed?, Jeffrey Altman
    • Re: [saag] [Sam Hartman] draft-harris-ssh-arcfour-fixes-02: informational or proposed?, Brian E Carpenter
• [saag] Re: saag Digest, Vol 28, Issue 10 (Out of Office), Paul DEWSNAP
• [saag] RPSEC, Russ Housley
• [saag] Some old messages from March and other list administrivia, Jeffrey I. Schiller
• RE: Abstract APIs are good (Re: [saag] Problems with SIP security), bill
  • Re: Abstract APIs are good (Re: [saag] Problems with SIP security), Nicolas Williams
  • <Possible follow-ups>
  • RE: Abstract APIs are good (Re: [saag] Problems with SIP security), Blumenthal, Uri
    • Re: Abstract APIs are good (Re: [saag] Problems with SIP security), RJ Atkinson
  • RE: Abstract APIs are good (Re: [saag] Problems with SIP security), bill
    • Re: Abstract APIs are good (Re: [saag] Problems with SIP security), Nicolas Williams
• [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Marcus Leech
  • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Cullen Jennings
  • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Sam Hartman
    • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Jari Arkko
      • Re: [saag] Problems with SIP security, RJ Atkinson
      • Abstract APIs are good (Re: [saag] Problems with SIP security), Nicolas Williams
  • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Mark Baugher
    • Message not available
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Mark Baugher
  • <Possible follow-ups>
  • RE: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Blumenthal, Uri
    • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Jari Arkko
  • RE: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Blumenthal, Uri
    • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Mark Baugher
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Jari Arkko
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Mark Baugher
  • RE: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Michael.G.Williams
    • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Marcus Leech
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Michael Richardson
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Marcus Leech
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Lakshminath Dondeti
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Michael Richardson
      • Re: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Marcus D. Leech
      • Re: [saag] Layer-2 issues, RJ Atkinson
      • Re: [saag] Layer-2 issues, Bernard Aboba
      • Re: [saag] Layer-2 issues, Bernard Aboba
      • [saag] IEEE 802.16e Security Review group, Bernard Aboba
      • Re: [saag] Layer-2 issues, Jari Arkko
  • RE: [saag] Problems with draft-ietf-mmusic-sdescriptions-09.txt, Blumenthal, Uri
• [saag] Fwd: Cryptographic Hash Workshop - Call for Participation, Tim Polk
• [saag] From: NIST SP 800-53 Errata Sheet (through 04/22/05), Jeff Williams
• [saag] Re: saag Digest, Vol 27, Issue 3 - probable solution, Vishal Gupta
  • Re: [saag] Re: saag Digest, Vol 27, Issue 3 - probable solution, Sam Hartman
• [saag] RSA Signature padding recommendations, Brian Weis
• [saag] New to this mailing list, Vishal Gupta
• [saag] Attacks on Cryptographic Hashes in Internet Protocols, Paul Hoffman
  • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, der Mouse
    • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Michael Silk
      • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Ben Laurie
    • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, RJ Atkinson
    • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Steven M. Bellovin
  • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Steven M. Bellovin
  • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Paul Hoffman
  • <Possible follow-ups>
  • RE: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Hallam-Baker, Phillip
    • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Michael Silk
  • RE: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Hallam-Baker, Phillip
    • RE: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Bill Sommerfeld
      • Re: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Michael Richardson
  • RE: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Hallam-Baker, Phillip
    • RE: [saag] Attacks on Cryptographic Hashes in Internet Protocols, Paul Hoffman
• [saag] draft-vives-v6ops-ipv6-security-ps, Russ Housley
• [saag] RSA Conference surprise - Did MS buy the report?, Jeff Williams
• [saag] On Demand Staffing for Information Technology Projects, 周立
  • <Possible follow-ups>
  • RE: [saag] On Demand Staffing for Information Technology Projects, Jaques, James III
• [saag] RE: Propping up SHA-1 (or MD5), Charlie Kaufman
  • [saag] Re: Propping up SHA-1 (or MD5), Ben Laurie
  • <Possible follow-ups>
  • RE: [saag] Re: Propping up SHA-1 (or MD5), Blumenthal, Uri
    • Re: [saag] Re: Propping up SHA-1 (or MD5), Ben Laurie
  • [saag] RE: Propping up SHA-1 (or MD5), Charlie Kaufman
• [saag] Propping up SHA-1 (or MD5), Ben Laurie
  • [saag] Re: Propping up SHA-1 (or MD5), Barney Wolff
    • [saag] Re: Propping up SHA-1 (or MD5), Ben Laurie
      • Re: [saag] Re: Propping up SHA-1 (or MD5), Ken Raeburn
      • Re: [saag] Re: Propping up SHA-1 (or MD5), Ben Laurie
  • [saag] Re: Propping up SHA-1 (or MD5), Michael Silk
  • Re: [saag] Propping up SHA-1 (or MD5), Nicolas Williams
    • Re: [saag] Propping up SHA-1 (or MD5), Ben Laurie
      • Re: [saag] Propping up SHA-1 (or MD5), Nicolas Williams
      • Re: [saag] Propping up SHA-1 (or MD5), Ben Laurie
      • Re: [saag] Propping up SHA-1 (or MD5), Nicolas Williams
  • [saag] Re: Propping up SHA-1 (or MD5), Dan Kaminsky
    • [saag] Re: Propping up SHA-1 (or MD5), Ben Laurie
  • [saag] Re: Propping up SHA-1 (or MD5), Florian Weimer
• [saag] RE:Media types, delise_palumbo
• [saag] Re: saag Digest, Vol 26, Issue 8 (Out of Office), Paul DEWSNAP