1 / 5

Identifying intra-realm calls with explicit addressing realm identifier attribute

SIPPING WG Meeting IETF-57. Identifying intra-realm calls with explicit addressing realm identifier attribute. draft-audet-sipping-add-realm-00.txt. François AUDET (audet@nortelnetworks.com). Explicit addressing realm identifier.

jasmine-buckner
Download Presentation

Identifying intra-realm calls with explicit addressing realm identifier attribute

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIPPING WG Meeting IETF-57 Identifying intra-realm calls with explicit addressing realm identifier attribute draft-audet-sipping-add-realm-00.txt François AUDET (audet@nortelnetworks.com)

  2. Explicit addressing realm identifier • Allows for explicitly adding a realm-id for private (i.e., “local”) addresses • UAs can make decisions based on the presence of the realm-id • Core idea is that if both media termination in a session have a-priory knowledge that they have have IP addresses in same addressing realm, they can use it draft-audet-sipping-add-realm-00.txt

  3. Explicit addressing realm identifier • UA know that they have private adds in same realm only if they have the same realm-id • If realm-id are different, use normal treatment (STUN, ICE, pray, etc.) • If realm-id are same, use those addresses • Need to configure realm-id only if multiple UA are behind same NAT • Burden is on configuring the realm-id when needed • Mechanism to configure outside of scope draft-audet-sipping-add-realm-00.txt

  4. Relationship to ICE • Can be used with or without ICE • Syntax based on ICE -00 • Needs to be updated to ice-01 • Allows for better migration to ICE • Use realm-id to handle UAs that do not support ICE • Optimize for not using ICE when we know we don’t need it draft-audet-sipping-add-realm-00.txt

  5. Format of realm identifier • Has to be globally unique • Could be a number, VPN identifier, something that looks like a domain name, etc. • New attribute: • includes an addressing-realm-type & addressing-realm-identifier • Example in draft looks like a domain name • Similar to phone-context in RFC2806-bis (tel URI) • E.g.: a=addressing-realm:userdomain lab3.sanjose@foo.com draft-audet-sipping-add-realm-00.txt

More Related