RE: profiles in AS2
"Dominique Danvoye" <[email protected]> Wed, 21 Dec 2005 14:21:53 -0500
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
------=_NextPart_000_0033_01C60639.E426AC00
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
First, we understand and agree that AS2 partnerships management
could be enhanced. Unfortunately right now major hubs need to deploy a lot
of effort to
manage their great number of trading partners.
At this point our reading of the actual comments from this list, we do not
see
the real added value of this draft. We think that a use case for this "AS2
Software Features
Profiles" should be presented to the group for clearer understanding and
further discussion.
Actually it seems that comments are in favor of Option #2, but we think that
this Option
suffer from major drawbacks.
Our concerns are related to:
- Statement #5 in the "EDI-INT Features Header" draft.
5. Security Considerations
Because headers are often un-encrypted, it may be possible for the
feature header to be altered. Trading partners MAY consult out-of-
band to confirm feature support.
- We think it does not provide solid and secure foundation to build future
protocol's
extensions. We think that it is unsafe to take any manual or automated
decisions
based on unsigned informations. May be this aspect is solved by Option
4.
We think that industry would benefit to consider "AS2 Software Features
Profiles" as an
extension to all AS protocols (AS1, AS2, AS3) than only AS2.
Regarding Option #2. our point of view at this point of the discussion is
that those headers
are not modifying the AS2 transport protocol (RFC 4130). So upgrade of the
AS2 version
number from 1.1 to 1.2 should not be done since no change to the AS2 envelop
is achieved.
We think if we would advertise the features through the the use of specific
headers, it should
be done consistently across all AS protocols. Given that AS1 obviously
require the header
to be preceded by the prefix "X-". We think the header should be the same
for AS2 and AS3
and we do not expect interoperability problem.
So we do not see the requirement to increment the protocol version number
since the
addition of this extension header would just be considered by software which
support it and
just being ignored by software which don't.
Regarding Option #4. the Capability MDN should be signed to address security
concern
we expressed above. In that case the signaling of this capability would be
done using
an X-... header which open the possibility to upgrade specifically the AS2
(for example)
protocol without require all vendors to support this Capability MDN.
Regarding the future of this group:
~> The closing of WG is decision to be made by Rik Drummond and
~> Scott Hollenbeck. Discussion on EDIINT-Features, CEM and the
~> like are peripheral to EDIINT but not part of the charter.
~> When EDIINT charter is complete, and only a decision on AS3
~> is remaining, the elist will be closed as well.
This group discuss the change of AS2 protocol version number.
How this could be outside the scope of this EDIINT group ?
If it is not discuss here, where it will be discuss ? It will become a
proprietary protocol ?
From my point of view, since AS2 is born from an IETF group, it should
remain to
IETF and in the public domain.
Dominique Danvoye
Vice-president, Internet Solutions
<mailto:[email protected]> [email protected]
Alligacom Inc.
_____
From: [email protected] [mailto:[email protected]]
On Behalf Of Kyle Meadors
Sent: Thursday, December 15, 2005 5:21 PM
To: [email protected]
Subject: RE: profiles in AS2
Not a lot of comments on this thread. But to summarize.
3 in favor of Option 2 (Features header) and use of AS2-Version 1.2
1 in favor Option 3 where filtering is done on a message
Still does not fully address the initial start-up conditions as Richard
pointed out, but perhaps that just can not be done without some manual
setup.
Since this EDIINT WG will likely be closing relatively soon, I hope we can
get some more to weigh in on this. Do others object to Option 2 (with
AS2-Version 1.2)?
For those AS2 vendors supporting Option 2, would this impact your product,
including those deployed in existing supply chains? Are their significant
backward compatibility problems with this choice?
Kyle Meadors
DGI
_____
From: Tim McCarthy [mailto:[email protected]]
Sent: Wednesday, December 07, 2005 9:14 AM
To: Kyle Meadors; [email protected]
Subject: RE: profiles in AS2
Seems to me that a combination of features 2 and 4 would provide everything
we'd need.
_____
From: [email protected] [mailto:[email protected]]
On Behalf Of Richard Bigelow
Sent: Tuesday, December 06, 2005 5:07 PM
To: Kyle Meadors; [email protected]
Subject: RE: profiles in AS2
These are my comments. Option 2 is preferred. This memo essentially
supports John Duker's memo of Dec. 5, Features Profile in AS2.
1. This option requires that implementers of feature 1.n also implement all
earlier features. Is that reasonable? What if 1.5 is difficult and many
vendors don't want to do it, but many want to support 1.6? Not recommended.
2. The features header allows the partner A receiving the message to know
the other partner's (B's) capabilities. So when A sends to B, A knows what
is allowed. A can also check B's AS2-version; 1.1 does not allow any of the
controlled features, but does allow compression. A should update some state
for every message received from B. B might stop supporting some feature.
Recommended.
A possible variant of (2) is that a partner could send some message to all
its trading partners when its capabilities change. This message would have
headers only, no content. It might be useful to send this capabilities
message to partners that would rarely receive normal messages.
3. This option allows receivers to ignore messages they don't understand,
and to detect those messages without looking for unknown headers. But it
does not provide a mechanism for the sender to know whether a receiver can
receive the message. Suppose we had done compression this way. A could
send a compressed file to B, and B could ignore it based on the feature
header, but then the file is lost. B could return a new MDN code indicating
unsupported-feature, and A could then send the uncompressed file, in this
example. In other cases, A would have to use some other mechanism. A could
remember that B rejected the file and not try that feature again, but how
would A know if B upgraded and can now support the feature? The original
intent of the features header was that the sender could know in advance if
the receiver supports the feature. 3 is not recommended.
4. Before sending a message to B, A should ask B for B's capabilities, and
check if B supports the feature. Since B might stop supporting a feature, A
should ask each time. This is ok for rare messages, like CEM, but not for
common ones, like Multiple Attachments. Not recommended.
None of these protocols fully addresses the initial case. Before any
messages are exchanged, how do the partners know each other's capabilities?
Each partner must assume that the other supports only the basic 1.0 AS2
protocol. Hopefully, they will be able to exchange normal messages, which
will contain at least the 1.2 version header. They can then use option 2 to
discover each other capabilities. This probably works for most features.
For CEM, either they must first exchange test messages that are unencrypted
and unsigned to establish CEM capability, or exchange initial certificates
manually.
Alternatively, the partners would configure each other manually the first
time. Thereafter, they would be automatically updated on each other's
capabilities.
Richard Bigelow
Inovis
[email protected]
_____
From: [email protected] [mailto:[email protected]]
On Behalf Of Kyle Meadors
Sent: Thursday, December 01, 2005 9:04 AM
To: [email protected]
Subject: profiles in AS2
I am needing the opinion of the AS2 community on the use of a feature
profiles within AS2. Back in 2002, compression was added as an extra
feature. Using "AS2-Version: 1.1" in a message indicated the UA could
support compression even if the actual message did not contain the
compressed envelope. This assisted implementers in knowing if their trading
partners could support compression.
Moving to the present, users are requesting new features. These include I-Ds
for Reliability (from GS1), Multiple-Attachments (oil & gas users) and
Certificate Exchange Messaging (Wal-mart, P&G and others GS1 companies).
Given AS2's adoption, I am sure there will be others in the future.
My question to those on this elist is how to do move forward with new
features. What do we do to insure only those who support a feature receive
it (e.g., only sending CEM message to trading partners who support that
profile)? Also, can anything be done to insure backward compatibility to
keep new Feature Header messages from being sent to & breaking older,
existing implementations (e.g. older implementation errors gracefully when
getting an unrecognized MA message).
Here are some options. I would like to hear your thoughts on what is best or
other ideas.
1. Use AS2-Version header to indicate UA support of profiles (e.g. 1.2
indicates CEM, 1.3 indicates CEM, Reliability). Works like compression (e.g.
"1.2" indicates capability of CEM but not an actual CEM message).
2. Use a new header, e.g. EDIINT-Features. The features header shows all
features supported by UA (e.g. EDIINT-Features: CEM, multiple-attachment)
but like AS2-Version does not indicate every message contains profile.
3. Use a new header for each feature which is present ONLY in the message
using that feature. For example, "CEM-Profile" for CEM messages. This could
allow receiving UA to filter in only profiles it recognizes.
4. Create a "Capability Query" AS2 Message which returns a Capability MDN.
MDN indicates what features receiving UA can support.
Kyle Meadors
Principal, Test Process
Drummond Group Inc.
615.212.0826
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.13.12/193 - Release Date: 12/6/2005
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.0/203 - Release Date: 12/15/2005
------=_NextPart_000_0033_01C60639.E426AC00
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:ns0 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]-->
<STYLE>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.source, li.source, div.source
{margin-top:0in;
margin-right:-.75in;
margin-bottom:0in;
margin-left:.2in;
margin-bottom:.0001pt;
font-size:9.0pt;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D184545215-20122005><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT =
color=3D#000000>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">First,=20
we understand and agree that AS2 partnerships management=20
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">could be =
enhanced.=20
Unfortunately right now major hubs need to deploy a lot of effort =
to</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> =
</SPAN><o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">manage their =
great=20
number of trading partners.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"> =
<o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"> <o:p></o:p></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">At this =
point our=20
reading of the actual comments from this list, we do not see =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">the real =
added value=20
of this draft. We think that a use case for this "AS2 Software Features=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Profiles" should=20
be presented to the group for clearer understanding and further=20
discussion.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"> <SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Actually it =
seems that=20
comments are in favor of Option #2, but we think that this Option =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">suffer from =
major=20
drawbacks.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"> <SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Our concerns =
are=20
related to:</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> -=20
Statement #5 in the "EDI-INT Features Header" draft.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> =20
5. Security=20
Considerations <BR> &=
nbsp; =20
Because headers are often un-encrypted, it may be possible for=20
the <BR> feature header =
to be=20
altered. Trading partners MAY consult=20
out-of-<BR> band to confirm =
feature=20
support. </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"> - We =
think it=20
does not provide solid and secure foundation to build future protocol's=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> =20
extensions. We think that it is unsafe to take any manual or =
automated=20
decisions </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"> =20
based on unsigned informations. May be this aspect is solved by =
Option=20
4.</SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial"></SPAN><SPAN =
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN> </P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">We think =
that industry=20
would benefit to consider "AS2 Software Features Profiles" as an=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">extension to =
all AS=20
protocols (AS1, AS2, AS3) than only AS2. </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Regarding =
Option #2.=20
our point of view at this point of the discussion is that those =
headers=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">are not =
modifying the=20
AS2 transport protocol (RFC 4130). So upgrade of the AS2 version =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">number from =
1.1 to 1.2=20
should not be done since no change to the AS2 envelop is achieved. =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">We think if =
we would=20
advertise the features through the the use of specific headers, it =
should=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">be done =
consistently=20
across all AS protocols. Given that AS1 obviously require the =
header=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">to be =
preceded by the=20
prefix "X-". We think the header should be the same for AS2 and AS3 =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">and we do =
not expect=20
interoperability problem. </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">So we do not =
see the=20
requirement to increment the protocol version number since the =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">addition of =
this=20
extension header would just be considered by software which support it =
and=20
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">just being =
ignored by=20
software which don't.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Regarding =
Option #4.=20
the Capability MDN should be signed to address security concern =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">we expressed =
above. In=20
that case the signaling of this capability would be done using =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">an X-... =
header which=20
open the possibility to upgrade specifically the AS2 (for example) =
</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">protocol =
without=20
require all vendors to support this Capability MDN.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Regarding =
the future=20
of this group:</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><BR></SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">~> The =
closing of=20
WG is decision to be made by Rik Drummond and <BR>~> Scott =
Hollenbeck.=20
Discussion on EDIINT–Features, CEM and the <BR>~> like are =
peripheral to=20
EDIINT but not part of the charter. <BR>~> When EDIINT charter is =
complete,=20
and only a decision on AS3 <BR>~> is remaining, the elist will be =
closed as=20
well. </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">This group =
discuss the=20
change of AS2 protocol version number. <BR>How this could be =
outside the=20
scope of this EDIINT group ? </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">If it is not =
discuss=20
here, where it will be discuss ? It will become a proprietary protocol=20
?</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">From my =
point of view,=20
since AS2 is born from an IETF group, it should remain to </SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 0in 0in 0pt"><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">IETF and in =
the public=20
domain.</SPAN><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in =
0pt"><o:p> </o:p></P></FONT></SPAN></SPAN><SPAN=20
class=3D184545215-20122005><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></DIV>
<DIV dir=3Dltr align=3Dleft><FONT =
color=3D#000000></FONT></o:p></SPAN></SPAN><SPAN=20
class=3D184545215-20122005><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p><SPAN=20
class=3D184545215-20122005><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><FONT=20
color=3D#000000></FONT></SPAN></SPAN> </DIV></o:p></SPAN></SPAN><!--=
Converted from text/plain format -->
<P><FONT face=3DArial size=3D2></FONT><!-- Converted from text/plain =
format --></P>
<P><FONT face=3DArial size=3D2>Dominique Danvoye<BR>Vice-president, =
Internet=20
Solutions<BR></FONT><A =
href=3D"mailto:[email protected]"><FONT=20
face=3DArial color=3D#000000=20
size=3D2>[email protected]</FONT></A><BR><FONT =
face=3DArial=20
size=3D2>Alligacom Inc.</FONT></P>
<P><BR><BR></P>
<DIV> </DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
[email protected]=20
[mailto:[email protected]] <B>On Behalf Of </B>Kyle=20
Meadors<BR><B>Sent:</B> Thursday, December 15, 2005 5:21 =
PM<BR><B>To:</B>=20
[email protected]<BR><B>Subject:</B> RE: profiles in=20
AS2<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Not a lot =
of comments=20
on this thread. But to summarize…<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">3 in favor =
of Option=20
2 (Features header) and use of AS2–Version 1.2 =
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1 in favor =
Option 3=20
where filtering is done on a message<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Still does =
not fully=20
address the initial start–up conditions as Richard pointed out, =
but perhaps=20
that just can not be done without some manual=20
setup.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Since this =
EDIINT WG=20
will likely be closing relatively soon, I hope we can get some more to =
weigh=20
in on this. Do others object to Option 2 (with AS2–Version=20
1.2)?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">For those =
<SPAN=20
style=3D"TEXT-TRANSFORM: uppercase">AS2 </SPAN>vendors supporting =
Option 2,=20
would this impact your product, including those deployed in existing =
supply=20
chains? Are their significant backward compatibility problems with =
this=20
choice?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Kyle=20
Meadors</SPAN></FONT><FONT color=3Dnavy><SPAN=20
style=3D"COLOR: navy"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">DGI</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Tim=20
McCarthy [mailto:[email protected]] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, December 07, =
2005 9:14=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Kyle =
Meadors;=20
[email protected]<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
RE: profiles in AS2</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Seems to me =
that a=20
combination of features 2 and 4 would provide everything we’d=20
need.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
[email protected] [mailto:[email protected]] =
<B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Richard=20
Bigelow<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Tuesday,=20
December 06, 2005 5:07 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
Kyle Meadors; [email protected]<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: profiles in=20
AS2</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">These are =
my=20
comments. Option 2 is preferred. This memo essentially =
supports=20
John Duker's memo of Dec. 5, Features Profile in=20
AS2.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1. This =
option=20
requires that implementers of feature 1.n also implement all earlier=20
features. Is that reasonable? What if 1.5 is difficult and =
many=20
vendors don't want to do it, but many want to support 1.6? Not=20
recommended.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">2. =
The features=20
header allows the partner A receiving the message to know the other =
partner's=20
(B's) capabilities. So when A sends to B, A knows what is =
allowed. =20
A can also check B's AS2-version; 1.1 does not allow any of the =
controlled=20
features, but does allow compression. A should update some state =
for=20
every message received from B. B might stop supporting some=20
feature. Recommended.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">A possible =
variant of=20
(2) is that a partner could send some message to all its trading =
partners when=20
its capabilities change. This message would have headers only, =
no=20
content. It might be useful to send this capabilities message to =
partners that would rarely receive normal=20
messages.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">3. This =
option allows=20
receivers to ignore messages they don't understand, and to detect =
those=20
messages without looking for unknown headers. But it does not =
provide a=20
mechanism for the sender to know whether a receiver can receive the=20
message. Suppose we had done compression this way. A could =
send a=20
compressed file to B, and B could ignore it based on the feature =
header, but=20
then the file is lost. B could return a new MDN code indicating=20
unsupported-feature, and A could then send the uncompressed file, in =
this=20
example. In other cases, A would have to use some other =
mechanism. =20
A could remember that B rejected the file and not try that feature =
again, but=20
how would A know if B upgraded and can now support the feature? =
The=20
original intent of the features header was that the sender could know =
in=20
advance if the receiver supports the feature. 3 is not=20
recommended.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">4. Before =
sending a=20
message to B, A should ask B for B's capabilities, and check if B =
supports the=20
feature. Since B might stop supporting a feature, A should ask =
each=20
time. This is ok for rare messages, like CEM, but not for common =
ones,=20
like Multiple Attachments. Not =
recommended.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">None of =
these=20
protocols fully addresses the initial case. Before any messages =
are=20
exchanged, how do the partners know each other's capabilities? =
Each=20
partner must assume that the other supports only the basic 1.0 AS2=20
protocol. Hopefully, they will be able to exchange normal=20
messages, which will contain at least the 1.2 version header. =
They can=20
then use option 2 to discover each other capabilities. This =
probably=20
works for most features. For CEM, either they must first =
exchange test=20
messages that are unencrypted and unsigned to establish CEM =
capability, or=20
exchange initial certificates manually.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Alternatively, the=20
partners would configure each other manually the first time. =
Thereafter,=20
they would be automatically updated on each other's=20
capabilities.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV>
<DIV>
<P class=3DMsoNormal=20
style=3D"mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"><FONT=20
face=3DVerdana color=3Dgray size=3D1><SPAN=20
style=3D"FONT-SIZE: 9pt; COLOR: gray; FONT-FAMILY: Verdana">Richard=20
Bigelow<BR>Inovis<BR><A=20
=
href=3D"mailto:[email protected]">[email protected]</A>=
</SPAN></FONT><FONT=20
color=3Dgray><SPAN=20
style=3D"COLOR: gray"><o:p></o:p></SPAN></FONT></P></DIV></DIV></DIV>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
[email protected] [mailto:[email protected]] =
<B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Kyle=20
Meadors<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Thursday,=20
December 01, 2005 9:04 AM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
[email protected]<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B>=20
profiles in AS2</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am needing the opinion =
of the=20
AS2 community on the use of a feature profiles within AS2. Back in =
2002,=20
compression was added as an extra feature. Using "AS2–Version: =
1.1" in a=20
message indicated the UA could support compression even if the actual =
message=20
did not contain the compressed envelope. This assisted implementers in =
knowing=20
if their trading partners could support compression.</SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Moving to=20
the present, users are requesting new features. These include =
I–Ds for=20
Reliability (from GS1), Multiple–Attachments (oil & gas =
users) and=20
Certificate Exchange Messaging (Wal–mart, P&G and others GS1 =
companies).=20
Given AS2's adoption, I am sure there will be others in the=20
future.</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">My=20
question to those on this elist is how to do move forward with new =
features.=20
What do we do to insure only those who support a feature receive it =
(e.g.,=20
only sending CEM message to trading partners who support that =
profile)? Also,=20
can anything be done to insure backward compatibility to keep new =
Feature=20
Header messages from being sent to & breaking older, existing=20
implementations (e.g. older implementation errors gracefully when =
getting an=20
unrecognized MA message).</SPAN></FONT> <BR><FONT face=3DArial =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT> =
<BR><FONT=20
face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Here are=20
some options. I would like to hear your thoughts on what is best or =
other=20
ideas.</SPAN></FONT> <BR><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"> <o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">1. Use AS2–Version =
header to=20
indicate UA support of profiles (e.g. 1.2 indicates CEM, 1.3 indicates =
CEM,=20
Reliability). Works like compression (e.g. “1.2” indicates =
capability of CEM=20
but not an actual CEM message).<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">2. Use a new header, =
e.g.=20
EDIINT–Features. The features header shows all features =
supported by UA (e.g.=20
EDIINT–Features: CEM, multiple–attachment) but like =
AS2–Version does not=20
indicate every message contains profile.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">3. Use a new header for =
each=20
feature which is present ONLY in the message using that feature. For =
example,=20
“CEM–Profile” for CEM messages. This could allow =
receiving UA to filter in=20
only profiles it recognizes.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">4. Create a =
“Capability Query”=20
AS2<FONT color=3Dnavy><SPAN style=3D"COLOR: navy"> =
</SPAN></FONT>Message which=20
returns a Capability MDN. MDN indicates what features<FONT =
color=3Dnavy><SPAN=20
style=3D"COLOR: navy"> </SPAN></FONT>receiving UA can=20
support.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Kyle=20
Meadors</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Principal, Test=20
Process</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Drummond Group=20
Inc.</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">615.212.0826</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: =
12pt"><o:p> </o:p></SPAN></FONT></P></DIV><BR>
<P><FONT size=3D2>--<BR>No virus found in this outgoing =
message.<BR>Checked by=20
AVG Free Edition.<BR>Version: 7.1.362 / Virus Database: 267.13.10/189 =
-=20
Release Date: 11/30/2005<BR></FONT></P><BR>
<P><FONT size=3D2>--<BR>No virus found in this incoming =
message.<BR>Checked by=20
AVG Free Edition.<BR>Version: 7.1.371 / Virus Database: 267.13.12/193 =
-=20
Release Date: 12/6/2005<BR></FONT></P><BR>
<P><FONT size=3D2>--<BR>No virus found in this outgoing =
message.<BR>Checked by=20
AVG Free Edition.<BR>Version: 7.1.371 / Virus Database: 267.14.0/203 - =
Release=20
Date: 12/15/2005<BR></FONT></P>
<P><FONT face=3DArial size=3D2></FONT></P></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0033_01C60639.E426AC00--