Re: [sipcore] 4244bis-05: the infamous "rc" param

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 17 June 2011 20:02 UTC

From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Shida Schubert <shida@ntt-at.com>
Date: Fri, 17 Jun 2011 16:02:56 -0400
Thread-Topic: [sipcore] 4244bis-05: the infamous "rc" param
Thread-Index: AcwtCKR5V/loV58AR7+qFsLYCHw+MQAH0Kgv
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907EA00@DC-US1MBEX4.global.avaya.com>
References: <7A463F33-4115-4E9D-8D1C-C8F49BA9CFDD@acmepacket.com> <7E5B50A1-81D0-433A-BAEF-F7B9037F4691@ntt-at.com>, <88801004-2367-4BE3-8564-3228A279B9E1@acmepacket.com>
In-Reply-To: <88801004-2367-4BE3-8564-3228A279B9E1@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sipcore@ietf.org WG" <sipcore@ietf.org>
Subject: Re: [sipcore] 4244bis-05: the infamous "rc" param
Precedence: list

> From: Hadriel Kaplan [HKaplan@acmepacket.com]
> 
> What "rc" should actually stand for is "Request-uri Changed".  It
> should be populated in ALL cases where the request-URI is changed, but
> where the new target is still the same identity (ie, it's not an "mp"
> tag instead), and it should still use an index to point to the
> previous H-I entry it changed from as it does now.

I'm not so concerned about the different categories of redirection and how we record them,
but that there will be some redirections to which neither "rc" nor "mp" will apply.
In those cases, there is no way to record which URI this URI is derived from, because the
back-pointer is the value of rc/mp.

And it doesn't look like the draft thinks about that case much.  There three examples that
I can find where a URI is not the same as its parent but does not have an rc/mp parameter:

Messages F6 and F9 in B.1 and one message in B.2:

   F6 INVITE example.com -> office

   INVITE sip:office@192.0.2.3.com SIP/2.0

   History-Info: <sip:bob@example.com>;index=1
   History-Info: <sip:bob@192.0.2.4?Reason=SIP%3Bcause%3D302>;\
                 index=1.1;rc=1
   History-Info: <sip:office@example.com>;index=1.2;mp=1
   History-Info: <sip:office@192.0.2.5>;index=1.2.1 <------------------
 


   F9 INVITE example.com -> home

   INVITE sip:home@192.0.2.6 SIP/2.0

   History-Info: <sip:bob@example.com>;index=1
   History-Info: <sip:bob@192.0.2.4?Reason=SIP%3Bcause%3D302>;\
                 index=1.1;rc=1
   History-Info: <sip:office@example.com>;index=1.2;mp=1
   History-Info: <sip:office@192.0.2.5?Reason=SIP%3Bcause%3D408>;\
                 index=1.2.1>;index=1.2.1
   History-Info: <sip:home@example.com>;index=1.3;mp=1
   History-Info: <sip:home@192.0.2.6>;index=1.3.1 <----------------------


  |                |   INVITE sip:bob@biloxi.example.com;p=x
  |                |--------------->|                |
  | History-Info: <sip:anonymous@anonymous.invalid>;index=1
  | History-Info: <sip:bob@biloxi.example.com;p=x>;index=1.1

[Though the last one was due to anonymization.]


I think we need to adjust the parameters to put the back-pointer into a separate
parameter from the "type of redirection" information.

Dale

[sipcore] 4244bis-05: the infamous "rc" param Hadriel Kaplan
Re: [sipcore] 4244bis-05: the infamous "rc" param Shida Schubert
Re: [sipcore] 4244bis-05: the infamous "rc" param Hadriel Kaplan
Re: [sipcore] 4244bis-05: the infamous "rc" param Worley, Dale R (Dale)
Re: [sipcore] 4244bis-05: the infamous "rc" param Cullen Jennings
Re: [sipcore] 4244bis-05: the infamous "rc" param Shida Schubert
Re: [sipcore] 4244bis-05: the infamous "rc" param Shida Schubert