RE: [reSIProcate] FlowId Class Questions

["Derek MacDonald" <derek@xxxxxxxx>]

As mentioned in the commit comments, it is part of implementing
draft-jennings-sipping-outbound-01.txt in repro.  It is possible they may be
used by other TU's, or it could end up residing in repro.

--Derek

CONFIDENTIALITY NOTICE

This email and any files transmitted with it contains proprietary
information and, unless expressly stated otherwise, all contents and
attachments are confidential. This email is intended for the addressee(s)
only and access by anyone else is unauthorized. If you are not an addressee,
any disclosure, distribution, printing or copying of the contents of this
email or its attachments, or any action taken in reliance on it, is
unauthorized and may be unlawful. If you are not an addressee, please inform
the sender immediately and then delete this email and any copies of it.
Thank you for your co-operation.


> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alan Hawrylyshen
> Sent: Tuesday, June 07, 2005 10:22 PM
> To: reSIProcate List
> Subject: [reSIProcate] FlowId Class Questions
> 
> All, especially Dave and Derek
> Can someone involved in the design of this class let me know the
> application?
> I'm very concerned about the direction it is taking and there has
> been no public discussion about the scope model or usage. I'm only
> looking for a couple bullet points. Will they go on the wire? Are
> they strictly transaction : TU scoped?
> 
> I consider these critical questions since certain answers will result
> in me declaring that 'we all need to talk' :-)
> 
> Thanks
> Alan
> 
> 
> 
> a l a n a t j a s o m i d o t c o m
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel