IETF Discussion Archive - Thread Index

• Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, (continued)
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Iljitsch van Beijnum
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, David Morris
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Sam Hartman
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, james woodyatt
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Randy Presuhn
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, TJ
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Joel M. Halpern
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Peter Dambier
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Magnus Westerlund
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Tony Hain
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, David Conrad
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Tony Hain
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, David Conrad
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, michael.dillon
  • The internet architecture, Hallam-Baker, Phillip
  • Re: The internet architecture, Stephane Bortzmeyer
  • Re: The internet architecture, Marc Manthey
  • Re: The internet architecture, Keith Moore
  • Re: The internet architecture, Stephane Bortzmeyer
  • Re: The internet architecture, Dave CROCKER
  • Re: The internet architecture, John Day
  • Re: The internet architecture, Dave CROCKER
  • RE: The internet architecture, Hallam-Baker, Phillip
  • RE: The internet architecture, michael.dillon
  • RE: The internet architecture, Hallam-Baker, Phillip
  • Re: The internet architecture, Carsten Bormann
  • Re: The internet architecture, Christian Vogt
  • Re: The internet architecture, Rémi Després
  • Re: The internet architecture, Keith Moore
  • Re: The internet architecture, Marc Manthey
  • Re: The internet architecture, Stephane Bortzmeyer
  • Re: The internet architecture, Marc Manthey
  • Re: The internet architecture, Stephane Bortzmeyer
  • Re: The internet architecture, Stig Venaas
  • Re: The internet architecture, Keith Moore
  • Re: The internet architecture, Ken Raeburn
  • Re: The internet architecture, Keith Moore
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Fred Baker
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Ted Hardie
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Keith Moore
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Iljitsch van Beijnum
  • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Eric Klein
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Margaret Wasserman
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Eric Klein
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to application developers, Peter Dambier
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Margaret Wasserman
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, ned+ietf
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Margaret Wasserman
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, ned+ietf
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Margaret Wasserman
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Eric Klein
    • Please move this thread to BEHAVE mailing list ... Was Re: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Cullen Jennings
    • RE: Please move this thread to BEHAVE mailing list ... Was Re: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Tony Hain
    • where to have the NAT66 discussion (was Re: [BEHAVE] Please move this thread to BEHAVE mailing list ... ), Keith Moore
    • Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Brian E Carpenter
    • RE: Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Tony Hain
    • Re: Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Keith Moore
    • Re: Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], David Morris
    • Re: Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Keith Moore
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Iljitsch van Beijnum
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Ted Hardie
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Iljitsch van Beijnum
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Scott Brim
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Iljitsch van Beijnum
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Ralph Droms
    • Re: [BEHAVE] Handwaving? [Re: where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Iljitsch van Beijnum
    • Re: Handwaving? [Re: [BEHAVE] where to have the NAT66 discussion (was Re: Please move this thread to BEHAVE mailing list ... )], Scott Brim
    • Re: where to have the NAT66 discussion (was Re: [BEHAVE] Please move this thread to BEHAVE mailing list ... ), Dan York
    • NAT66 discussion has been exhausted long ago (was: RE: where to have the NAT66 discussion ), Hallam-Baker, Phillip
    • Re: NAT66 discussion has been exhausted long ago, Keith Moore
    • Re: Please move this thread to BEHAVE mailing list ... Was Re: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Cullen Jennings
    • Where to discuss NAT66?, Magnus Westerlund
    • RE: Where to discuss NAT66?, Tony Hain
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Mark Andrews
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, David Morris
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Tony Hain
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Fred Baker
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Iljitsch van Beijnum
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Christian Huitema
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Steven M. Bellovin
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Christian Huitema
    • Re: [was BEHAVE] Lack of need for 66nat : Long term impacttoapplicationdevelopers, trejrco
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Steven M. Bellovin
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Christian Huitema
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Tony Hain
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Fred Baker
    • RE: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Tony Finch
    • Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers, Fred Baker
    • RE: [BEHAVE] Lack of need for 66nat : Long term impacttoapplicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impacttoapplicationdevelopers, Iljitsch van Beijnum
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Mark Andrews
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact toapplicationdevelopers, Keith Moore
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Keith Moore
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Stig Venaas
    • RE: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, AJ Jaghori
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Eric Klein
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Eric Klein
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Iljitsch van Beijnum
  • Re: Lack of need for 66nat : Long term impact to application developers, Marc Manthey
    • Re: Lack of need for 66nat : Long term impact to application developers, Patrik Fältström
  • RE: Lack of need for 66nat : Long term impact to applicationdevelopers, Hallam-Baker, Phillip
    • Re: [BEHAVE] Lack of need for 66nat : Long term impact to applicationdevelopers, Keith Moore
• [Sip] Last Call: draft-ietf-sip-session-policy-framework (A Framework for Session Initiation Protocol (SIP) Session Policies) to Proposed Standard, Andrew Allen
• RE: [mpls] Last Call: draft-ietf-mpls-cosfield-def ("EXP field" renamed to "Traffic Class field") to Proposed Standard, Venkat Doddaballapur (dvenkata)
• draft-ietf-sieve-refuse-reject approved by IESG, Matthew Elvey
• Last Call sender-auth-header, Douglas Otis
  • Re: Last Call sender-auth-header, SM
    • Re: Last Call sender-auth-header, Douglas Otis
• Plenary Online Experiment, IETF Chair
  • Re: Plenary Online Experiment, Marc Manthey
    • Re: Plenary Online Experiment, Marshall Eubanks
      • Re: Plenary Online Experiment, Marc Manthey
      • Re: Plenary Online Experiment, Marshall Eubanks
      • Re: Plenary Online Experiment, Marc Manthey
      • Re: Plenary Online Experiment, Brian E Carpenter
      • Re: Plenary Online Experiment, Marc Manthey
  • RE: Plenary Online Experiment, Stephane H Maes
    • Re: Plenary Online Experiment, Daniel Brown
  • Re: Plenary Online Experiment, Dan York
  • Re: Plenary Online Experiment, Marc Manthey
    • Re: Plenary Online Experiment, Marc Manthey
• Re: [73all] Google, Open Source & Android, lars.eggert
  • Re: [73all] Google, Open Source & Android, Dave CROCKER
• 合作, 刘海
• Re:[73attendees] Is USA qualified for 2.3 ofdraft-palet-ietf-meeting-venue-selection-criteria?, 张国强
  • RE: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Ross Callon
    • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, qdang
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Patrik Fältström
      • RE: [73attendees] Is USA qualifiedfor 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Eric Gray
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Randy Bush
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Ed Jankiewicz
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Dave CROCKER
      • Re: [73attendees] IsUSA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Tom.Petch
      • Re: [73attendees] IsUSA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Jari Arkko
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Scott Brim
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Randy Bush
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Melinda Shore
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Randy Presuhn
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Gene Gaines
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Fred Baker
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Dave CROCKER
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Ole Jacobsen
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Dave CROCKER
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Phillip Hallam-baker
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, David Morris
      • RE: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Stephane H Maes
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Keith Moore
      • Message not available
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, YAO Jiankang
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Olivier MJ Crepin-Leblond
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Randy Bush
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Nicholas Weaver
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, David Quigley
      • RE: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Yi Zhao
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Joel Jaeggli
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Soininen Jonne (NSN FI/Espoo)
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Matthew Ford
      • RE: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Livingood, Jason
      • Re: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, James Seng
      • RE: [73attendees] Is USAqualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Fleischman, Eric
      • Re: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Nicholas Weaver
      • Re: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Fernando Gont
      • RE: [73attendees] Is USAqualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, DRAGE, Keith \(Keith\)
      • Message not available
      • Re: [73attendees] Is USAqualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, YAO Jiankang
      • Re: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Fred Baker
      • Re: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Fred Baker
      • Re: [73attendees] Is USA qualifiedfor2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Adrian Farrel
      • RE: [73attendees] Is USA qualified for2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Yi Zhao
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Raj Yaralagadda
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Marshall Eubanks
      • Re: [73attendees] Is USA qualified for 2.3ofdraft-palet-ietf-meeting-venue-selection-criteria?, Marc Manthey
• Review of draft-ietf-monami6-multiplecoa-10.txt, Bernard Aboba
  • Re: Review of draft-ietf-monami6-multiplecoa-10.txt, Ryuji Wakikawa
• update on draft-irtf-asrg-dnsbl, Aaron Falk
• Re: [Tsvwg] Last Call: draft-ietf-tsvwg-admitted-realtime-dscp (DSCP for Capacity-Admitted Traffic) to Proposed Standard, Bob Briscoe
  • Re: [Tsvwg] Last Call: draft-ietf-tsvwg-admitted-realtime-dscp (DSCP for Capacity-Admitted Traffic) to Proposed Standard, Fred Baker
• Names of People Encoded On RFID Cards, Athar Shiraz Siddiqui
  • RE: [Sipping] Names of People Encoded On RFID Cards, DRAGE, Keith \(Keith\)
• 2nd Call for IAOC Nominations and Volunteers, IAB Chair
• Who Wants an RFID Badge for the Upcoming IETF Conference?, Athar Shiraz Siddiqui
  • Re: Who Wants an RFID Badge for the Upcoming IETF Conference?, Andrew G. Malis
    • Re: Who Wants an RFID Badge for the Upcoming IETF Conference?, Fred Baker
      • Re: Who Wants an RFID Badge for the Upcoming IETF Conference?, Henning Schulzrinne
• secdir review of draft-cheshire-dnsext-dns-sd, Kurt Zeilenga
• comments on draft-ietf-p2psip-base-00 re enrollment, Das, Saumitra
• Gen-ART LC Review of draft-cheshire-dnsext-dns-sd-05, Ben Campbell
• TSV Area review of draft-ietf-dime-qos-parameters, Scott O. Bradner
• Re: [BEHAVE] Can we have on NAT66 discussion?, Eric Klein
  • Re: [BEHAVE] Can we have on NAT66 discussion?, Mark Townsley
    • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Scott Brim
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Iljitsch van Beijnum
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • adm plea: avoid/reduce massive cross-posting? (was: Can we have on NAT66 discussion?), Lixia Zhang
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Keith Moore
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Keith Moore
      • FTP to HISTORIC? RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • Re: FTP to HISTORIC? RE: [BEHAVE] Can we have on NAT66 discussion?, Keith Moore
      • Message not available
      • Re: FTP to HISTORIC? RE: [BEHAVE] Can we have on NAT66 discussion?, SM
      • Re: FTP to HISTORIC? RE: [BEHAVE] Can we have on NAT66 discussion?, Tom.Petch
      • Re: FTP to HISTORIC? RE: [BEHAVE] Can we have on NAT66 discussion?, Iljitsch van Beijnum
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Iljitsch van Beijnum
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Keith Moore
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Iljitsch van Beijnum
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Eric Klein
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Hallam-Baker, Phillip
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Darrel Lewis (darlewis)
      • Re: [BEHAVE] Can we have on NAT66 discussion?, RÃmi Denis-Courmont
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Eric Klein
      • RE: [BEHAVE] Can we have on NAT66 discussion?, michael.dillon
      • RE: [BEHAVE] Can we have on NAT66 discussion?, Darrel Lewis (darlewis)
      • Re: [BEHAVE] Can we have on NAT66 discussion?, Margaret Wasserman
• Queries about SAE Beaer setup request while UE is in detach state., Bivudendu Rout
• Anyone need a hotel room for Minneapolis?, Randall Gellens
• Re: [P2PSIP] P2PSIP diagnostics: PING discussion, Das, Saumitra
  • RE: [P2PSIP] P2PSIP diagnostics: PING discussion, Roni Even
    • RE: [P2PSIP] P2PSIP diagnostics: PING discussion, Das, Saumitra
      • Re: [P2PSIP] P2PSIP diagnostics: PING discussion, Bruce Lowekamp
      • Message not available
      • Re: [P2PSIP] P2PSIP diagnostics: PING discussion, Bruce Lowekamp
    • Re: [P2PSIP] P2PSIP diagnostics: PING discussion, Colin Perkins
      • RE: [P2PSIP] P2PSIP diagnostics: PING discussion, Song Haibin
  • RE: [P2PSIP] P2PSIP diagnostics: PING discussion, Song Haibin
• Re: [P2PSIP] How to describe the processing power, Das, Saumitra
  • RE: [P2PSIP] How to describe the processing power, Song Haibin
    • RE: [P2PSIP] How to describe the processing power, Roni Even
      • Re: [P2PSIP] How to describe the processing power, Bruce Lowekamp
      • RE: [P2PSIP] How to describe the processing power, Das, Saumitra
    • RE: [P2PSIP] How to describe the processing power, Das, Saumitra
• RE: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), Joe St Sauver
  • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), David Kessens
    • RE: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl(DNS Blacklists and Whitelists)), Hallam-Baker, Phillip
