1. GIN with Literal AoRs for SIP in SSPs (GLASS) draft-kaplan-martini-glass-00 Hadriel Kaplan

2. The Problem Draft-gin handles E.164 How do we handle alpha-numeric usernames? sip:bob@ssp.com

3. The Solution “Bulk” REGISTER any provisioned AoR, as if the PBX had separately Registered for each one Contact-routing a la RFC3261 still works –If it would have worked for explicit REGISTERs The Contact-URI “expansion” is the provisioned AoR user portion –The same that would be provisioned for a separate REGISTER

4. Example PBX does a draft-gin REGISTER SSP has provisioning for bob@ssp.com INVITE to bob@ssp.com follows rfc3261 OriginatorSSPPBX INVITE sip:bob@ssp.com INVITE sip:bob@192.1.2.3 REGISTER sip:ssp.com To: Contact:

5. Perceived Problems don’t apply Draft-gin really did Register globally unique AoRs –E.g., sip:+123456789@ssp.com So now we’re bulk Registering other globally unique AoRs, scoped to the Registered domain (ssp.com) –Just like RFC 3261 would do for any AoR

6. What about bob@ssp.co.ca? Question: –How does the PBX know the call was for bob@ssp.com and not for bob@ssp.co.ca? (if both are handled) Answer: it won’t –It wouldn’t have in rfc3261 either, if one REGISTER for bob@ssp.com did more –Really the call is being re-targeted to bob@ssp.com – and we have hist-info for figuring out the original target, right?

7. Other solutions for bob@ssp.co.ca 1.The PBX can REGISTER to ssp.co.ca –By definition it knows about ssp.co.ca, so it can REGISTER to ssp.co.ca separately 2.Or we can define a new URI user parameter named “user-context”: sip:bob;user-context=ssp.co.ca@192.1.2.3 –Why is this legit? Same thing as phone- context really, just for any alphanumeric

8. Open Issues Can this just be informational vs. standards-track?