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

The Problem Draft-gin handles E.164 How do we handle alpha-numeric usernames?

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

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

Perceived Problems don’t apply Draft-gin really did Register globally unique AoRs –E.g., 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

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

Other solutions for 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”: –Why is this legit? Same thing as phone- context really, just for any alphanumeric

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