ietf  

Messages by Thread

• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP SM
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Chris Grundemann
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP SM
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Chris Grundemann
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Mark Andrews
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Ronald Bonica
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP David Conrad
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Chris Grundemann
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Roger Jørgensen
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP SM
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP John C Klensin
• RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees Frequently Asked (travel) Questions) to Informational RFC Adrian Farrel
• Re: IAB statement: "The interpretation of rules in the ICANN gTLD Applicant Guidebook" Stephane Bortzmeyer
• RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC Adrian Farrel
  • RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC Weingarten, Yaacov (NSN - IL/Hod HaSharon)
• Re: Last Call: <draft-ietf-v6ops-v6nd-problems-04.txt> (Operational Neighbor Discovery Problems) to Informational RFC Fernando Gont
• Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC Stephen Farrell
  • Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC t.petch
  • RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC Ross Callon
  • Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC Randy Bush
• Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03 Ben Campbell
  • Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03 Ben Campbell
  • RE: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03 Maglione Roberta
• Comments on Section 10.10 of OAuth 2.0 Nat Sakimura
• Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Erik Kline
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Tina TSOU
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Fred Baker
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Erik Kline
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Lorenzo Colitti
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Joel jaeggli
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Lorenzo Colitti
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Roger Jørgensen
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Doug Barton
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Fred Baker
  • Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC Mark Andrews
• Yet Another Reason? Alan Johnston
  • Re: Yet Another Reason? Chris Grundemann
  • Re: Yet Another Reason? Nick Hilliard
  • RE: Yet Another Reason? Worley, Dale R (Dale)
  • Re: Yet Another Reason? Douglas Otis
  • Re: Yet Another Reason? Fernando Gont
• Gen-ART review for draft-kucherawy-authres-spf-erratum-01 kathleen.moriarty
• Nomcom 2011-2012: IAB Appointments NomCom Chair
• REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Francisco Corella
  • RE: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard Tschofenig, Hannes (NSN - FI/Espoo)
  • Re: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard Francisco Corella
• Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Chris Grundemann
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Brian E Carpenter
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP George, Wes
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Noel Chiappa
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP George, Wes
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Pete Resnick
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Brian E Carpenter
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP C. M. Heard
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Pete Resnick
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Brian E Carpenter
  • RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Jean-Francois . TremblayING
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Noel Chiappa
  • Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Jinesh Doshi
  • Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP Doug Barton
• Re: REVISED Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard Francisco Corella
• IPR statement... Intentionally creating derivatives which infringe on protected IP creates numerous claims and grounds for pain we don't need here. todd glassey
• OAuth 2.0 Bearer Token Specification Draft -16 Mike Jones
  • RE: [OAUTH-WG] OAuth 2.0 Bearer Token Specification Draft -16 Mike Jones
• Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt Alexey Melnikov
  • RE: Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt Mike Jones
  • IPR issues = Re: Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt todd glassey
  • Re: IPR issues = Re: Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt IETF Chair
  • Re: Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt Alexey Melnikov
  • Re: [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt Alexey Melnikov
  • Re: [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt Stephen Farrell
• Gen-ART LC review of draft-ietf-dnsext-ecdsa-04 Roni Even
  • Re: Gen-ART LC review of draft-ietf-dnsext-ecdsa-04 Olafur Gudmundsson
• Commentary about IETF protocols which do not provide IP protection in their use. todd glassey
  • Re: Commentary about IETF protocols which do not provide IP protection in their use. Vinayak Hegde
  • Re: Commentary about IETF protocols which do not provide IP protection in their use. todd glassey
• Nomcom 2011-2012: IAOC Appointment NomCom Chair
• Nomcom 2011-2012: IESG Appointments NomCom Chair
• License Disclosure Protocol - a Research and then Standards Track Proposal todd glassey
• Le Meridien Etoile for $149 ( ¤115 ) per night. Randall Gellens
• Security review of draft-ietf-radext-radsec Sam Hartman
  • Re: [radext] Security review of draft-ietf-radext-radsec Stefan Winter
  • Re: [radext] Security review of draft-ietf-radext-radsec Sam Hartman
• unsubscribe Daniel Maia
• Forthcoming draft: draft-farrresnickel-ipr-sanctions Pete Resnick
  • RE: Forthcoming draft: draft-farrresnickel-ipr-sanctions Adrian Farrel
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Eric Burger
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Richard L. Barnes
  • RE: Forthcoming draft: draft-farrresnickel-ipr-sanctions Adrian Farrel
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Hector
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Dave CROCKER
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Pete Resnick
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Lou Berger
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Hector
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Stephan Wenger
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions Hector
  • Re: Forthcoming draft: draft-farrresnickel-ipr-sanctions SM
• Gen-ART review of draft-ietf-payload-rtp-klv-02 Richard L . Barnes
  • Re: Gen-ART review of draft-ietf-payload-rtp-klv-02 Jeff Downs
• RE: Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) Adrian Farrel
  • RE: Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM
• Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Adam Roach
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Adrian Farrel
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Peter Saint-Andre
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Thomas Nadeau
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Worley, Dale R (Dale)
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard John C Klensin
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Harald Alvestrand
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Not ifica tion Mechanism: SIP MESSAGE) to Proposed Standard John C Klensin
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Not ifica tion Mechanism: SIP MESSAGE) to Proposed Standard Murray S. Kucherawy
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard SM
  • encouraging compliance with IPR disclosure rules Peter Saint-Andre
  • Re: encouraging compliance with IPR disclosure rules SM
  • Re: encouraging compliance with IPR disclosure rules Polk, William T.
  • Re: encouraging compliance with IPR disclosure rules Scott Brim
  • Re: encouraging compliance with IPR disclosure rules todd glassey
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard todd glassey
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Cyrus Daboo
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard John C Klensin
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Kevin P. Fleming
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> Martin Rex
  • Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notifica tion Mechanism: SIP MESSAGE) to Proposed Standard Arnt Gulbrandsen
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Worley, Dale R (Dale)
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard SM
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Cyrus Daboo
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Michael Richardson
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Murray S. Kucherawy
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt>(Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard t.petch
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Barry Leiba
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Ted Hardie
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Steven Bellovin
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Barry Leiba
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard SM
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Murray S. Kucherawy
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Hector Santos
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Alexey Melnikov
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Hector
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Adam Roach
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Dave CROCKER
  • Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Dave CROCKER
  • Re: [sieve] Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Bob Hinden
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard SM
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Peter Saint-Andre
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Dave Cridland
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Murray S. Kucherawy
  • RE: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Murray S. Kucherawy
  • Re: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard Pete Resnick
  • Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM
  • RE: Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) Adrian Farrel
  • RE: Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) SM
  • RE: Violation of IETF process (was: Second Last Call: <draft-ietf-sieve-notify-sip-message-08.txt> (Sieve Notification Mechanism: SIP MESSAGE) to Proposed Standard) Murray S. Kucherawy
  • Re: Violation of IETF process todd glassey
• T-Shirt Design Contest for IETF 83 Paris Alexa Morris
  • Re: T-Shirt Design Contest for IETF 83 Paris Olaf Kolkman
  • Re: T-Shirt Design Contest for IETF 83 Paris Marshall Eubanks
  • Re: T-Shirt Design Contest for IETF 83 Paris Francis Dupont
• Re: Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard SM
• RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Julian Reschke
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The Martin Rex
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The Mike Jones
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The Bjoern Hoehrmann
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The Martin Rex
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The Julian Reschke
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Eran Hammer
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Eran Hammer
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard John Bradley
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard William Mills
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Peter Saint-Andre
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
• FYI : Canada's CRTC mandates all IP Interconnection for voice. Richard Shockey
  • Re: FYI : Canada's CRTC mandates all IP Interconnection for voice. Kevin P. Fleming
  • RE: FYI : Canada's CRTC mandates all IP Interconnection for voice. Richard Shockey
  • Re: FYI : Canada's CRTC mandates all IP Interconnection for voice. Kevin P. Fleming
• Gen-ART LC Review of draft-ietf-avtcore-srtp-vbr-audio-04 Ben Campbell
• Re: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Stephen Farrell
• Gen-ART LC review of draft-harkins-ipsecme-spsk-auth-06 Roni Even
• Room sharing in Paris? Kevin P. Fleming
  • Re: Room sharing in Paris? Yoav Nir
  • Re: Room sharing in Paris? Kevin P. Fleming
• Re: Last Call: <draft-ietf-dnsext-xnamercode-00.txt> (xNAME RCODE and Status Bits Clarification) to Proposed Standard SM
  • Re: Last Call: <draft-ietf-dnsext-xnamercode-00.txt> (xNAME RCODE and Status Bits Clarification) to Proposed Standard Donald Eastlake
  • RE: Last Call: <draft-ietf-dnsext-xnamercode-00.txt> (xNAME RCODE and Status Bits Clarification) to Proposed Standard Murray S. Kucherawy
  • Re: Last Call: <draft-ietf-dnsext-xnamercode-00.txt> (xNAME RCODE and Status Bits Clarification) to Proposed Standard Andrew Sullivan
  • RE: Last Call: <draft-ietf-dnsext-xnamercode-00.txt> (xNAME RCODE and Status Bits Clarification) to Proposed Standard Murray S. Kucherawy
• Re: Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard Barry Leiba
  • Re: Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0 Authorization Protocol) to Proposed Standard Peter Saint-Andre
• Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Julian Reschke
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Julian Reschke
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Mike Jones
  • Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard Julian Reschke

• Earlier messages