Re: APEX documents on hold
Patrik Fältström <[email protected]> Wed, 17 Jul 2002 08:59:12 +0900
| Newsgroups | gmane.ietf.apex |
|---|---|
| Message-ID | <1279614.1026896352@localhost> |
--On 2002-07-16 08.46 +0900 Patrik F=E4ltstr=F6m <[email protected]> wrote: > The IESG has decided to keep the apex documents on hold until a mapping > document from APEX to CPIM exists, so all documents can be published > together. >=20 > Patrik F=E4ltstr=F6m > co-Area Director, Applications Area The IESG (no surprise I guess) once again discuss the APEX documents this morning. I was (of course) told the statement above is not coherent with what the decision was yesterday, and I personally apologise. Let me first point out that the fact that it was detected that references "towards" the CPIM documents (direct, or indirectly via the 5th last APEX document which is to specify the mapping between APEX and CPIM) is completely unrelated to the discussion about (a) XML transport protocols = in the IETF (b) whether jabber makes sense as an IMPP protocol (c) whether jabber should become a wg. What IESG is talking about regarding the APEX documents is _only_ the lac= k of references towards CPIM. Now, what IESG decided yesterday (which i worded badly) was that we requested the documents to be on hold while discussing because it was detected that references were missing. Not "until those references were added". Today, after discussing with the APEX chair and Graham (author of relevan= t document(s)), IESG decided: - To request at the RFC-Editor that the 3 APEX base specifications: draft-ietf-apex-core-06.txt draft-ietf-apex-access-08.txt draft-ietf-apex-party-04.txt - To keep the hold on the IM part of APEX and continue to discuss with authors, wg chairs etc on how to do the referencing draft-ietf-apex-presence-06.txt Note once again: (a) This is unrelated with XML/Jabber/whatever issues (b) The hold requested is just because we think we all need to think some more on an issue which was not rised during last call or during IESG discussions, "we" as in IETF, not just IESG Patrik F=E4ltstr=F6m co-Area Director, Applications Area