RE: [Sip] Requirements on Reason information. New I-D

This is why we have SIPPING: the REASON header would be a sensible way of
solving the issues raised by Gonzalo in his draft.  In addition, it would,
with some modifications, also solve the issues raised in
draft-watson-sipping-req-history-00.txt.

I would propose that the requirements raised in
draft-camarillo-sipping-reason-00.txt get folded into a revision of
draft-watson-sipping-req-history.

Correct me if I'm wrong, but I don't think
draft-schulzrinne-sip-reason-01.txt, as it stands today, addresses the
history part of the SIPPING requirements.  The draft is silent on this
point, but it looks like the SIP entity generating the message with the
Reason header inserts it only for *its* operation.  That is, it explains why
that particular entity failed.  Said differently, it looks to me that there
will be only one Reason header in a SIP message.

If we can carry and identify the source of the Reason headers, like we do
for Via or SMTP does for Received-By, then this header can satisfy both
camarillo-sipping-reason's and watson-sipping-req-history's requirements.

-----Original Message-----
From: sip-admin@ietf.org [mailto:sip-admin@ietf.org]On Behalf Of Gonzalo
Camarillo
Sent: Tuesday, March 19, 2002 3:01 AM
To: sip; Brian Rosenberg (EUS); Dean Willis; Joerg Ott; rohan@cisco.com
Cc: Henning Schulzrinne; oran@cisco.com
Subject: [Sip] Requirements on Reason information. New I-D

Chairmen,

I presented the Reason header field draft today in the SIP WG meeting:
http://search.ietf.org/internet-drafts/draft-schulzrinne-sip-reason-01.txt

Some folks considered that the requirements for this work were not clear
enough, so I was asked by the chairmen to write a set of requirements.
We agreed that there was no need to wait for the next IETF meeting in
order to progress such a requirements draft. Discussions in the mailing
list were encouraged.

I have put together an I-D with those requirements.

http://standards.ericsson.net/gonzalo/draft-camarillo-sipping-reason-00.txt

I would like to know if these requirements are what you expected or if,
on the other hand, you wanted something else...

I intend to submit this draft, including the comments I may receive, on
Monday.

Thanks,

Gonzalo
--
Gonzalo Camarillo                    Phone :   +1 212 939 71 71
Columbia University                  Mobile:  +358 40 702 35 35
472 Computer Science Building        Fax   :  +358  9 299 30 52
1214 Amsterdam Ave., Mail Code 0401  http://www.hut.fi/~gonzalo
New York, NY 10027
USA                              Gonzalo.Camarillo@ericsson.com

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip