Presence and IntComm WG

[Jeremy George <>]

Jeff,

> >My first question would be:   For this demonstration, should another UA
> >outside the scope of the ser.uits.indiana.edu demonstration be able to
> >place

  Nope, this is mostly a closed system for demo purposes only.  The
exception is outbound calls to SIP.edu enabled schools.

> >a call to our friend John Doe?    (e.g. John Doe's colleague back at

> >Also as per RFC 3261: "Realm strings MUST be globally unique."  Using

  Yes, absolutely right.  Domain hijacking is probably not rfc3261
compliant.  We made that concession in order to highlight SIP.edu
(/sip.edu/).

> >It seems the more conventional approach would be to assign an AOR of
> >.

  No one ever accused us of being conventional :)

> >I think one issue here with Session and with other UAs I have seen is
> >that the Request URI of the REGISTER request should be able to name the
> >domain of the location service for which the registration is meant (e.g.
> >sip:ser.uits.indiana.edu) rather than naming the "right-hand side" of
> >the "sign-in" name (e.g. sip:companyabc.com).  We will look at providing
> >this function in a future release.  In the meantime, configuring the
> >outbound proxy is one approach or using the proxy in the server address
> >field is another approach, but in that case you cannot have an '"@" in
> >the username field.

  For the purposes of this demo I think we'll have to sidestep this.
But, if I understand it (multidomain services within a single proxy),
I'd like to encourage discussion.  This is a good issue, thanks.

> >I guess my preferred approach for this demo would to be to define a
> >username without an "@" (e.g. johndoe rather than
> >).
> >  The complete SIP URI would then be
> >
> > rather than the equivalent of

  After this demo we can certainly discuss how to promote our goals in
a more standards compliant way.  In fact a major agenda item of the
working group meeting at the MM will be a deconstruction of the demo.
Should we do it again?  What worked?  What didn't?  If we do it again,
how should it be structured.  Please come to the meeting and make these
points.

  And thanks for the fast work!  I'm beginning to think this is all
going to work.  

- Jeremy

-- 

----------------------------------------------------------------wg-pic-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

----------------------------------------------------------------wg-pic--