• Announcement: New Boilerplate Text Required for all new Submissions to IETF, Ed Juskevicius
  • Re: Announcement: New Boilerplate Text Required for all new Submissions to IETF, Tim Chown
    • Re: Announcement: New Boilerplate Text Required for all new Submissions to IETF, Iljitsch van Beijnum
      • RE: Announcement: New Boilerplate Text Required for all new Submissions to IETF, Ed Juskevicius
    • RE: Announcement: New Boilerplate Text Required for all newSubmissions to IETF, David B. Nelson
      • RE: Announcement: New Boilerplate Text Required for allnewSubmissions to IETF, Livingood, Jason
• Comments on Draft IRTF ASRG DNSBL - 07, Jonathan Curtis
  • Re: Comments on Draft IRTF ASRG DNSBL - 07, Randy Presuhn
    • Re: Comments on Draft IRTF ASRG DNSBL - 07, Dave CROCKER
      • Re: Comments on Draft IRTF ASRG DNSBL - 07, Eliot Lear
    • Re: Comments on Draft IRTF ASRG DNSBL - 07, Rich Kulawiec
  • Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
    • Re: Comments on Draft IRTF ASRG DNSBL - 07, Tony Finch
      • Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
      • Re: Comments on Draft IRTF ASRG DNSBL - 07, Dave CROCKER
      • Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
      • SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Tony Finch
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Pekka Savola
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Pekka Savola
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
      • Re: SMTP+TLS to MXs, was Re: Comments on Draft IRTF ASRG DNSBL - 07, Mark Andrews
