IETF IPTEL WG 55 th IETF, Atlanta, GA Trunk Group Open Issues <draft-ietf-iptel-trunk-group-00> Vijay Gurbani, Cullen Jennings, and Jon Peterson Presented by: Vijay Gurbani 55 Tue, Nov 19, 2002 1 SPIRITS WG vkg
Issues • Issue 1: “sip” URI or “tel” URI? – Defining them as extensions to the “tel” URI appears reasonable (since trunks are tied to the PSTN, anyway). – Easy to derive a SIP URI from the tel URI. 55 Tue, Nov 19, 2002 2 SPIRITS WG vkg
Issues • Issue 2: Global or local namespace? – Most trunk groups will be locally scoped; however, for the sake of flexibility, a naming convention has been proposed in the I-D which is flexible enough to accommodate both. – ABNF has been proposed in the I-D for this purpose, resulting in a URI which may look like: • tel:+14085551212;tgrp=local=tg55/3 55 Tue, Nov 19, 2002 3 SPIRITS WG vkg
Issues • Issue 3: Originating and destination trunk groups should be able to appear separately and concurrently in the SIP message. – Originating trunk group: Contact header – Destination trunk group: R-URI • Other options: – Originating trunk group: From header (abstract identifier that persists even after the session is completed – probably not a good choice). – Destination trunk group: To header (same reservation as above, plus, proxies make routing decisions based on R-URIs). 55 Tue, Nov 19, 2002 4 SPIRITS WG vkg
Issues • Issue 4: SIP intermediaries should be able to add the destination trunk group to SIP requests as a route is selected for the session. – Argues more in favor of using R-URI. 55 Tue, Nov 19, 2002 5 SPIRITS WG vkg
Recommend
More recommend
