who

IETF Adelaide and interim meetings for APPS WGs

It has come to the attention of the Applications Area Directors
that one or more Applications area working groups have elected
to not meet in Adelaide, and instead to hold an "interim meeting"
in the United States, presumably because of distance and/or cost issues.

IETF is an international organization, and it is IETF's longstanding 
practice to hold its meetings in various locations around the planet.
This serves both to encourage wider participation in IETF and also
to more fairly distribute travel costs and inconvenience (over time) 
among all participants.  The scheduleing of an interim WG meeting in 
the US in lieu of a WG meeting in Adelaide undermines this policy.  
This is insulting to non-US participants of IETF (many of whom have 
attended meetings in the US for years), embarassing to IETF as 
a whole, and a threat to IETF's international stature.

Even if a working group has few participants outside the United
States, a working group does not work in isolation from other
working groups.  Attendance at IETF meetings is an invaluable 
mechanism for cross-group collaboration.  

RFC 2418 states:

   Interim meetings are subject to the
   same rules for advance notification, reporting, open participation,
   and process, which apply to other working group meetings.

Since normal working group meetings require advance notification
via email to the entire IETF list, and the process for getting a meeting
slot involves prior approval of the Area Directors, the same
requirements apply to interim working group meetings.  Part of the 

status

The as1 document and the requirements documents have moved through iesg
final call. they will be voted on in the iesg in the next few weeks.. if
(when) they pass we will have two rfc's. the as2 document is almost ready
for another version release and for your review.  we are going to start work
on defining additional headers in xml as the auto industry suggested in the
next few weeks. things are finally starting to move. the long wait for
s/mime to get approved in ietf is over and we are moving forward.... best
regards, rik

////////////////////////
Rik Drummond           /
CEO Drummond Group     /
v: 817.294.7339        /
f: 817.294.795         /
www.drummondgroup.com  /
////////////////////////

ebXML and EDIINT coordination

ebXML is an effort sponsored by the un/cefact and oasis. I lead the
transport and routing team which will defining XML headers and transport
specifications for the next generation of EC. I believe this effort is our
only chance to establish the next generation of EC in this decade. if you
are interested in participating we can do it two ways. I can keep this list
in synch with the ebXML list or you may join the ebXML list by going to the
ebxml.org site and looking under workgroups and then find the transport and
packaging area to enroll in it's list serv.

we will be defining the specifications, and releasing them down both the
ebXML and the EDIINT avenues. they will be jointly developed *unofficially*
by both groups.

please let me know your thoughts.

Best regards, rik

////////////////////////
Rik Drummond           /
CEO Drummond Group     /
v: 817.294.7339        /
f: 817.294.795         /
www.drummondgroup.com  /
////////////////////////

Re: ebXML and EDIINT coordination

Rik,

I will join the mailing list from the ebXML site.

Joe

Rik Drummond wrote:
> 
> ebXML is an effort sponsored by the un/cefact and oasis. I lead the
> transport and routing team which will defining XML headers and transport
> specifications for the next generation of EC. I believe this effort is our
> only chance to establish the next generation of EC in this decade. if you
> are interested in participating we can do it two ways. I can keep this list
> in synch with the ebXML list or you may join the ebXML list by going to the
> ebxml.org site and looking under workgroups and then find the transport and
> packaging area to enroll in it's list serv.
> 
> we will be defining the specifications, and releasing them down both the
> ebXML and the EDIINT avenues. they will be jointly developed *unofficially*
> by both groups.
> 
> please let me know your thoughts.
> 
> Best regards, rik
> 
> ////////////////////////
> Rik Drummond           /
> CEO Drummond Group     /
> v: 817.294.7339        /
> f: 817.294.795         /

Re: ebXML and EDIINT coordination

Hello Rik,

             I have joined the mailing list from the ebXML site.

    All the best,

Best Regards,
Siju Joseph,

Rik Drummond wrote:

> ebXML is an effort sponsored by the un/cefact and oasis. I lead the
> transport and routing team which will defining XML headers and transport
> specifications for the next generation of EC. I believe this effort is our
> only chance to establish the next generation of EC in this decade. if you
> are interested in participating we can do it two ways. I can keep this list
> in synch with the ebXML list or you may join the ebXML list by going to the
> ebxml.org site and looking under workgroups and then find the transport and
> packaging area to enroll in it's list serv.
>
> we will be defining the specifications, and releasing them down both the
> ebXML and the EDIINT avenues. they will be jointly developed *unofficially*
> by both groups.
>
> please let me know your thoughts.
>
> Best regards, rik
>
> ////////////////////////
> Rik Drummond           /