• Audio Streaming - IETF 73 November 16-21, 2008, Joel Jaeggli
  • <Possible follow-ups>
  • Audio Streaming - IETF 73 November 16-21, 2008, Joel Jaeggli
    • Re: Audio Streaming - IETF 73 November 16-21, 2008, Joel Jaeggli
• Comment on draft-ietf-radext-design-05.txt, Glen Zorn
  • Re: Comment on draft-ietf-radext-design-05.txt, Alan DeKok
• What Sort Of Jabber Server For IETF Conference?, Athar Shiraz Siddiqui
  • Re: What Sort Of Jabber Server For IETF Conference?, Peter Saint-Andre
    • Re: What Sort Of Jabber Server For IETF Conference?, Athar Shiraz Siddiqui
      • Re: What Sort Of Jabber Server For IETF Conference?, Peter Saint-Andre
• Gen-ART Last Call review of draft-ietf-tsvwg-rsvp-proxy-proto-07.txt, Spencer Dawkins
• Gen-ART review of draft-irtf-asrg-dnsbl-07, Spencer Dawkins
  • Re: Gen-ART review of draft-irtf-asrg-dnsbl-07, Dave CROCKER
• Last Call: draft-ietf-geopriv-pdif-lo-profile (GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations) to Proposed Standard, creed
• Punycode at ASCII for IDN & MDN via Y2K Project Management, linuxa linux
  • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, Ruszlan Gaszanov
  • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, Ruszlan Gaszanov
    • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, linuxa linux
      • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, linuxa linux
      • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, Ruszlan Gaszanov
      • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, linuxa linux
  • <Possible follow-ups>
  • RE: Punycode at ASCII for IDN & MDN via Y2K Project Management, linuxa linux
