Re: [sipcore] rfc4244bis: what is "aor" used for?

["Francois Audet" <[e-mail]>]

So you are proposing something that is not backward compatible then.

We did talk about the "weeding out" (as opposed to marked) earlier, and
decided to "mark" instead of weeding out. In fact, it was in my
presentation in San Francisco.

The problem with many IETF groups is we keep going in circle. Once we 
decide something, we should stick to it. Otherwise, it's impossible to
make progress. 

> -----Original Message-----
> From: Hadriel Kaplan [mailto:[e-mail]] 
> Sent: Tuesday, July 14, 2009 10:48
> To: Audet, Francois (SC100:3055); Paul Kyzivat
> Cc: Dean Willis; SIPCORE
> Subject: RE: [sipcore] rfc4244bis: what is "aor" used for?
> 
> 
> 
> > -----Original Message-----
> > From: Francois Audet [mailto:[e-mail]]
> > Sent: Tuesday, July 14, 2009 12:06 PM
> > 
> > > For example, if alice sends a request to 
> > > "sip:[e-mail]", which gets sent to 
> > > "sip:[e-mail]" and Bob's UAS receives it after
> > that, the
> > > H-I list of ALL "mp" tagged entries will be this:
> > > 
> > > H-I: <sip:[e-mail]>;mp
> > > H-I: <sip:[e-mail]>;mp
> > 
> > Actually, no. Absolutely not. You'd get:
> > 
> > History-Info: <sip:[e-mail]>;aor;index=1
> > History-Info: <sip:[e-mail]>;aor;mp;index=1.1
> > History-Info: <sip:bob@192.168.0.5>;rc;index=1.1.1
> 
> Sorry that was a typo - I meant all the "mp" tagged and the 
> original req-uri from Alice would be:
> 
> H-I: <sip:[e-mail]>;aor
> H-I: <sip:[e-mail]>;mp
> 
> You would NOT get:
> > History-Info: <sip:bob@192.168.0.5>;rc;index=1.1.1
> 
> ...in the list I'm describing, because that is not "mp" 
> tagged - it's in the full H-I list sure, but if you 
> weed-out/cull the list to the first entry and all "mp" tagged 
> ones, you'd get those two.
>  
> -hadriel
>