Requirements for Open Pluggable Edge Services (OPES) Callout Protocols
draft-ietf-opes-protocol-reqs-03
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2015-10-14
|
03 | (System) | Notify list changed from <mrose+mtr.ietf@dbc.mtview.ca.us>, <hofmann@bell-labs.com> to <mrose+mtr.ietf@dbc.mtview.ca.us> |
|
2004-09-21
|
03 | (System) | Ballot writeup text was added |
|
2004-09-21
|
03 | (System) | Last call text was added |
|
2004-09-21
|
03 | (System) | Ballot approval text was added |
|
2004-09-21
|
03 | Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2004-09-21
|
03 | Amy Vezza | [Note]: 'RFC 3836' added by Amy Vezza |
|
2004-08-31
|
03 | (System) | RFC published |
|
2003-02-27
|
03 | Jacqueline Hargest | State Changes to RFC Ed Queue from Approved-announcement sent by Hargest, Jacqueline |
|
2003-02-11
|
03 | Jacqueline Hargest | State Changes to Approved-announcement sent from Approved-announcement to be sent by Hargest, Jacqueline |
|
2003-02-06
|
03 | Ned Freed | Note sent to WG: The IESG has approved the drafts ietf-opes-protocol-reqs-03.txt draft-ietf-opes-architecture-04.txt for publication as informational RFCs. An announcement to this effect will … Note sent to WG: The IESG has approved the drafts ietf-opes-protocol-reqs-03.txt draft-ietf-opes-architecture-04.txt for publication as informational RFCs. An announcement to this effect will be sent shortly. As explained previously, the IESG believes that draft-ietf-opes-scenarios-01.txt is too dependent on draft-ietf-opes-threats-00.txt to publish at this time. The IESG is concerned, however, that what appears in these drafts is a fairly high level overview of OPES requirements and architecture. Missing is any mention of specific mechanisms to provide security and congestions. This is not necessarily a problem given these are informational requirement and architecture documents. However, the IESG notes that the lack of specificity at this point could lead to problems deciding on actual protocol details later in the process. Requirement and architecture documents have often proved to be useful tools in reaching consensus on subsequent protocol specifications. Should difficulties arise in reaching consensus later it may be necessary and useful to expand on these documents with information about specific mechanisms to be used. |
|
2003-02-06
|
03 | Ned Freed | State Changes to Approved-announcement to be sent from IESG Evaluation by Freed, Ned |
|
2003-02-06
|
03 | (System) | IESG has approved the document |
|
2002-12-27
|
03 | Ned Freed | State Changes to IESG Evaluation :: AD Followup from IESG Evaluation :: Revised ID Needed by Freed, Ned |
|
2002-12-12
|
03 | (System) | New version available: draft-ietf-opes-protocol-reqs-03.txt |
|
2002-10-28
|
03 | Ned Freed | State Changes to IESG Evaluation -- New ID Needed from IESG Evaluation by freed |
|
2002-10-08
|
03 | Stephen Coya | State Changes to IESG Evaluation from Last Call Requested by scoya |
|
2002-10-07
|
03 | Ned Freed | Intended Status has been changed to Informational from None |
|
2002-10-07
|
03 | Ned Freed | State Changes to Last Call Requested from Publication Requested by freed |
|
2002-08-05
|
02 | (System) | New version available: draft-ietf-opes-protocol-reqs-02.txt |
|
2002-06-20
|
03 | Ned Freed | Draft Added by freed |
|
2002-06-19
|
01 | (System) | New version available: draft-ietf-opes-protocol-reqs-01.txt |
|
2002-05-28
|
00 | (System) | New version available: draft-ietf-opes-protocol-reqs-00.txt |