Hadriel,

Comment at the end.

John 

> -----Original Message-----
> From: Hadriel Kaplan [mailto:[EMAIL PROTECTED] 
> Sent: 17 January 2008 21:10
> To: Dean Willis; IETF SIP List
> Subject: RE: [Sip] Vocabulary and problem statement for 
> Request-URI,retargeting, and SIP routing (long, but read it!)
> 
> 
> 
> > -----Original Message-----
> > From: Dean Willis [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, January 17, 2008 2:13 PM
> >
> > Call for clarity on exactly which problems we're solving with UA-
> > Loose-Routing, target, CPID, etc. Proposed: target identity, end-to-
> > end parameters.
> 
> Not exactly.  I believe the idea in the UALR draft is to get 
> the target identity/params created by the nearest 
> re-targeting event relative to the UAS, where those created 
> by the UAC is the default such event (and thus the logical 
> "farthest").  In other words, what you say is true, except if 
> the request got retargeted, the identity and params will be 
> those of the new target, and thus not end-to-end and not 
> always what the UAC sent.  Right?
> 
> For example, given the following, where "RTRG" means 
> Re-Targeting, "RRT" means Re-Routing, "RT" means Routing, and 
> the single letters represent connections:
> 
>                     RRT
>                    +---+
>                    |R1 |
>                 B /+---+\ C
>             RT   /       \  RT
>            +---+/         \+---+
>            |P1 |           |P1 |
>         A /+---+           +---+\ D
>          /                       \
>    +---+/                         \+---+
>    |UAC|                           |UAS|
>    +---+                           +---+
> 
> UA-Loose-routing wants the req-uri seen on connection "A" I think.
> To header gives you A.
> PCPID gives you B.
> Hist-Info gives you A,B,C.
> 
> 
> But in the re-targeting scenario such as:
>                     RTRG                    RRT
>                    +---+                   +---+
>                    |R1 |                   |R2 |
>                 B /+---+\ C             E /+---+\ F
>             RT   /       \  RT      RT   /       \  RT
>            +---+/         \+---+ D +---+/         \+---+
>            |P1 |           |P2 +---+P3 |           |P4 |
>         A /+---+           +---+   +---+           +---+\ G
>          /                                               \
>    +---+/                                                 \+---+
>    |UAC|                                                   |UAS|
>    +---+                                                   +---+
> 
> UA-Loose-routing wants the req-uri seen on connection "C" I think.
> To header gives you A.
> PCPID gives you E.
> Hist-Info gives you A,B,C,D,E,F.
[JRE] According to Dean's definition of RT, it does not change the
Request-URI (only the Route header field presumably, or maybe not even
that).
So C, D and E are the same. Also A and B are the same, and F and G are
the same.
So I think:
- UA-Loose-routing gives you C/D/E
- To gives you A/B
- PCPID gives you C/D/E
- Target gives you C/D/E
- Hist-info gives you A/B, C/D/E and F/G.

 
> 
> -hadriel
> 
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [EMAIL PROTECTED] for questions on current sip
> Use [EMAIL PROTECTED] 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 [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip

Reply via email to