• IP-based reputation services vs. DNSBL (long), Keith Moore
  • Re: IP-based reputation services vs. DNSBL (long), John Leslie
    • RE: IP-based reputation services vs. DNSBL (long), Lawrence Rosen
      • Re: IP-based reputation services vs. DNSBL (long), John Levine
      • RE: IP-based reputation services vs. DNSBL (long), Lawrence Rosen
      • Re: IP-based reputation services vs. DNSBL (long), Eliot Lear
      • RE: IP-based reputation services vs. DNSBL (long), michael.dillon
      • Re: IP-based reputation services vs. DNSBL (long), Dave CROCKER
      • RE: IP-based reputation services vs. DNSBL (long), Hallam-Baker, Phillip
      • Re: IP-based reputation services vs. DNSBL (long), Keith Moore
      • Re: IP-based reputation services vs. DNSBL (long), Eliot Lear
      • Re: IP-based reputation services vs. DNSBL (long), Keith Moore
      • Re: IP-based reputation services vs. DNSBL (long), Eliot Lear
      • Re: IP-based reputation services vs. DNSBL (long), Keith Moore
      • Re: IP-based reputation services vs. DNSBL (long), TS Glassey
      • Re: IP-based reputation services vs. DNSBL (long), Dave CROCKER
      • Re: IP-based reputation services vs. DNSBL (long), Dave CROCKER
  • Re: IP-based reputation services vs. DNSBL (long), Sam Hartman
  • Re: IP-based reputation services vs. DNSBL (long), Tony Finch
    • Re: IP-based reputation services vs. DNSBL (long), Keith Moore
      • Re: IP-based reputation services vs. DNSBL (long), TS Glassey
      • Re: IP-based reputation services vs. DNSBL (long), Matthias Leisi
      • Re: IP-based reputation services vs. DNSBL (long), TS Glassey
      • Re: IP-based reputation services vs. DNSBL (long), Chris Lewis
      • RE: IP-based reputation services vs. DNSBL (long), Hallam-Baker, Phillip
      • Re: IP-based reputation services vs. DNSBL (long), Chris Lewis
      • RE: IP-based reputation services vs. DNSBL (long), Hallam-Baker, Phillip
      • Re: IP-based reputation services vs. DNSBL (long), Chris Lewis
      • RE: IP-based reputation services vs. DNSBL (long), Hallam-Baker, Phillip
      • Re: not spoofing, was IP-based reputation services vs. DNSBL, John Levine
      • Re: IP-based reputation services vs. DNSBL (long), Matthias Leisi
• Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, SM
  • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Russ Housley
    • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Jari Arkko
      • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, SM
  • Message not available
    • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, SM
• Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, John C Klensin
  • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Jari Arkko
    • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Russ Housley
  • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Russ Housley
    • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, SM
      • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Russ Housley
      • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, John C Klensin
      • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Russ Housley
      • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, Jari Arkko
  • Re: Last Call: draft-housley-iesg-rfc3932bis (IESG Procedures for Handling of Independent and IRTF Stream Submissions) to BCP, John C Klensin
• Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Stephane Bortzmeyer
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Stephane Bortzmeyer
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John L
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Dave CROCKER
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Sam Hartman
      • The purpose of a Last Call, Dave CROCKER
      • Re: The purpose of a Last Call, Pete Resnick
      • Re: The purpose of a Last Call, Sam Hartman
      • Re: The purpose of a Last Call, Leslie Daigle
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
    • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Livingood, Jason
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), ned+ietf
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Dave CROCKER
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Paul Hoffman
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Theodore Tso
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), David Conrad
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
      • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), michael.dillon
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tim Chown
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Doug Otis
      • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Livingood, Jason
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Matthias Leisi
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Livingood, Jason
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Eric Rescorla
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Dave CROCKER
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Eric Rescorla
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Steven M. Bellovin
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Hansen
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Steven M. Bellovin
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Matthias Leisi
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Dave CROCKER
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Doug Otis
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Andrew Sullivan
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Andrew Sullivan
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Florian Weimer
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Mark Andrews
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Florian Weimer
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Florian Weimer
      • Re: Last Call: draft-irtf-asrg-blinds (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Mark Andrews
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Florian Weimer
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Mark Andrews
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Florian Weimer
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
  • <Possible follow-ups>
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Doug Ewell
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Theodore Tso
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
    • draft-irtf-asrg-bcp-blacklists, John Leslie
      • Re: draft-irtf-asrg-bcp-blacklists, SM
      • Re: draft-irtf-asrg-bcp-blacklists, John Levine
      • Re: draft-irtf-asrg-bcp-blacklists, Chris Lewis
      • Re: draft-irtf-asrg-bcp-blacklists, Rich Kulawiec
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John C Klensin
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), John Levine
    • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Livingood, Jason
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
  • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Steve Linford
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Theodore Tso
      • RE: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), michael.dillon
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Steve Linford
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Lisa Dusseault
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Tony Finch
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Chris Lewis
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), der Mouse
    • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Keith Moore
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), der Mouse
      • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), SM
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Joe St Sauver
    • IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), David Kessens
      • Re: IPv6 traffic stats, Harald Alvestrand
      • Re: IPv6 traffic stats, Turchanyi Geza
      • Re: IPv6 traffic stats, Harald Alvestrand
      • Re: IPv6 traffic stats, Marc Manthey
      • Re: IPv6 traffic stats, Pekka Savola
      • Re: IPv6 traffic stats, Harald Alvestrand
      • RE: IPv6 traffic stats, Hallam-Baker, Phillip
      • Re: IPv6 traffic stats, Geoff Huston
      • Re: IPv6 traffic stats, Peter Sherbin
      • Re: IPv6 traffic stats, Pekka Savola
      • Re: IPv6 traffic stats, Iljitsch van Beijnum
      • Re: IPv6 traffic stats, Pekka Savola
      • Re: IPv6 traffic stats - limitations of 6to4, Rémi Després
      • Re: IPv6 traffic stats - limitations of 6to4, Pekka Savola
      • Re: IPv6 traffic stats, Danny McPherson
      • Re: IPv6 traffic stats, Iljitsch van Beijnum
      • RE: IPv6 traffic stats, TJ
      • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), Danny McPherson
      • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), David Kessens
      • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), Danny McPherson
      • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)), David Kessens
      • Re: IPv6 traffic stats (was: Re: Last Call: draft-irtf-asrg-dnsbl(DNS Blacklists and Whitelists)), Olivier MJ Crepin-Leblond
  • Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists), Jamie Tomasello
