RE: EDIINT and HIPAA

[chris@xxxxxxxxxxxxxxxxxx (Chris Davenport)]

senderID and receiverID sound good to me too, but perhaps Sender-ID and
Receiver-ID (ie. with hyphens) would be more in keeping with the syntax
of SMTP and HTTP headers?

These seem to be very generic, like they may have been used somewhere
else.  Has anyone checked that this will not conflict with any current
or planned usage by other groups?

Be happy,

Chris.

---------- Original Message ----------
>From   : "Dick Brooks" <dick@xxxxxxxx>
To     : "Moberg, Dale" <Dale_Moberg@xxxxxxxxxxxx>,"'Terry Harding'" <tharding@xxxxxxxxxxxxxxxxxxx>,
Date   : Fri, 17 Nov 2000 07:22:01 -0600
Subject: RE: EDIINT and HIPAA
>I like senderId and receiverId.
>
>Rik, will the EDIINT workgroup hold a session to discuss the new AS2 draft
>at the next IETF meeting in San Diego?
>
>Dick Brooks
>http://www.8760.com/
>
>
>-----Original Message-----
>From: Moberg, Dale [mailto:Dale_Moberg@xxxxxxxxxxxx]
>Sent: Thursday, November 16, 2000 12:22 PM
>To: 'Terry Harding'; ietf-ediint@xxxxxxx; chris@xxxxxxxxxxxxxxxxxx
>Cc: b2b_int_as2@xxxxxxxxxxxxxxxxxxxxxxx
>Subject: RE: EDIINT and HIPAA
>
>
>List-Subscribe:
> <mailto:b2b_int_as2-request@xxxxxxxxxxxxxxxxxxxxxxx?body=subscribe>
>List-Unsubscribe:
> <mailto:b2b_int_as2-request@xxxxxxxxxxxxxxxxxxxxxxx?body=unsubscribe>
>List-Archive: <http://lists.drummondgroup.com/archives/b2b_int_as2>
>List-Help: <http://lists.drummondgroup.com/doc/email-manage.html>,
> <mailto:b2b_int_as2-request@xxxxxxxxxxxxxxxxxxxxxxx?body=help>
>
>OK by me.
>
>Anybody not like these?
>Please respond quickly
>so we can get this
>settled.
>
>
>> -----Original Message-----
>> From: Terry Harding [mailto:tharding@xxxxxxxxxxxxxxxxxxx]
>> Sent: Thursday, November 16, 2000 1:02 PM
>> To: ietf-ediint@xxxxxxx; Moberg, Dale; chris@xxxxxxxxxxxxxxxxxx
>> Cc: b2b_int_as2@xxxxxxxxxxxxxxxxxxxxxxx
>> Subject: Re: EDIINT and HIPAA
>>
>>
>> How about.
>>
>> senderId and receiverId.
>>
>> Terry
>> ----- Original Message -----
>> From: "Chris Davenport" <chris@xxxxxxxxxxxxxxxxxx>
>> To: <Dale_Moberg@xxxxxxxxxxxx>; <ietf-ediint@xxxxxxx>
>> Sent: Thursday, November 16, 2000 8:19 AM
>> Subject: RE: EDIINT and HIPAA
>>
>>
>> > I was afraid you might say that!  Actually I'm not clued up
>> on why it was
>> > considered necessary to introduce these headers.  The
>> answer does not
>> appear
>> > to be in the AS2 revision in internet-drafts.  Perhaps I
>> missed it being
>> > discussed on this list?
>> >
>> > How about: "EDI-To" and "EDI-From"
>> >
>> > Be happy,
>> >
>> > Chris.
>> >
>> > ---------- Original Message ----------
>> > From   : "Moberg, Dale" <Dale_Moberg@xxxxxxxxxxxx>
>> > To     : "'chris@xxxxxxxxxxxxxxxxxx'"
>> <chris@xxxxxxxxxxxxxxxxxx>,ietf-ediint@xxxxxxx
>> > Date   : Thu, 16 Nov 2000 09:27:22 -0500
>> > Subject: RE: EDIINT and HIPAA
>> > >Suggest them now!
>> > >
>> > >Dale Moberg
>> > >
>> > >
>> > >> -----Original Message-----
>> > >> From: chris@xxxxxxxxxxxxxxxxxx [mailto:chris@xxxxxxxxxxxxxxxxxx]
>> > >> Sent: Thursday, November 16, 2000 5:33 AM
>> > >> To: ietf-ediint@xxxxxxx
>> > >> Subject: RE: EDIINT and HIPAA
>> > >>
>> > >>
>> > >> Could we not come up with some more meaningful names for
>> > >> these new headers?
>> > >> I'm thinking that in 10 years time no-one will remember what
>> > >> "AS2-To" means.
>> > >>
>> > >> Just a thought.
>> > >>
>> > >> Chris.
>> > >>
>> > >> >
>> > >> >I agree, the original AS2 spec was based on AS1, but there
>> > >> were problems
>> > >> >discovered during AS2 interoperability testing (using RFC
>> > >> 822 (email) style
>> > >> >packaging)  related to "To" and "From" headers, which
>> resulted in the
>> > >> >creation
>> > >> >of two new headers specific to AS2, "AS2-To" and "AS2-From".
>> > >>  We (as the
>> > >> >authors
>> > >> >of AS2) will have to provide details of  these new routing
>> > >> headers and
>> > >> >cannot
>> > >> >depend entirely on AS1, as we had originally.
>> > >> >
>> > >> --
>> > >> Chris Davenport              chris@xxxxxxxxxxxxxxxxxx
>> > >> Davros Computer Systems
>> > >>
>> > --
>> > Chris Davenport              chris@xxxxxxxxxxxxxxxxxx
>> > Davros Computer Systems
>>
>
--
Chris Davenport              chris@xxxxxxxxxxxxxxxxxx
Davros Computer Systems