profiles in AS2
"Kyle Meadors" <[email protected]> Thu, 1 Dec 2005 11:04:17 -0600
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
------=_NextPart_000_00DE_01C5F666.FA8F4E80
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
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=96Version: 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.=20
=20
Moving to the present, users are requesting new features. These include =
I=96Ds
for Reliability (from GS1), Multiple=96Attachments (oil & gas users) and
Certificate Exchange Messaging (Wal=96mart, P&G and others GS1 =
companies).
Given AS2's adoption, I am sure there will be others in the future.=20
=20
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).=20
=20
Here are some options. I would like to hear your thoughts on what is =
best or
other ideas.=20
=20
1. Use AS2=96Version header to indicate UA support of profiles (e.g. 1.2
indicates CEM, 1.3 indicates CEM, Reliability). Works like compression =
(e.g.
=931.2=94 indicates capability of CEM but not an actual CEM message).
=20
2. Use a new header, e.g. EDIINT=96Features. The features header shows =
all
features supported by UA (e.g. EDIINT=96Features: CEM, =
multiple=96attachment)
but like AS2=96Version does not indicate every message contains profile.
=20
3. Use a new header for each feature which is present ONLY in the =
message
using that feature. For example, =93CEM=96Profile=94 for CEM messages. =
This could
allow receiving UA to filter in only profiles it recognizes.
=20
4. Create a =93Capability Query=94 AS2 Message which returns a =
Capability MDN.
MDN indicates what features receiving UA can support.
=20
=20
Kyle Meadors
Principal, Test Process
Drummond Group Inc.
615.212.0826
=20
--=20
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
=20
------=_NextPart_000_00DE_01C5F666.FA8F4E80
Content-Type: text/html;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1250">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* 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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@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 link=3Dblue vlink=3Dpurple>
<div class=3DSection1>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>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.</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> </span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>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.</span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> </span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>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).</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> </span></font>
<br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Here
are some options. I would like to hear your thoughts on what is best or =
other
ideas.</span></font> <br>
<font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> <o:p=
></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>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).<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>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.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>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.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>4. Create a “Capability Query” AS2<font
color=3Dnavy><span style=3D'color:navy'> </span></font>Message which =
returns a
Capability MDN. MDN indicates what features<font color=3Dnavy><span
style=3D'color:navy'> </span></font>receiving UA can =
support.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Kyle Meadors</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Principal, Test Process</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Drummond Group Inc.</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>615.212.0826</span></font><o:p></o:p></p>
<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>
<BR>
<P><FONT SIZE=3D2>--<BR>
No virus found in this outgoing message.<BR>
Checked by AVG Free Edition.<BR>
Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: =
11/30/2005<BR>
</FONT> </P>
------=_NextPart_000_00DE_01C5F666.FA8F4E80--