• Re: Last Call: draft-hoffman-dac-vbr (Vouch By Reference) to Proposed Standard, SM
  • Re: Last Call: draft-hoffman-dac-vbr (Vouch By Reference) to Proposed Standard, Paul Hoffman
    • Re: Last Call: draft-hoffman-dac-vbr (Vouch By Reference) to Proposed Standard, John Levine
      • Re: Last Call: draft-hoffman-dac-vbr (Vouch By Reference) to Proposed Standard, Paul Hoffman
      • Re: Last Call: draft-hoffman-dac-vbr (Vouch By Reference) to Proposed Standard, SM
• draft-kucherawy-sender-auth-header and last call draft-hoffman-dac-vbr-04, Douglas Otis
• Review of draft-ietf-behave-dccp-04, Christian Vogt
  • Re: Review of draft-ietf-behave-dccp-04, Rémi Denis-Courmont
    • Re: Review of draft-ietf-behave-dccp-04, Christian Vogt
      • Re: Review of draft-ietf-behave-dccp-04, Rémi Denis-Courmont
      • Re: Review of draft-ietf-behave-dccp-04, Christian Vogt
      • Re: Review of draft-ietf-behave-dccp-04, Rémi Denis-Courmont
      • Re: Review of draft-ietf-behave-dccp-04, Christian Vogt
• Re: Last Call: draft-igoe-secsh-aes-gcm (AES Galois Counter Mode for, Russ Housley
• Gen-ART Last Call Review of draft-ietf-pim-rpf-vector-06, Ben Campbell
  • Re: Gen-ART Last Call Review of draft-ietf-pim-rpf-vector-06, IJsbrand Wijnands
• Gen-ART Last Call review of draft-ietf-ospf-lls-05.txt, Spencer Dawkins
  • Re: Gen-ART Last Call review of draft-ietf-ospf-lls-05.txt, Abhay Roy
    • Re: Gen-ART Last Call review of draft-ietf-ospf-lls-05.txt, Liem Nguyen
• Gen-ART LC Review of draft-ietf-nfsv4-pnfs-block-09, Ben Campbell
• Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Cyrus Daboo
  • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Stuart Cheshire
  • <Possible follow-ups>
  • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Cullen Jennings
  • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Dave Cridland
    • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Mark Townsley
      • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Henning Schulzrinne
      • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Dave Cridland
  • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Chris Newman
    • Re: Last Call: draft-cheshire-dnsext-dns-sd (DNS-Based Service Discovery) to Informational RFC, Marc Manthey
• Gen-ART Telechat Review of draft-ietf-avt-dtls-srtp-06, Ben Campbell