Archive of ietf-openproxy, by thread
Go to date index
Go to main page for ietf-openproxy
Page 4 of 8
[Prev Page] [Next Page] [First Page]
[Last Page]
- Re: OPES definition/scope, (continued)
- Re: OCP questions,
The Purple Streak, Hilarie Orman
- Re: OCP questions,
Alex Rousskov
- Re: OCP questions,
jfcm
- BEEP as OCP transport,
Alex Rousskov
- OCPTRAN as OCP transport,
Alex Rousskov
- Re: OCPTRAN as OCP transport,
Alex Rousskov
- Re: BEEP as OCP transport,
Marshall Rose
- Re: BEEP as OCP transport,
Alex Rousskov
- Re: BEEP as OCP transport,
Marshall Rose
- Re: BEEP as OCP transport,
Alex Rousskov
- SOAP and OCP,
Alex Rousskov
- Re: BEEP as OCP transport,
Marshall Rose
- Re: BEEP as OCP transport,
Alex Rousskov
- Re: BEEP as OCP transport,
Alex Rousskov
- Re: BEEP as OCP transport,
Marshall Rose
- Re: BEEP as OCP transport,
Alex Rousskov
- Re: BEEP as OCP transport,
Marshall Rose
- Re: BEEP as OCP transport,
Alex Rousskov
- ICAP RFC available,
Frank Berzau
- Shortcuts,
The Purple Streak, Hilarie Orman
- Charter issues,
The Purple Streak, Hilarie Orman
- OCP Core version head_sid4 available,
Alex Rousskov
- Some attempts at clarification,
The Purple Streak, Hilarie Orman
- Tracing Draft version-0004082003,
Abbie Barbir
- Notification,
Abbie Barbir
- OCP version head_sid3 available,
Alex Rousskov
- fixing "application message" mess,
Alex Rousskov
- Rules language,
The Purple Streak, Hilarie Orman
- feedback: OCP version head_sid2 thread: Try 2,
Abbie Barbir
- feedback: OCP version head_sid2 thread,
Abbie Barbir
- OCP version head_sid2 available,
Alex Rousskov
- More comments on ocp-00,
Martin Stecher
- RE: Comments on ocp-00,
Alex Rousskov
- Re: Comments on ocp-00,
Reinaldo
- a question ONES again?,
jfcm
- Re: a question ONES again?,
The Purple Streak, Hilarie Orman
- Re: a question ONES again?,
jfcm
- set of OPES documents,
Alex Rousskov
- RE: set of OPES documents,
Oskar Batuner
- RE: set of OPES documents,
Alex Rousskov
- Re: set of OPES documents,
The Purple Streak, Hilarie Orman
- Re: set of OPES documents,
Markus Hofmann
- Re: a question ONES again?,
Alex Rousskov
- Re: a question ONES again?,
jfcm
- Re: a question ONES again?,
Alex Rousskov
- Re: Comments on ocp-00,
Markus Hofmann
- Re: Comments on ocp-00,
Reinaldo Penno
- Re: Comments on ocp-00,
Markus Hofmann
- ICAP extensions for parsing av responses? (fwd),
Alex Rousskov
- Comments on ocp-00,
Reinaldo Penno
- [Fwd: Need to look at tracing and debuggig],
Markus Hofmann
- Need to look at tracing and debuggig,
Markus Hofmann
- RE: Need to look at tracing and debuggig,
Oskar Batuner
- <Possible follow-ups>
- RE: Need to look at tracing and debuggig,
Abbie Barbir
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- RE: Need to look at tracing and debuggig,
Oskar Batuner
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- RE: Need to look at tracing and debuggig,
Oskar Batuner
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- Re: Need to look at tracing and debuggig,
Weisong Shi
- Re: Need to look at tracing and debuggig,
Alex Rousskov
- usage of Squid Web cache on the Internet,
Weisong Shi
- RE: Need to look at tracing and debuggig,
jfcm
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- RE: Need to look at tracing and debuggig,
Oskar Batuner
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- RE: Need to look at tracing and debuggig,
The Purple Streak, Hilarie Orman
- RE: Need to look at tracing and debuggig,
Alex Rousskov
- Protocol next steps,
Markus Hofmann
- Re: Protocol next steps,
Alex Rousskov
- Re: Protocol next steps,
Markus Hofmann
- Re: Protocol next steps,
Alex Rousskov
- Re: Protocol next steps,
Markus Hofmann
- Re: Protocol next steps,
The Purple Streak, Hilarie Orman
- Re: Protocol next steps,
Marshall Rose
- Re: Protocol next steps,
Markus Hofmann
- Re: Protocol next steps,
Alex Rousskov
- Re: Protocol next steps,
The Purple Streak, Hilarie Orman
- Re: Protocol next steps,
Alex Rousskov
- Re: Protocol next steps,
Markus Hofmann
- Re: Protocol next steps,
Markus Hofmann
- <Possible follow-ups>
- RE: Protocol next steps,
bindignavile.srinivas
- RE: Protocol next steps,
Abbie Barbir
- RE: Protocol next steps,
Abbie Barbir
- RE: Protocol next steps,
Abbie Barbir
- RE: Protocol next steps,
jfcm
- copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
Markus Hofmann
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
Markus Hofmann
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
Markus Hofmann
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
The Purple Streak, Hilarie Orman
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
The Purple Streak, Hilarie Orman
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
The Purple Streak, Hilarie Orman
- Re: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
Markus Hofmann
- <Possible follow-ups>
- RE: copying commitment and deadlock,
Abbie Barbir
- RE: copying commitment and deadlock,
Alex Rousskov
- RE: copying commitment and deadlock,
The Purple Streak, Hilarie Orman
- RE: copying commitment and deadlock,
Alex Rousskov
- RE: copying commitment and deadlock,
jfcm
- RE: copying commitment and deadlock,
Alex Rousskov
- RE: copying commitment and deadlock,
The Purple Streak, Hilarie Orman
- RE: copying commitment and deadlock,
Alex Rousskov
- Re: copying commitment and deadlock,
Markus Hofmann
- RE: copying commitment and deadlock,
jfcm
- RE: copying commitment and deadlock,
Alex Rousskov
- RE: copying commitment and deadlock,
jfcm
- ICAP header questions,
Yimin Chen
- Example of SMTP Fan-Out,
Eric Burger
- Agenda for OPES at IETF 56,
Markus Hofmann
- Draft Agenda for IETF 56,
Markus Hofmann
- Re: Draft Agenda for IETF 56,
Alex Rousskov
- Re: Draft Agenda for IETF 56,
Markus Hofmann
- Re: Draft Agenda for IETF 56,
jfcm
- <Possible follow-ups>
- RE: Draft Agenda for IETF 56,
Abbie Barbir
- RE: Draft Agenda for IETF 56,
Abbie Barbir
- RE: Draft Agenda for IETF 56,
jfcm
- RE: Draft Agenda for IETF 56,
Reinaldo Penno
- RE: Draft Agenda for IETF 56,
Reinaldo Penno
- RE: Draft Agenda for IETF 56,
Reinaldo Penno
- RE: Draft Agenda for IETF 56,
Abbie Barbir
- RE: Draft Agenda for IETF 56,
jfcm
- RE: Draft Agenda for IETF 56,
Abbie Barbir
- RE: Draft Agenda for IETF 56,
Abbie Barbir
- RE: Draft Agenda for IETF 56,
Reinaldo Penno
- Re: Draft Agenda for IETF 56,
Markus Hofmann
- Re: Draft Agenda for IETF 56,
Alex Rousskov
- Re: Draft Agenda for IETF 56,
Markus Hofmann
- Re: Draft Agenda for IETF 56,
Alex Rousskov
- Re: Draft Agenda for IETF 56,
Markus Hofmann
- RE: Draft Agenda for IETF 56,
Oskar Batuner
- RE: Draft Agenda for IETF 56,
Alex Rousskov
- RE: Draft Agenda for IETF 56,
Oskar Batuner
- RE: Draft Agenda for IETF 56,
jfcm
- RE: Draft Agenda for IETF 56,
Oskar Batuner
- RE: Draft Agenda for IETF 56,
jfcm
- RE: Draft Agenda for IETF 56,
Alex Rousskov
- RE: Draft Agenda for IETF 56,
Oskar Batuner
- RE: Draft Agenda for IETF 56,
Alex Rousskov
- Re: Draft Agenda for IETF 56,
Markus Hofmann
- Message not available
- Re: Draft Agenda for IETF 56,
Alex Rousskov
- Message not available
- Re: Draft Agenda for IETF 56,
Alex Rousskov
- RE: Draft Agenda for IETF 56,
jfcm
- RE: Draft Agenda for IETF 56,
Alex Rousskov
RE: Draft Agenda for IETF 56,
Reinaldo Penno
RE: Draft Agenda for IETF 56,
Reinaldo Penno
RE: Draft Agenda for IETF 56,
Abbie Barbir
RE: Draft Agenda for IETF 56,
Reinaldo Penno
RE: Draft Agenda for IETF 56,
Abbie Barbir
RE: Draft Agenda for IETF 56,
Abbie Barbir
RE: Draft Agenda for IETF 56,
Reinaldo Penno
is IDNA an OPES?,
jfcm
RE: plug-out?,
chen
AW: too fast out-of-SENT-order messages,
Martin Stecher
RE: too fast out-of-SENT-order messages,
Martin Stecher
too fast out-of-order messages,
Alex Rousskov
WG meeting agenda,
Alex Rousskov
RE: OPES transport protocol,
Abbie Barbir
OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Oskar Batuner
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Oskar Batuner
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Oskar Batuner
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Oskar Batuner
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Alex Rousskov
- <Possible follow-ups>
- Fwd: RE: OPES protocol, pre-draft 01,
jfcm
- RE: OPES protocol, pre-draft 01,
Abbie Barbir
- RE: OPES protocol, pre-draft 01,
Abbie Barbir
AW: OPES protocol, additional message needed?,
Martin Stecher
AW: OPES protocol, pre-draft,
Martin Stecher
OPES protocol, additional message needed?,
Martin Stecher
OPES protocol, pre-draft,
Alex Rousskov
- Re: OPES protocol, pre-draft,
The Purple Streak, Hilarie Orman
- RE: OPES protocol, pre-draft,
Oskar Batuner
- <Possible follow-ups>
- RE: OPES protocol, pre-draft,
Reinaldo Penno
- Re: OPES protocol, pre-draft,
jfcm
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
Abbie Barbir
- Re: OPES protocol, pre-draft,
jfcm
- Re: OPES protocol, pre-draft,
Alex Rousskov
- RE: OPES protocol, pre-draft,
Martin Stecher
- RE: OPES protocol, pre-draft,
Alex Rousskov
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
Alex Rousskov
- RE: OPES protocol, pre-draft,
Oskar Batuner
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
jfcm
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
jfcm
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
jfcm
- RE: OPES protocol, pre-draft,
Oskar Batuner
- Re: OPES protocol, pre-draft,
Markus Hofmann
- RE: OPES protocol, pre-draft,
Oskar Batuner
- RE: OPES protocol, pre-draft,
Alex Rousskov
- RE: OPES protocol, pre-draft,
Alex Rousskov
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
Markus Hofmann
- Re: OPES protocol, pre-draft,
Alex Rousskov
- RE: OPES protocol, pre-draft,
jfcm
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
Martin Stecher
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
jfcm
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
Abbie Barbir
- RE: OPES protocol, pre-draft,
bindignavile.srinivas
- RE: OPES protocol, pre-draft,
jfcm
AW: SMTP filtering use case,
Martin Stecher
SMTP filtering use case,
Martin Stecher
- Re: SMTP filtering use case,
Alex Rousskov
- RE: SMTP filtering use case,
Oskar Batuner
- Re: SMTP filtering use case,
The Purple Streak, Hilarie Orman
- <Possible follow-ups>
- RE: SMTP filtering use case,
Reinaldo Penno
- RE: SMTP filtering use case,
Abbie Barbir
- RE: SMTP filtering use case,
Abbie Barbir
- RE: SMTP filtering use case,
Abbie Barbir
- RE: SMTP filtering use case,
Abbie Barbir
- RE: SMTP filtering use case,
jfcm
protocol core now, transport/encoding later,
Alex Rousskov
Request/response pairs,
Martin Stecher
AW: Start on OPES protocol work,
Martin Stecher
Start on OPES protocol work,
Markus Hofmann
- Re: Start on OPES protocol work,
Marshall Rose
- <Possible follow-ups>
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
jfcm
- Re: Start on OPES protocol work,
Martin Stecher
- Re: Start on OPES protocol work,
Martin Stecher
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
Martin Stecher
- RE: Start on OPES protocol work,
Martin Stecher
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
Abbie Barbir
- RE: Start on OPES protocol work,
Martin Stecher
- RE: Start on OPES protocol work,
Abbie Barbir
FW: I-D ACTION:draft-iab-sec-cons-03.txt,
Abbie Barbir
Document Action: Requirements for OPES Callout Protocols to Informational,
The IESG
I-D ACTION:draft-ietf-opes-threats-02.txt,
Internet-Drafts
I-D ACTION:draft-ietf-opes-authorization-02.txt,
Internet-Drafts
publish draft-ietf-opes-threats-02,
Abbie Barbir
publish draft: draft-ietf-opes-authorization-02,
Abbie Barbir
IESG concerns regarding the OPES requirements and architecture documents,
ned . freed
to share OPES operations experience,
jfcm
I-D ACTION:draft-ietf-opes-authorization-01.txt,
Internet-Drafts
I-D ACTION:draft-ietf-opes-threats-01.txt,
Internet-Drafts
ICAP header extensions,
Martin Stecher
FW: publish draft: draft-ietf-opes-authorization-01,
Abbie Barbir
[Fwd: publish draft: draft-ietf-opes-authorization-01],
Markus Hofmann
WG Last Call: draft-ietf-opes-threats-01,
Markus Hofmann
publish draft-ietf-opes-threats-01,
Abbie Barbir
OPES Status and IETF 56,
Markus Hofmann
I-D ACTION:draft-ietf-opes-protocol-reqs-03.txt,
Internet-Drafts
I-D ACTION:draft-ietf-opes-architecture-04.txt,
Internet-Drafts
draft-ietf-opes-protocol-reqs-03,
Andre Beck
FW: Autoreply from Internet Draft Submission Manager,
Abbie Barbir
Publish Draft: draft-ietf-opes-architecture-04,
Abbie Barbir
Call for Comments on OPES Drafts,
Markus Hofmann
Page 4 of 8
[Prev Page] [Next Page] [First Page]
[Last Page]
The web site for this mailing list is sponsored by the Internet Mail
Consortium. If you have any suggestions for additions or corrections
to this Web page, please send them to
phoffman@imc.org.